Page History

Add_workflow_for_techpubs

AUTH2	UserResourceIdentifier{userKey=8a00a0c86820e56901685f374974002d, userName='null'}
AUTH1	UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
JIRAIDAUTH	SBX-117394
REV5	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb1f0553, userName='null'}
REV1	UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb1f0553, 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.

Multiexcerpt

MultiExcerptName	Private Header for ISDN 64K Unrestricted

Available_since

Type	Available Since
Release	10.1.2

Private Header for ISDN 64K Unrestricted

The SBC supports the ISUP signal transfer using the Japanese unique private header "P-N-ISUP-R" between the NNI-GWs. The private header "P-N-ISUP-R" carries the ISUP message-specific information in the SIP message. "P-N-ISUP-R" is required for 64K unrestricted and voice calls. The SBC converts P-N-ISUP-R header contents to ISUP parameters in the SIP-T MIME. Additionally, the SBC creates P-N-ISUP-R header based on the ISUP parameter received in the SIP-T MIME. The SBC uses the following configuration for SIP-T to SIP (JJ-90.30) calls during interworking with the P-N-ISUP-R header.

The SBC adds the parameter pnisuprHeaderInterworking inside the SIP-JJ-90-30 Interworking profile. This parameter is used only if sipFlavor is JJ9030".

The SBC adds the parameter siptOriginatingCarrierCodesForPniusprIwk inside the SIP-JJ-90-30 Interworking profile to configure multiple originating carrier codes.

"Originating Carrier Code" is 4 digits.
Maximum number of originating carrier codes are 50.
This configuration is available only if the sipFlavor is SIP-T.

Note: This configuration mentions all of the supported originating carriers on the SIP-T side.

The list of ISUP parameters and messages supported in the P-N-ISUP-R header are shown below.

Message Type/ISUP Parameter	ISUP Message
Message Type/ISUP Parameter	IAM	ACM	CPG	ANM	REL
Message Type (0x00)	M	M	M	M	M
Forward Call Indicators (0x07)	M	-	-	-	-
Transmission Medium Requirement (0x02)	M	-	-	-	-
Event Information (0x24)	-	-	M	-	-
Backward Call Indicators (0x11)	-	M	O	O	－
Cause Indicators (0x12)	-	O	O	-	V
User Service Information (0x1d)	O	-	-	-	-
Access Transport (0x03)	O	O	O	O	-
Optional Backward Call Indicators (0x29)	-	O	O	O	-
User-to-User Indicator (0x2A)	-	O	O	-	-

M= Mandatory

O= Optional

V= Mandatory variable

Multiexcerpt

MultiExcerptName	UUI interworking - SIP-T and SIP

Available_since

Type	Available Since
Release	10.1.3

User to User Information (UUI) interworking between ISUP MIME (SIP-T) and SIP

The interworking between UUI parameter and User-to-User header is categorized in the following two ways:

Interwork of User-to-User Information (UUI) of ISUP MIME (SIP-T) to/from "User-to-User" header of the SIP message.
Interwork of User-to-User Indicators (UUIN) of ISUP MIME (SIP-T) to/from "P-N-ISUP-R" header of the SIP message.

If the terminating carrier does not use User-User Information, interworking between UUI parameter and User-to-User header is not performed.

Interworking of User-to-User Indicator (0x2A)

The SBC decodes/encodes the User-to-User Indicator (0x2A) parameter in P-N-ISUP-R header for the ACM message and CPG message. UUI interworking is controlled by userToUserHdrSupport flag on the SIP trunk group.

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]>
    	pnisuprHeaderInterworking <disabled | enabled>
		setHiPresentationRestricted <disabled | enabled>
		sipFlavor
			JJ9030
			SIP-T
			SIP-ttc-charging-params
			X-Header         
		siptOriginatingCarrierCodesForPnisuprIwk <list of 4-digit carrier codes>
		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:

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.

pnisuprHeaderInterworking

N/A

Enable this flag on SIP JJ9030 leg to support P-N-ISUP-R header interworking in SIP-T to SIP JJ90.30 and SIP JJ90.30 to SIP-T calls.

disabled (default)
enabled

Available_since

Type	Available Since
Release	10.1.2

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

siptOriginatingCarrierCodesForPnisuprIwk

A list of 4-digit carrier codes,
up to 50 elements

List of supported originating carrier codes on the SIP-T leg for the P-N-ISUP-R header interworking in a SIP-T to SIP JJ9030 call.

Available_since

Type	Available Since
Release	10.1.2

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 configure sipJJ9030InterworkingProfile with the parameter sipFlavor set to X-Header, refer to the example below:

Code Block

language	none

set profiles signaling sipJJ9030InterworkingProfile test_sip_JJ9030 sipFlavor X-Header origIoi test_origIoi termIoi test_termIoi originatingCarrierCode 9999 chargeAreaInformation 56789 
commit

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

To attach a configured SIP JJ9030 Interworking Profile with a SIP Trunk Group, refer to the example below:

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

To detach an attached SIP JJ9030 Interworking Profile from a SIP Trunk Group, refer to the example below:

Code Block
delete addressContext default zone defaultSigZone sipTrunkGroup test_sip signaling sipJJ9030InterworkingProfile commit

Code Block

set profiles signaling sipJJ9030InterworkingProfile jj9030 pnisuprHeaderInterworking enabled
show profiles signaling sipJJ9030InterworkingProfile jj9030
sipFlavor JJ9030;
pnisuprHeaderInterworking enabled;
commit

Code Block

set profiles signaling sipJJ9030InterworkingProfile sipt siptOriginatingCarrierCodesForPnisuprIwk [ 1234 1235 1236 1237 1238 1239 ]
show profiles signaling sipJJ9030InterworkingProfile sipt
sipFlavor SIP-T;
siptOriginatingCarrierCodesForPnisuprIwk [ 1234 1235 1236 1237 1238 1239 ];
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:

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

Figure 2: Call from JJ90.30 to SIP

Figure 3: Call from JJ90.30 to JJ90.30

Space shortcuts

Page tree

Versions Compared

Old Version 4

New Version Current

Key

Private Header for ISDN 64K Unrestricted

User to User Information (UUI) interworking between ISUP MIME (SIP-T) and SIP

Interworking of User-to-User Indicator (0x2A)

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 4

New Version Current

Key

Private Header for ISDN 64K Unrestricted

User to User Information (UUI) interworking between ISUP MIME (SIP-T) and SIP

Interworking of User-to-User Indicator (0x2A)

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