CLI Changes in This Release

New CLI in 8.2.0R0

SBX-70938 RTCP for T.140 Pass-through

Command Syntax

% set system media mediaRtcpControl t140RtcpMonitorInterval 6

% set profiles media packetServiceProfile DEFAULT rtcpOptions generateRtcpForT140IfNotReceivedFromOtherLeg enable

Command Parameters

SBX-75865 Alarm Generation when SBC Receives RCODE Except for 0

Command Syntax

The rcodeErrorMonitorTimer parameter is added to the DNSGroup configuration to support monitoring timer interval which the 

% set addressContext <address_context_name> dnsGroup <dnsgroup> rcodeErrorMonitorTimer <rcode_error_monitor_timer>

Command Parameters

SBX-76610 Selection Feature for ARS Recovery Algorithm

The following is the full syntax to create a SIP ARS profile, including the new recoveryAlgForTimeouts and recoveryAlgForNoRetryAfter options and their parameters for selecting the ARS recovery algorithm for each blacklist algorithm.

 set profiles services sipArsProfile <Profile Name> recoveryAlgForTimeouts < probe | timer | none >

 set profiles services sipArsProfile <Profile Name> recoveryAlgForNoRetryAfter < probe | timer | none >

% set profiles services sipArsProfile <profile name>
   blkListAlgRetryAfterType sip-503
   blkListAlgTimeoutsDuration <1-3600>
   blkListAlgTimeoutsNumTimeouts <1-3600>
   blkListAlgTimeoutsType sip-invite
   blkListAlgorithms <retryafter | timeouts | noRetryAfer>
   blkListAlgNoRetryAfterNum503 <1-3600>
   blkListAlgNoRetryAfterDuration <1-3600>
   failureResponseCodes <400-699 | all |all4xx | all5xx | all6xx>
   midDialogArsScreenLevel <always | never | onlyIfNotBlackListDueto503>
   recoveryAlgProbeDuration <1-3600>
   recoveryAlgProbeInterval <1-600>
   recoveryAlgProbeMethod sip-options
   recoveryAlgProbeNumResponses <1-32>
   recoveryAlgTimerDuration <1-3600>
   recoveryAlgorithm <probe|timer>
   recoveryAlgForTimeouts <probe|timer|none>
   recoveryAlgForNoRetryAfter <probe|timer|none>

Command Parameters

SBX-85716  Re-initiate Pre-condition Negotiation Towards Ingress

Two new parameters are added to SIP trunk group signaling and are shown in the context of the complete command syntax.

• performPrecondtionRenegotiation: to re-initiate precondition procedure when the 
  Unable to show "metadata-from": No such page "_space_variables"
  changes the ingress side SDP due to 18x/200 OK or UPDATE received from the egress side.
• preferUPDATEOverReINVITE: to use UPDATE instead of Re-INVITE on the ingress to communicate SDP, when the call goes to the confirmed state.

Command Syntax

% set addressContext default zone <zone_name> sipTrunkGroup <siptrunkgroup_name> signaling preferUPDATEOverReINVITE <enabled | disabled>

% set addressContext default zone <zone_name> sipTrunkGroup <siptrunkgroup_ingress_name> signaling performPrecondtionRenegotiation 
<enabled | disabled>

Command Parameters

SIP Trunk Group - Signaling - CLI

SIP TG - Signaling - Prefer UPDATE Over ReINVITE - CLI

SIP TG - Signaling - Perform Precondtion Renegotiation - CLI

SBX-86658 Offer-Answer Timer Configuration

Command Syntax

A new configurable object,  offerAnswerTimer, is added under Trunk Group signaling timers.

% set global signaling sipSigControls offerAnswerTimer 
Possible completions:
<Enter offer answer timer value in range of (10..300) in seconds.> (20):

Command Parameters

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

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

Command Parameters

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.

The following table describes the parameters in the sipParamBasedActionProfile.

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

