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

Compare with Current View Page History

« Previous Version 43 Next »

In this section:

New CLI in 8.2.0R0

Info

Default values are enclosed in square brackets [ ].

SBX-75174 - Generate or Replace SSRC Values for Calls Toward a Kandy Link WebRTC Gateway

The synchronization source (SSRC) identifier uniquely identifies media streams within an RTP session and is included in SDP signaling when establishing or modifying media sessions. The WebRTC specification requires that the SSRC value in an RTP stream match the SSRC sent in the SDP. However some endpoints, such as PSTN gateways, are not capable of generating SSRC values so they are not present in the SDP. Other endpoints change the SSRC during call hold/resume scenarios. The SBC provides two flag parameters to the Packet Service profile to determine whether the SBC generates and updates the SSRC and related attributes.

Command Syntax

The SBC adds the following two flags to the Packet Service profile. 

% set profiles media packetServiceProfile <profile name> flags
      generateAndSignalSSRCAndCname <disabled | enabled>
      allowMidCallSSRCModification <disabled | enabled>

The SBC only allows mid-call modifications to the SSRC if it is generating the SSRC. Therefore, the first parameter, generateAndSignalSSRCAndCname, must be enabled for the second parameter, allowMidCallSSRCModification, to become available.

Command Parameters

ParameterDescription

generateAndSignalSSRCAndCname

Enable this flag to generate an SSRC value and associated attributes and include them in SDP signaling and RTP/RTCP streams. Options are:

  • disabled (default)
  • enabled

Note: This flag takes precedence over the Packet Service Profile ssrcRandomize flag.

allowMidCallSSRCModification

Enable this flag so that in call hold/resume scenarios the SBC modifies the SSRC and associated attributes after the call resumes. The SBC sends both the previous and updated SSRC in SDP signaling and includes the new SSRC iin RTP/RTCP streams. Options are:

  • disabled (default)
  • enabled

Note: You must enable the generateAndSignalSSRCAndCname flag before you can enable this flag.

Note: If you enable the IP Signaling profile common IP attributes flag minimizeRelayingOfMediaChangesFromOtherCallLegAll, you must also enable the relayDataPathModeChangeFromOtherCallLeg flag to have the SSRC modification processing take effect.

SBX-86768 SBC Should Create TLS Connection Based on Contact Header

The SBC provides the following new SIP trunk group parameter to specify whether to use the Contact header information instead of the source IP address when routing a call to an access user over TLS transport. 

Command Syntax

 

% set addressContext <address context>  zone <zone> sipTrunkGroup <trunk group name> signaling honorContactInRegisterForTLSCalls <disabled | enabled>

 

Command Parameters

Parameter
Description

honorContactInRegisterForTLSCalls

Use this flag to specify where the SBC directs access calls from the internal network to users in the access network when the call is over TLS transport. The options are:

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

SBX-88542 Prefix-based TG Selection using SMM

The SBC adds support for using  SIP Message Manipulation (SMM) to enable secondary selection of an ingress trunk group. This processing requires two new SMM operations and SIP Param Based Action profiles.

Command Syntax

The following new operations are supported in SMM sipAdaptorProfiles.

%  set profiles signaling sipAdaptorProfile <profileName> rule <rule index> action <action index> operation 
        storeSipParam
        storeProfileName

The SIP Param Based Action profile is supported.

%   set profiles signaling sipParamBasedActionProfile <profileName> 
          action <none | selectTG>
          entry <0 to 2056>
             trunkGroupName <trunk group name>
             matchType 
               full 
                 param <parameter value>
               none
               range 
                 rangeEnd <end of parameter range>
                 rangeStart <start of parameter range>
               regexp
                 paramRegexp <regular expression>

Command Parameters

The following table describes the new SMM operations.

ParameterDescription

storeSipParam

SMM operation that extracts a specified value (header, parameter, token) from the incoming SIP message to compare to mapping defined in a sipParamBasedActionProfile in order to select a new ingress trunk group.

storeProfileName

SMM operation that stores the name of a sipParamBasedActionProfile to use in selecting a new ingress trunk group.


The following table describes the parameters in the sipParamBasedActionProfile.

ParameterLength/RangeDescription

sipParamBasedActionProfile
<profileName>

up to 23 characters

Name for the sipParamBasedActionProfile.

action

n/a

Action to be performed by the sipParamBasedActionProfile. Options are:

  • none (default)
  • selectTG

entry

0 to 2056Index value for the entry. A sipParamBasedActionProfile can contain a maximum of 2056 entries.

trunkGroupName

up to 23 charactersThe name of the trunk group to set as the new ingress trunk group if the corresponding entry matches the value extracted with the SMM storeSipParam operation.

