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 this object to configure the SIP Headers and Parameters flags. On the SBC main screen, choose a path: The Flags window is displayed. H.323 Egress IP Attributes do not support this feature. On the Flags window, choose the IP Signaling Profile as DEFAULT_SIP to view the Flags for SIP Trunk Group. SIP Headers And Parameters - Flags Parameters: Parameter Description If enabled, the SBC includes the Carrier Identification Code in a cic= parameter in outgoing INVITE messages. If enabled, the SBC includes the Calling Party Category (CPC) parameter value in the From header of outgoing SIP INVITE messages.The CPC parameter characterizes the station used to originate a call, such as ordinary, priority, data, test, operator, pay phone, prison, hotel or unknown. If enabled, the SBC includes the Numbering Plan Indicator in a npi= parameter in outgoing INVITE messages. If enabled, the SBC includes the Originating Line Information Parameter in a oli= parameter in outgoing INVITE messages. When enabled, the SBC includes the P-K-Adn header in egress SIP messages. When disabled, the SBCdoes not include the P-K-Adn header. The P-K-Adn header is a customer-specific SIP header used for ISUP-to-SIP interworking and contains the Translation Source Number (TSN) used in Number to SIP URL translation via the Number Username Translation screen (Generic variant only). If enabled, the SBC includes a set of specific PSTN parameters in a pstn-params= entry in outgoing INVITE messages. The PSTN parameters currently included in pstn-params are Screening Indicator, ISDN Indicator, and Transmission Medium Requirement (TMR). If enabled, the ERE SIP proxy/redirector includes the qvalue parameter (for example, q=0.9) in the Contact header of outgoing 3xx messages. When enabled, the SBC accepts multiple SIP requests in which the CSeq number in a later request is of a lesser value than the CSeq number received in earlier requests. When enabled, if ERE receives both tgrp parameter and trunk-context in an ingress INVITE Request-URI, ERE as proxy transparently passes the tgrp parameter and trunk-context in the egress INVITE Request-URI. Values selected for the "Destination Trunk Group Option" are ignored. When enabled, the ACK is sent towards Egress for the initial invite after receiving it from the Ingress (remote) entity. Make the required changes and click Save.To View and Edit SIP Headers And Parameters - Flags
DEFAULT_H323
DEFAULT_SIP
Include Cic Include CPC Information Include Npi Include Olip Include PKA dn Include Pstn Parameters Include Qvalue Skip CSeq Check In Early Dialog Transparency For Destination Trunk Group Parameter End To End Ack