In this section:
IMPORTANT
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 object specifies the values associated with the flags of Egress IP Attributes.
To View and Edit Flags
On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Egress Ip Attributes > Flags. The Flags window is displayed.
DEFAULT_H323
On the Flags window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Flags for H323 Trunk Group.
Trunk Provisioning - Egress Ip Attributes H323 Flags
The following fields are displayed:
Egress IP Attributes - Flags Parameters
Parameter | Description |
|---|---|
| Specifies whether to enable the Delay Cut Through flag or not. The options are:
|
| Specifies whether to send the fast start proposal or not. The options are:
|
| Specifies whether to enable the Insert In Band Indications flag or not. The options are:
|
| Specifies whether to wait to connect before the abandon fast start or not. The options are:
|
| Specifies whether to enable the Qos based Routing or not. The options are:
|
DEFAULT_SIP
On the Flags window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Flags for SIP Trunk Group.
Trunk Provisioning - Egress Ip Attributes SIP Flags
The following fields are displayed:
Egress Ip Attributes SIP Flags Parameters
Parameter | Description |
|---|---|
Bgcf Target Scheme Transparency | When enabled, the SBC 5000 series preserves the scheme used by the SIP INVITE Request-URI when the INVITE is routed by the SBC 5000 series, acting as a BGCF supporting Tel-URL. When disabled, the SBC 5000 serieschanges the scheme used by the Request-URI parameter to SIP in the egress INVITE message (this is the default). The options are:
|
Convert Inactive To Sendrecv | This flag is used by the SBC 5000 series to control the a-line in the SDP of an egress SIP INVITE message. When enabled, the SBC 5000 series converts a=inactive to a=sendrecv in the egress INVITE message. When disabled, the SBC 5000 seriescontinues to use a=inactive, when appropriate, in the egress INVITE message. The options are:
|
Disable2806Compliance | If enabled, the 2806 Compliance Code is disabled, and no phone context or user=phone parameters are signaled in egress messages. The options are:
|
Disable Optional Register Parameters | Controls whether the SBC 5000 series sends the DTG (Destination Trunk Group) parameter in the Contact header of egress REGISTER messages. When enabled, the SBC 5000 series does not send the DTG parameter. When disabled, the SBC 5000 seriessends the DTG parameter. The options are:
|
Map181Or182Message To 183 | This parameter is used by the SBC 5000 series to control SIP response processing. When enabled, the SBC 5000 series maps 181 or 182 response messages to 183. When disabled, the SBC 5000 serieshandles 1xx response messages normally. The options are:
|
Map Contractor Number In PSig Info Header | When enabled, the Contractor Number parameter will be mapped into the outgoing SIP P-Sig-Info header. The P-Sig-Info header is a customer-specific SIP header used to convey ISUP information in SIP messages. The options are:
|
Same call Id For Required Authorization | Enable this flag to support sending an INVITE with credentials on receiving a 401 (Unauthorized) or 407 (Proxy Authentication Required) response to initial INVITE with the same call ID as in the original INVITE. The options are:
|
Suppress Unregister | When enabled, the SBC 5000 series does not send an unregister message (Register=0) to the registrar upon expiration of a SIP UA registration. When deselected (default), the SBC 5000 seriesgenerates unregister messages on the egress leg if the UA does not refresh the registration on time. The options are:
|
Ttc Isup Mapping | When enabled, and when the IP protocol type of the IP signaling profile entry is SIP or SIP-I, the application that receives the SBC 5000 series policy response (which can be either the SIP signaling gateway application on the SBC 5000 series or the SIP core proxy on the SBC 5000 series) applies the mapping necessary for TTC-ISUP signaling. The options are:
|
Use Called Party In Request Uri | When enabled, the SBC 5000 series copies the username that has been selected for the "To" header to the Request URI instead of the registered username. When disabled, the SBC 5000 series includes the registered username in the Request URI. This flag is used by the SBC 5000 serieswhen interoperating with IP-PBXs that require the real end station number in the Request URI in order to do proper routing of calls terminating on them. The options are:
|
Use Colon In Sdp Media Type Parameter | When enabled, a colon ":" is used as the separator between the SDP Media Type parameter key and value. When disabled, an equal sign (=) is used as the separator between the SDP Media Type parameter key and value. The options are:
|
Validate Isub Address | When enabled, the SBC 5000 series validates ISUB digits for called and calling parties. When disabled, the SBC 5000 serieswill not validate ISUB digits. The options are:
|
Qos Based Routing | Specifies whether to enable Qos Based Routing or not. The options are:
|
Ignore SDP After Offer Answer Completed | If enabled, SBC ignores the new SDP at egress leg in subsequent 1xx-rel or final 200 OK after Offer Answer for the initial Invite dialog have been completed and would not trigger a new offer or answer. The options are:
|
Include Enum Parameters | If enabled, SBC sends ENUM parameters in the outgoing INVITE. If disabled, SBC drops ENUM parameters received from ENUM server. The options are:
|
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
Overview
Content Tools