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. The SBC supports up to 100 call transfers for a call. Modified: for 10.1.1 Use this window to specify parameters that control SIP signaling for a specific SIP trunk group. On the SBC main screen, navigate to Configuration → System Provisioning → Category: Trunk Provisioning → Trunk Group → SIP Trunk Group → Signaling or The Signaling window is displayed. Use the drop-down boxes to select the Address Context, Zone and SIP Trunk Group you want to configure. The Edit Signaling window displays. Use the following table to edit the options as needed, then click Save. SIP Trunk Group - Signaling parameters Parameter Description Access Class Set parameter to 3GPP to select the GIBA security mechanism when a REGISTER message is received without specific security headers. The SBC validates the source IP address against the Via header IP address and transparently passes the UE's Via header in egress messages towards network entities. If a REGISTER message is received with "sec-agree" in the Proxy-Require header along with Auth headers, and no IPsec profile is configured, the SBC rejects the message with a "4xx Bad Extension" error response irrespective of the Access Class parameter value. When GIBA security mechanism is selected and the 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. Route Msg Validation 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 the SBC detects an invalid message type is received. No Validation (default) SIP I – Route validation on received messages for SIP-I. SIP Only – Route validation on received messages for SIP-only messages. Max Fwds Default Backward Info Msg Con Dialog If enabled, an INFO message will only be sent after a confirmed dialog. ISUP Mime Body Relay Enable this 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. Use this flag to enable End-To-End Prack Support on the SBC and receive a reliable 180 Message. Rel100Support Enable to allow option tag 100rel support for the reliability of provisional messages as specified in RFC3262. NOTE: The SBC gives precedence to SIP Adaptive Transparency Profile over this flag. Enable this flag to support asymmetric PRACK interworking for late media calls. NOTE: The SBC gives precedence to SIP Adaptive Transparency Profile over this flag. Pref Require Transparency Enable (on Core network side) to parse and transparently pass “pref” SIP Option tag in incoming Require headers of REGISTER messages. The “pref” option tag is used to publish and request support for RFC 3840 caller capabilities. Privacy Param Restricted Enabled NOTE: The Relay Non Invite Request flag applies to SIP peering scenarios only. The SBC relays all out-of-dialog non-INVITE requests from registered endpoints irrespective of the value of the Relay Non Invite Request flag. Enable this flag to have the SBC locally handle out-of-dialog (OOD) REFER requests. When certain conditions are met, an OOD REFER request can be used to terminate an active call. Refer to Terminating Calls using OOD REFER Messages for more information. Enabled Use this flag to control how the 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 either trunk group, the offer/answer appearing on that trunk group inherits audio-less behavior. This flag is used to relay an UPDATE request with an Offer immediately after receiving or sending an 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: Inter Operator ID Specifies the inter-operator id (ioi) is a globally unique identifier shared between sending and receiving networks. The value ranges up to 23 characters. URI Preference Use this object to define URI presentation preference for outgoing messages. Strict Parse Enable this flag to reject requests which are understandable, but violate a relevant RFC Augmented Backus-Naur Form (ABNF) production rule. Skip DTGLookup For Route Hdr Enable this flag to skip destination trunk group look-up on a Route header when routing calls using Route headers received in a request. The egress IP trunk group is determined based on existing routing logic. Process Tgrp Context Use this flag to determine "tgrp" parameter behavior. 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 the P-CSCF to globalize the To header in a REGISTER request URI in a SUBSCRIBE for the regevt, to perform a PSX dip for non-INVITE for the tel URI, and to control the dial string feature. Enable this flag to allow the P-CSCF to delete the parent RCB and all its children during de-registration of any of child IP Multimedia Public Identities (IMPUs). If enabled, the AoR must be validated. If disabled, calls are allowed from anonymous users or users whose AOR do not match with the one stored in the SBC as part of RCB created during initial registration. 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. Disabled (default) Enabled Enable this flag to use the ingress message Allow header content in the egress message. Only methods which are configured as allowed at the egress trunk group are populated from the ingress to the egress message. Methods with no configuration present are considered allowed (example: INVITE). Use this Zone/Trunk Group object to associate a Sip Adapter Profile configured for flexible policy (Profile Type=Flexible Policy) with a particular Zone/Trunk Group. If a Flexible Policy Adapter Profile is provisioned both at the trunk group and zone levels, the trunk group’s profile takes precedence. If an Input Adapter Profile is configured, it is applied first to manipulate the PDU and then the Flexible Policy Adapter Profile rules are applied on the manipulated PDU. Enable this flag to accept History-Info headers received on the ingress trunk group. This flag enables the Bye-Challenge feature. When this flag is enabled, BYEs might get challenged either by 401 or 407 and the call is released only when a BYE with appropriate credentials is received. Enable this flag to enforce using TLS to egress a request if the Request-URI/topmost Route header usesthe “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 TLS Peer Name with this trunk group using either the host name or the IP address. If the TLS Peer Name is in IP address format, the SBC validates it against the IP address entries in the Subject Alternate Name Extension (SAN) field. Otherwise, the TLS Peer Name is compared against DNS entries in the SAN plus the Common Name (CN) in the subject field. This field accepts multiple TLS Peer name separated by comma, up to a total of 255 characters. NOTE: Enable this flag to allow the SBC to use a PSX-returned route instead of stored Service Route information for processing emergency calls from registered users. Enable this flag to pass the SDP information to PSX (excluding data up to the first occurrence of m-line). NOTE: This flag is not applicable when the SBC is configured for ERE. Use this flag to control how the SBC handles KPML events for In-Dialog and Out-Of-Dialog (OOD) Subscribe messages for the specified ingress/egress trunk group. This feature only works in GW-GW scenarios when Kpml Subscribe Mode is set to "Consume". The Cisco Unified Communication Manager (CUCM) only supports KPML service for calls if it receives an Allow-Events header with the value 'kpml'. Use the SMM below to add the header, when required. For additional feature details, refer to DTMF and RTP Relay. Modified: for 10.1.3 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 Disable Rn in the IP Signaling Profile is enabled. NOTE: If this flag is disabled and Disable Rn is enabled (Egress Ip Attributes - Number Portability Attributes flag), the SBC populates the routing number (rn) in the R-URI and the To headers. Enable this flag to support the keep-alive mechanism (RFC 6223). Use this parameter to specify whether a call is transitioned to a fax or voice call when "silenceSupp:off" is received in re-INVITE. A call is considered a fax call when the Packet Service Profile Apply Fax Tone Treatment flag is enabled and either: Use this parameter to control how the PEM header is sent during Preconditions Interworking. When this flag is enabled, the SBC sends a 500 (Server Internal Error) response upon receipt of a BYE when the CSeq is a lower value than the preceding INVITE request (as per RFC 3261). Enabled 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 OKs to an INVITE after the timer expiry. When this flag is disabled, the SBC continues to acknowledge retransmitted 200 OKs (as per RFC 3261). Enabled Enable flag to use a randomly-generated value as UserInfo in the Contact header. The options are: If enabled, response for non-route INVITE is suppressed. The options are: NOTE: With Suppress Non Route Invite Response enabled, the NO_ROUTE_FOUND script is always ignored when an INVITE is dropped even if the script is returned from the ERE/PSX. Enable this flag to allow the SBC to retry requests resolved from an external DNS server to the IP/port, and skipping the internal DNS cache on a REGISTER transaction timeout. If enabled, the SBC uses the 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 the Enable this flag to allow the SBC to rewrite identities for both ingress and egress trunk groups to achieve SIP URI transparency for SIP-URIs present in outbound SIP messages. When this parameter is enabled, for an egress trunk group, the SBC updates the originating and terminating identities in outbound SIP messages as per the policy response from PSX. NOTE: For this feature to work, Rewrite Identities should be enabled on both ingress and egress SIP trunk groups. Enable this flag to allow the usage of different IP-Port as contact for each active registration towards the 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: This feature is supported only for UDP. Disable the transparency flag Pass Complete Contact Header to use this feature. Do not use this feature if two Interfaces are configured on the same Interface Group. Disable this flag before performing LSWU. NOTE: 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 this flag to clear the TCP connection between a UE and the SBC once its registration becomes inactive. The SBC clears (closes) the TCP connection even when there are user agent registration failures. 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 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 a 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. The flag CPC Interworking for NNI has two possible values: When set to Enabled, the SBC populates the parameter Calling Party Category (CPC) with the value 11, on receiving a Resource Priority Header (RPH) in the initial INVITE. Here, the value 11 denotes "Calling Subscriber with priority". When an RPH is absent in the initial INVITE, the SBC populates the parameter CPC from the PAI Header. Enable this option 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 Disabled, the SBC plays tones based on the LMSD format. NOTE: If applicable, use the Convert Alert To Progress flag to convert the '180 response' to a '183 session progress' towards the ingress. 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: Indicates the GPRS-IMS-Bundled Authentication (GIBA) procedure support for S8HR inbound user. When enabled, the GIBA procedure is applied for the S8HR inbound user. When disabled, the GIBA procedure is not applied for the S8HR inbound user. Enable this flag on trunk groups that receive simultaneous UPDATE/18x messages in order to allow processing of UPDATE/18x messages even when transaction states for the message are pending. The options are: Enable this flag on the ingress trunk group to allow the The options include: Note: This is not applicable when the dialog transparency flag or the Enable this flag on the ingress trunk group to allow the The options include: Note: Specifies the name of the SIP JJ-90.30 Interworking profile associated with this SIP Trunk Group. For more information, refer to Signaling - SIP JJ9030Interworking Profile. Specifies the name of the SIP XHeader Profile to attach to a SIP trunk group to support various call transfer scenarios. For more information, refer to REFER Relay and INVITE with Replaces, for additional information. Modified: for 10.1.1 Specifies the Called Prefix Match table associated with this SIP Trunk Group. For more information, refer to Signaling - Called Prefix Match Profile and Called Prefix Match Profile - Prefix Match. Enable this flag to allow the SBC to send SDP in subsequent unreliable 18x messages. Once the reliable response is sent, the SBC stops sending the SDPs. This behavior is RFC 6377 compliant. When disabled, the SBC sends the SDP in subsequent 18x messages, regardless of their reliability. This is the same behavior as releases prior to 8.2.0 The options include: For more information, refer to Ingress Ip Attributes - Flags Enable this option to configure the SBC to relay media changes when it detects any of the following in a new offer: The options include: Note: The option Minimize Relaying Of Media Changes From Other Call Leg All in the IP Signaling Profile for the trunk group must also be enabled for this option to take effect. Refer to Common IP Attributes - Flags for more information. Enable this flag to allow the SBC to queue the SDP offer and send it out once the previous procedure is complete. For more information, refer to Sending a No-Charge Notification to the Ingress Call Leg. Modified: for 10.1.1 Use this flag in conjunction with the IPSP "Map Uui In PSig Info Header" flag and the Trunk group "Ucid Support" flag to control the behavior of the User-to-User Header field at the ingress and egress level.
IMPORTANT
Note
To Edit Signaling Parameters
All → Address Context → Zone → SIP Trunk Group → Signaling
Specifies the default value for the Max Forwards header. The value ranges from 1 to 100 and the default value is 70. Proxy Behavior For 18x When E2E Prack Enabled Sdp 100rel Iwk For Prack Use this object to define SIP Privacy header parameter mapping (incoming to outgoing call). Relay Non Invite request Enable this flag to relay out-of-dialog non-INVITE requests. Local OODRefer Support Treat Port Zero as No Audio Relay Updatewith SDP Isub Param Preference This trunk group attribute specifies how the ISDN Sub-Address parameter is handled. Variant Type Specifies the SIP variant type. Factor Value 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. Always Reply Inactive If Received Inactive Local Number Support Disable Term IOIFor Pcscf Enable this flag to prevent the P-CSCF from adding an “erm-ioi” parameter to any requests while creating a P-Charging-Vector (PCV) header. De Reg Parent With Child Dereg Use PSXRoute As Req URI in Reg Enable this flag to allow the P-CSCF to use the PSX-returned route as the Request URI in the REGISTER. PSX Route For Subscribe Enable this flag to use PSX routes for routing OOD (Out-Of-Dialog) methods to registered users. Default Calling Party Number Specifies the default calling number for the Caller Privacy feature. If the party number is configured and the IP Signaling Profile flag Ms Lync Privacy Support 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. Validate Aor Source Address Validation Cond Inc Meth in Allow Hdr Flexible Policy Adapter Profile NOTE: Flexible Policy is not supported on ERE and is intended for use with an external PSX only.SIP Filter Profile 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 Disabled. NNI Profile 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. PSX Script Profile The name (1-23 characters) of the PSX Script Profile which contains the list of script names for which the SBC performs ingress preconditions interworking. Accept History Info Egress Call ID Static String 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. Allow Bye Challenge Enforce TLS if Sips URI Scheme Enforce Sips if Egress is TLS TLS Peer Name Use PSX Route For Emergency Call OCS Support Enable this flag to enable OCS (Office Communications Server/ MS Lync) support. Relay Replaces Header When enabled, the P-CSCF relays Replaces headers with INVITEs. Feid for PDCS The FEID value sent out in an egress PDCS-Billing-Info header when sending JIP values in PDCS headers. FEID consists of a hexadecimal string of up to 16 characters followed by a domain name (for example, abc1234@98.245.153.111). The value ranges up to 127 characters.Send SDP to PSX Kpml Subscribe Mode
Use GAPwhen Rn Disabled Support199Option Tag Enable this flag to include Option tags in Supported Headers for the 199 Extension. Keep Support Outbound Support Enable this flag to support outbound procedures specified in RFC 5626. Silence Supp Treatment Pem Interworking Rfc3261Validate CSeq In BYE Rfc3261Validate Invite200Ok Retransmissions Use Random User Info In Contact Hdr Suppress Non Route Invite Response DNS Force Re Query Use Pcfa Ccf Honor Maddr Param Maddr parameter present in the Contact header of incoming requests/responses or in Refer-To headers.MaddrMaddrMaddrmaddr value is IPv4, IPv6, or FQDN (resolving to either IPv4 or IPv6).Rewrite Identities
When this parameter is disabled for an egress trunk group, the SBC does not update the originating and terminating identities in outbound SIP messages as per policy response from PSX.Transit IOI Use this parameter to specify a Transit IOI value for for inclusion in the P-Charging-Vector header. This parameter must be configured on the trunk group facing the transit network and the configured value is inserted on the other leg in case of an egress message. Refer to P-Charging-Vector Header for additional details. Term IOI Use this parameter to specify a terminating Inter Operator Identifier (term-ioi) (up to 63 characters) for inclusion in the P-Charging-Vector header. The SBC creates and sends a term-ioi parameter when there is no egress network, which occurs when a call is terminated in a script. When there is an egress network, the term-ioi parameter is received from the egress network and sent to the ingress network. Use Port Range Flag Store ICID Clear TCP Connectionsfor Registration Stop Lmsd Tone On Update Drop ISUP Mime Body CPC Interworking for NNI Ai To Pem Interworking Convert Alert To Progress Rfc7732Validate Max Forwards When this flag is enabled, the SBC will use the Max-Forwards header value received from the end-user, and decrements this header value by 1 before forwarding it to the other end-user. If the value received from the end-user is 0 or 1, the SBC will discard that request with an error response of "483 - Too Many Hops." S8hr Support Indicates the support for S8 Home Routing (S8HR) roaming calls. When enabled, S8HR calls are supported. When disabled, S8HR calls are not supported. Giba Support For S8hr Inbound User Embedded Register Infoin User Part Enable this option to allow the SBC to append a RegInfo value to the user part of the Contact header of a REGISTER request to uniquely identify the registering subscriber. If the subscriber registers from multiple devices using the same phone number, the SBC will use this value in subsequent routing to identify the correct subscriber instance. The options are: Allow Simultaneous 18x UPDATEtransaction Honor Contact In Register for TLSCalls Enable this option to o specify where the SBC directs access calls from the internal network to users in the access network when the call is over TLS transport. The options are: Prefer UpdateOver Re Invite Unable to show "metadata-from": No such page "_space_variables" to use UPDATE instead of Re-INVITE to communicate SDP towards ingress, when the call is in the confirmed state.updatedAnswerIn200Ok flag is in enabled state on the Unable to show "metadata-from": No such page "_space_variables".Perform Precondition Renegotiation Unable to show "metadata-from": No such page "_space_variables" to renegotiate the precondition on the ingress when there is a change in SDP during early dialog phase or whenever the call goes to confirmed state. TheUnable to show "metadata-from": No such page "_space_variables" supports this flag for SIP gateway-gateway call.updatedAnswerIn200Ok flag is in enabled state on the Unable to show "metadata-from": No such page "_space_variables"SIP JJ9030 Interworking Profile SIP XHeader Profile
Called Prefix Match Profile Only Send Subsequent 18x SDP If Unreliable Effective Relay Of Media Changes From Other Call Leg Do Not Auto Answer Send PAI URI To PSX Enable this flag to allow the SBC to send both SIP and TEL URIs from the P-Asserted-Identity header to the PSX in a policy request. This option should be configured on the ingress trunk group. The options are: Prefer Ptime In SDP Enable this flag so that when the SBC sends out a ptime value in SDP, it gives preference to the ptime value it received in the a=ptime attribute in the incoming SDP over the a=maxptime value. This flag should be enabled in conjunction with the IP Signaling Profile flag Send Ptime In SDP which enables the SBC to send out an a=ptime value. Enabling the Prefer Ptime In SDP flag then ensures that the SBC sends out the a=ptime value if both values are received in the incoming SDP. When configuring, if you enable Send Ptime In SDP on the egress trunk group, enable Prefer Ptime In SDP on the ingress trunk group, and vice versa.
The options are:User to User Hdr Support
Use this configuration in conjunction with the IPSP and Trunk Group parameters.
Overview
Content Tools