DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.



IMPORTANT

Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as 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.

Use the Relay Flags window to set relay flag parameters in a selected IP signaling profile.

Note

The methods relay flags control the relay of in-dialog non-INVITE and non-REGISTER methods within dialogs established by the SIP INVITE method.

On the SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > IP Signaling Profile > Common IP Attributes > Relay Flags. The Relay Flags window opens.

In IP Signaling Profile, select the profile you want to view or configure. Note that profiles using the H323 protocol do not support relay flags. The following figure shows the DEFAULT_SIP IP Signaling Profile.

Common IP Attributes SIP Relay Flags

 


The following fields are displayed:

SIP Relay Flags Parameters


Parameter

Description

Dialog Event Package 
Enable this flag to allow the SBC to send the Dialog Event Package to the peer.
  • Disable (default)
  • Enable
Note

To pass this body transparently, enable the dialog-info xml body relay flag.

Dtmf BodyEnable this flag to allow the SBC to relay DTMF bodies 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.
  • Disable (default)
  • Enable
InfoEnable this flag to relay SIP INFO method messages to the peer. If disabled, the SBC processes them locally.
  • Disable (default)
  • Enable
 
Message Enable this flag to relay SIP MESSAGE method messages to the peer. If disabled, the SBC processes them locally.
  • Disable (default)
  • Enable
Notify Enable this flag to relay SIP NOTIFY method messages to the peer. If disabled, the SBC processes them locally.
  • Disable (default)
  • Enable
Options
 Enable this flag to relay SIP OPTIONS method messages to the peer. If disabled, the SBC processes them locally.
  • Disable (default)
  • Enable
Note

The SBC relays the OPTIONS method if a Route header is present and the Max-forwards value is not "0," irrespective of whether this flag is enabled or disabled. If no suitable route is found, the SBC returns a "404 Not Found" error response.


Reg Event PackageEnable this flag to relay Registration Event Package information to the peer. If disabled, the SBC rejects the Registration Event Package.
  • Disable (default)
  • Enable
Refer
When enabled, the SBCrelays SIP REFER method messages to the peer. When disabled, the SBC processes them locally.
  • Disable (default)
  • Enable

Note: Starting with SBC SWe version 8.1, D-SBC deployments support REFER (without replace) in relay and local processing mode for audio pass-through calls.

Sonus Media BodyEnable this flag to relay the 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.
  • Disable (default)
  • Enable
Status Code3xxEnable this flag to relay a 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).
  • Disable (default)
  • Enable
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).
  • Disable (default)
  • Enable
Note

You must enable this flag when using authcodeHeaders transparency flag.


Third Party BodiesEnable 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.
  • Disable (default)
  • Enable
Force503to500RelayEnable flag to force 503 Service Unavailable message to map to 500 Internal Server Error message.
  • Disable (default)
  • Enable
Publish
Controls the transfer of instant messages (IMs). Enable flag to allow SBCto 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.
  • Disable (default)
  • Enable
Update Without SdpEnable this flag to relay UPDATE messages without SDP.
  • Disable (default)
  • Enable
Conference Event Package
Enable to relay conference event xml message bodies (application/conference-info+xml body ) to the peer.
  • Disable (default)
  • Enable
Note

To pass this body transparently, enable the conference-info xml body relay flag.


Refer to Header Relay

Use this flag to relay the replaces in refer-To header of relayed REFER request. The options are:

  • Reject Refer Ifno Match Forcall Id: If there is no match found for the call-Id received , then REFER is rejected.
  • Relay Refer If No Match For Call Id: SBC tries to match the received call-Id. If  a match is found, SBC translates the replaces header and relays the REFER. If there is no match found for call-id, SBC relays the replaces without any changes.
  • Relay Refer Without Matching: SBC always relays the replaces in refer-to without searching for match of call-id.