Wholesale: Products & Services

Archived System CR SCR041504-01 Detail

2. AT&T is also requesting Qwest to investigate their 8XXrecordings. Approximately 10% of 110125 records have an unknown jurisdiction with an Interlata lata code. This also is a large percentage of usage with a lata code. 1% is normal for 8XX traffic to contain a lata code other than unknown.

AT&T is requesting that Qwest populate the correct LATA indicator.

Status History

Project Meetings

Jill Martain/Qwest stated that this request was implemented on August 22nd and that there are no known problems. Sharon Van Meter/AT&T stated that this CR could be closed.

8/17/05 Systems CMP Meeting

Jill Martain - Qwest stated that this CR will deploy on 8/22/05. There were no questions.

3/16/05 Systems CMP Meeting

Jill Martain - Qwest stated that there were two parts to this request. Jill stated that Qwest does not receive the data associated with the 8XX information and is technically not feasible to provide. Jill stated that we could provide the portion of the request asking for the LATA identifier. She also stated that we are currently in the process of providing a targeted implementation date. There were no questions or comments. Jill Martain - Qwest stated that this action item could be closed.

12/15/04 Systems CMP Meeting

Jill Martain/Qwest asked if there were any questions for Attachment J. Sharon Van Meter/AT&T asked for an updated status on #52, #57, #66 and #67. Sharon stated that these CRs are still in a Presented Status and asked if the status should be changed to something else. Jill Martain/Qwest said that these CRs are being worked on even though they are in a presented status and are part of the funding effort that is underway. Jill said that they remain in presented status until the CRs are scheduled and would then move to development status. There were no additional questions or comments.

8/18/04 Systems CMP Meeting

Jill Martain/Qwest stated that the LOE for this CR is 1300 to 1800 hours and that this action item will be closed.

5/20/04 Systems CMP Meeting

Carla Pardee/AT&T reviewed the CR description. Carla stated that approximately 61% of all interstate traffic recorded by Qwest has a lata indicator of 9 (unknown/undetermined). Carla stated that it is a standard obligation for LECs to provide a correct lata indicator. AT&T is requesting Qwest to investigate why such a large percentage of interstate traffic has an unknown lata code. Carla stated that AT&T is also requesting Qwest to investigate their 8XX recordings and that approximately 10% of 110125 records have an unknown jurisdiction with an interlata lata code. Carla said that AT&T is requesting that Qwest populate the correct LATA indicator. Peggy Esquibel-Reed/Qwest stated that the status of this CR is in Presented Status.

5/5/04 Clarification Meeting

Attendees: Carla Pardee - AT&T, Jama Simms - AT&T, Wendy Thurnau - Qwest, Alan Zimmerman - Qwest, Fred Howard - Qwest, Michael Lopez - Qwest, Lynn Stecklein

Review Description of change request Lynn Stecklein/Qwest reviewed the CR description. AT&T stated that Approximately 61% of all interstate traffic recorded by Qwest has a lata indicator of 9 (unknown/undetermined) and it is a standard obligation for LEC’s to provide a correct lata indicator. AT&T is requesting Qwest to investigate why such a large percentage of interstate traffic has an unknown lata code. AT&T is also requesting Qwest to investigate their 8XXrecordings. Approximately 10% of 110125 records have an unknown jurisdiction with an Interlata lata code. This also is a large percentage of usage with a lata code. 1% is normal for 8XX traffic to contain a lata code other than unknown.

AT&T is requesting that Qwest populate the correct LATA indicator.

Discussion Lynn Stecklein/Qwest asked what AT&T's business need is with this CR.

Carla Pardee/AT&T stated that this problem was negatively impacting AT&T's revenue.

Fred Howard/Qwest stated that he will look into AT&T's questions on the 'from' and 'to' NPA NXX issue.

Wendy Thurnau/Qwest stated that Qwest understands the request.

AT&T stated that they will also send examples.

Lynn Stecklein/Qwest stated that she will provide the AT&T Trouble Ticket 579177 history log to the Qwest participants.

Confirm Areas and Products Impacted This is a Wholesale Billing Interface request and impacts UNE-P

Establish Action Plan AT&T will Present this CR in the May CMP Systems Meeting.

Trouble Ticket History 579177 Trouble Ticket # 579177

2/3/2004 1:28:44 PM dxwils4 CASE CLOSURE NOTIFICATION SENT TO CONTACT

1/27/2004 2:34:14 PM plopez I talked with the customer advising if she needs information on the report that is not being provided today she needs to go through the change process with her qwest service manager.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/27/2004 12:36:42 PM dxwils4 I emailed to Jama: "Jama, Here is status from tier 2:

"I've looked at the spreadsheet these are CAT 11 (Access records) examples. The Lata Code appears in Position 100 in the EMI record which is Indicator 19 which in the EMI hand book states:::: indicates that the LATA was not determined. (Valid on Category 11 records only). I'm not sure what else can be done for this customer Qwest is following OBF guidelines and if this customer wants changes it would need to go through OBF.

Talked to Alan Zimmerman again on this issue and he recommends if the customer wants the Lata populated got through the CMP for a Change Request."

Thanks, David WSHD"

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/27/2004 12:28:14 PM abcox Jama requested e-mail of resolution from tier II sent to her e-mail address is=jsims@att.com

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/27/2004 11:37:00 AM dxwils4 I left v/m to client with tier 2 status, asked that she call and let me know that she rec'd my v/m and that I can close this ticket.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/26/2004 7:44:32 AM dklinge 1-26-04 Talked to Alan Zimmerman again on this issue and he recommends if the customer wants the Lata populated got through the CMP for a Change Request.

1/23/2004 10:22:06 AM dklinge 1-23-04 I've looked at the spreadsheet these are CAT 11 (Access records) examples. The Lata Code appears in Position 100 in the EMI record which is Indicator 19 which in the EMI had book states:::: indicates that the LATA was not determined. (Valid on Category 11 records only). I'm not sure what else can be done for this customer Qwest is following OBF guidelines and if this customer wants changes it would need to go through OBF.

1/23/2004 9:40:35 AM dxwils4 email from Jama: "As I stated during our phone conversation. Attached is a sample of the records from Qwest containing a 9 in the lata code for records other than 110125 (800) records.

It is acceptable to receive records from an ILEC with an undetermined lata code for 800 calls. However, for other record types containing to and from #'s, the lata code should be populated with something other than a 9. One exception to this is if the settlement code cannot be determined, then you would see a 9 in the lata code.

As you can see from the attached, there are records types (pos. 1 -6) other than 110125 with a 9 in the lata code, position 100.

Please forward this to your Tier 2 support for resolution. Thanks for your help." ... I attached the doc to email to Deb K.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/22/2004 12:15:58 PM dxwils4 I called the customer, asked her for examples per tier 2. Seeing in 110101 records 110120. She is seeing to and from numbers present. She will email examples to us, I will then add them to this ticket.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/21/2004 2:06:16 PM dklinge 1-21-04 I went to the most recent file today and the only messages that is populating Lata code 9 is in 1101XX. which is valid. Ask the customer for examples of the Lata code that is not going to an 8XX.

1/21/2004 1:44:09 PM dklinge 1-21-04 I have researched and investigated everything about the Lata Code being populated. I have talked to Alan Zimmerman the DUF SME/the PP42 SME on 1101XX messages we either populate a 5 intrastate or a 9 unknown and checked the EMI book regarding what is suppose to be populated in the Lata Code we are populating correctly per the OBF standards. The only thing I can suggest is to have the Customer contact their Service Manager to get clarification. This is not a DUF issue we are processing correctly.

1/21/2004 1:17:33 PM plopez I paged the tier2 with ticket update.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/21/2004 1:17:12 PM plopez the customer said lata code is populated with 9 - unknown.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/21/2004 1:12:20 PM plopez The customer called back. She said there are all different types of records that have unknown and have lata codes. She has records with jurisdiction of interstate with to and from numbers not 800 calls - why can't lata codes be populated?

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/21/2004 12:33:31 PM ckillio Client called stated that she is checking to see if there are more #'s than just the 8xx. Client wants to keep this ticket open until she finds out more information.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/21/2004 11:54:55 AM dxwils4 2nd attempt, I left v/m to client asking if can close ticket or reason to keep open.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/19/2004 2:50:20 PM dxwils4 I left v/m to Jama with tier 2 status, asked that she let me know if can close ticket or reason to keep it open.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/16/2004 6:10:18 AM dklinge 1-16-04 Have verified with that AMA group, Access SME Alan Zimmerman and the EMI handbook. The Lata Code 9 is valid for access records we are not able to determine the Lata code for Interstate calls. These calls are going to an 8XX number and we have no way of determining what the Lata code is.

1/14/2004 1:13:07 PM plopez The customer called back and said 95% of the usage has lata code undetermined. The data has jurisdiction interstate. The lata code is determined by the to and from number - it could be any lata code. I net tooled the tier2. NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/14/2004 12:38:03 PM dxwils4 I left v/m to Jama asking, again, what she expects should be in lata code fields.

NOTES LOG NOTIFICATION SENT TO ASSIGNEE

1/14/2004 11:07:38 AM dklinge 1-14-04 Checking for status

1/13/2004 7:34:38 AM dklinge 1-13 checking for updated status

1/10/2004 7:13:36 AM ARESCALATOR Notification for Business Rule: Moderate 48 hr has been fired

1/9/2004 1:26:04 PM dxwils4 I left v/m to client stating tier 2 status. I asked her to call and let me know what they think should be in lata code fields.

1/9/2004 6:48:44 AM dklinge 1-9-04 Talked to the DUF SME and found that the 202109 headers will stay the same until the new PTID is implemented changing it to 202409's we have no targeted date at this time. In reference to the Lata code 9 what do they think it should be?

1/8/2004 1:03:54 PM dklinge 1-8-04 Pulled the file TOL.#CO.R730.BJ97A02Z.G0179V00 date 1-7-04. Checked position 100 and is populated with 9 which per OBF standards indicates unable to determine the Lata. I also checked the header/trailer and those are correct. I did request validation from Alan Zimmerman and will update this when I get the information.

1/8/2004 8:41:12 AM dxwils4 Kathy left me v/m that this should go to DUF group, assigning to DUF. Debbie K left me v/m to call her so I called her with info rather than net tool.

ASSIGNMENT NOTIFICATION SENT TO CONTACT

ASSIGNMENT NOTIFICATION SENT TO GROUP

1/8/2004 7:06:51 AM dxwils4 I left v/m to Kathy P with all info.

1/8/2004 7:02:31 AM dxwils4 Can Be Reached Number= 770-750-3745 Complete Description of the Problem=2 problems with files. Lata codes are being populated incorrectly on category 11 access records. 95% of usage have lata code of 9, which is unknown, and to and from numbers in the records. Wants the lata codes populated correctly and wants to know why they were not. Header is incorrect. Dataset Name Sent=AF60.USWCO.UNEPC.ACCESS Dataset Name Received=AF60.USWCO.UNEPC.ACCESS Pack Invoice # (header and trailer info)=invoice number of last file rec'd: 202109 is header on files. She says it should be 202409. Invoice # is 39. Create Date=1/7/04 Date Received=1/7/04 Volser # (if tape)=na State or Region=AZ Record Count #=158,740 How they Receive the File=NDM How often they Receive the File=Daily OCN=7963 RAO=153 RSID=A02

E-mail from AT&T 4/15/04 Osborne-Miller, Donna, NEO [dosborne@att.com]

I received as you will read, an explanation of what has happened on this topic and AT&T's need. Perhaps after reading her account(s) you can decide the best route of action: that being the CR process or to work with the account team. I do not know historically if Carla and Liddell conversed about this before we decided to submit a CR. Nonetheless let me be still now and let you read and respond to the path you believe we should take on this topic.

I called in a trouble ticket for this issue back in January. What I reported to Qwest with the trouble ticket was there seems to be a recording problem because a very large % of their usage has an unknown lata code. This is unusual especially if the settlement code can be determined. And the settlement codes were populated. I asked them to look into this.

Their response back to me was they were populating the records with a valid lata code, which is correct, however the lata code is unknown/undetermined. Once again, I asked if the settlement code could be determined why can't the lata code be determined. I explained that it is a standard recording procedures to populate settlement codes/lata codes in the EMI field if they can be determined. I was then told by Qwest that I needed to go through change management to get this fixed. This is only happening in the Qwest states, all other LEC's provide valid lata codes with a settlement code.

This could very well be a recording problems which could require some system/programming changes. Either way, if it the lata can be determined, Qwest is not following the expected recording procedures implemented by the OBF.

As far as the language in the CR, we need to tell Qwest.......... There appears to be a recording problems in all the UNEPC Qwest states. Approx 90% of the usage received from Qwest is populated with an undetermined lata code. Also, for the 8YY recordings it is highly unusual to receive 8YY data with a lata code other than undetermined. Can we tell Qwest that we called in a trouble ticket and were told to go through change management? The ticket number was 579177.

CenturyLink Response

July 20, 2004

RE: SCR041504-01 Provide LATA Identifier in Billing Output (DUF)

Qwest has reviewed the information submitted as part of Change Request SCR041504-01. Based upon the scope of this CR as agreed to in the Clarification Meeting (held May 5, 2004) Qwest is able to provide an estimated Level of Effort (LOE) of 1300 to 1800 hours for this Wholesale Billing Interface Change Request.

At the next Monthly Systems CMP Meeting, CMP participants will be given the opportunity to comment on this Change Request and provide additional clarifications. Any clarifications and/or modifications identified at that time will be incorporated into Qwest’s further evaluation of this Change Request. Upon obtaining consensus from CMP participants as to the appropriate direction for Qwest to take on this Change Request, Qwest will review release schedules and development timetables in an effort to evaluate options for potential scheduling of Change Request SCR041504-01.

Sincerely, Qwest