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 Flags window to configure Packet Service Profile flags.
To View and Edit Flags
On the SBC main screen, go to Configuration > Profile Management > Category: Media Profiles > Packet Service Profile > Flags or
All > Profiles > Media > Packet Service Profile > Flags
Select the Packet Service Profile you want to configure from the drop-down list. The Flags window is displayed.
Figure 1: Profile Management - Media Profiles - Packet Service Profile - Flags
Use the following table to configure the parameters and then click Save.
Table 1: Packet Service Profile - Flags
Parameter | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Disallow Data | Disallow Data Calls Flag. Specifies whether data calls are allowed. If enabled, digit data calls are rejected. The options are:
| ||||||||
Digit Detect | Digit Detect Send Enabled Flag. Specifies whether digit detection is enabled on digits sent to the network. The options are:
Note: If interworking without DSP resources is desired, this flag must be enabled. | ||||||||
Use Direct | Administrative state to use the direct media. The options are:
| ||||||||
Validate Peer Support For DTMF Events | Administrative state to validate the peer support for DTMF events. The options are:
| ||||||||
Interwork Dtmf Without Transcoding | Specifies whether to enable Interworking DTMF OOB 2833 Without Transcoding option or not. The options are:
Note: If you enable Interwork Dtmf Without Transcoding, ensure Preferred Rtp Payload Type For Dtmf Relay is set to a valid value (96-127). If thePreferred Rtp Payload Type For Dtmf Relay value is invalid (set to "128"), the system may fail to pick up the value configured using the "set system dspPad rtpDtmfRelay" command because DSPs are not used for the call. | ||||||||
Dscp Passthrough | When enabled on both the Ingress and Egress call leg, the DSCP value in the IP header of the media packets will be transparently passed through the system. Once media has been received from the peer, any value set in the typeOfService field on the PSP takes no effect when dscpPassthrough is configured on both legs for the associated call. The options are:
| ||||||||
Ssrc Randomize | This parameter generates a new SSRC for the new RTP stream when re-activating the resource chain. The options are:
| ||||||||
HDCodec Preferred | Enable flag to set HD codecs as preferred codec over non-HD codecs even if transcoding is required. When flag is disabled, continue with existing PSP/IPSP behavior. The options are:
When enabled,
Note:
| ||||||||
Prefer NBPassthru Over HDTranscode | Enable this flag to allow the SBC to choose NB-NB pass-through over HD-HD transcoded call. The options are:
When disabled, the SBC prefers HD-HD transcoded call over NB-NB pass-thru. Note:
| ||||||||
Match Offered Codec Group If Nb Only | Enable this flag to allow the SBC to send only NB in outgoing offer if only NB is received in the ingress offer. Otherwise, do nothing. While sending the offer, this flag becomes is ignored if either HD-only or (HD+NB) is received in incoming offer. The options are:
If this flag is disabled, the SBC uses existing behavior. Note: The flag Transcoder Free Transparency overrides this flag. If Transcoder Free Transparency is enabled, this flag is ignored. | ||||||||
Force Route PSPOrder | Enable this flag to send the outgoing offer in the same order as egress route Packet Service Profile irrespective of HD/NB priorities. The options are:
Note:
| ||||||||
Generate and Signal SSRCAnd Cname | Enable this flag to generate an SSRC value and associated attributes and include them in SDP signaling and RTP/RTCP streams. Options are:
Note: This flag takes precedence over the Packet Service Profile Ssrc Randomize flag. | ||||||||
Allow Mid Call SSRCModification | Enable this flag so that in call hold/resume scenarios the SBC modifies the SSRC and associated attributes after the call resumes. The SBC sends both the previous and updated SSRC in SDP signaling and includes the new SSRC iin RTP/RTCP streams. Options are:
Note: You must enable the Generate and Signal SSRCAnd Cname flag before you can enable this flag. Note: If you enable the IP Signaling profile common IP attributes flag Minimize Relaying Of Media Changes From Other Call Leg All, you must also enable the Relay Data Path Mode Change From Other Call Leg flag to have the SSRC modification processing take effect. | ||||||||
Reserve BW For Preferred Audio Common Codec | Reserves bandwidth on the basis of the preferred common codec, and police on the worst case codec. This applies to both known and unknown codecs. The options are:
Note: This flag is active for a call when both the PSPs have this flag enabled. If this flag is disabled in any of the PSPs, the flag is not applied. | ||||||||
Police On Heaviest Audio Codec | When enabled, SBC reserves the worst case common codec bandwidth on trunk groups and interfaces, but polices on maximum bandwidth for all codecs from Offer or Answer in a pass-through call. The options are:
Note: This configuration applies to all pass-through calls. It works independently from Audio Transparency feature and Reserve BW For Preferred Audio Common Codec flag. | ||||||||
T140Call | Specifies whether text media calls, using T.140 codec, are allowed or not. The options are:
For more information on text codecs, refer to Text Codecs. | ||||||||
Allow Audio Transcode For Multi Stream Call | Specifies whether or not to allow audio transcoding when a session contains other media streams, such as a video stream. Options are:
| ||||||||
Ssrc Randomize for Srtp | Enable this option to determine how the SBC handles SSRCs in SRTP media flows. When enabled, the SBC:
When disabled, the SBC relays the SSRC for pass-through media flows it receives from the peer. The options are:
|