matchType

n/a

Type of matching to use when comparing the value extracted with the SMM storeSipParam operation with the corresponding entry. Options are:

  • full - compare against the list of param values defined for the entry. The extracted value must match exactly.
  • none - (default) matching is not done.
  • range - compare against a defined range. The extracted value must be within the range to match.
  • regexp - compare against a defined regular expression. The extracted value must match the regular expression.

param

up to 128 charactersParameter value to compare against when matchType is full. More than one param value can be defined for an entry when matchType is full.

rangeEnd

up to 128 charactersEnding value for a range to compare against when matchType is range.

rangeStart

up to 128 charactersStarting value for a range to compare against when matchType is range.

paramRegexp

up to 128 charactersRegular expression to compare against when the matchType is regexp.

SBX-88601 SMM: Support Global Configuration

The SBC adds support for applying SIP message manipulation (SMM) profiles (SIP adaptor profiles) at both the global and address context levels and options that control how to execute profiles when they are specified at more than one level.

Command Syntax

Global

The following new options specify the names of SIP adaptor profiles to apply at the global level.

% set global signaling messageManipulation
      inputAdapterProfile <profile name>
      outputAdapterProfile <profile name>
Address Context

The following new options specify the names of SIP adaptor profiles to apply to sessions within a specified address context..

% set addressContext <address context> signaling messageManipulation
      inputAdapterProfile <profile name>
      outputAdapterProfile <profile name>
SIP Trunk Group

The following new options specify whether or not to use fixed order execution when multiple SMM profiles apply to a session. When fixed order execution is enabled, you can also specify which of the four profile types to enable and therefore include in SMM processing.

% set addressContext <address context>  zone <zone> sipTrunkGroup <trunk group name> signaling messageManipulation smmProfileExecution 
      none
      fixedOrder 
         addressContext acState <disable | enable>
         global globalState <disable | enable> 
         iptg iptgState <disable | enable>  
         zone zoneState <disable | enable>

Command Parameters

Global
ParameterLength/RangeDescription

inputAdapterProfile

0-23 characters

<profile name> – Enter the name of a SIP adaptor profile to use globally on inbound messages.

outputAdapterProfile

0-23 characters<profile name> – Enter the name of a SIP adaptor profile to use globally on outbound messages.
Address Context
ParameterLength/RangeDescription

inputAdapterProfile

0-23 characters

<profile name> – Enter the name of a SIP adaptor profile to use for the address context on inbound messages.

outputAdapterProfile

0-23 characters<profile name> – Enter the name of a SIP adaptor profile to use for the address context on outbound messages.
SIP Trunk Group
ParameterDescription

smmProfileExecution

Specifies whether or not to use fixed order processing when more than one SIP adaptor profile applies to messages in sessions associated with the specified SIP trunk group. The options are:

  • fixedOrder - the SBC logically concatenates the rules in all applicable profiles and executes them in the following order: global, address context, zone, SIP trunk group. Rules are treated as though they resided in a single profile and therefore variables set at the beginning of the sequence are accessible to rules that follow in the sequence. Selecting fixedOrder also enables configuring options for each specific level (global, address context, zone, SIP trunk group) to define whether or not to execute the profiles configured at that level. These options are described in the next four rows of this table.
  • none (default) - the SBC does not execute multiple profiles for a session. If configured, the SIP adaptor profile configured for the SIP trunk group takes precedence. If no profile is assigned to the trunk group the SBC executes the zone-level profile.

addressContext acState

Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the address context level on messages in sessions associated with the specified SIP trunk group. The options are:

  • disabled - the address-context-level profiles are not applied.
  • enabled (default) - the address-context-level profiles are applied.

This option is only available after you set smmProfileExecution to fixedOrder.

global globalState

Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the global level on messages in sessions associated with the specified SIP trunk group. The options are:

  • disabled - the global-level profiles are not applied.
  • enabled (default) - the global-level profiles are applied.

This option is only available after you set smmProfileExecution to fixedOrder.

iptg iptgState

Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the SIP trunk group level on messages in sessions associated with the specified SIP trunk group. The options are:

  • disabled - the trunk-group-level profiles are not applied.
  • enabled (default) - the trunk-group-level profiles are applied.

This option is only available after you set smmProfileExecution to fixedOrder.

zone zoneState

Specifies whether the SBC executes the rules in the SIP adaptor profiles assigned at the zone level on messages in sessions associated with the specified SIP trunk group. The options are:

  • disabled - the zone-level profiles are not applied.
  • enabled (default) - the zone-level profiles are applied.

This option is only available after you set smmProfileExecution to fixedOrder.


Deprecated CLI

 

CLI GOES HERE

  • No labels