In this section:



IMPORTANT

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.


Note

 The SBC supports up to 100 call transfers for a call.


Use this window to specify parameters that control SIP signaling for a specific SIP trunk group.

To Edit Signaling Parameters

On the SBC main screen, navigate to Configuration → System Provisioning → Category: Trunk Provisioning → Trunk Group → SIP Trunk Group → Signaling or
All → Address Context → Zone → SIP Trunk Group → Signaling

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


Note

The SBC does not support Lync/Skype.


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.

  • 3GPP – Select to enable the GIBA security mechanism.
  • none (default) – When selected, the SBC defaults to SIP digest without TLS authentication.
  • Tispan-NASS – Select for the SBC to identify if a request arrives on TISPAN NASS.

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

Specifies the default value for the Max Forwards header. The value ranges from 1 to 100 and the default value is 70.

Backward Info Msg Con Dialog

If enabled, an INFO message will only be sent after a confirmed dialog.

  • Disabled (default)
  • Enabled

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.

  • Disabled (default)
  • Enabled
Proxy Behavior For 18x When E2E Prack Enabled

Use this flag to enable End-To-End Prack Support on the SBC and receive a reliable 180 Message.

  • Disabled
  • Enabled (default)

Rel100Support

Enable to allow option tag 100rel support for the reliability of provisional messages as specified in RFC3262.

  • Disabled
  • Enabled (default)

NOTE: The SBC gives precedence to SIP Adaptive Transparency Profile over this flag.

Sdp 100rel Iwk For Prack

Enable this flag to support asymmetric PRACK interworking for late media calls.

  • Disabled (default)
  • Enabled

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.

  • Disabled (default)
  • Enabled

Privacy Param Restricted

Use this object to define SIP Privacy header parameter mapping (incoming to outgoing call).
  • Default – (default) Map Privacy header parameters, id or user to “restrict”.
  • Idonly – Only map Privacy header parameter id to “restrict”.
Relay Non Invite requestEnable this flag to relay out-of-dialog non-INVITE requests.
  • Disabled (default)

  • 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.

Local OODRefer Support

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.

  • Disabled (default)

  • Enabled

Treat Port Zero as No Audio

Use this flag to control how the audio portion of a call on port 0 is treated.

  • Disabled (default) – Audio on port 0 is treated as on hold. The audio towards egress is sent out on a valid port, and the direction is set as inactive. Calls without audio m-lines are supported.
  • Enabled – Audio on port 0 is treated as 'audioless'. The audio towards egress is sent out on port 0. Calls without audio m-lines are supported.

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.

Relay Updatewith SDP

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).

  • Disabled (default)
  • Enabled

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.

  • None (default)
  • SIP
  • Tel

Strict Parse

Enable this flag to reject requests which are understandable, but violate a relevant RFC Augmented Backus-Naur Form (ABNF) production rule.

  • Disabled (default)
  • Enabled

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.

  • Disabled (default) 
  • Enabled

Process Tgrp Context

Use this flag to determine "tgrp" parameter behavior.

  • Disabled (default) – If "tgrp" and "trunk-context" are present in the Request URI, Route header or 3xx is processed by the PSX depending on the PSX flag setting to process the tgrp parameters.
  • Enabled – If "trunk-context" is present in the Request URI, Route header or 3xx is checked against the SBC address. If they match, "tgrp" must be used for routing. Otherwise, "tgrp" and "trunk-context" are relayed to the peer in the subsequent INVITE message.
Isub Param PreferenceThis trunk group attribute specifies how the ISDN Sub-Address parameter is handled.
  • Nonstandard – When receiving, treat the percentage character (%) as an escape character. When sending, do not include characters not allowed by certain proxies.
  • Rfc2806 (default) – Use for default behavior when handling ISUB parameter.
  • Rfc3966 – Encode/decode the ISUB parameter based on the ABNF for ISUB specified in RFC3966.