Address Context

SIP Trunk Group

SBX-67554 LCQ CC/SIP Issue - Multiple Call Transfer - SIP Layer Stops Responding

The SBC is enhanced with the parameter maxNumTransfers under the object global signaling.

Command Syntax

To configure maxNumTransfers, use the following syntax:

% set global signaling maxNumTransfers <10-100>

Command Parameters

Configuration Examples

To configure maxNumTransfers, use the following example:

% set global signaling maxNumTransfers 30

To display the maxNumTransfers, use the following example:

• In the "configure" mode:

  % show global signaling maxNumTransfers
  maxNumTransfers 30

• In the "display" mode (when you exit the "configure" mode):

  > show table global signaling
  maxNumTransfers 30;
  messageManipulation {
      inputAdapterProfile  DD1;
      outputAdapterProfile DD1;
  }
  sipPeerOverloadControl {
      samplingPeriod  2;
      discardPeriod   2;
      stepDownGain    100;
      rejectThreshold 1;
  }
  sipSigControls {
      registrarSupportContactParam enabled;
      maxPduSizeValue              pdusize15kb;
  }
  
  

SBX-41671 TTY/TDD Interworking Support for RFC-4103 and/or RFC-4351

Parameter generateRtcpForT140IfNotReceivedFromOtherLeg

The parameter generateRtcpForT140IfNotReceivedFromOtherLeg is added to packetServiceProfile rtcpOptions rtcp. When the parameter is set to enable, the SBC generates RTCP for T140 media streams if RTCP is not received from peer.

Command Syntax

To configure the parameter generateRtcpForT140IfNotReceivedFromOtherLeg, use the following syntax:

set profiles media packetServiceProfile <packetServiceProfile_name: INGRESS>
	rtcpOptions 
		rtcp <disable | enable> 
			generateRtcpForT140IfNotReceivedFromOtherLeg <disable | enable>

Command Parameters

Configuration Examples

To configure the SBC to generate RTCP for T140 media streams if it does not receive RTCP from peer, refer to the following example:

% set profiles media packetServiceProfile INGRESS rtcpOptions rtcp enable generateRtcpForT140IfNotReceivedFromOtherLeg enable
% commit

% set profiles media packetServiceProfile INGRESS flags t140Call enable
% commit

% set profiles media packetServiceProfile INGRESS qosValues t140Dscp 63
% commit

Statistics

• The following statistics are added to the results of the command show <status | table> system dspStatus dspUsage:
  • amrNbT140Total
  • amrNbT140Utilization
  • amrWbT140Total

  • amrWbT140Utilization

    Note

    The results of the command show table system dspStatus dspUsage is similar to that of the command show status system dspStatus dspUsage, but in a tabular format.

    In the following example, only the results of the command show status system dspStatus dspUsage is shown.

     

    Statistics Description

    dspUsage statistics

    Statistics	Description
    amrNbT140Total	Total AMR-NB with T.140 resource capacity on this server.
    amrNbT140Utilization	Percentage utilization of AMR-NB with T.140 resources on this server.
    amrWbT140Total	Total AMR-WB with T.140 resource capacity on this server.
    amrWbT140Utilization	Percentage utilization of AMR-WB with T.140 resources on this server.

    
    Example

    Click to display example...

    admin@SBC> show status system dspStatus dspUsage
    dspUsage SBC-SA {
    	<... other statistics ...>
    	amrNbT140Total          700;
    	amrNbT140Utilization    0;
    	<... other statistics ...>
    	amrWbT140Total          1062;
    	amrWbT140Utilization    0;
    	<... other statistics ...>
    }
    [ok][<YYYY-MM-DD> <HH:MM:SS>]
    
    

    
    

• The following statistics are added to the results of the command show <status | table> system dspRes <dspUsageCurrentStatistics | dspUsageIntervalStatistics>:
  • amrWithT140PeakUsedCount
  • amrWithT140AverageUsedCount
  • amrWithT140AverageAvailCount
  • amrwbWithT140PeakUsedCount
  • amrwbWithT140AverageUsedCount

  • amrwbWithT140AverageAvailCount

    Note

    The results of the command show table system dspRes is similar to that of the command show status system dspRes, but in a tabular format.

    In the following example, only the results of the command show status system dspRes is shown.

    
    Statistics Description

    dspUsage current and interval statistics

    Statistics	Description
    amrWithT140PeakUsedCount	The current peak usage of type AMR with T.140 DSP PAD.
    amrWithT140AverageUsedCount	The current average usage of type AMR with T.140 DSP PAD.
    amrWithT140AverageAvailCount	The current average availability of type AMR with T.140 DSP PAD.
    amrwbWithT140PeakUsedCount	The current peak usage of type AMR-WB with T.140 DSP PAD.
    amrwbWithT140AverageUsedCount	The current average usage of type AMR-WB with T.140 DSP PAD.
    amrwbWithT140AverageAvailCount	The current average availability of type AMR-WB with T.140 DSP PAD.

    
    
    Example

    Click to display "dspUsageCurrentStatistics" example...

    admin@SBC> show status system dspRes dspUsageCurrentStatistics
    dspUsageCurrentStatistics SBC-SA {
    	<... other statistics ...>
    	amrWithT140PeakUsedCount        0;
        amrWithT140AverageUsedCount     0;
        amrWithT140AverageAvailCount    700;
        <... other statistics ...>
    	amrwbWithT140PeakUsedCount      0;
        amrwbWithT140AverageUsedCount   0;
        amrwbWithT140AverageAvailCount  1062;
    	<... other statistics ...>
    }
    
    

    Click to display "dspUsageIntervalStatistics" example...

    admin@SBC> show status system dspRes dspUsageIntervalStatistics
    dspUsageIntervalStatistics 268 SBC-SA {
    	<... other statistics ...>
    	amrWithT140PeakUsedCount        0;
        amrWithT140AverageUsedCount     0;
        amrWithT140AverageAvailCount    700;
        <... other statistics ...>
    	amrwbWithT140PeakUsedCount      0;
        amrwbWithT140AverageUsedCount   0;
        amrwbWithT140AverageAvailCount  1062;
    	<... other statistics ...>
    }
    
    

SBX-70005 Relay Changes in PAID as per RFC-5876

A new Services profile, sipAdaptiveTransparencyProfile, is added to configure SIP header transparency for P-ASSERTED-IDENTITY.

Under sipAdaptiveTransparencyProfile, the following parameters are added:

• sipMethod
• sipResponse
• state
• triggerHeader
• action
• trigger

Command Syntax

% set profiles services
	sipAdaptiveTransparencyProfile <profile_name>
		sipMethod <UPDATE | INVITE>
		sipResponse <180 | 183 | 200>
		state <disabled | enabled>
		triggerHeader <P-ASSERTED-ID>
			action new-value
			trigger value-change
		

Command Parameters

sipMethod

Configuration Examples

To configure SIP Adaptive Transparency Profile, execute the following steps:

1. Configure SIP Adaptive Transparency Profile with a SIP Method, or a SIP Response:

   • To configure a SIP Adaptive Transparency Profile with a SIP Method:

     % set profiles services sipAdaptiveTransparencyProfile TPforPAI sipMethod UPDATE triggerHeader P-ASSERTED-ID
     % commit
     

   • To configure a SIP Adaptive Transparency Profile with a SIP Response:

     % set profiles services sipAdaptiveTransparencyProfile TPforPAI sipResponse 200 triggerHeader P-ASSERTED-ID
     % commit
     

2. Enable the profile:

   % set profiles services sipAdaptiveTransparencyProfile TPforPAI state enabled
   % commit

