|Ribbon Documentation Center|
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 specify parameters controlling the specifics of SIP signaling for this SIP trunk group.
On the SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Trunk Group > SIP Trunk Group > Signaling.
The Signaling window is displayed.
The Signaling can be checked for each Address Context, for each Zone, for each SIP Trunk Group created or for all the Address Contexts, Zones and SIP Trunk Groups created.
Use the drop-down boxes to select the desired Address Context, Zone and SIP Trunk Group. The Edit Signaling window displays.
Click to view Edit Signaling UI example...
The following fields are available for configuration:
Set parameter to "
When GIBA security mechanism is selected and Via header is configured to pass transparently to egress leg, the SBC inserts a “received” parameter with the source IP address of the PDU if the host portion of the UE’s Via header does not equate to the source IP address seen by the SBC.
Specifies if route validation should be done for the received message and if the message should be validated to ensure it is SIP-only or SIP-I. The call is released after invalidation if an invalid message type is received.
|Specifies the default value for the Max Forwards Header. The value ranges from 1 to 100 and the default value is 70.|
If enabled, an INFO message will only be sent after confirmed Dialog.
Enable flag to transparently relay (in egress SIP signaling) an ISUP mime body received in SIP signaling. When disabled, ISUP mime bodies are decoded and interworked based on the egress signaling configuration.
Enable to allow option tag 100rel support for the reliability of provisional messages as specified in RFC3262.
Enable this flag to support Asymmetric PRACK Interworking for late media calls.
Enable (on Core network side) to parse and transparently pass “pref” SIP Option tag in incoming Require header of Register message. The “pref” option tag is used to publish and request support for RFC 3840 caller capabilities.
|Use this object to define SIP Privacy header parameter mapping (incoming to outgoing call).|
|Enable this flag to relay non-Invite requests.|
Use this flag to control how audio portion of a call on port 0 is treated.
NOTE: The legacy behavior of treating audio on port 0 as on hold is possible only when this flag is disabled for both ingress and egress trunk groups. If this flag is enabled on just one trunk group, the offer/answer appearing on that trunk group inherits audio-less behavior.
This flag is used to relay UPDATE request with Offer immediately after receiving or sending answer in unreliable provisional responses. This flag is applicable only in case of interworking where one side supports reliable response (from where the UPDATE is received) and the other side does not (towards which it needs to be relayed). The options are:
Specifies the inter-operator id (ioi) is a globally unique identifier shared between sending and receiving networks. The value ranges up to 23 characters.
Use this object to define URI presentation preference for outgoing messages.
Enable this flag to reject requests which are understandable, but violate the relevant RFC Augmented Backus-Naur Form (ABNF) production rule.
Enable flag to skip destination trunk group look-up on Route header when routing calls using Route headers received in a request. Egress IP trunk group is determined based on existing routing logic.
Use this flag to determine "tgrp" parameter behavior.
|This trunk group attribute specifies how the ISDN Sub-Address parameter is handled in SIP.|
|Specifies the SIP variant type.|
|Enter the factor value to use to interwork the SIP Max-Forwards header and the ISUP Hop counter parameter. The value ranges from 1 to 50 and the default value is 1.|
Enable this flag to allow the SBC to reply with "a=inactive" in an Answer message when the SBC receives an Offer with "a=inactive".
Enable this flag to allow P-CSCF to globalize. To hdr in Register,req URI in SUBSCRIBE for regevt and perform a PSX dip for non-INVITE for tel URI as well as control the dial string feature.
|Enable this flag to prevent P-CSCF from adding “erm-ioi” parameter to any requests while creating P-Charging-Vector (PCV) header.|
Enable this flag to allow P-CSCF to delete parent RCB and all its childs during de-registration of any of the child IP Multimedia Public Identities (IMPUs).
|Enable this flag to allow P-CSCF to use the PSX returned route as the Request URI in the register.|
|Enable this flag to use PSX routes for routing OOD (Out-Of-Dialog) methods to registered users.|
|Specifies the default calling number for Caller Privacy feature. If the party number is configured and the flag msLyncPrivacySupport is enabled, the configured number is inserted as the user name of either the from header or the P-Asserted-Identity fields depending on the configuration. The value ranges up to 23 characters.|
If enabled, the AoR must be validated. If disabled, calls from anonymous users or users whose AOR does not match with the one stored in the SBC as part of RCB created during initial registration are allowed.
NOTE: For surrogate registered users, set this flag to "disabled".
Enable this flag to support source address validation so that messages coming from a different IP address or port than expected are not allowed.
Enable this flag to use ingress message ALLOW header content in the egress message. Only methods which are configured as allowed at the egress TG are populated from ingress to the egress message. Methods with no configuration present are considered allowed (example: INVITE).
Use this Zone/Trunk Group object to associate a
|The name (1-23 characters) of the SIP Filter Profile created, and optionally attached to a SIP Trunk Group. In the default SIP Filter Profile, the transparency settings of all permissible headers is set to |
|The name (1-23 characters) of the NNIProfile used to control SBC interworking of charging parameters for SIP to/from SIP-I/T, GW-GW and ISUP calls. The NNI Profile is attached to a SIP trunk group.|
Enable this flag to accept History-Info header received on the ingress trunk group.
|String for generating the egress callid when configured option for egressCallIdType in PSX is "Use Static String". (default is a hyphen “-”). Egress Call-id is the aggregate of Ingress Call-id and locally generated string in the SBC.|
This flag enables the Bye-Challenge feature. When this flag is enabled, the BYE's might get challenged either by 401 or 407 and the call is released only when the BYE with appropriate credentials are received.
Enable this flag to enforce using TLS to egress a request if the Request-URI/topmost Route header uses “sips” scheme on a per-peer group basis.
Enable this flag to change the URI scheme as described below.
Use this parameter (0-255 characters; default = 0 characters) to associate the
This field accepts multiple TLS Peer name separated by comma, up to a total of 255 characters.
Enable this flag to allow the SBC to use PSX returned Route instead of stored-service route information for processing Emergency calls from Registered users.
|Enable this flag to enable OCS (Office Communications Server, a.k.a MS Lync) support.|
|When enabled, P-CSCF relays Replaces header with INVITE.|
|The FEID value sent out in egress PDCS-Billing-Info header when sendiing JIP value in PDCS header. FEID consists of hexadecimal string of up to 16 characters followed by a domain name (for example, |
Enable flag to pass the SDP information to the PSX (excluding data up to the first occurrence of m-line).
NOTE: This flag is not applicable when the SBC is configured for ERE.
Enable this flag to cause the SBC to populate the GAP/OCN in the R-URI and To headers at the egress Trunk Group. This flag is valid only when the egress profile flag "
NOTE: If this flag is disabled and “
|Enable flag to include Option tag in Supported Header for the 199 Extension.|
Enable flag to support the keep-alive mechanism (RFC 6223).
|Enable flag to support outbound procedures specified in RFC 5626.|
Use this parameter to specify whether call is transitioned to fax or voice call when "silenceSupp:off" received in re-INVITE.
A call is considered a fax call when Packet Service Profile
When this flag is enabled, the SBC sends a 500 (Server Internal Error) response upon receipt of a BYE when CSeq is a lower value than the preceding INVITE request (as per RFC 3261).
When this flag is enabled, the SBC starts a timer for 64 * T1 (32 seconds) upon receiving a 200 OK to an INVITE. The SBC does not acknowledge re-transmitted 200 OK to an INVITE after the timer expiry. When this flag is disabled, the SBC continues to acknowledge retransmitted 200 OKs (as per RFC 3261).
Enable flag to use randomly-generated value as UserInfo in contact header. The options are:
If enabled, response for non-route invite is suppressed. The options are:
Enable this flag to allow the SBC to retry requests resolved from external DNS server to the IP/port, and skipping the internal DNS cache on a REGISTER transaction timeout.
If enabled, the SBC uses CCF received in PCFA as CDF. The options are:
Enable this flag to allow the SBC to process (and make routing decisions) the
The following behavior is supported with this feature:
NOTE: The SBC supports this feature even when
When this parameter is enabled, for egress trunk group, the SBC updates the originating and terminating identities in outbound SIP message as per policy response from PSX.
NOTE: For this feature to work, Rewrite Identities should be enabled on both ingress and egress SIP Trunk Groups.
|Use this parameter to specify a |
Enable this flag to allow the usage of different IP-Port as contact for each active registration towards Cisco Unified Communication Manager (CUCM). The SBC uses either an independent media port range configured per IP Trunk Group (IPTG), or a new port from the system-wide media port range if no independent media port range is configured per IPTG. The options are:
The SBC supports this feature when:
Feature limitations and restrictions:
Enable this flag to allow the SBC to retain the same ICID value generated in the first egressed INVITE for the crankback/redirect (3xx) call in the P-Charging-Vector header of the egressed INVITE. The options are:
Enable flag to clear the TCP connection between UE and the SBC once the registration becomes inactive. The SBC clears (closes) the TCP connection even when there are user agent failure registrations.
When this flag is disabled, the SBC relies on the UE to clear the TCP connection between the two If the registration becomes inactive.
For calls originating from the MSC server, enable this flag to send a split response on the leg which receives the a ringing tone from the MSC in order to force the MSC to stop the ringback tone: 1) Send a 180 ringing without SDP with Alert-Info to stop the LMSD tone, and 2) Send an update with the SDP offer.
NOTE: The 180 ringing is sent only if the SBC has relayed the Alert-Info with the non-null URI.
Enable this flag for the SBC to drop the ISUP MIME body received in SIP-I messages and treat the call as a normal SIP call. if SIP-I is configured for incoming messages, the SBC adds the ISUP MIME to the outgoing messages.
To start CPC (Calling Part Category) Interworking for NNI, set this flag to
Enable this flag on the egress trunk group to support Alert-Info and P-Early Media header interworking (whether the SBC is configured to play tones or not), and to not perform LMSD interworking.
If set to default, the SBC plays tones based on the LMSD format.
NOTE: If applicable, use the
This flag is used to convert 180 ringing to 183 Session Progress when the SBC is configured to play tone. This flag is configured on the ingress TG.
The options are:
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
Additional topics in this section: