Page History

Access Class

Set parameter to

3GPP

to select GIBA security mechanism when a REGISTER message is received without specific security headers. The  SBC validates Source IP Address against Via header IP Address and transparently passes UEs Via header in egress messages towards network entities. If REGISTER message is received with "sec-agree" in Proxy-Require header along with Auth headers, and no IP Sec profile is configured, the

SBC rejects the message with "4xx Bad Extension" error response irrespective of the accessClass parameter value.

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.

• 3GPP  –  Select to enable GIBA security mechanism as explained above.
• none – (default) When selected, the SBC defaults to SIP Digest without TLS authentication.

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 after invalidation if 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 confirmed Dialog.

• Disabled (default)
• Enabled

ISUP Mime Body Relay

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.

• Disabled (default)
• Enabled

Rel100Support

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

• Disabled
• Enabled (default)

Enable this flag to support Asymmetric PRACK Interworking for late media calls.

• Disabled (default)
• Enabled

Pref Require Transparency

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.

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

• Disabled (default)

• Enabled

NOTE: Use Relay Non Invite Request flag for unregistered users only.

Use this flag to control how 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 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:

• 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 the relevant RFC Augmented Backus-Naur Form (ABNF) production rule.

• Disabled (default)
• Enabled

Skip DTGLookup For Route Hdr

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.

• 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 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) - ased on RFC 3261 and RFC 3398
• Ttc - reserved for future use
• 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 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.

• Disabled (default)
• Enabled

• Disabled (default)
• Enabled

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

• Disabled (default)
• Enabled

• Disabled (default)
• Enabled

• Disabled (default)
• Enabled

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.

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

• Disabled (default)
• Enabled

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 Flexible Policy Adapter Profile is provisioned both at the trunk group and zone levels, the trunk group’s profile takes precedence. If Input Adapter Profile is configured, it is applied first to manipulate the PDU and then 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.

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

• Disabled (default)
• Enabled

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.

• Disabled (default)
• Enabled

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.

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

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

• Disabled – (default) If flag is disabled at AS side, the SBC uses SIP URI scheme. If disabled at IAD side, the SBC sets the URI scheme of any header using sips:, as SIPS.
• Enabled – If flag is enabled at AS side, the SBC enforces SIPS URI scheme in Request-Uri and Contact Header if request is egressed using TLS as transport. If enabled at 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 TLS Profile object else, 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 for creating or copying a Sip Trunk Group, and not while editing a SIP Trunk Group.
• You cannot include multiple TLS Peer Names by using regular expression patterns or wildcard expressions.

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.

• Disabled (default)
• Enabled

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

• Disabled – Process INVITE locally.
• Enabled (default) – Translate dialog identifier and   relay Replaces header in INVITE.

Enable flag to pass the SDP information to the 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 "disableRn" in ipSignalingProfile 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 flag to support the keep-alive mechanism (RFC 6223).

• Disabled (default)
• Enabled

• Disabled (default) 
• Enabled

Use this parameter to specify whether call is transitioned to fax or voice call when "silenceSupp:off" 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 voice call with silenceSupp:off.

A call is considered a fax call when Packet Service Profile applyFaxToneTreatment flag is enabled and either:

• a=fax is received in the reInvite, or
• G.711 “silenceSupp:off” is received in the reInvite, and SIP Trunk Group signaling flag is set to

• “treatAsFaxTransmissionIndication”.

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

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

• Disabled (default)

• Enabled

Enable flag to use randomly-generated value as UserInfo in 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 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 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 Contact header of incoming requests/responses or in Refer-To header.

• Disabled (default) - SBC does not perform any special processing

• for Maddr parameter in SIP message.
  
• Enabled

The following behavior is supported with this feature:

• When Maddr is present in the received SIP request’s Contact Header or in the Contact header of 18x, 20x, and 3xx, the SBC uses it as the remote target.
• When routing based

• on Maddr value, the SBC uses the port information present in the received Contact (or Refer-To) header.
• When routing based

• on 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 maddr value is IPv4, IPv6, or FQDN (resolving to either IPv4 or IPv6).

Rewrite Identities when enabled (for both ingress and egress trunk group) achieve SIP URI transparency for SIP-URIs present in outbound SIP message.

• Disabled (default): When this parameter is disabled for ingress trunk group, the SBC does not send originating and terminating identities URI information as separate fields in policy request to PSX. As the result, originating and terminating identities URI information is not rewritten as per rules configured in PSX.
  
  When this parameter is disabled for egress trunk group, the SBC does not update the originating and terminating identities in outbound SIP message as per policy response from PSX.

• Enabled : When this parameter is enabled for ingress trunk group, the SBC sends the originating and terminating identities URI information as separate fields in policy request to PSX. These originating and terminating identities URI information is rewritten as per rules configured in PSX and sent to the SBC in policy response.

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.

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:

• Disabled (default) 
• Enabled

The SBC supports this feature when:

• • Only

• • one Sip Sig Port is configured on egress.
  • IP address of 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 the Live Software Upgrade (LSWU).
• The SBC uses 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 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.

• Disabled (default)
• Enabled

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.

• Disabled (default)
• Enabled

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.

• Disabled (default)
• Enabled

The flag CPC Interworking for NNI has two possible values:

• Disabled (default)
• Enabled

To start CPC (Calling Part Category) Interworking for NNI, set this flag to Enabled. When set to Enabled, the SBC populates the parameter Calling Party Category (CPC) with the value 11, on receiving the Resource Priority Header (RPH) in the initial INVITE. Here, the value 11 denotes "Calling Subscriber with priority". When RPH is absent in the initial INVITE, SBC populates the parameter CPC from the PAI Header.

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