Versions Compared

Old Version 5

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 6

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Panel

In this section:

Table of Contents
maxLevel3

 

Include Page
Transparency_Profile_Note
Transparency_Profile_Note

This section specifies all the parameters associated with Relay Flags of H323 and SIP.

To View and Edit Relay Flags

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.

DEFAULT_H323

On the Relay Flags window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Relay Flags for H323 Trunk Group.

Caption
0Figure
1Trunk Provisioning - Common Ip Attributes H323 Relay Flags
 

There are no Relay Flags for DEFAULT_H323 type of Common Ip Attributes.

DEFAULT_SIP

On the Relay Flags window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Relay Flags for SIP Trunk Group.

Caption
0Figure
1Trunk Provisioning - Common Ip Attributes SIP Relay Flags
 

The following fields are displayed:

Caption
0Table
1SIP 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

 

Info
Note
iconfalse
titleNote

To pass this body transparently, enable the

conference

dialog-info xml body relay flag.


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.
  • disable (default)
  • enable
InfoEnable to relay SIP INFO method to the peer. If disabled, the SBC processes SIP INFO methods locally.
  • disable (default)
  • enable
 
Message Enable to relay SIP MESSAGE method to the peer. If disabled, the SBC processes SIP MESSAGE methods locally.
  • disable (default)
  • enable
Notify Enable this flag to relay SIP NOTIFY method to the peer. If disabled, the SBC processes SIP NOTIFY methods locally.
  • disable (default)
  • enable
Options Enable this flag to relay SIP OPTIONS method to the peer. If disabled, the SBC processes SIP OPTIONS methods locally.
  • disable (default)
  • enable
NOTE:
Info
titleNote

The SBC

will relay

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 PackageEnable this flag to relay Registration Event Package information to the peer. If disabled, the SBC rejects the Registration Event Package.
  • disable (default)
  • enable
ReferWhen enabled, the 
Spacevars
0product
relays SIP REFER methods to the peer. When disabled, the SBC processes SIP REFER methods locally.
  • disable (default)
  • enable
Sonus Media BodyEnable 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.
  • disable (default)
  • enable
Status Code3xxEnable 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).
  • disable (default)
  • enable
Status Code4xx6xxEnable 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

 

Info
Note
iconfalse
titleNote

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
PublishControls the transfer of instant messages (IMs). Enable flag to allow 
Spacevars
0product
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.
  • disable (default)
  • enable
Update Without SdpEnable this flag to relay UPDATE message without SDP.
  • disable (default)
  • enable
Conference Event PackageEnable to relay conference event xml message body (application/conference-info+xml body ) to the peer.
  • disable (default)
  • enable
false
Note
icon
Info
titleNote

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:

  • rejectReferIfnoMatchForcallId: If there is no match found for the call-Id received , then REFER is rejected.
  • relayReferIfNoMatchForCallId: 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.
  • relayReferWithoutMatching: SBC always relays the replaces in refer-to without searching for match of call-id.

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.