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.
Use this object to configure the SIP Headers and Parameters flags.
To View and Edit Sip Headers And Parameters - Flags
On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Egress Ip Attributes > Sip Headers And Parameters > 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 Sip Headers and parameters - Flags
There are no Flags parameters for DEFAULT_H323 type of Egress Ip Attributes.
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 Sip Headers And Parameters - Flags
The following fields are displayed:
Egress Ip Attributes Sip Headers and Parameters - Flags
Parameter | Description |
|---|---|
Include Cic | If enabled, the Unable to show "metadata-from": No such page "_space_variables" includes the Carrier Identification Code in a cic= parameter in outgoing INVITE messages. The options are:
|
Include Cpc Information | If enabled, the Unable to show "metadata-from": No such page "_space_variables" 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. The options are:
|
Include Npi | If enabled, the Unable to show "metadata-from": No such page "_space_variables" includes the Numbering Plan Indicator in a npi= parameter in outgoing INVITE messages. The options are:
|
Include Olip | If enabled, the Unable to show "metadata-from": No such page "_space_variables" includes the Originating Line Information Parameter in a oli= parameter in outgoing INVITE messages. The options are:
|
Include PKAdn | When enabled, the Unable to show "metadata-from": No such page "_space_variables" 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). The options are:
|
Include Pstn Parameters | If enabled, the Unable to show "metadata-from": No such page "_space_variables" 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). The options are:
|
Include Qvalue | If enabled, the ERE SIP proxy/redirector includes the qvalue parameter (for example, q=0.9) in the Contact header of outgoing 3xx messages. The options are:
|
Skip CSeq Check In Early Dialog | When enabled, the Unable to show "metadata-from": No such page "_space_variables" 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. The options are:
|
Transparency For Destination Trunk Group Parameter | 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. The options are:
|
End To End Ack | When enabled, the ACK is sent towards Egress for the initial invite after receiving it from the Ingress (remote) entity. 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