Wholesale: Products & Services

Archived System CR SCR070804-02 Detail

Expected Deliverable:

AT&T would like a parsed and structured CSR for Trunks. We would like to see the Trunk "Telephone Numbers" displayed in the WTN Feature and Feature Detail section like the format presented in IMA 14.0.

IMPACTED PRODUCTS - CONFIRMED DURING 7/16/04 CLARIFICATION CALL:

IN SCOPE:

UNE-P DSS Trunks

UNE-P ISDN PRI Trunks

UNE-P PBX Trunks

UNE-P PBX DID Trunks

REQ TYPE: MB for SCR070804-02 Products noted above

ACT TYPE is not applicable for Pre-Order

OUT of SCOPE:

Analog Line Side Port / REQ TYPE: FB

DID/PBX Trunk Port Facility / REQ TYPE: FB

Digital Line Side Port / REQ TYPE: FB

Analog Trunk Port / REQ TYPE: FB

DS1 Trunk Port / REQ TYPE: FB

Enhanced Extended Loop (EEL) / REQ TYPE: MB

Facility Based Directory Listings (FBDL) / REQ TYPE: JB

Interim Number Portability (INP) / REQ TYPE: CB

Line Sharing/Shared Loop / REQ TYPE: AB

Listings Only / REQ TYPE: HB

Local Number Portability (LNP) / REQ TYPE: CB

Resale - Centrex 21 / REQ TYPE: PB

Resale - Centrex Plus & Centron / REQ TYPE: PB

Resale - DID Trunks / REQ TYPE: KB

Resale - Frame Relay Service (FRS)/ REQ TYPE: EB

Resale - ISDN BRI / REQ TYPE: EB

Resale - ISDN PRI Facility / REQ TYPE: KB

Resale - ISDN PRI Trunks / REQ TYPE: EB

Resale - PAL / REQ TYPE: EB

Resale - PBX Trunk Service / REQ TYPE: EB

Resale - PBX Trunk Service - Designed / REQ TYPE: EB

Resale - POTS / REQ TYPE: EB

Resale - Private Line Transport (PLT) - Non-switched / REQ TYPE: KB

Resale - Qwest DSL / REQ TYPE: EB

Unbundled Distribution Loop (UDL) / REQ TYPE: AB

Unbundled Distribution Loop (UDL)-Local Number Portability (LNP) / REQ TYPE: AB

Unbundled Feeder Loop (UFL) / REQ TYPE: AB

Unbundled Local Loop / REQ TYPE: AB

Unbundled Local Loop Split / REQ TYPE: UB

Unbundled Local Loop-Local Number Portability (LNP) / REQ TYPE: BB

UNE-P/STAR - Centrex 21 / REQ TYPE: MB

UNE-P /STAR- Centrex 21 Split / REQ TYPE: SB

UNE-P/STAR - Centrex Plus and UNE-P - Centron / REQ TYPE: MB

UNE-P - DSS Facility / REQ TYPE: MB

UNE-P - ISDN BRI / REQ TYPE: MB

UNE-P - ISDN PRI Facility / REQ TYPE: MB

UNE-P - PBX Trunks Split / REQ TYPE: MB

UNE-P/STAR-POTS / REQ TYPE: MB

UNE-P - POTS Split / REQ TYPE: SB

Status History

Project Meetings

- August 16, 2004 Email Received from AT&T: Hi Peggy, I received an email from Bill Micou Friday evening. AT&T will withdraw both our CR's that we had submitted that dealt with a parsed and structured CSR for Centrex and for Trunks. The CR numbers are:SCR070804-01 (Centrex) and SCR070804-02 (Trunks). Thank you, Donna

- August 9, 2004 Voicemail Received from Donna at AT&T: "AT&T is still not ready for a subsequent call to discuss Parsed & Structured CSRs for Trunks and for Centrex. AT&T is still discussing internally in order to determine if the CRs are to move forward or if AT&T will withdraw the CRs.

- August 3, 2004 Email Received from AT&T: Hello Peggy, I am still waiting for Bill and Regina to respond to meeting availability. I hope to let you know that tomorrow or Wednesday. Will contact you as soon as I hear back from Regina or Bill. Thank you, Donna

