In this section:
This object specifies the values associated with the Flags of Egress IP Attributes.
On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Egress Ip Attributes > Flags. The Flags window is displayed.
On the Flags window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Flags for H323 Trunk Group.
The following fields are displayed:
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:
|
On the Flags window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Flags for SIP Trunk Group.
The following fields are displayed:
Parameter | Description |
---|---|
Bgcf Target Scheme Transparency | When enabled, the Unable to show "metadata-from": No such page "_space_variables" preserves the scheme used by the SIP INVITE Request-URI when the INVITE is routed by the Unable to show "metadata-from": No such page "_space_variables" , acting as a BGCF supporting Tel-URL. When disabled, the Unable to show "metadata-from": No such page "_space_variables" changes 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 Unable to show "metadata-from": No such page "_space_variables" to control the a-line in the SDP of an egress SIP INVITE message. When enabled, the Unable to show "metadata-from": No such page "_space_variables" converts a=inactive to a=sendrecv in the egress INVITE message. When disabled, the Unable to show "metadata-from": No such page "_space_variables" continues to use a=inactive, when appropriate, in the egress INVITE message.The options are:
If 'onhold' is received on ingress leg and ‘sendrecv’ is sent to egress leg, then the peer egress must respond with 18x/2xx with ‘sendrecv’. Only the ingress leg can trigger ‘offhold’. Other behavior is not supported. |
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 Unable to show "metadata-from": No such page "_space_variables" sends the DTG (Destination Trunk Group) parameter in the Contact header of egress REGISTER messages. When enabled, the Unable to show "metadata-from": No such page "_space_variables" does not send the DTG parameter. When disabled, the Unable to show "metadata-from": No such page "_space_variables" sends the DTG parameter.The options are:
|
Map181Or182Message To 183 | This parameter is used by the Unable to show "metadata-from": No such page "_space_variables" to control SIP response processing. When enabled, the Unable to show "metadata-from": No such page "_space_variables" maps 181 or 182 response messages to 183. When disabled, the Unable to show "metadata-from": No such page "_space_variables" handles 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:
To view and configure this flag, you must first enable both ' |
Suppress Unregister | When enabled, the Unable to show "metadata-from": No such page "_space_variables" does not send an unregister message (Register=0) to the registrar upon expiration of a SIP UA registration. When deselected (default), the Unable to show "metadata-from": No such page "_space_variables" generates 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 Unable to show "metadata-from": No such page "_space_variables" policy response (which can be either the SIP signaling gateway application on the Unable to show "metadata-from": No such page "_space_variables" or the SIP core proxy on the Unable to show "metadata-from": No such page "_space_variables" ) applies the mapping necessary for TTC-ISUP signaling.The options are:
|
Use Called Party In Request Uri | When enabled, the Unable to show "metadata-from": No such page "_space_variables" copies the username that has been selected for the "To" header to the Request URI instead of the registered username. When disabled, the Unable to show "metadata-from": No such page "_space_variables" includes the registered username in the Request URI. This flag is used by the Unable to show "metadata-from": No such page "_space_variables" when 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 Unable to show "metadata-from": No such page "_space_variables" validates ISUB digits for called and calling parties. When disabled, the Unable to show "metadata-from": No such page "_space_variables" will 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:
If |
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.