Page History

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

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

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.

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

• Default – (default) Map Privacy header parameters,

• id or user to “restrict”.
• Idonly – Only map Privacy header parameter

• id to “restrict”.

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

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.

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:

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

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

• 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

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

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

• Disabled (default)
• Enabled

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

• Disabled (default)
• Enabled

• Disabled (default)
• Enabled

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.

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

• Disabled (default)
• Enabled

Enable this flag to accept History-Info

headers received on the ingress trunk group.

• Disabled (default)
• Enabled

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

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.

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.

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.

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

• Disabled – (default) CSTA

• INVITEs are rejected with a 415 “Unsupported Media Type” error message.
• Enabled – Relays CSTA

• INVITEs to the far side.

• Disabled (default) – Process

• INVITEs locally.
• Enabled

• – Translate the dialog identifier and

• relay the Replaces header in an INVITE.

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.

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.

• Disabled (default)
• Enabled

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

• Disabled (default)
• Enabled

• Disabled (default) 
• Enabled

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

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

• ReINVITE, or
• G.711

• "silenceSupp:

• off" is received in the

• ReINVITE, and the SIP Trunk Group signaling flag is set to

• Treat As Fax Transmission Indication.

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.

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

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

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

• Disabled (default) 
• Enabled

If

enabled, response for non-route

INVITE is suppressed. The options are:

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

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

If enabled, the SBC uses the CCF received in PCFA as CDF. The options are:

• Disabled (default) 
• Enabled

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

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.

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:

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

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:

• Disabled (default) 
• Enabled

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

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.


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

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.

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.

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:

• Disabled (default)
• Enabled

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.

• Disabled (default)
• Enabled

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

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 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 behaviour as releases prior to 8.2.0

The options include:

• Disabled (default)
• Enabled
  For more information, refer to Ingress Ip Attributes - Flags