August 3, 2004 Email Sent to AT&T: Donna, SCR070804-01 Parsed and Structured CSR for Centrex SCR070804-02 Request for a parsed and structured CSR for Trunks This is a follow-up to see if AT&T is ready to meet with Qwest in order to discuss the CRs noted above. Would you please send me the following: - The completed form that contains the Directory Listings fields for your request for ‘Trunks’ CR (this is the form that Lynn sent you on July 27, 2004) - Your availability for a meeting to discuss and clarify. Thanks, Donna. We will then be able to move forward with the evaluation of these CRs. Peggy Esquibel-Reed Qwest CMP CRPM-Systems

- July 28, 2004 Email Received Copy of an Email from AT&T:

I just got a call from Qwest and they are needing the parsed and structured Directory Listings fields we seek for this CR. Qwest would like AT&T to fill out this attached form in the same manner as was done previously for a former candidate. They found this detail to be quite helpful in meeting our needs before. We need to have this information today, and back to Qwest for the call tomorrow. Otherwise they will postpone the call until next week. Lynn, have I stated Qwest's request correctly? Bill. Regina, I am out of the office this afternoon. Carla Pardee is my back-up. Please pass the required information back to Carla, and she will get it to Lynn today. If we are not able to populate this form for them, will you let Carla know that. She will then negotiate the next dates of availability for the call in that is needed. Sorry for the last minute request. Thank you, Donna

- July 27, 2004 Email Received from AT&T: Lynn, Here is information for our call on Thursday. Thank you. Donna This is trunk-level detail information. Of course, in addition to this, we would need to see account-level information about the account as well as (such as AN, Service Address, etc. -- similar fields as would be sent at the account-level on a POTS parsed CSR). In addition to the change to get the TN parsed and the USOCs subordinate to the TN, I would like to see the following Trunks data parsed as well: DID Numbers TERs Route Index Hunt ID and Multi-line Hunt ID PIC LPIC TLI ECCKT Trunk ID Trunk Group Number Start Signaling Digits Out Pulse Signaling

-- July 27, 2004 Email Sent to AT&T: Hi Donna, I am sending the attached document to request additional information associated with SCR070804-02 (Request for a parsed and structured for Trunks). We are looking for what fields you are requesting on this CR. AT&T previously provided this information on SCR022703-04 Support of Parsed and Structured CSR and we found it very helpful. Do you think you would be able to provide this information before our call on Thursday? Let me know. Thanks, Lynn

-- July 26, 2004 Email Received from AT&T: I did not get a message from Bill Micou. Now it is very possible that they will write to me (Regina and Bill) early in the morning. I did not know if you penciled us in for tomorrow. If not Lynn, can you give me dates and times. Here is Bill and Regina's times that they cannot be on a call for the week of July 26th up to and including the 30th of July: The times below are depicted as Eastern Time! When you are looking at the calendar, can you check Qwest SME availability for next week and if need be, the following week? Thank you, Donna

July 26, 2004 Voicemail Received from Donna at AT&T: "Will send a memo with AT&Ts availability and needs to revisit the intent and language. Regina sent examples for Centrex, however, as it appears when you read her memo, that AT&T Business may be in better shape as AT&T has a Parsed understanding of Centrex, so it looks like AT&Ts greater need is for Trunks and might be asking for a Late Adder for Trunks. Also need to talk about Parsed and Structure for Directory Listings for Trunks. Could be a new CR of a separate CR."

July 22, 2004 Systems CMP Meeting Discussion: Donna Osborne-Miller/AT&T stated that AT&T has 2 similar CRs, for Centrex and for Trunks, items 1 and 2 in Attachment B. Donna reviewed the CR descriptions. Connie Winston/Qwest noted that AT&T knows how much trouble we have with Centrex, it doesn’t fit the parsed and structured model and the CLECs that worked with Centrex agree it shouldn’t be changed. Donna Osborne-Miller/AT&T stated that the Clarification Call had been held and that AT&T had submitted revisions to the CRs. Peggy Esquibel-Reed/Qwest stated that the revisions were received and that a follow-up call would be scheduled with AT&T to discuss the changes to the CRs. Liz Balvin/MCI asked why the REQ TYPE comes into play. John Gallegos/Qwest explained that this is one piece of information that Qwest is starting to ask for in order to better clarify the request. John Gallegos/Qwest stated that these CRs are for IMA Common. Jill Martain/Qwest stated that the CRs would move to Presented Status.