3. Attach the configured SIP Adaptive Transparency Profile to the trunk group that sends the UPDATE request.

   % set addressContext default zone defaultSigZone sipTrunkGroup test_sip services sipAdaptiveTransparencyProfile TPforPAI
   % commit

   Tip

   To decide the Trunk Group to which the SIP Adaptive Transparency Profile is attached, consider the following example:

   A calls B and the call is connected. Suppose, A sends UPDATE request with changed PAI header. To configure the SBC to relay the UPDATE request to B, attach the profile to A's Trunk Group.

   Similarly, if B sends the UPDATE request that the SBC must relay to A, attach the profile with B's Trunk Group.

4. (Optional) Display the configured profile.

   admin@SBC% show profiles services sipAdaptiveTransparencyProfile
   sipAdaptiveTransparencyProfile TPforPAI {
       state disabled;
       sipMethod INVITE;
       sipMethod UPDATE {
           triggerHeader P-ASSERTED-ID;
       }
       sipResponse 180;
       sipResponse 200 {
           triggerHeader P-ASSERTED-ID;
       }
   }
   sipAdaptiveTransparencyProfile TPforPAI_2;
   [ok][<YYYY-MM-DD> <HH:MM:SS>]

   Alternatively, exit from the "configure" mode and display the profile in a tabular form.

   admin@SBC> show table profiles services sipAdaptiveTransparencyProfile
                         METHOD                                          RSP
   NAME        STATE     NAME    HDR NAME       TRIGGER       ACTION     CODE  HDR NAME       TRIGGER       ACTION
   --------------------------------------------------------------------------------------------------------------------
   TPforPAI    disabled  INVITE
                         UPDATE  P-ASSERTED-ID  value-change  new-value  180
                                                                         200   P-ASSERTED-ID  value-change  new-value
   TPforPAI_2  disabled
   [ok][<YYYY-MM-DD> <HH:MM:SS>]
   
   

SBX-85818 + SBX-85655 Support for SIP-ISUP

The CLI changes are as follows:

• The following profiles are added under the object profiles signaling:
  • calledPrefixMatchProfile
  • carrierCodeToIoiMappingProfile
  • ioiToCarrierCodeMappingProfile
  • sipJJ9030InterworkingProfile
    For information on the parameters associated with each of the profiles, see the sub-section Command Syntax.
• The following parameter is added under the object profiles signaling NNIProfile:
  • contractorNumInterworking
• The following profiles are added under the object addressContext zone sipTrunkGroup signaling:
  • calledPrefixMatchProfile
  • sipJJ9030InterworkingProfile

Command Syntax

To configure the signaling profile calledPrefixMatchProfile, use the following syntax:

% set profiles signaling
	calledPrefixMatchProfile <called_prefix_match_profile_name: 1-23 characters>
		prefixMatch 
			<stringPattern: 1-12 digits, 'X' or 'x' characters>
			<startPosition: 0-11>
			<digitLength: 1-30>

To configure the signaling profile carrierCodeToIoiMappingProfile, use the following syntax:

% set profiles signaling
	carrierCodeToIoiMappingProfile <carrier_code: 4 digits [0-9]>
		accessParam <class | type>
		accessValue <access_value_string: 1-64 characters>
		ioi <inter_operator_identifier_string: 1-128 characters>

To configure the signaling profile ioiToCarrierCodeMappingProfile, use the following syntax:

% set profiles signaling
	ioiToCarrierCodeMappingProfile <inter_operator_identifier_string: 1-128 characters>
		carrierCode <carrier_code: 4 digits [0-9]>

To configure the signaling profile sipJJ9030InterworkingProfile, use the following syntax:

% set profiles signaling
	sipJJ9030InterworkingProfile <sip_JJ9030_Interworking_Profile_name: 1-23 characters>
		addUserEqualPhoneforDivHiInterworking <disabled | enabled>
		bciCalledPartyCategory <noIndication | ordinary | payphone | spare>
		bciChargeIndicator <charge | noCharge | noIndication | spare>
		bciTerminatingIsdnAccess <isdn | nonIsdn>
		chargeAreaInformation <charge_area: 5 digits [0-9]>
		origIoi <originating_inter_operator_identifier_string: 1-128 characters>
		originatingCarrierCode <originating_carrier_code: 4 digits [0-9]>
		setHiPresentationRestricted <disabled | enabled>
		sipFlavor
			JJ9030
			SIP-T
			SIP-ttc-charging-params
		termIoi <terminating_inter_operator_identifier_string: 1-128 characters>

To configure the parameter contractorNumInterworking under the profile NNIProfile, use the following syntax:

% set profiles signaling NNIProfile <nni_profile_name>
	contractorNumInterworking <disabled | enabled>

To attach the signaling profiles calledPrefixMatchProfile and sipJJ9030InterworkingProfile with sipTrunkGroup, use the following syntax:

% set addressContext <address_context_name> zone <zone_name> sipTrunkGroup <SIP_TG_name> signaling
	calledPrefixMatchProfile <called_prefix_match_profile_name>
	sipJJ9030InterworkingProfile <sip_JJ9030_interworking_profile_name>

Command Parameters

The parameter descriptions for profiles signaling calledPrefixMatchProfile are as follows:

The parameter descriptions for profiles signaling carrierCodeToIoiMappingProfile are as follows:

The parameter descriptions for profiles signaling ioiToCarrierCodeMappingProfile are as follows:

The parameter descriptions for profiles signaling sipJJ9030InterworkingProfile are as follows:

The descriptions for new parameters under profiles signaling NNIProfile are as follows:

The descriptions for new parameters under addressContext zone sipTrunkGroup signaling are as follows:

Configuration Examples

Called Prefix Match Profile

To configure calledPrefixMatchProfile, refer to the example below:

% set profiles signaling calledPrefixMatchProfile test_calledPrefixMatch prefixMatch 98520 0 4
% set profiles signaling calledPrefixMatchProfile test_calledPrefixMatch prefixMatch 98766 0 3
% commit

To display calledPrefixMatchProfile, refer to the example below:

> show table profiles signaling calledPrefixMatchProfile
                        STRING   START     DIGIT
NAME                    PATTERN  POSITION  LENGTH
---------------------------------------------------
test_calledPrefixMatch  98520    0         10
                        98766    0         10

To delete calledPrefixMatchProfile, refer to the example below:

% delete profiles signaling calledPrefixMatchProfile test_calledPrefixMatch
% commit

Carrier Code To Ioi Mapping Profile

To configure carrierCodeToIoiMappingProfile, refer to the example below:

% set profiles signaling carrierCodeToIoiMappingProfile 9999 ioi test_ioi accessValue test_access_value accessParam type
% commit

To display the configured carrierCodeToIoiMappingProfile, refer to the example below:

> show table profiles signaling carrierCodeToIoiMappingProfile
CARRIER                               ACCESS
CODE     IOI       ACCESS VALUE       PARAM
----------------------------------------------
9999     test_ioi  test_access_value  type

To delete the configured carrierCodeToIoiMappingProfile, refer to the example below:

% delete profiles signaling carrierCodeToIoiMappingProfile 9999
% commit

Ioi To Carrier Code Mapping Profile

To configure ioiToCarrierCodeMappingProfile, refer to the example below:

% set profiles signaling ioiToCarrierCodeProfile test_ioi carrierCode 9999
% commit

To display the configured ioiToCarrierCodeMappingProfile, refer to the example below:

> show table profiles signaling ioiToCarrierCodeMappingProfile
            CARRIER
IOI         CODE
---------------------
test_ioi    9999

To delete the configured ioiToCarrierCodeMappingProfile, refer to the example below:

% delete profiles signaling ioiToCarrierCodeMappingProfile test_ioi
% commit

