The ISUP Jurisdiction Information Parameter (JIP) is a 6-digit parameter in the format of NPA-NXX that is signaled in the Initial Address Message (IAM) by the originating switch.  The JIP is used by carriers downstream in the call path to identify the originating switch for billing settlement purposes.  When carriers signal an incorrect JIP to another carrier, e.g., signaling an NPA-NXX in the JIP that is LERG-assigned to another carrier, this will result in improper identification of the originating switch.

 The LNPA WG supports and reiterates the following signaling requirements and guidelines for JIP as documented in ATIS’ (www.atis.org) industry standard for Local Number Portability – Technical Requirement on Number Portability Switching Systems (T1.TRQ.2-2001) and in ATIS’ Network Interconnection Interoperability Forum’s (NIIF) (www.atis.org/niif/index.asp) Reference Document, Part III, Installation and Maintenance Responsibilities for SS7 Links and Trunks:

 From ATIS’ Technical Requirement on Number Portability Switching Systems:

Page 6, Assumption 19:  “An NPA-NXX used as a JIP is a LERG-assigned code on the switch.”

And, where technically feasible:

Page 50, cites from REQ-03300: 

“The ISUP JIP parameter shall be included in the IAM for all line and private trunk call originations.”

“The JIP identifies the switch from which the call originates, and can be recorded to identify that switch.”

From ATIS NIIF Reference Document, Part III, Installation and Maintenance Responsibilities for SS7 Links and Trunks:

Rules for Populating JIP

1.                  JIP should be populated in the IAMs of all wireline and wireless originating calls where technically feasible.

2.                  JIP should be populated with an NPA-NXX that is assigned in the LERG to the originating switch or MSC.

3.                  The NIIF does not recommend proposing that the JIP parameter be mandatory since calls missing any mandatory parameter will be aborted. However, the NIIF strongly recommends that the JIP be populated on all calls where technologically possible.

4.                  Where technically feasible if the originating switch or MSC serves multiple states/LATAs, then the switch should support multiple JIPs such that the JIP used for a given call can be populated with an NPA-NXX that is specific to both the switch as well as the state and LATA of the caller.

5.                  If the JIP cannot be populated at the state and LATA level, the JIP should be populated with an NPA-NXX specific to the originating switch or MSC where it is technically feasible.

6.                  Where the originating switch cannot signal JIP it is desirable that the subsequent switch in the call path populate the JIP using a data fill default associated with the incoming route.  The value of the data fill item is an NPA-NXX associated with the originating switch or MSC and reflects its location. 

7.                  When call forwarding occurs, the forwarded from DN (Directory Number) field will be populated, the JIP will be changed to a JIP associated with the forwarded from DN and the new called DN will be inserted in the IAM.

8.                  As per T1.TRQ2, the JIP should be reset when a new billable call leg is created.