In this section:
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. 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. 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 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 The interworking between UUI parameter and User-to-User Header is categorized in the following two ways: If the terminating carrier does not use User-User Information, interworking between UUI parameter and User-to-User Header is not performed. 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 the SIP Trunk Group Private Header for ISDN 64K Unrestricted
User to User Information (UUI) Interworking Between ISUP MIME (SIP-T) and SIP
Interworking Between UUI and User-to-User Header
Interworking of User-to-User Indicator (0x2A)
userToUserHdrSupport
flag.
To configure the signaling profile sipJJ9030InterworkingProfile
, use the following syntax:
% 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>
The parameter descriptions for profiles signaling
are as follows:sipJJ9030InterworkingProfile
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:
% set profiles signaling sipJJ9030InterworkingProfile test_sip_JJ9030 sipFlavor JJ9030 origIoi test_origIoi termIoi test_termIoi originatingCarrierCode 9999 chargeAreaInformation 56789 % commit
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:
% 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
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:
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:
> 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:
% set addressContext default zone defaultSigZone sipTrunkGroup test_sip signaling sipJJ9030InterworkingProfile test_sip_jj9030 % commit
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
set profiles signaling sipJJ9030InterworkingProfile jj9030 pnisuprHeaderInterworking enabled show profiles signaling sipJJ9030InterworkingProfile jj9030 sipFlavor JJ9030; pnisuprHeaderInterworking enabled; commit
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
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: