In this section:
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. This object specifies the values associated with the flags of Egress IP Attributes. On the SBC main screen, choose a path: The Flags window is displayed. On the Flags window, choose the IP Signaling Profile as DEFAULT_H323 to view the flags for H.323 trunk groups. Trunk Provisioning - H.323 Egress IP Attribute Flags Egress IP Attributes - Flags Parameters Parameter Description Delay Cut Through Enable this flag for the ERE to issue a call cut-through until the egress media setup completes (through a fast start or H.245 procedure). Disable this flag for the ERE to issue a call cut-through as soon as the egress peer indicates in-band tone is available through progress indicators independent of the availability of media information from the egress peer. Dont Send Fast Start Proposal Enable this flag for the ERE to omit a fast start proposal in early media calls. This relies on H.245 procedure to complete media setup. Disable this flag for the ERE to always include a fast start proposal in a SETUP message for early media calls. Insert In Band Indication When this flag is enabled, on receipt of an H.225 ALERT message the egress H.323 signaling gateway on the ERE inserts an in-band indication in the ALERT message in the backward direction (toward the PSTN). Wait Till Connect Before Abandon Fast Start When this flag is enabled, the ERE honors the procedures defined in H.323 V4 for switching to H.245. The ERE abandons FastStart procedures if an H.323 Connect message, a FastConnectRefused message or an H.245 address is received. QOS Based Routing Enable this flag to enable QoS-based routing so the ERE can associate the QoS profiles (Signaling and/or Media) an IP Peer/IPTG. Enable3261Cancel Handling Use this flag to decide whether to send a CANCEL immediately after getting the INVITE or wait until a 100 Trying message. When enabled, the SBC alerts the gateway initiating an INVITE that it can only send a SIP CANCEL after receiving a SIP provisional response (the SIP CANCEL must conform to RFC 3261). Modified: for 12.1.3 On the Flags window, choose the IP Signaling Profile as DEFAULT_SIP to view the flags for SIP trunk groups. Trunk Provisioning - SIP Egress IP Attribute Flags Egress IP Attributes SIP Flags Parameters Parameter Description When enabled, the SBC preserves the scheme used by the SIP INVITE Request-URI when the INVITE is routed by the SBC, acting as a BGCF supporting Tel-URL. When disabled, the SBCchanges the scheme used by the Request-URI parameter to SIP in the egress INVITE message (this is the default). This flag is used by the SBC to control the a-line in the SDP of an egress SIP INVITE message. When enabled, the SBC converts a=inactive to a=sendrecv in the egress INVITE message. When disabled, the SBCcontinues to use a=inactive, when appropriate, in the egress INVITE message. 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. If enabled, the 2806 Compliance Code is disabled, and no phone context or user=phone parameters are signaled in egress messages. Controls whether the SBC sends the DTG (Destination Trunk Group) parameter in the Contact header of egress REGISTER messages. When enabled, the SBC does not send the DTG parameter. When disabled, the SBCsends the DTG parameter. This parameter is used by the SBC to control SIP response processing. When enabled, the SBC maps 181 or 182 response messages to 183. When disabled, the SBChandles 1xx response messages normally. 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. 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. To view and configure this flag, you must first enable both ' When enabled, the SBC does not send an unregister message (Register=0) to the registrar upon expiration of a SIP UA registration. When deselected (default), the SBCgenerates unregister messages on the egress leg if the UA does not refresh the registration on time. 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 policy response (which can be either the SIP signaling gateway application on the SBC or the SIP core proxy on the SBC) applies the mapping necessary for TTC-ISUP signaling. When enabled, the SBC copies the username that has been selected for the "To" header to the Request URI instead of the registered username. When disabled, the SBC includes the registered username in the Request URI. This flag is used by the SBCwhen 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. 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. When enabled, the SBC validates ISUB digits for called and calling parties. When disabled, the SBCwill not validate ISUB digits. Specifies whether to enable Qos Based Routing. 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. If enabled, SBC sends ENUM parameters in the outgoing INVITE. If disabled, SBC drops ENUM parameters received from ENUM server. If the Include Enum Parameters flag is enabled, other flags for standard parameters such as cic, npdi should not be configured. Use this flag to specify whether or not to monitor the RTP when an UPDATE message is received to determine whether to continue playing a tone. Use this flag to decide whether to send a CANCEL immediately after getting the INVITE or wait until a 100 Trying message. When enabled, the SBC alerts the gateway initiating an INVITE that it can only send a SIP CANCEL after receiving a SIP provisional response (the SIP CANCEL must conform to RFC 3261). Modified: for 12.1.3 Make the required changes and click Save.
IMPORTANT
To View and Edit Flags
DEFAULT_H323
DEFAULT_SIP
Bgcf Target Scheme Transparency Convert Inactive To Sendrecv
Note:
Disable2806Compliance Disable Optional Register Parameters Map181Or182Message To 183 Map Contractor Number In PSig Info Header Same call Id For Required Authorization
Note:
Auth Code Headers' transparency flag and 'Status Code 4xx6xx' relay flag.Suppress Unregister Ttc Isup Mapping Use Called Party In Request Uri Use Colon In Sdp Media Type Parameter Validate Isub Address Qos Based Routing Ignore SDP After Offer Answer Completed Include Enum Parameters
Note:
Monitor Rtp On Egress Update Enable3261Cancel Handling
Overview
Content Tools