OBF Issues 2241 and 2308 Bill Krall (732) Copyright © 2002 Telcordia Technologies All Rights Reserved Prepared For: November 2002 OBF Billing Committee Meeting Montreal, Canada An Company

OBF / Nov 2002 – 2 OBF Issue 2241 (CIC in ISUP) Recording changes to support billing due to changes in MECAB Issue 7 This issue has [at least] two separate aspects 1. Recording [originating] calls bound for an IXC at a tandem switch incoming on a [super] trunk group provisioned as CNA 2. Recording incoming access calls at an end office switch [on a CNA trunk group] that have transited a tandem Challenge is to identify the incoming calls as access calls [from an IC] vs. intraLATA/local calls

OBF / Nov 2002 – 3 OBF Issue 2241 Originating Recording at Access Tandem LEC ‘B’ SSP IXC-2 POP S W C LEC ‘A’ AT End User-B End User-C CNA Trunk Group CNA “Super” Trunk Group Dedicated IXC Trunk Group Common Access Trunk Group IXC-1 POP S W C Pending Generic Requirements Change TNS present generates CTC 110 CTC 720 SSP CTC 720 AMA SSP End User-A AMA LEC ‘A’ CTC 720 if TNS not present CNA TGs Provisioned independently by both LECs - Billing Number - Interconnecting Network Code [CIC] - LRN

OBF / Nov 2002 – 4 OBF Issue 2241 Originating Recording at Access Tandem 1.Recording [originating] calls at a tandem switch incoming on a CNA [super] trunk group that are bound for an IXC, the tandem provider could request that the switch vendors capture the routing CIC contained in the TNS parameter in incoming signaling –Would not require changes to SS7 protocol –Would require an AMA changes at the tandem This AMA change would allow the tandem provider to record the equivalent of an originating end office FGD record at the tandem and eliminate the need to rely on end office recordings from end offices that do not belong to the tandem company Proposal will work with Equal Access MF signaling

OBF / Nov 2002 – 5 OBF Issue 2241 Terminating Recording at End Office LEC ‘B’ SSP IXC-2 POP S W C LEC ‘A’ AT End User-B End User-C CNA “Super” Trunk Group Dedicated IXC Trunk Group Common Access Trunk Group IXC-1 POP S W C Potential Requirements Change CTC 119 Tandem populates ISUP with CIP + Ind SSP CTC 720 when CIP + Ind is not present SSP End User-A LEC ‘A’ CNA TGs Provisioned independently by both LECs - Billing Number - Interconnecting Network Code [CIC] - LRN CTC 119 when CIP + Ind is present

OBF / Nov 2002 – 6 OBF Issue 2241 Terminating Recording at End Office 2.Recording incoming access calls at an end office switch [on a CNA trunk group] that have transited a tandem requires changes that are more significant ISUP parameter is needed to convey the CIC of the incoming IXC to the EO –The CIP is not present in the signaling from an IXC on a terminating call –Call processing at the tandem switch would have to be modified to do the following: Modify call set-up to populate the IAM in forward signaling with the CIC provisioned on the incoming TG from the IXC Add a parameter [e.g., CIP] to the incoming ISUP IAM to pass the newly generated CIC information –End office call processing would then have to be programmed to recognize the CIP [and perhaps another indicator denoting] on calls incoming over a CNA TG, and either Generate a CTC 720 populated with CIP plus some indication that this is an access call, or Add the capability to generate a CTC 119 on a CNA trunk group incoming from a tandem when the CIP [and probably an indicator] is present Proposal does NOT work for MF trunking arrangements

OBF / Nov 2002 – 7 OBF Issue 2241 Summary From Telcordia’s perspective, recording originating calls at an Access Tandem that are being routed from an End Office to an IXC can be addressed by AMA generic requirements independent of other call processing considerations (e.g., SS7 changes) Recording terminating calls at a terminating end office with the proper CIC that have come from an IXC POP and have been routed through an Access Tandem requires changes to call processing and signaling beyond AMA. –Signaling changes need to precede any AMA requirements update

OBF / Nov 2002 – 8 OBF Issue 2241 (CIC in ISUP) Telcordia’s Plan Telcordia is in the process of developing Issue 4 of GR CORE, Generic Requirements for Exchange Access Automatic Message Accounting (AMA) (FSD ) Due out January 2003 Issue 4 will include generic requirements that address originating recording at the tandem for calls to IXCs Issue 4 will not address the terminating end office recording requirements for calls that have transited a tandem –The GR can only be modified after the industry adopts whatever SS7 protocol change is developed by T1S1.3 to address sending the CIC of the IXC from an Access Tandem to an End Office for a terminating call

OBF / Nov 2002 – 9 OBF Issue 2308 (JIP) Discussion Telcordia representative (Maria Elshamy) and ATS representative (Ken Babcock) agreed to approach the AMATSG for assistance in populating JIP in the AMA recordings At the last OBF some questions were posed that Telcordia AMA would like to comment on: –Can both the originating and terminating JIP be passed through the network? –How can JIP be captured in the AMA recordings? –Are additional fields available (to include intermediate JIPs)? –Is the lack of specific guidelines part of the problem?

OBF / Nov 2002 – 10 OBF Issue 2308 (JIP) Telcordia AMA’s Perspective Considerations on JIP –JIP is incapable of handling both a jurisdictional role and a switch identification role given the way LRNs are assigned. –To work the way OBF wants it to work, at least one LRN per state [per LATA] served must be assigned in each switch and the switch must be programmed to use the appropriate LRN to populate the 6-digit JIP in the IAM for each call. –Given the LRN assignment guidelines, JIP cannot do both roles and, in our opinion, is presently suited to only one, namely the one it was designed and named for – identifying jurisdiction. –To identify the switch, a separate parameter is needed