Variant TypeSpecifies the SIP variant type.
  • Mgcf - based on the 3GPP 29.163 specification 
  • Q1912 - based on the Q1912.5 specification 
  • Sonus (default) - (default) based on RFC 3261 and RFC 3398 
  • Ttc - based on the JJ90.30 specification (refer to JJ90.30 Support from TTC Variant Type for more information)
  • Uk - based on the ND1017 specification
Factor ValueEnter 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 

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".

  • Disabled (default)
  • Enabled
Local Number Support

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.

  • Disabled (default)
  • Enabled
Disable Term IOIFor PcscfEnable this flag to prevent the P-CSCF from adding an “erm-ioi” parameter to any requests while creating a P-Charging-Vector (PCV) header.
  • Disabled (default)
  • Enabled
De Reg Parent With Child Dereg

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).

  • Disabled (default)
  • Enabled
Use PSXRoute As Req URI in RegEnable this flag to allow the P-CSCF to use the PSX-returned route as the Request URI in the REGISTER.
  • Disabled (default)
  • Enabled
PSX Route For SubscribeEnable this flag to use PSX routes for routing OOD (Out-Of-Dialog) methods to registered users.
  • Disabled (default)
  • Enabled
Default Calling Party NumberSpecifies 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

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.

  • Disabled
  • Enabled (default)

NOTE: For surrogate registered users, set this flag to Disabled.

Source Address Validation

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

Cond Inc Meth in Allow Hdr

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).

  • Disabled (default)
  • Enabled
Flexible Policy Adapter Profile

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.

NOTE:  Flexible Policy is not supported on ERE and is intended for use with an external PSX only.


SIP Filter ProfileThe 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.
Delay 18x SDP Answer

When this flag is enabled, the SBC will delay early media answers to the originating endpoint until RTP packets are detected from answering endpoints. Once the SBC detects RTP packets, it will forward the 183 SDP response toward the endpoints.

  • Disabled (default)
  • Enabled

Modified: for 12.1.4



NNI ProfileThe 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 ProfileThe 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

Enable this flag to accept History-Info headers received on the ingress trunk group.

  • Disabled (default)
  • Enabled
Egress Call ID Static StringString 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

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.

  • Disabled (default)
  • Enabled
Enforce TLS if Sips URI Scheme

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.

  • Disabled – (default) If flag is disabled at the AS side, the SBC uses the SIP URI scheme. If disabled at the IAD side, the SBC sets the URI scheme of any header using sips:, as SIPS. 
  • Enabled – If flag is enabled at the AS side, the SBC enforces the use of TLS for egressing any dialog initiating request if the incoming request has the SIPS URI scheme in either the Request-Uri or the top-most non-NBS Route header. If enabled at the IAD side, the SBC sets the URI scheme of any header using sips, as SIPS.
Enforce Sips if Egress is TLS

Enable this flag to change the URI scheme as described below.

  • Disabled – (default) If the flag is disabled at the AS side, the SBC uses the SIP URI scheme. If disabled at the IAD side, the SBC sets the URI scheme of any header using sips:, as SIPS.
  • Enabled – If the flag is enabled at the AS side, the SBC enforces the SIPS URI scheme in the Request-Uri and Contact header if the request is egressed using TLS as transport. If enabled at the IAD side, the SBC sets the URI scheme of any header using sips, as SIPS.
TLS Peer Name

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 the parameter, Peer Name Verify, under the TLS Profile object otherwise the parameter TLS Peer Name will be ignored. Once enabled, retain the parameter, Auth Client, in the default state (True) for future configurations. For more information on TLS Profile, refer to Security Configuration - TLS Profile.
  • The parameter TLS Peer Name is applicable only while creating or copying a SIP trunk group, and not while editing.
  • You cannot include multiple TLS peer names by using regular expression patterns or wildcard expressions.
Use PSX Route For Emergency Call

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.

  • Disabled (default)
  • Enabled
OCS Support

Use this feature to enable/disable OCS (Office Communications Server) support that controls the relaying of Computer-Supported Telecommunications Application (CSTA) invites.

