National LNP Billing Forum Minutes

6/18/97

 

 

 

REVIEW OF PREVIOUS DAYS MEETING

 

LRN issue was not resolved.

 

Need to make the meeting more efficient by staying focused on national level issues. Team agreed that we need to focus on issues that impact at least 2 regions.

 

 

 

 

Description Issue/Action Item

 

Resp.

Resolution

1

If thereís a need to have the switch derive more than one LRN on the originating side, the team needs to define the criteria and submit vendor change requests. The request needs to be specific as far as how many originating LRNs/how many terminating LRNs would be need to be derived and what the criteria would be (e.g. one per rate center or lower level).

All

 

2

Contact your METRG/OBF reps to get the EMR/EMI records put into the national standards document so that they can be openly discussed. This is a key billing issue from a data exchange point of view.

All

 

3

Baseline the Delta Document. Use revision number going forward

Debi

 

4

Need the NORTEL patch number for the host/remote change.

Elizabeth

 

5

If companies have specific number pooling concerns, they should participate in the next Illinois Conference Call. The call is July 15 at 11:00am EDT. Check with Armen or Jill for conference bridge.

All

 

6

Elizabeth Keddy will check to see what NORTEL is doing in regards to ICC req. 1196

Elizabeth

 

7

Re-look access billing needs with AIN service and Delta Item #4 in general for access vs. end user originating module requirements. This team needs to reach consensus on the best solution and submit change requests to the vendors **CHANGE DELTA**

All

 

8

If your company is interested in participating in the Bellcore SPID requirements definition effort, call Bill Krall at 908 758-4296.

All

 

9

Should the Account Owner SPID be used in the SCP or the Facilities Owner SPID? Would system changes be required if we mix facilities/end user owners?

Armen

 

10

LSMS/NPAC Issue: Is the connection SPID the one that gets populated in the SCP entry for a given ported TN or is the new provider OCN from the service order used?

Tom Santos

 

11

For terminating access records we need terminating Account Owner SPID. Is the AO SPID in the SCP Today (no). **New DELTA**

Debi

 

12

Each company should research the need for SPID on originating numbers. Queries are not performed on the originating number, so the SPID would have to be a line attribute. Assess whether the SPID would be a critical requirement. **NEW DELTA?** This item will be discussed on the next conference call.

All

 

13

CNAT Requirements - Request a change to ignore ANI AND CPN and use Billing Account Number provisioned on the trunk instead. **NEW DELTA** Reference is ICC 1330

Debi

 



REVIEW OF PREVIOUS DAYS MEETING

 

LRN issue was not resolved.

 

Need to make the meeting more efficient by staying focused on national level issues.

 

IMPACT OF LNP ON RESALE AND UNBUNDLING Tom Santos

If a call originates from a ported TN from an unbundled switch element or resold line, an originating LNP module is required on the originating AMA. California Delta Item #4 covers this item. FDAF type documents have been submitted to the vendors.

 

When you buy a port and a loop, are you also buying the TNís that go with it. Itís TN by TN, like resale, not a bulk purchase.

 

Leasing facilities is an issue. Is this separate from Unbundling?

 

Which comes first: number ports in, then gets unbundled, or unbundled switching is purchased and then number gets ported in. Does it matter? Is a separate LRN required for the unbundler? Consensus was that the order doesnít matter.

 

At this time, the LRN will belong to the facilities provider. Like resale, the billing system will have to identify that the AMA belongs to an unbundler.

 

SPID will be the solution for the carrier identification problem.

 

Can a local carrier restrict porting in at a given switch? If so, they would be restricting what resellers or unbundlers might want to do.

 

To identify individual ported in TNís that are resold or unbundled will require a 10 digit "guiding" process.

 

Scenario A: Intranetwork call originating from an unbundled ported or resold ported TN

 

 

Scenario B: Inter-network call terminating to an unbundled ported or resold ported TN

 

 

Scenario C: Intranetwork call originating from an unbundled ported or resold ported TN to a LEC

 

 

Scenario D: Internetwork call terminating to a resold ported TN

 

 

Scenario E: Intranetwork/Interswitch call terminating to an unbundled ported TN (local call)

 

 

 

Scenario F: Intranetwork/Intraswitch call terminating to an unbundled ported TN

 

 

Scenario G: Call originating from an unbundled ported or resold ported TN to an IEC

 

 

Scenario H: Operator handled call originating from an unbundled ported or resold ported TN to an IEC

 

 

RESULTS OF DISCUSSION
Unbundling and resale have no incremental impact on LNP. No unique physical change requirements off the network or usage measurements.

 

LRN ISSUE REVISITED

 

 

 

HOST REMOTE (and misc.) Pat Witte

 

NUMBER POOLING Dave Whitney

 

 

 

 

AIN

 

 

 

SPID - SERVICE PROVIDER ID Dave Whitney

 

 

MUTUAL COMPENSATION Jill Blakeley