SIP JJ9030Interworking Profile

To configure sipJJ9030InterworkingProfile with the parameter sipFlavor set to JJ9030, refer to the example below:

% set profiles signaling sipJJ9030InterworkingProfile test_sip_JJ9030 sipFlavor JJ9030 origIoi test_origIoi termIoi test_termIoi originatingCarrierCode 9999 chargeAreaInformation 56789
% commit

To configure sipJJ9030InterworkingProfile with the parameter sipFlavor set to SIP-T, refer to the example below:

% set profiles signaling sipJJ9030InterworkingProfile test_2_sip_JJ9030 sipFlavor SIP-T origIoi test_origIoi termIoi test_termIoi chargeAreaInformation 98765
% commit

To configure sipJJ9030InterworkingProfile with the parameter sipFlavor set to SIP-ttc-charging-params, refer to the example below:

% set profiles signaling sipJJ9030InterworkingProfile test_3_sip_JJ9030 sipFlavor SIP-ttc-charging-params origIoi test_origIoi termIoi test_termIoi chargeAreaInformation 45679 bciCalledPartyCategory payphone bciChargeIndicator noCharge bciTerminatingIsdnAccess isdn
% commit

To display the configured sipJJ9030InterworkingProfile, refer to the example below:

> show table profiles signaling sipJJ9030InterworkingProfile
                                                                                                  ADD USER
                                                                                                  EQUAL                                  BCI
                                                                        ORIGINATING               PHONEFOR DIV  SET HI        BCI        CALLED    BCI
                                                                        CARRIER      CHARGE AREA  HI            PRESENTATION  CHARGE     PARTY     TERMINATING
NAME               SIP FLAVOR               ORIG IOI      TERM IOI      CODE         INFORMATION  INTERWORKING  RESTRICTED    INDICATOR  CATEGORY  ISDN ACCESS
----------------------------------------------------------------------------------------------------------------------------------------------------------------
test_2_sip_JJ9030  SIP-T                    test_origIoi  test_termIoi  -            98765        disabled      disabled      -          -         -
test_3_sip_JJ9030  SIP-ttc-charging-params  test_origIoi  test_termIoi  -            45679        disabled      disabled      noCharge   payphone  isdn
test_sip_JJ9030    JJ9030                   test_origIoi  test_termIoi  9999         56789        disabled      disabled      -          -         -

To delete the configured sipJJ9030InterworkingProfile, refer to the example below:

% delete profiles signaling sipJJ9030InterworkingProfile test_sip_jj9030
% delete profiles signaling sipJJ9030InterworkingProfile test_2_sip_jj9030
% delete profiles signaling sipJJ9030InterworkingProfile test_3_sip_jj9030
% commit

Configure contractorNumInterworking under NNI Profile

To enable contractorNumInterworking under NNIProfile, refer to the example below:

% set profiles signaling NNIProfile test_nni_profile contractorNumInterworking enabled
% commit

By default, contractorNumInterworking is set to disabled.

Attach calledPrefixMatchProfile and sipJJ9030InterworkingProfile with a sipTrunkGroup

To attach calledPrefixMatchProfile and sipJJ9030InterworkingProfile with a sipTrunkGroup, refer to the example below:

% set addressContext default zone defaultSigZone sipTrunkGroup test_sip signaling calledPrefixMatchProfile test_calledPrefixMatch
% set addressContext default zone defaultSigZone sipTrunkGroup test_sip signaling sipJJ9030InterworkingProfile test_sip_jj9030
% commit

To detach the profiles from the sipTrunkGroup, refer to the example below:

% delete addressContext default zone defaultSigZone sipTrunkGroup test_sip signaling calledPrefixMatchProfile
% delete addressContext default zone defaultSigZone sipTrunkGroup test_sip signaling sipJJ9030InterworkingProfile
% commit

Deprecated CLI

CLI GOES HERE