Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

In this section:

Table of Contents

Info
iconfalse

Related articles:

 

Multiexcerpt
MultiExcerptNameJIP Profile
Info
titleNote:

JIP handling is only supported when the 

Spacevars
0product
is configured to use using an external PSX in the network. 

The SBC supports sending Jurisdiction Information Parameter (JIP) is a 6-digit field (NPA-NXX format) in an IAM message to indicate the geographic location of the originating caller or switch.The 

Spacevars
0product
 platform, when configured, can provide the JIP parameter in SIP INVITE messages for SIPinformation in SIP-SIP, SIP-SIP-I and SIP-I to SIP . Additionally, the SBC supports sending JIP in the PAI/FROM/PDCS header, as well as sending JIP across a gateway to the GSX. 

JIP information can be carried in the P-Asserted-ID/FROM and P-DCS-Billing-Info headers of

scenarios. A JIP value indicates the geographic location of the originating caller or switch. 

SIP JIP profiles are assigned to ingress and egress SIP trunk groups to determine what parameter to extract the SIP JIP value from in an incoming SIP INVITE message and in

the PDCS header in a 3xx response. The 
Spacevars
0product
records JIP-related details in the Call Detail Record.

Multiple controls can be enabled at a time to select the header or parameter from which JIP value will be extracted. When multiple controls are configured, JIP information is extracted in the following order:

  • RN PARAMETER IN PAI
  • JIP PARAMETER IN PAI
  • RN PARAMETER IN FROM
  • what parameter to place the JIP value in the outgoing message when sipJurisdictionSupport is enabled on the trunk group. The SBC can take the JIP value from or place it in the following parameters:

    • rn parameter in the PAID header
    • jip parameter in the PAID header
    • rn parameter in the From header
    • jip parameter in the P-DCS-Billing-Info header

    JIP PARAMETER IN PDCS

    Command Syntax

    Code Block
    languagenone
    % set profiles services sipJipProfile defaultJipProfile<profile name> 
    	jipParameterAs <userInfo | uriParam>
    	sendJipIn <rnPAI|jipPAI | rnFROM | jipPDCS>
    	useJipFromFROM <disabled | enabled>
    	useJipFromPAIjip <disabled | enabled>
    	useJipFromPAIrn <disabled | enabled>
    	useJipFromPDCS <disabled | enabled>

    Command Parameters

    Caption
    0Table
    1Command Parameters
    Parameter Name
    Description

    sipJipProfile<profile name>

    defaultJipProfileThe default name of for the SIP JIP profile associated with ingress and egress SIP Trunk Group used to control the SIP header and the corresponding SIP parameter from which JIP value is extracted or sent. A default profile, defaultJipProfile, is provided and assigned to SIP trunk groups by default. You have the option to create additional profiles and assign your own.

    jipParameterAs

    The parameter format to use when sending JIP information.

    • uriParam URI parameter, for example: P-Asserted-Identity: <sip:+12817267815@198.229.181.6:5060; transport=udp; user=phone;rn=+1123456>1123456>
    • userInfo (default) – userinfo parameter, for example: P-Asserted-Identity: <sip:+12817267815;rn=+1123456@1981123456@198.229.181.6:5060; transport=udp; user=phone>
    sendJipIn

    Select the header/parameter option to send the JIP in the outgoing INVITE message:

    • rnPAI (default) – The
      Spacevars
      0product
      sends the JIP value in the rn parameter in the PAI header.
    • jipPAI – The
      Spacevars
      0product
      sends the JIP value in the jip parameter in the PAI header.
    • rnFROM – The
      Spacevars
      0product
      sends the JIP value in the rn parameter in the FROM header.
    • jipPDCS – The
      Spacevars
      0product
      sends the JIP value in the jip parameter in the PDCS-Billing-Info header.
    useJipFromFROM

    Enable this flag to extract allow extracting JIP information from the "rn" parameter in the FROM header of the INVITE message.

    • disabled (default)
    • enabled
    useJipFromPAIjip

    Enable this flag to extract allow extracting JIP information from the "jip" parameter in the PAI header of the INVITE message.

    • disabled (default)
    • enabled
    useJipFromPAIrn

    Enable this flag to extract allow extracting JIP information from the "rn" parameter parameter in the PAI header of the INVITE message.

    • disabled (default)
    • enabled
    useJipFromPDCS

    Enable this flag to extract allow extracting JIP information from the "jip" parameter in PDCS header of parameter in the PDCS header of the INVITE message.

    • disabled (default)
    • enabled
    Info
    titleNote:

    If you choose to enable more than one potential source from which to extract the JIP information, the SBC prioritizes them in the following order:

    • rn parameter in the PAID header
    • jip parameter in the PAID header
    • rn parameter in the From header
    • jip parameter in the P-DCS-Billing-Info header

    Command Examples

    Code Block
    languagenone
    % set profiles services sipJipProfile sjp2 useJipFromPAIjip enabled sendJipIn rnFROM jipParameterAs uriParam   
    % set profiles services sipJipProfile sjp2 useJipFromPAIrn enabled sendJipIn jipPDCS jipParameterAs userInfo 
    
    % show profiles services sipJipProfile sjp2 
    useJipFromPAIrn enabled;
    sendJipIn       jipPDCS;
    jipParameterAs  userInfo;
    
    > show table profiles services sipJipProfile 
                        USE JIP      USE JIP   USE JIP   USE JIP             JIP        
                        FROM         FROM      FROM      FROM      SEND      PARAMETER  
    NAME                PAIRN        P AIJIP   FROM      PDCS      JIP IN    AS         
    ----------------------------------------------------------------------------------
    sjp1                disabled     enabled   disabled  disabled  rnFROM    uriParam   
    sjp2                enabled      disabled  disabled  disabled  jipPDCS   userInfo   
    defaultJipProfile   disabled     disabled  disabled  disabled  rnPAI     userInfo   

    Pagebreak