- July 21, 2004 Email Sent to AT&T: Regina, In response to your question on the Trunks CR Late Adder vs. the Centrex CR; you can invoke the Late Adder process on any IMA CR that did not make the timeframe for the upcoming vote. We will need to go forward with the vote, and then we will start the Late Adder Process with the vote being in the August Systems CMP Meeting. Please advise me of your availability for a follow-up call. Thanks Much, Peggy Esquibel-Reed Qwest CMP Systems CRPM

July 20, 2004 Email Received from AT&T: Peggy, It looks like we may need to make some tweaks to the Centrex and Trunk CR's based on the clarifications I received from the AT&T SME's. CENTREX After more investigation, we are pretty satisfied with the way in which we receive the CSR for Centrex. The only clarification we would like to request is in regards to the TOS. Currently, this information is provided at the account level only so our interpretation is that all the TNs within the account have the same TOS. Can there be a mixed Type of Service (or class of service accounts) at the line level? If so, then we would like the TOS field parsed at the line level. This is our only requirement for Centrex Parsed CSR. TRUNKS Please see the attached example CSR for Trunks. It currently displays the CSR in a pre-14.0 format. AT&T Business would like to see the format parsed in the following way: TN 1/TER 1 PIC, LPIC, TLI, CLT (i.e. ECCKT), TGP (trunk group number), RTI (route index), SST (start signaling type), USDO (DID digits out, TPL (pulse type), Hunting USOCs, etc. (whatever is currently being passed as floating FIDs on the USOC). TN 1/TER 2 PIC, LPIC, TLI, CLT (i.e. ECCKT), TGP (trunk group number), RTI (route index), SST (start signaling type), USDO (DID digits out, TPL (pulse type), Hunting USOCs, etc. (whatever is currently being passed as floating FIDs on the USOC). TN1/TER 3.......etc. AT&T Business would like to see listings parsed for Trunks only. This would follow the same format that was provided in SCR103103-01 for TN based products. The main listing loop would repeat LFIDNUM of times and the SLN loops would be presented to show that they are part of the LML. Let me know if you need additional information and examples. Donna and Peggy, since the Centrex CSR is in better shape than anticipated, can we submit the Trunks parsed CSR as an exception for 17.0 rather than Centrex? Regina Mosley AT&T Business - Systems Analyst

- July 19, 2004 Email Received from AT&T: Peggy, I did not receive confirmation from the AT&T Trunks and Centrex SME's regarding the requirements for parsing out the CSR's. They are reviewing and providing comments, therefore, the close of business date today I had given you to supply the examples will not be met. I understand that the follow up clarification call will probably need to be moved, but I want to make sure that I provide you with the correct requirements for parsing the Centrex and Trunks CSR. Hopefully, I will have their comments by COB tomorrow. Thank you. Regina Mosley AT&T Business - Systems Analyst

Clarification Meeting-July 16, 2004 SCR070804-01 Parsed and Structured CSR for Centrex SCR070804-02 Request for a Parsed and Structured CSR for Trunks

Introduction of Attendees: Donna Osborne-Miller-AT&T, Regina Mosley-AT&T, Peggy Esquibel-Reed-Qwest, John Gallegos-Qwest, Susie Wells-Qwest, Conrad Evans-Qwest, Sami Hooper-Qwest, Paul Johnson-Qwest

Review Requested (Description of) Change and Discussion: SCR070804-01 Peggy Esquibel-Reed-Qwest reviewed the CR Description and Expected Deliverable. AT&T Business requests a parsed and structured CSR to be implemented for Centrex; in the same manner as SCR022703-04 Support of Parsed and Structured CSR for TN based products. Currently, the Qwest retail CSR for Centrex displays the data in the S&E Major Heading Section. AT&T gets the USOC and the Feature Detail, but the "Telephone Number" is not specifically identified, It is embedded in the Feature Detail of the USOC. Peggy stated that the expected deliverable is that AT&T would like a parsed and structured CSR for Centrex. AT&T would like to see the Centrex "Telephone Numbers" displayed in the WTN Feature and Feature Detail section like the format presented in IMA 14.0.

SCR070804-02 AT&T Business requests a parsed and structured CSR to be implemented for Trunks in the same manner as SCR022703-04 Support of Parsed and Structured CSR for TN based products. Currently, the Qwest retail CSR for Trunks displays the data in the S&E Major Heading Section. AT&T gets the USOC and the Feature Detail, but the "Telephone Number" is not specifically identified, It is embedded in the Feature Detail of the USOC. Peggy stated that the expected deliverable is that would like a parsed and structured CSR for Trunks. AT&T would like to see the Trunk "Telephone Numbers" displayed in the WTN Feature and Feature Detail section like the format presented in IMA 14.0.

Meeting Discussion: Donna Osborne-Miller-AT&T asked what the process was if other CLECs wanted to add other products to the CRs. John Gallegos-Qwest stated that an action item would be taken for Qwest to determine what the impacts to the LOE would be, and then would provide the information at a CMP Meeting. Donna Osborne-Miller-AT&T asked if Qwest would provide both an LOE for the originator’s requested products and an LOE for the additional products. Donna also asked if the decision to include or exclude the additional requested products would be made by the CRs originating CLEC. John Gallegos-Qwest stated yes, two LOE’s could be provided, and noted that the timing of the request for additional products should also be a factor to the inclusion or exclusion decision. Susie Wells-Qwest asked for clarity of the sentence "We would like to see the Centrex "Telephone Numbers" displayed in the WTN Feature and Feature Detail section like the format presented in IMA 14.0" for pre-order. Regina Mosley-AT&T stated that she thought that she received an email stating that the TN information on Centrex and Trunk Products was not at the WTN Level and that it was displayed in the S&E Level. Regina asked if that was not true. Susie Wells-Qwest stated that she just needed to make sure that she understood the request correctly. Regina Mosley-AT&T stated that with 14.0, now have the information at the WTN Level; have the features and USOCs associated to the Product’s. Regina stated that she is seeing the TNs in the pre-14.0 format and wants what they currently see with the 14.0 CR, which covered TN based products. Sami Hooper-Qwest asked for the Trunk piece, if is DID with most trunks having the same TN, is AT&T needing DID2 or DID3 and their features; such as DID TNs themselves. Sami stated that she is asking because Qwest does not know how they could be aligned due to the fact that they are aligned with the PBX. Regina Mosley-AT&T stated that they are looking to have detail in a parsed structure at that level. Regina stated that it would then have TN1, TN2, etc. Sami Hooper-Qwest stated that if is DID and for example has a group of 20 number’s, would AT&T consider that a feature of the trunk number. Regina Mosley-AT&T asked if Qwest would group the Trunk Group together. Sami Hooper-Qwest stated that if trunk, needs the RTI index. John Gallegos-Qwest stated that due to the issues with the previous candidates, he would like an example of what AT&T is looking for at the trunk perspective. John asked if AT&T could provide a mock CSR. Regina Mosley-AT&T stated that she would provide what she is looking at and an example of what AT&T is asking for. John Gallegos-Qwest stated that the examples and mock-up would give Qwest a good base to go from. Regina Mosley-AT&T agreed and stated that examples are good and stated that she would provide them to Peggy (Esquibel-Reed-Qwest) directly. John Gallegos-Qwest asked if the expectation is that Qwest would get the examples, from AT&T, and then have another conference call to discuss. Peggy Esquibel-Reed-Qwest stated that once the information was received, a follow-up call would be scheduled. Conrad Evans-Qwest stated that examples for both CRs, Centrex and Trunks, were needed. Susie Wells-Qwest stated that the Feature Detail, of the S&E Detail, contains the WTN that AT&T is looking for. Regina Mosley-AT&T stated that was correct. Susie Wells-Qwest asked that if the information is already there, would it make it easier if was in the WTN Field. Regina Mosley-AT&T stated that AT&T has developed coding for the other products and the coding for the specific products on these CRs has to be different. Conrad Evans-Qwest asked if AT&T is seeing the bills but that the data is not populated. Donna Osborne-Miller-AT&T stated that they do see the field but it is not populated. Regina Mosley-AT&T stated that they see it in the pre-14.0 structure, for Centrex Products. Conrad Evans-Qwest asked if the requests included the Listing Section. Regina Mosley-AT&T stated that AT&T Business does not have Listing information parsed out. Regina stated that the CRs do not impact the Listing Section. There were no additional questions or comments. Confirmed Impacted Area(s): Peggy Esquibel-Reed-Qwest asked to confirm that the impacted area is for Pre-Order only for both SCR070804-01 and SCR070804-02. Regina Mosley-AT&T responded yes, Pre-Order only for both CRs.

Confirmed Impacted Interfaces: Peggy Esquibel-Reed-Qwest asked to confirm that this was a request for IMA EDI only. Donna Osborne-Miller-AT&T stated that it should be IMA Common. John Gallegos-Qwest stated that IMA Common would be more appropriate. Peggy Esquibel-Reed-Qwest stated that she would make the change to the CR.

Confirmed Impacted Products: Peggy Esquibel-Reed-Qwest asked to confirm the impacted products. The In-Scope and Out-of-Scope Product Lists are as follows:

SCR070804-01 IN SCOPE: UNE-P Centrex 21 REQ TYPE: MB ACT TYPE is not applicable for Pre-Order

SCR070804-01 OUT of SCOPE: Analog Line Side Port / REQ TYPE: FB DID/PBX Trunk Port Facility / REQ TYPE: FB Digital Line Side Port / REQ TYPE: FB DS0/Analog Trunk Port / REQ TYPE: FB DS1 Trunk Port / REQ TYPE: FB Enhanced Extended Loop (EEL) / REQ TYPE: MB Facility Based Directory Listings (FBDL) / REQ TYPE: JB Interim Number Portability (INP) / REQ TYPE: CB Line Sharing/Shared Loop / REQ TYPE: AB Listings Only / REQ TYPE: HB Local Number Portability (LNP) / REQ TYPE: CB Resale - Centrex 21 / REQ TYPE: PB Resale - Centrex Plus & Centron / REQ TYPE: PB Resale - DID Trunks / REQ TYPE: KB Resale - Frame Relay Service (FRS)/ REQ TYPE: EB Resale - ISDN BRI / REQ TYPE: EB Resale - ISDN PRI Facility / REQ TYPE: KB Resale - ISDN PRI Trunks / REQ TYPE: EB Resale - PAL / REQ TYPE: EB Resale - PBX Trunk Service / REQ TYPE: EB Resale - PBX Trunk Service-Designed / REQ TYPE: EB Resale - POTS / REQ TYPE: EB Resale - Private Line Transport (PLT) - Non-switched / REQ TYPE: KB Resale - Qwest DSL / REQ TYPE: EB Unbundled Distribution Loop (UDL) / REQ TYPE: AB Unbundled Distribution Loop (UDL)-Local Number Portability (LNP) / REQ TYPE: AB Unbundled Feeder Loop (UFL) / REQ TYPE: AB Unbundled Local Loop / REQ TYPE: AB Unbundled Local Loop Split / REQ TYPE: UB Unbundled Local Loop-Local Number Portability (LNP) / REQ TYPE: BB UNE-P /STAR- Centrex 21 Split / REQ TYPE: SB UNE-P/STAR - Centrex Plus and UNE-P-Centron / REQ TYPE: MB UNE-P - DSS Facility / REQ TYPE: MB UNE-P - DSS Trunks / REQ TYPE: MB UNE-P - ISDN BRI / REQ TYPE: MB UNE-P - ISDN PRI Facility / REQ TYPE: MB UNE-P - ISDN PRI Trunks / REQ TYPE: MB UNE-P - PBX Trunks / REQ TYPE: MB UNE-P - PBX Trunks Split / REQ TYPE: MB UNE-P - PBX/DID Trunks / REQ TYPE: MB UNE-P/STAR-POTS / REQ TYPE: MB UNE-P - POTS Split / REQ TYPE: SB

SCR070804-02 IN SCOPE: UNE-P DSS Trunks UNE-P ISDN PRI Trunks UNE-P PBX Trunks UNE-P PBX DID Trunks REQ TYPE: MB for SCR070804-02 Products noted above ACT TYPE is not applicable for Pre-Order

SCR070804-02 OUT of SCOPE: Analog Line Side Port / REQ TYPE: FB DID/PBX Trunk Port Facility / REQ TYPE: FB Digital Line Side Port / REQ TYPE: FB Analog Trunk Port / REQ TYPE: FB DS1 Trunk Port / REQ TYPE: FB Enhanced Extended Loop (EEL) / REQ TYPE: MB Facility Based Directory Listings (FBDL) / REQ TYPE: JB Interim Number Portability (INP) / REQ TYPE: CB Line Sharing/Shared Loop / REQ TYPE: AB Listings Only / REQ TYPE: HB Local Number Portability (LNP) / REQ TYPE: CB Resale - Centrex 21 / REQ TYPE: PB Resale - Centrex Plus & Centron / REQ TYPE: PB Resale - DID Trunks / REQ TYPE: KB Resale - Frame Relay Service (FRS)/ REQ TYPE: EB Resale - ISDN BRI / REQ TYPE: EB Resale - ISDN PRI Facility / REQ TYPE: KB Resale - ISDN PRI Trunks / REQ TYPE: EB Resale - PAL / REQ TYPE: EB Resale - PBX Trunk Service / REQ TYPE: EB Resale - PBX Trunk Service-Designed / REQ TYPE: EB Resale - POTS / REQ TYPE: EB Resale - Private Line Transport (PLT) - Non-switched / REQ TYPE: KB Resale - Qwest DSL / REQ TYPE: EB Unbundled Distribution Loop (UDL) / REQ TYPE: AB Unbundled Distribution Loop (UDL)-Local Number Portability (LNP) / REQ TYPE: AB Unbundled Feeder Loop (UFL) / REQ TYPE: AB Unbundled Local Loop / REQ TYPE: AB Unbundled Local Loop Split / REQ TYPE: UB Unbundled Local Loop-Local Number Portability (LNP) / REQ TYPE: BB UNE-P/STAR - Centrex 21 / REQ TYPE: MB UNE-P /STAR- Centrex 21 Split / REQ TYPE: SB UNE-P/STAR - Centrex Plus and UNE-P-Centron / REQ TYPE: MB UNE-P - DSS Facility / REQ TYPE: MB UNE-P - ISDN BRI / REQ TYPE: MB UNE-P - ISDN PRI Facility / REQ TYPE: MB UNE-P - PBX Trunks Split / REQ TYPE: MB UNE-P/STAR-POTS / REQ TYPE: MB UNE-P - POTS Split / REQ TYPE: SB

Establish Action Plan & Resolution Time Frame: CR is due for presentation at the July 22, 2004 Systems CMP Meeting.

-- July 13, 2004 Email Sent to Donna at AT&T: Hi Donna, Can you provide me with your availability for the Clarification Call? Thanks, Peggy Esquibel-Reed Qwest CMP CRPM-Systems

-- July 9, 2004 Email Sent to Donna, Regina, & Carla at AT&T: Donna, SCR070804-01 Parsed and Structured CSR for Centrex SCR070804-02 Parsed and Structured CSR for Trunks Please advise of your availability for a Clarification Meeting. We can discuss both CRs, noted above, on one call, if that is agreeable to you. Several dates and times would be great. I will then schedule the meeting and send the call-in information.

Thanks, Peggy Esquibel-Reed Qwest CMP CRPM-Systems

CenturyLink Response

August 12, 2004

RE: SCR070804-02 Request for Parsed and Structured CSR for Trunks

Qwest has reviewed the information submitted as part of Change Request SCR070804-02. The Clarification Call was held on July 16, 2004 and additional information is pending from AT&T. Qwest will continue to examine the issue, upon receipt of the information.

Sincerely, Qwest