Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Use this object to specify parameters controlling the specifics of SIP signaling for this SIP trunk group.

To View and Edit Signaling

On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Trunk Group > Sip Trunk Group > Signaling. The Signaling window is displayed.

The Signaling can be checked for each Address Context, for each Zone, for each Sip Trunk Group created or for all the Address Contexts, Zones and Sip Trunk Groups created. Use the drop-down box to select the desired Address Context, Zone and Sip Trunk Group.

The Edit Signaling window is displayed.

Figure : Sip Trunk Group - Signaling

 

The following fields are displayed:

Table : Sip Trunk Group - Signaling parameters

Parameter

Description

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 SBCrejects 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,  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, 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.

  • noValidation (default)

  • sipI – Route validation on received messages for SIP-I.

  • sipOnly – 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 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)

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

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 non-Invite requests.
  • Disabled (default)
  • Enabled

Use relayNonInviteRequest flag for unregistered users only.

Treat Port Zero Has No Audio

Availability: Since 5.0.1

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.

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 audioless behavior.

Relay Updatewith Sdp

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

Enables 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. Otherwsie, "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 in SIP.
  • 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
  • q1912
  • sonus
  • ttc
  • uk
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.
Local Number Support

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
Disable Term IOIFor PcscfEnable this flag to prevent P-CSCF from adding   “erm-ioi” parameter to any requests while creating P-Charging-Vector (PCV)   header.
  • Disabled (default)
  • Enabled
De Reg Parent With Child Dereg

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
Use PSXRoute As Req Uri in RegEnable this flag to allow 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 Caller Privacy feature. If the party number is configured and the flag msLyncPrivacySupport is enabled, the configured number is inserted as the user name of either the from header or the P-Asserted-Identity fields depending on the configuration. The value ranges up to 23 characters.
Validate Aor

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 SBC as part of RCB created during initial registration are allowed.

  • Disabled
  • Enabled (default)

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 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
Accept History Info

Enable this flag to accept History-Info header 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 SBC.
Allow Bye Challenge

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
Enforce Tls if Sips Uri Scheme

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,  SBC uses SIP URI scheme.If disabled at IAD side,  SBC sets the URI scheme of any   header using sips:, as SIPS. 
  • Enabled – If flag is enabled at AS side,  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,  SBC sets 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 flag is disabled at AS side,  SBC uses SIP URI scheme. If disabled at IAD side,  SBC sets the URI scheme of any header using sips:, as SIPS.
  • Enabled – If flag is enabled at AS side,  SBC enforces SIPS URI scheme in Request-Uri and Contact Header if request is egressed using TLS as transport. If enabled at IAD side,  SBC sets the URI scheme of any header using sips, as SIPS.
Use Psx Route For Emergency Call

Enable this flag to allow  SBC to use PSX returned Route instead of stored-service route information for processing Emergency calls from Registered users.

  • Disabled (default)
  • Enabled
Ocs SupportEnable this flag to enable OCS (Office Communications Server, a.k.a MS Lync) support.
  • Disabled – (default) CSTA invites are rejected with 415 “Unsupported Media Type” error message.
  • Enabled – Relays CSTA invites to the far side.
Relay Replaces HeaderWhen enabled, P-CSCF relays Replaces header  with INVITE.
  • Disabled – Process INVITE locally.
  • Enabled (default) – Translate dialog identifier and   relay Replaces header in INVITE.
Feid for PDCSThe FEID value sent out in egress PDCS-Billing-Info header when sendiing JIP value in PDCS header. FEID consists of hexadecimal string of up to 16 characters followed by a domain name (for example, abc1234@98.245.153.111). The value ranges up to 127 characters.
Send Sdp to Psx

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

  • Disabled (default) 
  • Enabled

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


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 "disableRn" in ipSignalingProfile is enabled.

  • Disabled (default)  
  • Enabled

If this flag is disabled and “disableRn” is enabled (egressIpAttributes (SIP) flag), the SBC populates the routing number (rn) in the R-URI and the To headers.  


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

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

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

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

  • treatAsFaxTransmissionIndication (default) – Call is transitioned to a fax call.
  • treatAsG711SilenceSuppOff – 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”.
Rfc3261Validate CSeq In BYE

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

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

Use Random User Info In Contact Hdr

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

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

If enabled, response for non-route invite is suppressed. The options are:

  • Disabled (default) 
  • Enabled

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.


Use Pcfa Ccf

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

  • Disabled (default) 
  • Enabled
Honor Maddr Param

Availability: Since 5.0.1

Enable this flag to allow 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, SBC uses it as the remote target.
  • When routing based on Maddr value, SBC uses the port information present in the received Contact (or Refer-To) header.
  • When routing based on Maddr value, SBC uses the transport parameter present in the Contact as the new request's transport.

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


Rewrite Identities

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, 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, 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, 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 SBC in policy response.

When this parameter is enabled, for egress trunk group, SBC updates the originating and terminating identities in outbound SIP message as per policy response from PSX.

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. (see P-Charging-Vector Header for additional details)
Use Port Range Flag

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

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 flag Pass Complete Contact 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.

The flag, Use Port Range Flag, should be disabled before performing the Live Software Upgrade (LSWU).

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.


Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

 

 

  • No labels