DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

Note:

JIP handling is only supported when using an external PSX in the network.

The SBC supports sending Jurisdiction Information Parameter (JIP) information in SIP-SIP, SIP-SIP-I and SIP-I to SIP 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 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

Use the following command to view the SIP JIP Profile configuration details.

Command Syntax

 

> show table profiles services sipJipProfile <profile name> 

Command Parameters

SIP JIP Profile Parameters

ParameterDescription
nameThe name of the SIP JIP Profile.
useJipFromPAIrn

If set to enabled, the SBC extracts JIP information from the "rn" parameter in the PAI header of the INVITE message.

useJipFromPAIjip

If set to enabled, the  SBC extracts JIP information from the "jip" parameter in the PAI header of the INVITE message.

useJipFromFROM

If set to enabled, the  SBC extracts JIP information from the "rn" parameter in the FROM header of the INVITE message. 

useJipFromPDCS

If set to enabled, the  SBC extracts JIP information from the "jip" parameter in the PDCS header of the INVITE message. 

sendJipIn

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

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

The parameter format to use when sending JIP information.

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

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 Example

> show table profiles services sipJipProfile
                   USE JIP   USE JIP   USE JIP   USE JIP   SEND   JIP
                   FROM      FROM      FROM      FROM      JIP    PARAMETER
NAME               PAIRN     PAIJIP    FROM      PDCS      IN     AS
-----------------------------------------------------------------------------
defaultJipProfile  enabled   disabled  disabled  disabled  rnPAI  userInfo

 

  • No labels