Local Number Portability (LNP) refers to the ability of a "customer of record" of an existing fixed-line or mobile telephone number assigned by a local exchange carrier (LEC) to reassign the number to another carrier (Service Provider Portability), change the type of service (Service Portability), or move it to another location (Geographic Portability).

The SBC Core includes a NPA/Nxx object to provision the valid national destination code, associated country code and LATA, the lookup type for local number portability (LNP), and a flag indicating whether the national destination code has been ported for LNP. Refer to NPA/Nxx - CLI  or Call Routing: System Provisioning - Npa Nxx (EMA) for provisioning details.

Jurisdiction Information Parameter

 

Note:

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

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

The SBC, when configured, can provide the JIP parameter in SIP INVITE messages in SIP-SIP, SIP-SIP-I and SIP-I to SIP scenarios. The SBC extracts the JIP value from an incoming message and sends it to the external PSX which returns a JIP value based on the PSX configuration. The SBC sends out the JIP value returned by the PSX in the outgoing message.

Based on SIP JIP profile configuration, JIP information can be carried in the P-Asserted-ID/FROM and P-DCS-Billing-Info headers of a SIP INVITE message and in the PDCS header in a 3xx response. The SBC records JIP-related details in the Call Detail Record.


Refer to Services - Sip Jip Profile (EMA) or Show Table Profiles - Services - SIP JIP Profile (CLI) for details of configuring JIP support on the SBC.


  • No labels