Enable this flag to enable OCS (Office Communications Server) support.

  • Disabled – (default) CSTA INVITEs are rejected with a 415 “Unsupported Media Type” error message.
  • Enabled – Relays CSTA INVITEs to the far side.


Note

The SBC does not support Lync/Skype.


Relay Replaces HeaderWhen enabled, the P-CSCF relays Replaces headers with INVITEs.
  • Disabled (default) – Process INVITEs locally.
  • Enabled – Translate the dialog identifier and relay the Replaces header in an INVITE.
Feid for PDCSThe 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

Enable this flag to pass the SDP information to PSX (excluding data up to the first occurrence of m-line).

  • Disabled (default) 
  • Enabled

NOTE: This flag is not applicable when the SBC is configured for ERE.

Kpml Subscribe Mode

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.

  • Consume (default) – Use this option to consume a Subscribe message and trigger the KPML event for both In-Dialog and OOD Subscribe messages.
  • Relay – Use this option to relay the KPML Subscribe message for both In-Dialog and OOD Subscribe messages.

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.

set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 1 type message
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 1 message
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 1 message messageTypes request
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 1 message methodTypes [ invite ]
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 2 type header
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 2 header
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 2 header name Allow-Events
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 2 header condition absent
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 2 header hdrInstance all
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 criterion 2 header hdrRange undefined
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 type header
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 operation add
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 headerPosition last
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 from
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 from type value
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 from value presence,kpml
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 to
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 to type header
set profiles signaling sipAdaptorProfile add_Allow-Events rule 1 action 1 to value Allow-Events

For additional feature details, refer to DTMF and RTP Relay.

Use GAPwhen Rn Disabled

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.

  • Disabled (default)
  • 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.

Support199Option TagEnable this flag to include Option tags in Supported Headers for the 199 Extension.
  • Disabled (default)
  • Enabled
Keep Support

Enable this flag to support the keep-alive mechanism (RFC 6223).

  • Disabled (default)
  • Enabled
Outbound SupportEnable this flag to support outbound procedures specified in RFC 5626.
  • Disabled (default) 
  • Enabled
Silence Supp Treatment

Use this parameter to specify whether a call is transitioned to a fax or voice call when "silenceSupp:off" is received in re-INVITE.

  • Treat As Fax Transmission Indication (default) – Call is transitioned to a fax call.
  • Treat As G711 Silence Supp Off – If selected, the "a=silenceSupp:off" in the re-INVITE is interpreted as a request for a voice call with silenceSupp:off.

A call is considered a fax call when the Packet Service Profile Apply Fax Tone Treatment flag is enabled and either:

  • a=fax is received in the re-INVITE, or
  • G.711 "silenceSupp:off" is received in the re-INVITE, and the SIP Trunk Group signaling flag is set to Treat As Fax Transmission Indication.
Pem Interworking

Use this parameter to control how the PEM header is sent during Preconditions Interworking.

  • Send PEMBefore Ingress Preconditions (default) – The PEM header is sent in 183 and 200 OK responses to UPDATEs used for Ingress Preconditions Interworking.
  • Send PEMAfter Ingress Preconditions – The PEM header is not sent in 183 and 200 OK responses to UPDATEs used for Ingress Preconditions Interworking. The PEM header will be inserted in the next 18x and 200 OK to an UPDATE after Ingress Preconditions Interworking.
Rfc3261Validate CSeq In BYE

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).

  • Disabled (default)

  • Enabled

Rfc3261Validate Invite200Ok Retransmissions

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).

  • Disabled (default)

  • Enabled

Use Random User Info In Contact Hdr

Enable flag to use a randomly-generated value as UserInfo in the Contact header.

  • Disabled (default) 
  • Enabled
Suppress Non Route Invite Response

If enabled, response for non-route INVITE is suppressed.

  • Disabled (default) 
  • Enabled

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.

SIP Local Registrar

Use this flag to enable the SIP Local Registrar functionality. When enabled, the SBC routes the messages for the specific Trunk group to the SIP Registrar. For more information, refer to SIP Registrar Functionality.

  • Disabled (default)
  • Enabled
DNS Force Re Query

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.

  • Disabled (default)
  • Enabled
Use Pcfa Ccf

If enabled, the SBC uses the CCF received in PCFA as CDF.

  • Disabled (default) 
  • Enabled
Honor Maddr Param

Enable this flag to allow the SBC to process (and make routing decisions) the Maddr parameter present in the Contact header of incoming requests/responses or in Refer-To headers.

  • Disabled (default) - SBC does not perform any special processing for the Maddr parameter in SIP messages.
  • Enabled

The following behavior is supported with this feature:

  • When a Maddr is present in the received SIP request’s Contact header or in the Contact header of a 18x, 20x, and 3xx, the SBC uses it as the remote target.
  • When routing based on a Maddr value, the SBC uses the port information present in the received Contact (or Refer-To) header.
  • When routing based on a Maddr value, the SBC uses the transport parameter present in the Contact as the new request's transport.

NOTE: The SBC supports this feature even when the maddr value is IPv4, IPv6, or FQDN (resolving to either IPv4 or IPv6).

Rewrite Identities

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.

  • Disabled (default): When this parameter is disabled for an ingress trunk group, the SBC does not send originating and terminating identity URI information as separate fields in policy requests to PSX. As a result, originating and terminating identity URI information is not rewritten as per rules configured in PSX.
    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.
  • Enabled : When this parameter is enabled for an ingress trunk group, the SBC sends the originating and terminating identity URI information as separate fields in policy requesst to PSX. This originating and terminating identity URI information is rewritten as per rules configured in PSX and sent to the SBC in the policy response.

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.

Transit IOIUse 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 IOIUse 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

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. 

  • Disabled (default) 
  • Enabled

The SBC supports this feature when:

    • Only one Sip Sig Port is configured on egress.
    • The IP address of the Sip Sig Port is the same as the associated LIF IP.

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:

  • Ensure the flag Use Port Range Flag is disabled before performing a Live Software Upgrade (LSWU).
  • The SBC uses an independent media port range configured per IPTG. It also uses a new port from the system wide media port range if no independent media port range is configured per IPTG.
Store ICID

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. 

  • Disabled (default) 
  • Enabled
Clear TCP Connectionsfor Registration

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.

  • Disabled (default)
  • Enabled
Stop Lmsd Tone On Update

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.

  • Disabled (default)
  • Enabled

NOTE: The 180 ringing is sent only if the SBC has relayed the Alert-Info with a non-null URI.

Drop ISUP Mime Body

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.

  • Disabled (default)
  • Enabled
CPC Interworking for NNI

The flag CPC Interworking for NNI has two possible values:

  • Disabled (default)
  • Enabled

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.

Ai To Pem Interworking

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.

  • Disabled (default)
  • Enabled

NOTE: If applicable, use the Convert Alert To Progress flag to convert the '180 response' to a '183 session progress' towards the ingress.

Convert Alert To Progress

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.

  • Disabled (default)
  • Enabled
Rfc7732Validate Max ForwardsWhen 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 SupportIndicates 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

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.

Embedded Register Infoin User PartEnable 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.
  • Disabled (default)
  • Enabled
Allow Simultaneous 18x UPDATEtransaction

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.

  • Disabled (default)
  • Enabled
Honor Contact In Register for TLSCallsEnable 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.
  • Disabled (default) - Maintains the default SBC behavior to direct calls to the source IP address when the target user registered.
  • Enabled - Directs the call to the address the SBC stored from the Contact header that was part of the user's REGISTER request.

Prefer UpdateOver Re INVITE

Enable this flag on the ingress trunk group to allow the SBC to use UPDATE instead of re-INVITE to communicate SDP towards ingress, when the call is in the confirmed state.

  • Disabled
  • Enabled

Note:  This is not applicable when the dialog transparency flag or the updatedAnswerIn200Ok flag is in enabled state on the SBC.

