Page History

Add_workflow_for_techpubs

AUTH1	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7f046c, userName='null'}
JIRAIDAUTH	SBX-102181
REV5	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8c60186, userName='null'}
REV1	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8c60186, userName='null'}

Panel

In this section:

Table of Contents

Use the SIP JJ9030 Interworking profile to configure parameters needed for SIP JJ9030 Interworking. For information on other related profiles for SIP-ISUP and interworking between different SIP flavors, refer to Support for SIP-ISUP.

Command Syntax

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

Code Block

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

Command Parameters

The parameter descriptions for profiles signaling sipJJ9030InterworkingProfile are as follows:

Div

class	pdf8pttext

Caption

0	Table
1	Parameter Description - sipJJ9030InterworkingProfile

Parameter	Length/Range	Description
`sipJJ9030InterworkingProfile`	1-23 characters	`<profile_name>` - The name of the SIP JJ-90.30 Interworking Profile. NOTE: The SBC allows configuring a maximum of 32 `sipJJ9030InterworkingProfile`(s).
`addUserEqualPhoneforDivHiInterworking`	N/A	Enable this parameter to add "user=phone" and the "mp" parameter for `diversionHistoryInfoInterworking`. `disabled` (default) `enabled` For more information on `diversionHistoryInfoInterworking`, refer to Egress IP Attributes - SIP - CLI.
`bciCalledPartyCategory`	N/A	The Backwards Call Indicators Called Party Category. `noIndication` `ordinary` `payphone` `spare` NOTE: This parameter is mandatory when the parameter `sipFlavor` is set to `SIP-ttc-charging-params`.
`bciChargeIndicator`	N/A	The Backwards Call Indicators Charge Indicator. `charge` `noCharge` `noIndication` `spare` NOTE: This parameter is mandatory when the parameter `sipFlavor` is set to `SIP-ttc-charging-params`.
`bciTerminatingIsdnAccess`	N/A	The Backwards Call Indicators Terminating ISDN Access Indicator. `isdn` `noIsdn` NOTE: This parameter is mandatory when the parameter `sipFlavor` is set to `SIP-ttc-charging-params`.
`chargeAreaInformation`	5 digits (`0-9`)	The Charge Area Information, consisting of 5 digits (0-9).
`origIoi`	1-128 characters	The name of Originating Inter Operator Identifier.
`originatingCarrierCode`	4 digits (`0-9`)	The Originating Carrier Code, consisting of 4 digits (0-9). Note: This parameter is mandatory when the parameter `sipFlavor` is set to `JJ9030`.
`setHiPresentationRestricted`	N/A	Set Presentation Indicator as "restricted" for `historyInfoInterworking`. `disabled` (default) `enabled` For more information on `historyInfoInterworking`, refer to NNI Profile - CLI.
`sipFlavor`	N/A	The type of SIP parameters and procedures used for this interworking profile. `JJ9030` `SIP-T` `SIP-ttc-charging-params`
`terminatingCarrierCode`	4 digits (`0-9`)	The Terminating Carrier Code, consisting of 4 digits (0-9).
`termIoi`	1-128 characters	The name of the Terminating Inter Operator Identifier.
`transitIcidInInvite`	N/A	When enabled, the SBC transits the icid-value in P-Charging-Vector transparently in the INVITE sent on the current trunk for JJ90.30 to JJ90.30 calls. `disabled` (default) `enabled` Note: Enable this parameter only when the parameter `sipFlavor` is set to `JJ90.30`. For example use cases of this parameter, see Use Cases for Transit Pcv and Transit Icid In Invite.
`transitPcv`	N/A	When enabled, the SBC transits icid-value, orig-ioi and term-ioi of P-Charging-Vector transparently in JJ90.30 to JJ90.30 calls, using the current trunk group. `disabled` (default) `enabled` Note: Enable this parameter only when the parameter `sipFlavor` is set to `JJ90.30`. For example use cases of this parameter, see Use Cases for Transit Pcv and Transit Icid In Invite.

Command Examples

Info

title	Note

The SBC allows configuring a maximum of 32 sipJJ9030InterworkingProfile(s).

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

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

Info

title	Note

The parameter originatingCarrierCode is mandatory only when you set sipFlavor to JJ9030. For other values of the parameter sipFlavor, configuration of originatingCarrierCode is optional.

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

Code Block
% 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:

Code Block

% 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

Info

title	Note

The following parameters are mandatory only when you set sipFlavor to SIP-ttc-charging-params:

bciCalledPartyCategory
bciChargeIndicator
bciTerminatingIsdnAccess

For other values of the parameter sipFlavor, these parameters are optional.

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

Code Block

> show table profiles signaling sipJJ9030InterworkingProfile
                                                                                                             ADD USER
                                                                                                             EQUAL                                  BCI
                                                                        ORIGINATING TERMINATING              PHONEFOR DIV  SET HI        BCI        CALLED    BCI
                                                                        CARRIER     CARRIER     CHARGE AREA  HI            PRESENTATION  CHARGE     PARTY     TERMINATING
NAME               SIP FLAVOR               ORIG IOI      TERM IOI      CODE        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 attach the configured sipJJ9030InterworkingProfile with a sipTrunkGroup, refer to the example below:

Code Block
% set addressContext default zone defaultSigZone sipTrunkGroup test_sip signaling sipJJ9030InterworkingProfile test_sip_jj9030 % commit

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

Tip

title	Tip

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.

Code Block

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

Anchor
Use Cases for Transit Pcv and Transit Icid In Invite
Use Cases for Transit Pcv and Transit Icid In Invite
Use Cases for Transit Pcv and Transit Icid In Invite

When using the JJ90.30 standard to improve interconnectivity between IMS networks within Japan, the SBC Core may need to transit some or all of the P-Charging-Vector parameters: icid-value, orig-ioi, and term-ioi. To support this functionality, the SBC includes the configurable signaling parameters, transitPcv and transitIcidInInvite,in the SIP JJ90.30 Interworking profile.

The following diagrams illustrate some sample use cases of the configuration options:

Caption

0	Figure
1	Call from SIP to JJ90.30 (IN) to JJ99.30

Caption

0	Figure
1	Call from JJ90.30 to SIP

Caption

0	Figure
1	Call from JJ90.30 to JJ90.30

Pagebreak

Space shortcuts

Page tree

Versions Compared

Old Version 2

New Version 3

Key

Command Syntax

Command Parameters

Command Examples

Anchor
Use Cases for Transit Pcv and Transit Icid In Invite
Use Cases for Transit Pcv and Transit Icid In Invite
Use Cases for Transit Pcv and Transit Icid In Invite

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 2

New Version 3

Key

Command Syntax

Command Parameters

Command Examples

AnchorUse Cases for Transit Pcv and Transit Icid In InviteUse Cases for Transit Pcv and Transit Icid In InviteUse Cases for Transit Pcv and Transit Icid In Invite

Anchor
Use Cases for Transit Pcv and Transit Icid In Invite
Use Cases for Transit Pcv and Transit Icid In Invite
Use Cases for Transit Pcv and Transit Icid In Invite