In this section:
The Transparency Profile is the recommended method of configuring transparency on the SBC Core for new deployments as well as when applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.
Refer to the SBC SIP Transparency Implementation Guide for additional information.
This section specifies all the parameters associated with Relay Flags of H323 and SIP.
On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Common Ip Attributes > Relay Flags. The Relay Flags window is displayed.
On the Relay Flags window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Relay Flags for H323 Trunk Group.
There are no Relay Flags for DEFAULT_H323 type of Common Ip Attributes.
On the Relay Flags window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Relay Flags for SIP Trunk Group.
The following fields are displayed:
Parameter | Description |
---|---|
Dialog Event Package | Enable this flag to allow the SBC to send the Dialog Event Package to the peer.
Note
To pass this body transparently, enable the |
Dtmf Body | Enable flag to allow the SBC to relay DTMF body to the peer for responses to INVITE and BYE messages, relayed INFO, REFER, NOTIFY, OPTIONS, SUBSCRIBE request messages, and relayed 3xx, 4xx, 5xx, and 6xx in response to INVITE messages. Provision this flag on the ingress leg with respect to the message direction.
|
Info | Enable to relay SIP INFO method to the peer. If disabled, the SBC processes SIP INFO methods locally.
|
Message | Enable to relay SIP MESSAGE method to the peer. If disabled, the SBC processes SIP MESSAGE methods locally.
|
Notify | Enable this flag to relay SIP NOTIFY method to the peer. If disabled, the SBC processes SIP NOTIFY methods locally.
|
Options | Enable this flag to relay SIP OPTIONS method to the peer. If disabled, the SBC processes SIP OPTIONS methods locally.
Note
The SBC relays the OPTIONS method if Route header is present and Max-forwards value is not "0" irrespective of whether this flag is enabled or disabled. If no suitable route is found, the SBC returns "404 Not Found" error response. |
Reg Event Package | Enable this flag to relay Registration Event Package information to the peer. If disabled, the SBC rejects the Registration Event Package.
|
Refer | When enabled, the Unable to show "metadata-from": No such page "_space_variables" relays SIP REFER methods to the peer. When disabled, the SBC processes SIP REFER methods locally.
|
Sonus Media Body | Enable this flag to relay Sonus media body to the peer for responses to INVITE and BYE messages, relayed INFO, REFER, NOTIFY, OPTIONS, SUBSCRIBE request messages and relayed 3xx, 4xx, 5xx, and 6xx in response to INVITE messages. Provision this flag on the ingress leg with respect to the message direction.
|
Status Code3xx | Enable this flag to relay 3xx status code to the peer in response to INVITE requests. Provision this flag on the trunk group that receives the 3xx response (the egress leg of the call).
|
Status Code4xx6xx | Enable this flag to relay the error status codes (4xx, 5xx, or 6xx) in response to initial INVITE requests (does not apply to re-INVITEs). Provision this flag on the trunk group that receives the error response (the egress leg of the call).
Note
You must enable this flag when using |
Third Party Bodies | Enable this flag to relay third party bodies to the peer in response to INVITE and BYE messages, relayed INFO, REFER, MESSAGE, NOTIFY, OPTIONS, SUBSCRIBE request methods and relayed 3xx, 4xx, 5xx, and 6xx responses to INVITE methods. Provision this flag on the ingress leg with respect to the message direction.
|
Force503to500Relay | Enable flag to force 503 Service Unavailable message to map to 500 Internal Server Error message.
|
Publish | Controls the transfer of instant messages (IMs). Enable flag to allow Unable to show "metadata-from": No such page "_space_variables" to relay SIP PUBLISH methods to the peer. When disabled, the SBC processes SIP PUBLISH methods locally. Provision this flag on the ingress leg with respect to the message direction.
|
| Enable this flag to relay UPDATE message without SDP.
|
Conference Event Package | Enable to relay conference event xml message body (application/conference-info+xml body ) to the peer.
Note
To pass this body transparently, enable the |
Refer to Header Relay | Use this flag to relay the replaces in refer-To header of relayed
|
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.