In this section:
Default values are enclosed in square brackets [ ].
A parameter, t140RtcpMonitorInterval
, is added under mediaRTCPControl to define the RTCP monitoring interval. This enables the SBC to wait for an RTCP packet from peer before starting RTCP towards T.140 endpoint with the following PSP flag enabled.
A flag, generateRTCPForT140IfNotReceivedFromOtherLeg,
is added under RTCP Options in the Packet Service Profile so that the SBC is able to configure specific trunk groups to generate RTCP on T.140 to T.140 passthrough media streams. The SBC will start generating RTCP for T.140 stream if RTCP is NOT received from the endpoint.
% set system media mediaRtcpControl t140RtcpMonitorInterval 6
% set profiles media packetServiceProfile DEFAULT rtcpOptions generateRtcpForT140IfNotReceivedFromOtherLeg enable
t140RtcpMonitorInterval
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
t140RtcpMonitorInterval
| 2-20 seconds
| 6 seconds | Defines the interval for which the SBC monitors the RTCP packets for T140 stream from endpoints. If RTCP is not received within this interval, the SBC starts RTCP generation.
| O |
generateRtcpForT140IfNotReceivedFromOtherLeg
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
generateRtcpForT140IfNotReceivedFromOtherLeg
| Enable/Disable | Disabled | Use this flag to configure specific trunk groups to generate RTCP for text pass-through media streams. This flag can be provisioned if RTCP is "enabled" under rtcpOptions.
| O |
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>
Rcode Error Monitor Timer
Parameter | Length/Range | Default | Description |
---|---|---|---|
rcodeErrorMonitorTimer | 0 - 60 minutes | 0 minutes | Configure the RCODE error monitor timer interval to allow the Unable to show "metadata-from": No such page "_space_variables" to monitor RCODE errors.When the timer value is 0, this feature is disabled. |
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.
Ensure the ARS profile is configured with the recovery algorithms specified in the recovery flags.
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>
ARS Recovery Algorithm Parameter
Parameter | Length/Range | Default | Description |
---|---|---|---|
recoveryAlgForTimeouts | none | Specifies the type of recovery algorithm for the endpoints blacklisted with timeouts algorithm.
Note: When the flag is set to Unable to show "metadata-from": No such page "_space_variables" continues with the default behavior which is specified in the recoveryAlgorithm flag. | |
recoveryAlgForNoRetryAfter | none | Specifies the type of recovery algorithm for the endpoints blacklisted with 503 noRetryAfter algorithm.
Note: When the flag is set to Unable to show "metadata-from": No such page "_space_variables" continues with the default behavior specified in the recoveryAlgorithm flag. |
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 preferUPDATEOverReINVITE:
to use UPDATE instead of Re-INVITE on the ingress to communicate SDP, when the call goes to the confirmed state.
% 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>
Rcode Error Monitor Timer
Parameter | Length/Range | Default | Description |
---|---|---|---|
preferUPDATEOverReINVITE | NA | disabled | Enable this flag on the ingress trunk group to allow the Unable to show "metadata-from": No such page "_space_variables" to use UPDATE instead of Re-INVITE to communicate SDP towards ingress, when the call is in the confirmed state.The options include:
Note: This is not applicable when the dialog transparency flag or the Unable to show "metadata-from": No such page "_space_variables" . |
performPrecondtionRenegotiation | NA | disabled | Enable this flag on the ingress trunk group to allow the Unable to show "metadata-from": No such page "_space_variables" to renegotiate the precondition on the ingress when there is a change in SDP during early dialog phase or whenever the call goes to confirmed state. TheUnable to show "metadata-from": No such page "_space_variables" supports this flag for SIP gateway-gateway call.The options include:
Note: This is not applicable when the dialog transparency flag or theupdatedAnswerIn200Ok flag is in enabled state on the Unable to show "metadata-from": No such page "_space_variables" . |
SIP Trunk Group - Signaling - CLI
SIP TG - Signaling - Prefer UPDATE Over ReINVITE - CLI
SIP TG - Signaling - Perform Precondtion Renegotiation - CLI
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):
Offer Answer Timer
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
offerAnswerTimer | 10 - 300 seconds | 20 seconds | Specify the number of seconds for the Unable to show "metadata-from": No such page "_space_variables" to wait for the Offer-Answer handshake to complete before timing out. Once configured, the Unable to show "metadata-from": No such page "_space_variables" uses this value for all subsequent calls.For backward compatibility, set the Note: The | M |
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.
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.
Parameter | Description |
---|---|
| Enable this flag to generate an SSRC value and associated attributes and include them in SDP signaling and RTP/RTCP streams. Options are:
Note: This flag takes precedence over the Packet Service Profile |
| 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:
Note: You must enable the Note: If you enable the IP Signaling profile common IP attributes flag |
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.
% set addressContext <address context> zone <zone> sipTrunkGroup <trunk group name> signaling honorContactInRegisterForTLSCalls <disabled | enabled> |
Parameter | Description |
---|---|
| 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:
|
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.
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>
The following table describes the new SMM operations.
Parameter | Description |
---|---|
| SMM operation that extracts a specified value (header, parameter, token) from the incoming SIP message to compare to mapping defined in a |
| 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
.
Parameter | Length/Range | Description |
---|---|---|
| up to 23 characters | Name for the |
| n/a | Action to be performed by the
|
| 0 to 2056 | Index value for the entry. A sipParamBasedActionProfile can contain a maximum of 2056 entries. |
| up to 23 characters | The 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. |
| n/a | Type of matching to use when comparing the value extracted with the SMM
|
| up to 128 characters | Parameter value to compare against when matchType is full . More than one param value can be defined for an entry when matchType is full . |
| up to 128 characters | Ending value for a range to compare against when matchType is range . |
| up to 128 characters | Starting value for a range to compare against when matchType is range . |
| up to 128 characters | Regular expression to compare against when the matchType is regexp . |
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.
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>
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>
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>
Parameter | Length/Range | Description |
---|---|---|
| 0-23 characters |
|
| 0-23 characters | <profile name> – Enter the name of a SIP adaptor profile to use globally on outbound messages. |
Parameter | Length/Range | Description |
---|---|---|
| 0-23 characters |
|
| 0-23 characters | <profile name> – Enter the name of a SIP adaptor profile to use for the address context on outbound messages. |
Parameter | Description |
---|---|
| 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:
|
| 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:
This option is only available after you set |
| 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:
This option is only available after you set |
| 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:
This option is only available after you set |
| 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:
This option is only available after you set |
The SBC is enhanced with the parameter maxNumTransfers
under the object global signaling
.
To configure maxNumTransfers
, use the following syntax:
% set global signaling maxNumTransfers <10-100>
Parameter Description
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
maxNumTransfers |
| 10 | Specifies the maximum number of transfers (10-100 ) allowed within a call; default is 10 . | O |
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; }
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.
To configure the parameter generateRtcpForT140IfNotReceivedFromOtherLeg
, use the following syntax:
set profiles media packetServiceProfile <packetServiceProfile_name: INGRESS> rtcpOptions rtcp <disable | enable> generateRtcpForT140IfNotReceivedFromOtherLeg <disable | enable>
Parameter Descriptions
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
generateRtcpForT140IfNotReceivedFromOtherLeg | N/A | disable | The SBC generates RTCP for T140 media streams if RTCP is not received from peer.
| O |
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
show <status | table> system dspStatus dspUsage
:amrNbT140Total
amrNbT140Utilization
amrWbT140Total
amrWbT140Utilization
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. |
show <status | table> system dspRes <dspUsageCurrentStatistics | dspUsageIntervalStatistics>
:amrWithT140PeakUsedCount
amrWithT140AverageUsedCount
amrWithT140AverageAvailCount
amrwbWithT140PeakUsedCount
amrwbWithT140AverageUsedCount
amrwbWithT140AverageAvailCount
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. |
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
% 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
Parameter Descriptions
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
sipAdaptiveTransparencyProfile | 1-23 characters | N/A | <profile name> Specifies the profile name for which the SBC passes configured SIP headers "adaptive transparently". | O |
sipMethod | N/A | N/A | Specifies the SIP method for which the SBC performs the configured
Note: The SIP Method | M |
sipResponse | N/A | N/A | Specifies the SIP response code for which the SBC performs the configured
| M |
state | N/A | disabled | The administrative state of the SIP Adaptive Transparency Profile.
| O |
triggerHeader | N/A | N/A | Specifies the SIP header which, if present in the SIP request/method or response, triggers the configured
| M |
action | N/A | new-value | The action that the SBC performs, when the SIP header in the request/response matches with the configured
| O |
trigger | N/A | value-change | The action/process that the SBC initiates, when the SIP header in the request/response matches with the configured
| O |
To configure SIP Adaptive Transparency Profile, execute the following steps:
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
Enable the profile:
% set profiles services sipAdaptiveTransparencyProfile TPforPAI state enabled % commit
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
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.
(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>]
The CLI changes are as follows:
profiles signaling
:calledPrefixMatchProfile
carrierCodeToIoiMappingProfile
ioiToCarrierCodeMappingProfile
sipJJ9030InterworkingProfile
profiles signaling NNIProfile
:contractorNumInterworking
addressContext zone sipTrunkGroup signaling
:calledPrefixMatchProfile
sipJJ9030InterworkingProfile
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>
Create the profiles calledPrefixMatchProfile
and sipJJ9030InterworkingProfile
before attaching them with sipTrunkGroup
.
The parameter descriptions for profiles signaling
calledPrefixMatchProfile
are as follows:
Parameter Description - calledPrefixMatchProfile
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
calledPrefixMatchProfile | 1-23 characters | N/A | < Note: The SBC allows configuring a maximum of 10 | M |
prefixMatch | N/A | N/A | Use this parameter to configure the prefix that the SBC matches for the called number.
| M |
The parameter descriptions for profiles signaling carrierCodeToIoiMappingProfile
are as follows:
Parameter Description - carrierCodeToIoiMappingProfile
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
carrierCodeToIoiMappingProfile | 4 digits (0-9) | N/A | < Note: The SBC allows configuring a maximum of 200 entries for each | M |
accessParam | N/A | N/A | Specifies the access parameters for the carrier.
| M |
accessValue | 1-64 characters | N/A | Specifies the access value string associated with the accessParam chosen for the carrier. | M |
ioi | 1-128 characters | N/A | Specifies the Inter Operator Identifier (IOI) string for the carrier. | M |
The parameter descriptions for profiles signaling
are as follows:ioiToCarrierCodeMappingProfile
Parameter Description - ioiToCarrierCodeMappingProfile
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
| 1-128 characters | N/A | < Note: The SBC allows configuring a maximum of 200 entries for each | M |
carrierCode | 4 digits (0-9) | N/A | <carrier_code > - Specifies the carrier code (4-digit numeric string consisting of digits in the range 0-9) mapped to Inter Operator Identifier. | M |
The parameter descriptions for profiles signaling
are as follows:sipJJ9030InterworkingProfile
Parameter Description - sipJJ9030InterworkingProfile
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
sipJJ9030InterworkingProfile | 1-23 characters | N/A |
Note: The SBC allows configuring a maximum of 32 | M |
addUserEqualPhoneforDivHiInterworking | N/A | disabled | Enable this parameter to add "user=phone" and the "mp" parameter for
For more information on | M |
bciCalledPartyCategory | N/A | N/A | The Backwards Call Indicators Called Party Category.
Note: This parameter is mandatory when the parameter | O |
bciChargeIndicator | N/A | N/A | The Backwards Call Indicators Charge Indicator.
Note: This parameter is mandatory when the parameter | O |
bciTerminatingIsdnAccess | N/A | N/A | The Backwards Call Indicators Terminating ISDN Access Indicator.
Note: This parameter is mandatory when the parameter | O |
chargeAreaInformation | 5 digits (0-9 ) | N/A | The Charge Area Information, consisting of 5 digits (0-9). | M |
origIoi | 1-128 characters | N/A | The name of Originating Inter Operator Identifier. | M |
originatingCarrierCode | 4 digits (0-9 ) | N/A | The Originating Carrier Code, consisting of 4 digits (0-9). Note: This parameter is mandatory when the parameter | O |
setHiPresentationRestricted | N/A | disabled | Set Presentation Indicator as "restricted" for
For more information on | M |
sipFlavor | N/A | N/A | The flavor of the SIP parameters and procedures used for this interworking profile.
| M |
termIoi | 1-128 characters | N/A | The name of the Terminating Inter Operator Identifier. | M |
The descriptions for new parameters under profiles signaling NNIProfile
are as follows:
Parameter Description - New parameters under NNIProfile
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
contractorNumInterworking | N/A | disabled | Enable this parameter to interwork the parameter
| M |
The descriptions for new parameters under addressContext zone sipTrunkGroup signaling
are as follows:
Parameter Description - New parameters under sipTrunkGroup signaling
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
calledPrefixMatchProfile | 1-23 characters | N/A | < | O |
| 1-23 characters | N/A | <profile_name > - Specifies the name of the SIP JJ-90.30 Interworking profile associated with this SIP Trunk Group. | O |
Exit the configuration mode before executing the "show
" command.
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:
If the calledPrefixMatchProfile
is attached to a sipTrunkGroup
, detach the profile before you attempt to delete it. To detach, use the following syntax:
%
delete addressContext <address_context> zone <zone>
sipTrunkGroup <sip_tg> signaling calledPrefixMatchProfile
Commit the command to complete the process of deletion.
% 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:
If the sipJJ9030InterworkingProfile
is attached to a sipTrunkGroup
, detach the profile before you attempt to delete it. To detach, use the following syntax:
%
delete addressContext <address_context> zone <zone>
sipTrunkGroup <sip_tg> signaling sipJJ9030InterworkingProfile
Commit the command to complete the process of deletion.
% 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