Message translation tables allow rules to be put in place so that unusual message interactions during the ringing stage of a call setup can be manipulated such that proper ringback is provided to the originator of the call. For more details, see Message Translation Usage Overview.
To create or modify an Entry to a Message Translation Table:
In the left navigation pane, go to Telephony Mapping Tables > Message Translations > Entry.
Open the translation table by clicking its entry in the navigation panel.
Specifies the type of incoming message. Valid options: Progress, Alert, Connect, orProceeding.
Specifies the Information Element (IE) type/Session Descriptor Protocol to be matched and translated.
Specifies whether or not a Progress Indicator should be present in the message.
Specifies when to send an outgoing message.
Specifies the type of outgoing translated message. Valid options: Progress, Alert, Connect, or Proceeding.
Specifies the outgoing translated Information Element (IE) or Session Descriptor Protocol.
Specifies the use of media cut-through and when.
Specifies the handling for Early media status. Available only when the Incoming Message Type is Progress or Alert.
The available options for this filter are as follows:
For example, SBC Edge can receive 183 Session Progress with SDP and a following 180 Ringing with SDP. Since the early media audio path has already been negotiated with the 183 Session Progress message, SBC Edge can strip the SDP from the 180 Ringing. This can be done to either a SIP or an ISDN call leg. In order to do this, you would set the value of the Early Media Status to Negotiated. As a result, the message translation rule will only match calls if the early media path has already been negotiated.
You could also create a message translation rule that will match only if early media path has not been negotiated.