Perform Precondition Renegotiation

Enable this flag on the ingress trunk group to allow the SBC 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. TheSBC supports this flag for SIP gateway-gateway call.

  • Disabled
  • Enabled

Note:

This is not applicable when the dialog transparency flag or the updatedAnswerIn200Ok flag is in enabled state on the SBC.
SIP JJ9030 Interworking Profile

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.

SIP XHeader 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.

Called Prefix Match Profile

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.

Only Send Subsequent 18x SDP If Unreliable

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

  • Disabled (default)
  • Enabled

For more information, refer to Ingress IP Attributes - Flags

Effective Relay Of Media Changes From Other Call Leg

Enable this option to configure the SBC to relay media changes when it detects any of the following in a new offer: 

    • A change in the data path mode
    • A change in the codec order compared to the most recent previous offer
    • A new codec was added
    • A codec was deleted


  • Disabled (default)
  • Enabled

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.

Do Not Auto Answer

Enable this flag to allow the SBC to queue the SDP offer and send it out once the previous procedure is complete.

  • Disabled (default)
  • Enabled
Send PAI URI To PSXEnable 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. 
  • Disabled (default)
  • Enabled

For more information, refer to Sending a No-Charge Notification to the Ingress Call Leg.

Prefer Ptime In SDPEnable 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.
  • Disabled (default)
  • Enabled
Relay Ptime Maxptime If Received

Enable this flag to relay the values received in a=ptime and/or a=maxptime in the outgoing SDP when they are received in the incoming SDP.

  • Disabled (default)
  • Enabled

Modified: for 12.1.4



Emg Call Bye Handle Leg Hold Time

Enter the "Emergency Call BYE Handling" duration, in seconds, for calls to remain active on the leg At the same time, the Emergency Call Server (ECS) obtains the location information for the calling carrier.

Range: 0-20.

  • 0 (Default) – The Emergency Call BYE Handling feature is not used.
  • <non zero> – The Emergency Call BYE Handling feature is applied for the configured leg hold duration.

For additional details, refer to Emergency Call Disconnection Behavior.

User to User Hdr Support

Use this configuration in conjunction with the  IPSP and  Trunk Group parameters.

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.

  • Disabled (default)
  • Recv
  • Send
  • Sendrecv

The SBC saves the UUI data of the User-to-User header when it is present in the initial Invite. The SBC saves the UUI data based upon the trunk group configuration "User to User Hdr Support" (userToUserHdrSupport) when it is set to "Recv" (recv) or "Send" (sendrecv). The SBC uses the UUI data stored on ingress along with the hard-coded parameters encoding=hex; purpose=isdn-uui.

The SBC uses the saved UUI data on the egress either to generate a User-To-User header or interwork depending upon the egress configuration. If the egress is SIP-I, the SBC adds the UUI data in the SIP-I MIME body. If the egress is SIP, the SBC creates the User-to-User header. 

Transparent relay of the User-to-User header is achieved using the "User to User Header"  (userToUserHeader) transparency flag. On the egress, the Transparency flag takes precedence over userToUserHdrSupport if both the flag is set.

Interaction with 'Map Uui In P-Sig-Info Header'

When "Map Uui In PSig Info Header" (mapUuiInPSigInfoHeader) is enabled, the UUI data present in the P-Sig-Info header is stored in the CPC structure. This can overwrite the UUI data being stored from the User-to-user header. The same interaction can occur at the egress level when creating P-SIG-info. 

Do not enable the mapUuiInPSigInfoHeader flag when the userToUserHdrSupport flag is set to "send" or "sendRecv."

Interaction with 'Ucid Support'

When "Ucid Support" (ucidSupport) is set to passthruOrGen, the SBC either generates a User-to-User header with the UCID present in the Ingress User-to-User header or creates a new UCID and attaches it to the User-to-User header.

Do not enable this ucidSupport when userToUserHdrSupport  is set to "send" or "sendRecv." If both of these flags are enabled, userToUserHdrSupport takes precedence. 

  • No labels