Docstoc

Idaho Business Yellow Page Listings

Document Sample
Idaho Business Yellow Page Listings Powered By Docstoc
					Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                 Product or DWS     Field # or     Software     Date                                                                   Date
Q#      Status        Form            Name          Vendor     Opened                      Issue/Question                            Answered                  Resolution/Answer
                                                                        Phyllis Burt, AT&T: LNLN & LNFN fields - The
                                                                        special character %(percentage) was only valid in the
                                                                        Eastern Region.          For IMA 16.0 it states:     -
                                                                        Not valid as 1st character in Eastern Region – Only
                                                                        used in business listings (TOA=B) in Eastern Region-
                                                                        Requires PLA if to be used for alphabetizing in
                                                                        Eastern Region What is the impact to the Central &
                                                                        Western Regions? Is QWEST stating that                                  The % symbol is valid in all regions for business
                                                                        percentage is valid in the Central & Western Region                     (TOA=B) listings only. The limit in Eastern is not
                                  DL: 44-LNLN AT&T                      for both business and residential listings (TOA = R or                  allowing the % in the 1st character, where Central
     1 Closed    App C: DL        & 45-LNFN Consumer            8/24/04 B)?                                                              9/3/04 and Western do.

                                                                        Phyllis Burt, AT&T: Appendix J (Section1.1
                                                                        Directory Listings)under LACT=Z, it currently states
                                                                        “Since the LML is required for all orders, the LACT=Z
                                                                        is required when there is no change to the LML and it
                                                                        is only being recapped. “ Please update since this is
                                                                        no longer true based on the IMA 14.0 implementation
                                                  AT&T                  of SCR040403-01 System Generate LML for                                 Question was withdrawn for 16.0 and submitted to
     2 Closed    App J            Section 1.1     Consumer      8/24/04 additional listing only changes.                                 9/3/04 the IMA EDI 15.0 Question and Answer log.
                                                                        Phyllis Burt, AT&T: Appendix J (Section 1.2.2 Local
                                                                        Number Portability) Under ACT=Z it previously
                                                                        stated, “An ACT entry of Z will retain the current
                                                                        Listing(s)”. It has been updated with this release to
                                                                        state “An ACT entry of Z will discontinue the
                                                                        Listing(s) associated with the Port Activity (all listings
                                                                        are removed)” Is this correct? If so, please explain
                                                                        the difference between ACT=V vs ACT=Z? Follow-                          Qwest is revising Appendix J to reflect the
                                                AT&T                    up Question from CLEC Walkthrough: Does this                            difference between ACT=Z and ACT=V. Qwest will
     3 Closed    App J            Section 1.2.2 Consumer        8/24/04 mean that Qwest will not be retaining listings?                  9/3/04 retain the listings.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                    Page 1 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                 Product or DWS     Field # or    Software     Date                                                               Date
Q#      Status        Form            Name         Vendor     Opened                      Issue/Question                        Answered                 Resolution/Answer

                                                                       Phyllis Burt, AT&T: Appendix J (Section 1.8.8
                                                                       UNEP POTS) under ACT=V states the following:
                                                                       “Change LSP with only a Listing Change” use an
                                                                       LNA=X and “Change LSP with only a PIC Change”
                                                                       use LNA=P. There have been several CRs, over the
                                                                       last several IMA releases to get away from
                                                                       comparing our order to what is currently on the
                                                                       customer‟s account (CSR) to only specifying the end
                                                                       state. This seems like a step backwards. What CR is
                                                                       driving this change? AT&T doesn‟t want to perform
                                                                       this comparison. Will QWEST continue to support                     LNA=N is still valid for end-state for post
                                                                       LNA=N where we specify everything even when                         conversion. CLECs may alternatively choose to
                                                AT&T                   there‟s only a listing change or Pic change on an                   use LNA=X for each line and receive recap as
     4 Closed    App J            Section 1.8.8 Consumer       8/24/04 ACT=V? Or will QWEST reject these orders?                    9/3/04 necessary.

                                                                       Phyllis Burt, AT&T:             Appendix J (Section
                                                                       1.8.8 UNEP POTS) under ACT=C states the
                                                                       following: “(The LNA of X should be used if only the
                                                                       listing is changing. The LNA of P should be used if
                                                                       only the PIC/LPIC is changing)” Under LNA=X it still
                                                                       states the following          “This LNA should only be
                                                                       used for Number Changes without any other activity.
                                                                       FA entries would not be appropriate. If Number
                                                                       Changes occur with other activity, an LNA=C should
                                                                       be used.”                 Is this a typo under
                                                                       ACT=C? Can we still send a TN only change using
                                                AT&T                   an LNA=X along with the DL form (LACT = I & O) to
     5 Closed    App J            Section 1.8.8 Consumer       8/24/04 indicate the change in LTN?                                  9/3/04 LNA=X can only be used for TN changes.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                             Page 2 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                 Product or DWS     Field # or     Software     Date                                                                 Date
Q#      Status        Form            Name          Vendor     Opened                       Issue/Question                         Answered                 Resolution/Answer

                                                                        Phyllis Burt, AT&T:              Appendix J (Section
                                                                        1.8.8 UNEP POTS) under LACT=Z it states the
                                                                        following: “Only allowed on a conversion as specified
                                                                        (ACT = V), change order (ACT=C), or an outside
                                                                        move (ACT= T). The DL form must indicate the ALI
                                                                        code (if not a main list) and RTY for the listing to
                                                                        remain the same, along with the listing name and text
                                                                        information to ensure the correct listing is referenced.
                                                                        Where the RTY = LML and no change is occurring to
                                                                        the Main listing then it must be recapped if the
                                                                        Directory Listing From is sent.                  For
                                                                        ACT= C only listings that are changing are required.
                                                                        The recap of the LML is no longer required due to
                                                                        SCR040403-01. For ACT=T all listings are sent as
                                                AT&T                    new (LACT=N)                          References to                   Question was withdrawn for 16.0 and submitted to
     6 Closed    App J            Section 1.8.8 Consumer        8/24/04 ACT of C & T should be removed.                                9/3/04 the IMA EDI 15.0 Question and Answer log.
                                                                        Phyllis Burt, AT&T:                  LTN field on the
                                                                        DL Form, the Valid Values column states
                                                                        “Products 1, 3, 8, 9, 9a, 10, 11, 12, 13, 14, 16, 17,
                                                                        18, 20, 21, 25, 28, 29, 30, 31, 33, 34, 35, 37, 38, 39:
                                                                        1st 12 characters of EU.AN according to business
                                                                        rules. Dashes required in positions 4 and 8.”
                                                                        This is a little misleading the LTN will not equal the
                                                                        EU.AN for all cases. For example, the LTN can be
                                                  AT&T                  equal the WTN or BTN of a multi-line account. This                    Question was withdrawn for 16.0 and submitted to
     7 Closed    App C: DL        DL: 38-LTN      Consumer      8/24/04 statement should be removed.                                   9/3/04 the IMA EDI 15.0 Question and Answer log.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 3 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                 Product or DWS     Field # or     Software     Date                                                                Date
Q#      Status        Form            Name          Vendor     Opened Phyllis Burt, AT&T:     Issue/Question on the EU
                                                                                                       LOCNUM                     Answered                 Resolution/Answer
                                                                        FORM, Business Rules states:              “Products 1, 3,
                                                                        8, 9a, 10, 15, 16, 17, 25, 29, 31, 34, 35, 38, 39, 40:
                                                                        For ACT=T the second occurrence of the Location
                                                                        and Access section is required. For the second
                                                                        occurrence the LOCNUM=2 and the section contains
                                                                        the new end user address. For all other valid
                                                                        activities the first occurrence of the Location and
                                                                        Access section is required. For the first occurrence
                                                                        the LOCNUM=1 and the section contains the end
                                                                        user address.”             “Products 1, 25 and 38: For
                                                                        ACT = T, LOCNUM1 and LOCNUM2 are required.
                                                                        For LOCNUM1, the STATE field of the old end user
                                                                        address is required. For LOCNUM2, the complete
                                                                        new end user address is required.”            “Products
                                                                        1, 25, 29, 31, 34, 35, 38, 39, 40: If cust code is not
                                                                        provided in the AN field, for ACT=T the first
                                                                        occurrence of the Location and Access section is
                                                                        required. If provided, the section contains the old end
                                                                        user address or F location and for the first occurrence
                                                                        the LOCNUM=1.”                   Was there any reason
                                                                        why UNEP POTS ACT=T rule is mentioned three
                                  EU: 7-          AT&T                  times. Does each rule have a different meaning? Just                 Question was withdrawn for 16.0 and submitted to
     8 Closed    App B: EU        LOCNUM          Consumer      8/24/04 want to confirm based on the three rules above for            9/3/04 the IMA EDI 15.0 Question and Answer log.

                                                                        Phyllis Burt, AT&T:Why was the following UNEP
                                                                        POTS business rule deleted from the LSR APPTIME
                                                                        field? Has it been replaced by some other rule for
                                                                        IMA 16.0?                “Products 1, 3, 8, 9, 9a, 10,
                                                                        18, 19, 20, 21, 25, 28, 29, 30, 31, 33, 37, 38, 40: If
                                                                        appointment response time is provided as single time
                                                                        in the ABTIME field, then the APPTIME range equals                 The rule was redundant because for a single time
                                                                        the ABTIME (as the start time) and ends at 0000. For               appointment response, ABTIME, it is enough to
                                  LSR: 17-        AT&T                  example, if the ABTIME = 1600, then the APPTIME                    populate the single time in the APPTIME field. No
     9 Closed    App B: LSR       APPTIME         Consumer      8/24/04 range is 1600-0000.                                         9/3/04 new rule has replaced it.
                                                                        Phyllis Burt, AT&T:        Was “NIDO” for Northern
                                                                        Idaho added to the CALA valid value list? There is
                                                                        conflicting information in Summary of Change
                                                                        Appendix F. There‟s an ACTION of “ADDED” for the
                                                                        CALA field however the Description has a
                                  EU: 28a-        AT&T                  strikethough. Appendix B, EU 28a CALA field shows                  This value has been added to the worksheets. The
 10 Closed       App F            CALA            Consumer      8/24/04 “NIDO” as a new valid value. Is this correct?               9/3/04 change summary strikethrough is incorrect.

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 4 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                            Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                                                    Resolution/Answer
                                                                                                                              Answered The draft disclosure documents shows the
                                                                                                                                         following Usage Rules for Local Number Portability
                                                                                                                                         (Product #5) and provides notations here for
                                                                                                                                         clarification.
                                                                                                                                         EU #7 LOCUM – Not Required
                                                                        Phyllis Burt, AT&T:      Based on SCR093003-01,                  EU #9 NAME – Optional
                                                                        should all parsed End User Service Address fields be             EU #10 AFT – Conditional - This field is
                                                                        optional for LNP except for LOCNUM, AHN, SANO                    intentionally conditional to support non-Numbered
                                                                        and STATE? The draft disclosure documents shows                  Addresses. NBR -This field is optional for usage.
                                                                        the following Usage Rule for Local Number Portability            If the field is used, the field must be populated with
                                                                        (Product #5) EU #7 LOCUM – Not Required                          one of the four valid values provided. Valid
                                                                        EU #9 NAME – Optional                                            Values A = Rural Route or Route and Box number
                                                                        EU #10 AFT – Conditional                                         / B = Unnumbered / C = Provider assigned house
                                                                        EU #12 SAPR – Optional                                           number / D = Descriptive The field is truely
                                                                        EU #13 SANO – Conditional                                        optional but if it is used we requested the CLEC
                                                                        EU #14 SASF – Optional                                           provide a valid value to help identify the type of
                                                                        EU #15 SASD – Conditional                                        non-Numbered Address used.
                                                                        EU #16 SASN – Conditional                                        EU #12 SAPR – Optional
                                                                        EU #17 SATH – Optional                                           EU #13 SANO – Conditional - This field is
                                                                        EU #18 SASS – Optional                                           intentionally conditional to help differential
                                                                        EU #19 LD1 – Optional                                            Numbered vs non-Numbered Addresses. NBR
                                                                        EU #20 LV1 – Optional                                            Required for numbered addresses (AHN is not
                                                                        EU #21 LD1 – Optional                                            populated for numbered addresses), otherwise not
                                                                        EU #22 LV1 – Optional                                            applicable.       SANO can not be populated if
                                                                        EU #23 LD1 – Optional                                            ROUTE is populated.                  EU #14 SASF –
                                                                        EU #24 LV1 – Optional                                            Optional             EU #15 SASD – Conditional.
                                                                        EU #25a AHN – Conditional                                        Qwest will change to Optional.
                                                                        EU #25b ROUTE – Conditional                                      EU #16 SASN – Conditional. This field is
                                                                        EU #25c BOX – Optional                                           intentionally conditional to support non-Numbered
                                                                        EU #26 CITY – Optional                                           Addresses.                   NBR: If AHN is populated,
                                                                        EU #27 STATE – Optional                                          the "@" symbol is required and must be the first
                                  EU: many        AT&T                  EU #28 ZIP – Optional                                            character.
 11 Closed     App B: EU          fields          Consumer      8/24/04 EU #28a CALA – Optional                                   9/3/04 EU #17 SATH – Optional




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 5 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                  Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                          Answered                   Resolution/Answer

                                                                        Bill Micou, AT&T: While reviewing Appendix F
                                                                        “Appendices – Change Summary 15.0 – 16.0”, I
                                                                        noticed a change to Appendix J “Product Family and
                                                                        Product Matrices” that is in conflict with our current
                                                                        use of ACT = “Z” and does not agree with any other
                                                                        definition of ACT = “Z in this Appendix.
                                                                        In Section 1.2.2 for Local Number Portability (LNP),
                                                                        on page 191, ACT = “Z” has a change that makes the
                                                                        wording the same as ACT = “V”. The change
                                                                        replaces the text “retain the current listings” with the
                                                                        text “will discontinue the Listing(s) associated with the
                                                                        Port Activity (all listings are removed).” In all other
                                                                        instances of ACT = “Z” in Appendix J, the “retain the
                                                                        current listings” text is unchanged.
                                                                        Question: Is this truly a change in definition for                     Qwest is revising Appendix J to reflect the
                                                AT&T                    REQTYP = “C”, ACT = “Z” or is this a typographical                     difference between ACT=Z and ACT=V. Qwest will
 12 Closed     App F              Section 1.2.2 Business        8/24/04 error?                                                          9/3/04 retain the listings.

                                                                        Phyllis Burt, AT&T:               The PreOrder
                                                                        AAQ/AAR/ASQ/ASR business rules were impacted
                                                                        by SCR012204-01RG (TRO BHC IMA Changes and
                                                                        Appointment Scheduler). However it is not clear if the
                                                                        existing Appointment business rules were impacted.
                                                                        If a CLEC is currently using TXTYP=D (D =
                                                                        Appointment Scheduling non-UBL Products) are
                                                                        there any impacts to this process? For example, are
                                                                        the ABTIME and COMPTIME rules, data content and                        For TXTYP=D, the changes are to clarify already
                                                                        format of these fields the same as IMA 15.0 for                        existing rules only, f.i. ASQ11, ABTIME changes
                                                                        AAQ/AAR/ASQ/ASR for TXTYP=D? Are the                                   from:                     HHMM-HHMM or HHMM
                                                                        APPTIME & APTCON rules, data content and format                        to:          If TXTYP=D HHMM-HHMM
                                  Appt: many      AT&T                  on the Order the same as IMA 15.0 based on the                         If TXTYP=U HHMM               This applies to both
 13 Closed     App A: Appt        fields          Consumer      8/24/04 data received from PreOrder?                                    9/3/04 PreOrder and Order.

                                                                        Stephanie Prull, Eschelon:            Appendix A - D -
                                                                        Address Worksheet - AVQ31, AVR82, AVR86- CALA
                                                                        field. The document shows that a value has been
                                                                        added to the documents. However under the
                                  AVQ: 31-                              description the value of NIDO is striked through. Has                  The value has been added to the Developer
 14 Closed     App A: AVQ         CALA            Eschelon      8/24/04 this value been added or deleted? Please clarify.               9/3/04 Worksheets.


Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                    Page 6 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                         Answered                  Resolution/Answer
                                                                        Stephanie Prull, Eschelon:      Appendix A - D -
                                                                        Address Worksheet - AVR10 - WTNSTAT field. The
                                                                        document shows that a value has been added to the
                                                                        documents. However under the description the
                                                                        values of PND IN and PND OUT have been
                                  AVR: 10-                              struckthrough. Have these values been added or                        The value has been added to the Developer
 15 Closed     App A: AVQ         WTNSTAT         Eschelon      8/24/04 deleted? Please clarify.                                       9/3/04 Worksheets.
                                                                        Stephanie Prull, Eschelon:             Appendix A -
                                                                        D - Completion Worksheet - 13 - Action Code field.
                                                                        The document shows that both R and blank for EDI =
                                                                        Recap. Will EDI users see a combination of these
                                  Comp: 13-                             two values or will we always see a blank? Please
 16 Closed     App D: Comp        Action Code Eschelon          8/24/04 clarify.                                                       9/3/04 The CLEC will see either R or Blank for Recap.

                                                                        Stephanie Prull, Eschelon: Appendix A - D - End
                                                                        User Worksheet - 12 - SAPR field. The business rule                   Yes, it is required for ACT = V for UBL if doing a
                                                                        was added "For CLEC to CLEC conversion this field                     CLEC to CLEC and it is part of the address for
                                                                        is part of the overrall end user address......." Does                 which the order is being submitted. It is not an
                                                                        this mean this field is required for ACT = V for UBL if               upfront edit. IMA identifies CLEC to CLEC
                                                                        doing a CLEC to CLEC? Is this an upfront edit? If so                  conversion by comparing submitted CCNA to RSID
                                  EU: 12-                               how is the determination being made by the system                     or ZCID on the CSR. If the IDs are different it's a
 17 Closed     App B: EU          SAPR            Eschelon      8/24/04 that this is CLEC to CLEC vs. Qwest to CLEC?                   9/3/04 CLEC to CLEC conversion.
                                                                        Stephanie Prull, Eschelon:              Appendix A - D -
                                                                        End User Worksheet - 14 - SASF field. The business
                                                                        rule was added "For CLEC to CLEC conversion this
                                                                        field is part of the overrall end user address......."
                                                                        Does this mean this field is required for ACT = V for
                                                                        UBL if doing a CLEC to CLEC? Is this an upfront
                                                                        edit? If so how is the determination being made by
                                  EU: 14-                               the system that this is CLEC to CLEC vs. Qwest to
 18 Closed     App B: EU          SASF            Eschelon      8/24/04 CLEC?                                                          9/3/04 Please see the response to number 17 above.

                                                                        Stephanie Prull, Eschelon:              Appendix A - D -
                                                                        End User Worksheet - 9 - Name field. The business
                                                                        rule was added "If CLEC to CLEC conversion this
                                                                        field is required, otherwise it is optional". Again is
                                                                        this an upfront edit? How does the Qwest system                       Please see the response to number 17 above. The
                                                                        know this is CLEC to CLEC? This was never                             AN or TN is not a required field for CLEC to CLEC
                                                                        disclosed as an exception to the TN and SANO rules.                   migrations. Oftentimes the CLEC doesn't have the
 19 Closed     App B: EU          EU: 9-NAME Eschelon           8/24/04 Where is this business rule being driven from?                 9/3/04 TN, thus we need the address to validate the LSR.


Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 7 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                           Issue/Question                     Answered                  Resolution/Answer
                                                                          Stephanie Prull, Eschelon:             Appendix A - D -
                                                                          End User Worksheet - 15 - SASD field. The
                                                                          business rule was added "For CLEC to CLEC
                                                                          conversion this field is part of the overrall end user
                                                                          address......." Does this mean this field is required
                                                                          for ACT = V for UBL if doing a CLEC to CLEC? Is
                                                                          this an upfront edit? If so how is the determination
                                  EU: 15-                                 being made by the system that this is CLEC to CLEC
 20 Closed     App B: EU          SASD            Eschelon      8/24/04   vs. Qwest to CLEC?                                           9/3/04 Please see the response to number 17 above.
                                                                          Stephanie Prull, Eschelon:                 Appendix A -
                                                                          D - End User Worksheet - 16 - SASN field. The
                                                                          business rule was added "For CLEC to CLEC
                                                                          conversion this field is part of the overrall end user
                                                                          address......." Does this mean this field is required
                                                                          for ACT = V for UBL if doing a CLEC to CLEC? Is
                                                                          this an upfront edit? If so how is the determination
                                  EU: 16-                                 being made by the system that this is CLEC to CLEC
 21 Closed     App B: EU          SASN            Eschelon      8/24/04   vs. Qwest to CLEC?                                           9/3/04 Please see the response to number 17 above.
                                                                          Stephanie Prull, Eschelon:              Appendix A - D -
                                                                          End User Worksheet - 17 - SATH field. The business
                                                                          rule was added "For CLEC to CLEC conversion this
                                                                          field is part of the overrall end user address......."
                                                                          Does this mean this field is required for ACT = V for
                                                                          UBL if doing a CLEC to CLEC? Is this an upfront
                                                                          edit? If so how is the determination being made by
                                  EU: 17-                                 the system that this is CLEC to CLEC vs. Qwest to
 22 Closed     App B: EU          SATH            Eschelon      8/24/04   CLEC?                                                        9/3/04 Please see the response to number 17 above.
                                                                          Stephanie Prull, Eschelon:             Appendix A - D -
                                                                          End User Worksheet - 18 - SASS field. The business
                                                                          rule was added "For CLEC to CLEC conversion this
                                                                          field is part of the overrall end user address......."
                                                                          Does this mean this field is required for ACT = V for
                                                                          UBL if doing a CLEC to CLEC? Is this an upfront
                                                                          edit? If so how is the determination being made by
                                  EU: 18-                                 the system that this is CLEC to CLEC vs. Qwest to
 23 Closed     App B: EU          SASS            Eschelon      8/24/04   CLEC?                                                        9/3/04 Please see the response to number 17 above.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 8 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                  Date
Q#   Status          Form             Name          Vendor     Opened                         Issue/Question                        Answered                  Resolution/Answer
                                                                        Stephanie Prull, Eschelon:             Appendix A - D -
                                                                        End User Worksheet - 25c - Box field. The business
                                                                        rule was added "For CLEC to CLEC conversion this
                                                                        field is part of the overrall end user address......."
                                                                        Does this mean this field is required for ACT = V for
                                                                        UBL if doing a CLEC to CLEC? Is this an upfront
                                                                        edit? If so how is the determination being made by
                                  EU: 25c-                              the system that this is CLEC to CLEC vs. Qwest to
 24 Closed     App B: EU          BOX             Eschelon      8/24/04 CLEC?                                                           9/3/04 Please see the response to number 17 above.

                                                                        Stephanie Prull, Eschelon:              Appendix A - D -
                                                                        End User Worksheet - 26 - City field. The business
                                                                        rule was added "If CLEC to CLEC conversion this
                                                                        field is required, otherwise it is optional". Again is
                                                                        this an upfront edit? How does the Qwest system                        Please see the response to number 17 above. The
                                                                        know this is CLEC to CLEC? This was never                              AN or TN is not a required field for CLEC to CLEC
                                                                        disclosed as an exception to the TN and SANO rules.                    migrations. Oftentimes the CLEC doesn't have the
 25 Closed     App B: EU          EU: 26-CITY Eschelon          8/24/04 Where is this business rule being driven from?                  9/3/04 TN, thus we need the address to validate the LSR.
                                                                        Stephanie Prull, Eschelon:               Appendix A - D -
                                                                        End User Worksheet - 27 - State field. The business
                                                                        rule was added "Require for CLEC to CLEC
                                                                        conversion or when LSR Sup = 3, otherwise
                                                                        optional". Again is this an upfront edit? The
                                                                        statement says LSR Sup = 3. However the state is                       Please see the response to number 17 above.
                                                                        not required on an ACT = D and is optional for ACT =                   Qwest is currently reviewing this question to
                                  EU: 27-                               C, V, and M. So does this rule not apply for an ACT                    determine whether or not the rule should be
 26 Closed     App B: EU          STATE           Eschelon      8/24/04 = D, C, V, or M? Please clarify.                                9/3/04 removed.
                                                                        Stephanie Prull, Eschelon:               Appendix A - D -
                                                                        End User Worksheet - 28 - Zip field. The business
                                                                        rule was added "For CLEC to CLEC conversion this
                                                                        field is part of the overrall end user address......."
                                                                        Does this mean this field is required for ACT = V for
                                                                        UBL if doing a CLEC to CLEC? Is this an upfront
                                                                        edit? If so how is the determination being made by
                                                                        the system that this is CLEC to CLEC vs. Qwest to
 27 Closed     App B: EU          EU: 28-ZIP      Eschelon      8/24/04 CLEC?                                                           9/3/04 Please see the response to number 17 above.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 9 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                    Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                            Answered                    Resolution/Answer
                                                                        Stephanie Prull, Eschelon:            Appendix A - D -
                                                                        End User Worksheet - 28a - CALA field. The
                                                                        business rule was added "For CLEC to CLEC
                                                                        conversion this field is part of the overrall end user
                                                                        address......." Does this mean this field is required
                                                                        for ACT = V for UBL if doing a CLEC to CLEC? Is
                                                                        this an upfront edit? If so how is the determination
                                  EU: 28a-                              being made by the system that this is CLEC to CLEC
 28 Closed     App B: EU          CALA            Eschelon      8/24/04 vs. Qwest to CLEC?                                                9/3/04 Please see the response to number 17 above.
                                                                                                                                                 Qwest maintains that for products 5 and 7 the only
                                                                                                                                                 two valid activities are V or Z. Both V and Z have
                                                                                                                                                 the abbreviated order information and are not
                                                                          Stephanie Prull, Eschelon:               Appendix A - D -              required. The IMA GUI will accept an entry in the
                                                                          End User Worksheet - 19 - LD1 field. The products of                   LD1 field without a corresponding LV1 entry.
                                                                          5 and 7 were removed for the section "This field is                    However as a footnote EDI will not due to X12
                                                                          part of the ........". Please explain the removal.                     standards, the field is optional but the element
                                                                          These two products have this field as optional so they                 used will require an LD/LV relationship if
                                                                          should be dependant on this business rule if the                       populated. This X12 limitation is disclosed via the
 29 Closed     App B: EU          EU: 19-LD1      Eschelon      8/24/04   CLEC chooses to use this field.                                 9/3/04 EDI maps documentation.
                                                                          Stephanie Prull, Eschelon:           Appendix A - D -
                                                                          Facility Availability - FAQ37- CALA field. The
                                                                          document shows that a value has been added to the
                                                                          documents. However under the description the value
                                  FAQ: 37-                                of NIDO is striked through. Has this value been                        This value has been added to the worksheets. The
 30 Closed     App A: FAQ         CALA            Eschelon      8/24/04   added or deleted? Please clarify.                               9/3/04 change summary strikethrough is incorrect.
                                                                          Stephanie Prull, Eschelon:              Appendix A - D -
                                                                          Loop Qual - LQQ36, LQQ39- CALA field. The
                                                                          document shows that a value has been added to the
                                  LQQ: 36-                                documents. However under the description the value
                                  CALA & 39-                              of NIDO is striked through. Has this value been                        This value has been added to the worksheets. The
 31 Closed     App A: LQQ         CALA            Eschelon      8/24/04   added or deleted? Please clarify.                               9/3/04 change summary strikethrough is incorrect.
                                                                          Stephanie Prull, Eschelon:           Appendix A - D -
                                                                          Loop Service Worksheet - 14 - TSP field. The
                                                                          business rule added for product 4 states "When
                                                                          populated, this field will be validated against valid
                                                                          values". What valid values is it validating against?                   It is validating that a dash is present in position 10
 32 Closed     App C: LS          LS: 14-TSP      Eschelon      8/24/04   Where do these values come from?                                9/3/04 of the field.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                       Page 10 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                         Answered                    Resolution/Answer

                                                                        Stephanie Prull, Eschelon:         Appendix A - D -
                                                                        Loop Service Worksheet - 16 - ECCKT field. The
                                                                        business rule added states "ACT = V, CLEC to CLEC
                                                                        conversions, refer to the migrations and conversions
                                                                        Overview PCAT for rules on population of this field".
                                                                        If there is a negiotiated business rule it needs to be
                                                                        stated in this document. PCATs are not dependant
                                                                        on a major release for changes. A change to the
                                                                        business rule in the PCAT could require a coding                      Qwest will add "For Information Only" to this rule,
                                  LS: 16-                               change to a CLEC. Please publish any negotiated                       as nothing should be coded by the CLEC based on
 33 Closed     App C: LS          ECCKT           Eschelon      8/24/04 business rules in this document.                               9/3/04 this.
                                                                        Stephanie Prull, Eschelon:        Appendix A - D -
                                                                        LSNP Worksheet - 15 - TSP field. The business rule
                                                                        added states "When populated, this field will be
                                                                        validated against valid values". What valid values is it
                                  LSNP: 15-                             validating against? Where do these values come                        It is validating that a dash is present in position 10
 34 Closed     App C: LSNP        TSP             Eschelon      8/24/04 from?                                                          9/3/04 of the field.
                                                                                                                                              The customer code for the account being
                                                                                                                                              converted. At the present time, cust code is not
                                                                                                                                              required to be provided as part of the AN field as
                                                                                                                                              we have implemented CMP CR #SCR022703-18.
                                                                                                                                              However, when there is a multiple CSR match
                                                                                                                                              scenario, the customer needs to provide the cust
                                                                        Stephanie Prull, Eschelon:        Appendix A - D -                    code information as part of the AN.
                                                                        LSR Worksheet - 7 - AN field. Note added states                       Qwest is currently working to update Disclosure
                                                                        "When multiple CSR exists for a TN, and ACT = W,                      with a clarification for the AN (LSR-7), and in the
                                                                        V, or Z, customer code should be included as part of                  PCAT under the Pre-Ordering Overview section.
                                                                        the AN. If there is multiple CSRs which customer                      That clarification will tentatively appear as:
                                                                        Code needs to be added. If there are multiple CSRs                    "Note: When multiple CSR exists for a TN,
                                                                        there are multiple cus codes.      Please clarify                     customer code should be included as part of the
 35 Closed     App B: LSR         LSR: 7-AN       Eschelon      8/24/04 which code the system would look for.                          9/3/04 AN."
                                                                        Stephanie Prull, Eschelon:        Appendix A - D -
                                                                        LSR Worksheet - 17 - APPTIME field. Added value
                                  LSR: 17-                              is Blank, Not Populated (EDI only) = space. What                      This added entry was subsequently deleted. See
 36 Closed     App B: LSR         APPTIME         Eschelon      8/24/04 exactly does =space mean?                                      9/3/04 Appendix B.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                    Page 11 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                             Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                     Answered                   Resolution/Answer
                                                                        Stephanie Prull, Eschelon:            Appendix B - LSR
                                                                        Worksheet - 17 - APPTIME field. Added business
                                                                        rule states for product 4, 41, 7, 42 "For ACT = V, if
                                                                        CHC = B, Apptime must be HHMM -HHMM.
                                                                        However the rule right above it says for Product 4,
                                  LSR: 17-                              7,11, 12, 41, 42 Range not allowed. Please clarify                Product 4, 7, 41, and 42 will be removed from the
 37 Closed     App B: LSR         APPTIME         Eschelon      8/24/04 which business rule is correct.                            9/3/04 rule "Range not allowed".
                                                                        Stephanie Prull, Eschelon:            Appendix A - D -
                                                                        PSON Worksheet - 16 - Action Code field. The
                                                                        document shows that both R and blank for EDI =
                                                                        Recap. Will EDI users see a combination of these
                                  PSON: 16-                             two values or will we always see a blank? Please
 38 Closed     App D: PSON        Action Code Eschelon          8/24/04 clarify.                                                   9/3/04 The CLEC will see either R or Blank for Recap.

                                                                        Stephanie Prull, Eschelon:                Appendix A
                                                                        - D - Raw Loop Data- RLDQ31- CALA field. The
                                                                        document shows that a value has been added to the
                                                                        documents. However under the description the value
                                  RLDQ: 31-                             of NIDO is striked through. Has this value been                   The value has been added to the Developer
 39 Closed     App A: RLDQ        CALA            Eschelon      8/24/04 added or deleted? Please clarify.                          9/3/04 Worksheets.
                                                                        Stephanie Prull, Eschelon:            Appendix A - D
                                                                        - RPL Worksheet - 31a, 66a - CALA field. The
                                                                        document shows that a value has been added to the
                                  RPL: 31a-                             documents. However under the description the value
                                  CALA & 66a-                           of NIDO is striked through. Has this value been                   The value has been added to the Developer
 40 Closed     App C: RPL         CALA        Eschelon          8/24/04 added or deleted? Please clarify.                          9/3/04 Worksheets.

                                                                        Stephanie Prull, Eschelon:                Appendix A -
                                                                        D - TN Worksheet - TNAQ32 - CALA field. The
                                                                        document shows that a value has been added to the
                                                                        documents. However under the description the value
                                  TNAQ: 32-                             of NIDO is striked through. Has this value been                   The value has been added to the Developer
 41 Closed     App A: TNAQ        CALA            Eschelon      8/24/04 added or deleted? Please clarify.                          9/3/04 Worksheets.
                                                                        James McCluskey, Accenture:                 Was                   Yes. SCR093003-01was rolled into SCR120403-
 42 Closed     General                            Accenture     8/24/04 scr093003-01 included with this IMA 16.0 release?          9/3/04 01.
                                                                        James McCluskey, Accenture:                   On the LR
                                  LR: 35-                               form, field Rdet the valid value section of "testing,
 43 Closed     App D: LR          RDET            Accenture     8/24/04 p33,p34 etc seems to be listed twice?                      9/3/04 Qwest will rectify this error with the documentation.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 12 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                Product or DWS      Field # or    Software     Date                                                                Date
Q#   Status          Form             Name         Vendor     Opened                       Issue/Question                        Answered                  Resolution/Answer


                                                                       James McCluskey, Accenture:                        The
                                                                       following change was reflected for LNLN/LNFN valid
                                                                       values: FROM:                 % (Percentage)
                                                                       Not valid as 1st character – Only used in business
                                                                       listings (TOA=B)         - - Requires PLA if to be used
                                                                       for alphabetizing         - Valid in Eastern Only
                                                                       TO:       % (Percentage)         - Not valid as 1st
                                                                       character in Eastern Region         – Only used in
                                                                       business listings (TOA=B) in Eastern Region          --
                                                                       Requires PLA if to be used for alphabetizing in
                                                                       Eastern Region                 We would like to clarify
                                                                       whether the valid value of % is still valid ONLY in                  The % symbol is valid in all regions for business
                                                                       eastern region and prohibited on other regions or                    (TOA=B) listings only. The limit in Eastern is not
                                  DL: 44-LNLN                          whether its already valid in other region with the                   allowing the % in the 1st character, where Central
 44 Closed     App C: DL          & 45-LNFN Accenture          8/24/04 stated rules specific for eastern ones? Thanks.               9/3/04 and Western do.

                                                                                                                                            For Pre-order, Qwest will provide Pending
                                                                                                                                            Disconnect information on the CSR Response as
                                                                                                                                            indicated below:
                                                                       Phyllis Burt, AT&T:           Today, a pending                       VCSR eligible         When CSR date precedes the
                                                                       disconnect is detected on the CSR Response via the                   pending disconnect the disconnect order and due
                                                                       CSRR21 ACCTDESC (Account Status) field =                             date will appear in the pending order tab on the
                                                                       "DISC".           How will QWEST continue to                         CSR response, the account status will = DISC
                                                                       provide Pending Disconnect information on the CSR                    When CSR date post dates the pending
                                                                       Response with IMA 16.0 Virtual CSR Phase II? It is                   disconnect the CSR is not returned
                                                                       our understanding that only live CSRs are returned                   Not VCSR eligible Functionality will not change.
                                                                       on the CSR response. If our CSR DATE is after the                    The CSR returned will always be a static CSR from
                                  CSR: 21- AT&T                        due date associate with the Pending Disconnect to                    BOSS/CARS and a pending disconnect will result
 45 Closed     App A: CSR         ACCTDESC Consumer            8/24/04 determine that there is a pending disconnect?                 9/3/04 in account status = DISC.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 13 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                   Resolution/Answer

                                                                                                                                           The reasons are sited in the Developer Worksheet
                                                                                                                                           as:             “For Information Only: If a submitted
                                                                                                                                           conversion request is in an ISSUED status and the
                                                                                                                                           related conversion order (CSO1 and or CSO2) has
                                                                        Phyllis Burt, AT&T:             Question asked during              been merged in the virtual CSR data, the CIP
                                                                        walkthrough of SCR101403-01.            Do we still                indicator is not needed.       The new account
                                                                        need the CIP, CSO1, CSO2 field with Virtual CSR                    ownership will be correctly identified. Using the
                                                                        Phase II? Answer provided: Yes, the CIP, CSO1,                     CIP indicator in this situation will cause the request
                                                                        CSO2 fields are still needed for invalid statuses and              to drop to manual instead of being eligible for
                                                                        ineligible Virtual CSR products. Please document the               product specific flowthrough. The PreOrder CSR
                                                  AT&T                  reasons to use these fields in the Developer                       has a Pending Orders section that can be used to
 46 Closed     App A: CSR         VCSR            Consumer      8/24/04 worksheet.                                                  9/3/04 identify if the related order is merged.”

                                                                        Phyllis Burt, AT&T:          Question asked during
                                                                        Developer Worksheet Walkthru - IMA 16.0 deleted
                                                                        logic for the LSR APPTIME field which was originally
                                                                        added with IMA 13.0 addendum ver 1 dated 8-18-03
                                                                        based on event notification #100996 because EDI
                                                                        required a range in the APPTIME field. Does QWEST                  Qwest still requires a range. Qwest is instead
                                                                        really want to remove this requirement with IMA                    removing an example of how to convert a single
                                  LSR: 17-        AT&T                  16.0? Is an Apptime range value no longer required                 time to a range for an order. The valid values
 47 Closed     App B: LSR         APPTIME         Consumer      8/24/04 beginning with IMA 16.0?                                    9/3/04 specify that a range is required.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 14 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                  Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                          Answered                   Resolution/Answer
                                                                                                                                               The change is effective with 16.0.
                                                                                                                                               10/1/04: Correction to previous answer...
                                                                                                                                               PULSE - There was no system change. The
                                                                                                                                               following informational rule was corrected to match
                                                                                                                                               the PCAT and how the System was already
                                                                                                                                               working. The only thing that changed was the
                                                                                                                                               states for which the rule was applicable.
                                                                                                                                               FROM:
                                                                                                                                               Products: 1, 10, 17, 21, 25, 35:
                                                                                                                                               For Information Only - The PULSE field is only
                                                                                                                                               required in Arizona and
                                                                                                                                               Northern Idaho for the rules specified as follows:
                                                                                                                                               An entry is required if ACT=C and LNA=N.
                                                                                                                                               An entry is required if ACT=V or Z and LNA= N or
                                                                                                                                               V
                                                                                                                                               An entry is required if ACT=N and LNA=N.
                                                                                                                                               An entry is required if ACT=T and LNA=N.

                                                                                                                                               TO
                                                                        Phyllis Burt, AT&T:           There wasa a change to                   Products: 1, 10, 17, 21, 25, 35:
                                                                        the Information only section of the PULSE field on                     For Information Only - The PULSE field is only
                                                                        the RS form. Is this change effective with IMA 16.0 or                 required in South
                                                                        is this a clarification impacting all IMA production                   Dakota for the rules specified as follows:
                                                                        versions today (if so, please issue an event                           An entry is required if ACT=C and LNA=N.
                                                                        notification)? If there are other clarifications included              An entry is required if ACT=V or Z and LNA= N or
                                                                        in this documentation that impact current production                   V
                                  RS: 67-         AT&T                  please list those as well in your response to this                     An entry is required if ACT=N and LNA=N.
 48 Closed     App C: RS          PULSE           Consumer      8/24/04 question and issue an event notification.                       9/3/04 An entry is required if ACT=T and LNA=N.
                                                                                                                                               Qwest cannot respond to this question based on
                                                                                                                                               its non-specificity. Qwest recommends that, if
                                                                                                                                               AT&T has specific questions it would like to log
                                                                                                                                               around data requirements, that those individual
                                                  AT&T                  Phyllis Burt, AT&T:         What are Data Conversion                   questions be submitted through the IMA EDI 16.0
 49 Closed     General                            Consumer      8/24/04 requirements, if any, for IMA 16.0?                             9/3/04 Question and Answer Log process.
                                                                        Phyllis Burt, AT&T:               Beginning with IMA
                                                                        16.0, since ACT=Z will be treated the same as
                                                                        ACT=V for LNP (Product 5), will CLECs no longer                        Qwest is revising Appendix J to reflect the
                                                AT&T                    have the option of retaining Directory listing when the                difference between ACT=Z and ACT=V. Qwest will
 50 Closed     App J              Section 1.2.2 Consumer        8/24/04 end user migrates to LNP?                                       9/3/04 retain the listings.



Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 15 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                Product or DWS      Field # or    Software     Date                                                                   Date
Q#   Status          Form             Name         Vendor     Opened                        Issue/Question                          Answered                   Resolution/Answer

                                                                                                                                               This is something that came with the requirements
                                                                                                                                               from LFACS AN. This will only impact new data.
                                                                       Phyllis Burt, AT&T: What is driving the increased                       The data will still be valid. Currently, all the
                                                                       field size for the CITY field in PreOrder and Order?                    information or city fields that were in PREMIS were
                                                                       Will this only impact new date or will the increase                     input into LFACS AN. With the project, LFACS AN
                                                                       impact previous captured data? For example, can the                     wanted to be more like postal standards. Qwest
                                                                       CITY data stored from a previous validated service                      does not believe (based on investigation) that any
                                                                       address a year ago now become invalid? What type                        of the states will come up with a new city that has
                                              AT&T                     of data conversion, if any, will QWEST perform on                       32 characters, but if they do we will be able to
 51 Closed     App B: EU          EU: 26-CITY Consumer         8/24/04 the CITY field?                                                  9/3/04 handle this.
                                                                       Phyllis Burt, AT&T: Please explain the reason for                       IMA stores the NPA/NXX in this field. These
                                                                       the increase of the TTA (Traffic Terminating Area)                      requirements were based on the LFACS AN
                                                                       field in PreOrder Address Validation (AVR51). What                      project. This field was changed to reflect expected
                                                                       data is currently stored in the TTA field ? What data                   responses. Qwest does not expect that the data
                                              AT&T                     will it be stored in the TTA field in the future that will              will ever be that large, but Qwest will comply if that
 52 Closed     App A: AVQ         AVR: 51-TTA Consumer         8/24/04 require a larger field size?                                     9/3/04 happens.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                    Page 16 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                    Resolution/Answer
                                                                                                                                           9/3/04: Sent to SME
                                                                                                                                           9/10/04: The answer is the CLEC assumption
                                                                                                                                           about system date/same day is incorrect.
                                                                                                                                           If the CSR DATE = "Current Date" on the query,
                                                                                                                                           will the following always be true on the response:
                                                                                                                                           * VCSR(CSRR7a) - will always be 'N'....FALSE, It
                                                                                                                                           will tend to be this way but if a pending order is due
                                                                                                                                           that day that has not posted to the CSR, IMA will
                                                                                                                                           merge it accordingly and the value would be YES.
                                                                                                                                           * PENDING ORDER QTY(CSRR135a) - will never
                                                                                                                                           be provided....FALSE, If any pending orders exist
                                                                                                                                           against the account IMA will return them to the
                                                                                                                                           CLEC and this Quantity field will be a count for the
                                                                        My question is regarding a new field on the Customer               number of orders that exist. Order Merging does
                                                                        Service Records Query (Appendix A (A.5 - Customer                  not impact this count; all orders, merged or not, are
                                                                        Service Records)) named CSR DATE (CSRQ7a).                         included in the count.
                                                                        We intend to always populate this field with the                   *PENDING ORDERS SECTION - will never be
                                                                        current system date. It is my understanding that by                provided (ORDER NUMBER(CSRR135b) ,
                                                                        doing so, the response will not include any pending                ORDER DUE DATE(CSRR135c) , MERGE
                                                                        service orders that exist on that line. If the CSR                 INDICATOR(CSRR135d))....FALSE, If any pending
                                                                        DATE = "Current Date" on the query, will the                       orders exist against the account IMA will return
                                                                        following always be true on the response:                          them to the CLEC. Each order will have the order
                                                                        *VCSR(CSRR7a) - will always be 'N'                                 number, due date and Merge Indicator.
                                                                        *PENDING ORDER QTY(CSRR135a) - will never be
                                                                        provided        *PENDING ORDERS SECTION - will                     The only times their assumption is true is if it is a
                                                                        never be provided (ORDER NUMBER(CSRR135b) ,                        non VCSR eligible product or if there are no
                                  CSRQ: 7a-                             ORDER DUE DATE(CSRR135c) , MERGE                                   pending orders against a VCSR eligible products'
 53 Closed     App A: CSR         CSR DATE        Talk.com      8/31/04 INDICATOR(CSRR135d)) Thanks for your help.                 9/10/04 account
                                                                        Please explain the reason for the increase of the
                                                                        AVR59 SANO field in the PreOrder Address                           IMA stores the Street Address Number in this field.
                                                                        Validation Response. What data is currently stored in              These requirements were based on the LFACS AN
                                                                        the SANO field in the Multiple and Near Match                      project. This field was changed to reflect expected
                                                                        Address Section? What data will it be stored in the                responses. Qwest does not expect that the data
                                  AVR: 59-        AT&T                  AVR59 SANO field in the future that will require a                 will ever be that large, but Qwest will comply if that
 54 Closed     App A: AVQ         SANO            Consumer       9/3/04 larger field size for IMA 16.0?                            9/10/04 happens.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 17 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                            Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                     Answered                  Resolution/Answer
                                                                        The following was submitted during the IMA 16.0
                                                                        Comment Cycle however it wasn't included in the
                                                                        IMA 16 Q&A log.
                                                                        Question asked during Developer Worksheet
                                                                        Walkthru - IMA 16.0 deleted logic for the LSR
                                                                        APPTIME field which was originally added with IMA
                                                                        13.0 addendum ver 1 dated 8-18-03 based on event
                                                                        notification #100996 because EDI required a range in
                                                                        the APPTIME field. Does QWEST really want to
                                                                        remove this requirement with IMA 16.0? Is an
                                  LSR: 17-        AT&T                  Apptime range value no longer required beginning                 The question (and answer) appear as number 47 in
 55 Closed     App B: LSR         APPTIME         Consumer       9/3/04 with IMA 16.0?                                           9/10/04 the response document and in this log.
                                                                        During the walkthrough of SCR120403-02 Shon Higer
                                                                        stated that these questions and his answers during
                                                                        the walkthrough would be documented with the other
                                                                        IMA 16.0 questions. Unless the answers were
                                                                        documented with the meeting minutes, please add
                                                                        the following question & the answer to the IMA 16.0
                                                                        Q&A log:
                                                                        SCR120403-02 VCSR High Level Walkthrough doc
                                                                        states "Since Desired Due Date (DDD) is used to
                                                                        obtain a CSR for editing and flow through of new
                                                                        LSRs the DDD must be accurate at the time an LSR
                                                                        is submitted" What appens if the pending order is
                                                                        cancelled, due date changed, or receives a SX
                                                                        Jeopardy - FOC in Error? Will QWEST automatically
                                                                        re-evaluate all new LSRs that might have used this
                                              AT&T                      data and automatically reject pending orders that are            The answer was published in the Meeting Minutes
 56 Closed     Followup           Walkthrough Consumer           9/3/04 impacted?                                                9/10/04 from the Walkthrough held on August 19, 2004.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                         Page 18 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                Product or DWS      Field # or    Software     Date                                                              Date
Q#   Status          Form             Name         Vendor     Opened                     Issue/Question                        Answered                 Resolution/Answer

                                                                       During the walkthrough of SCR120403-02 Shon Higer
                                                                       stated that these questions and his answers during
                                                                       the walkthrough would be documented with the other
                                                                       IMA 16.0 questions. Unless the answers were
                                                                       documented with the meeting minutes, please add
                                                                       the following question & the answer to the IMA 16.0
                                                                       Q&A log:
                                                                       SCR120403-02 VCSR High Level Walkthrough doc
                                                                       states "The ownership check in IMA will recognize
                                                                       the new owner from the pending order allowing the
                                                                       request to flow through when DDD of the new request
                                                                       is greater than the due date of the pending
                                                                       conversion. If the new request pre-dates the pending
                                                                       conversion due date the IMA ownership check will
                                                                       reject the LSR noting the account is not owned by the
                                                                       submitting CLEC." What happens if the old owner
                                                                       has a pending order that was FOC'd and scheduled
                                                                       to complete sometime after the new pending
                                                                       conversion. Will QWEST automatically re-evaluate all
                                                                       pending LSRs that might be impacted based on a
                                                                       change in ownership and notify the old owner? If so,
                                              AT&T                     then when does the reject notification occur? After                The answer was published in the Meeting Minutes
 57 Closed     Followup           Walkthrough Consumer          9/3/04 the completion?                                            9/10/04 from the Walkthrough held on August 19, 2004.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                           Page 19 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                Product or DWS      Field # or    Software     Date                                                              Date
Q#   Status          Form             Name         Vendor     Opened                     Issue/Question                        Answered                 Resolution/Answer

                                                                       During the walkthrough of SCR120403-02 Shon Higer
                                                                       stated that these questions and his answers during
                                                                       the walkthrough would be documented with the other
                                                                       IMA 16.0 questions. Unless the answers were
                                                                       documented with the meeting minutes, please add
                                                                       the following question & the answer to the IMA 16.0
                                                                       Q&A log:
                                                                       How do we request a CSR if we just want a snapshot
                                                                       of how it looks today? For example, we have
                                                                       situations in production where are records indicate
                                                                       that we requested provisioning of specific features
                                                                       however our customers are stating that the feature is
                                                                       not operational. Or we try to change a listing and we
                                                                       get an error that our old listing (LACT=O) doesn't
                                                                       match the CSR. Today, when this happens we pull
                                                                       the QWEST CSR and compare it to our AT&T CSR
                                                                       to see if there is a gap. No LSR is required for this
                                                                       action. Shouldn't the new field CSR Date be setup as
                                              AT&T                     optional instead of required or conditional for VCSR               The answer was published in the Meeting Minutes
 58 Closed     Followup           Walkthrough Consumer          9/3/04 eligible products?                                         9/10/04 from the Walkthrough held on August 19, 2004.

                                                                       During the walkthrough of SCR120403-02 Shon Higer
                                                                       stated that these questions and his answers during
                                                                       the walkthrough would be documented with the other
                                                                       IMA 16.0 questions. Unless the answers were
                                                                       documented with the meeting minutes, please add
                                                                       the following question & the answer to the IMA 16.0
                                                                       Q&A log:
                                                                       SCR120403-02 VCSR High Level Walkthrough doc
                                                                       states "To ensure that the VCSR obtained at order
                                                                       time is correct, DDD is now edited on requests for
                                                                       VCSR eligible products. These requests will receive
                                                                       a reject from IMA when the due date interval is too
                                                                       short." Since all products are not VCSR eligible why
                                                                       is the new field CSR Date required on the CSR
                                                                       query? If the VCSR eligible product is not identified
                                              AT&T                     on the CSR query, how is QWEST going to                            The answer was published in the Meeting Minutes
 59 Closed     Followup           Walkthrough Consumer          9/3/04 determine if the due date interval is too short?           9/10/04 from the Walkthrough held on August 19, 2004.



Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                           Page 20 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                         Answered                   Resolution/Answer

                                                                        Follow-up to QWEST IMA 16 Q&A question #5. The
                                                                        question regarding DL was not answered. In UNEP
                                                                        POTS, what happens to the listing associated with
                                                                        the TN that is changing? Since IMA 12, we have
                                                                        always sent any listings impacted by the TN change
                                                                        on the ACT=C with LNA=X. (see PON 1520110609,                        If you are only changing the TN (you're not
                                                                        1520652069, 1520803716) to reflect the new LTN.                      changing features, hunting, blocking, etc.) than you
                                                                        (a)Can we continue to send our orders this way? (b)                  may continue to use Act=C, LNA=X to make that
                                                  AT&T                  If not, will QWEST automatically update the listed TN                change and include the DL form for the associated
 60 Closed     Followup           Q#5             Consumer       9/3/04 impacted? (c) What CR is causing this change?                9/10/04 listing, as you do today.
                                                                        Follow-up to #47 Answer stated "Qwest still
                                                                        requires a range. Qwest is instead removing an
                                                                        example of how to convert a single time to a range
                                                                        for an order. The valid values specify that a range is
                                                                        required". Please confirm that the CLEC is no
                                                                        longer required to convert a single time to a range
                                                                        because QWEST will always return a range on AAR                      Qwest will always return a range for ABTIME for
                                                  AT&T                  & ASR whenever the appointment time is required on                   products that are TXTYP=D (D = Appointment
 61 Closed     Followup           Q # 47          Consumer       9/3/04 the UNEP order.                                              9/10/04 Scheduling non-UBL Products - including UNE-P)

                                                                                                                                             9/10/04: Sent to SME
                                                                                                                                             9/17/04: (a) This difference is a result of our
                                                                                                                                             making updates to usage only as we review those
                                                                                                                                             fields for given products. As we review fields by
                                                                                                                                             product for other CRs we review whether there are
                                                                                                                                             valid value edits, etc. that would make the field
                                                                        Follow-up to Question #11 Since the requirement to                   conditional for that product only. The usage is
                                                                        migrate by TN and SANO with SCR093003-                               "conditional" based on valid values requirements,
                                                                        01/SCR120403-01 for LNP is similar to IMA 12.0                       but we didn't work the UNE-P product with this CR,
                                                                        SCR061302-01 for UNEP POTS, I expected similar                       so we only changed the LNP usage and not usage
                                                                        business rules however this is not the case for the                  for all other products.
                                                                        following fields. (a) For Product 25 the AFT field (EU               (b) For LNP, if the address is
                                                                        #10) for ACT= V & Z is optional however for Product                  unnumbered/descriptive with a Rural Route and
                                                                        5 for the same ACT types this field is conditional (b)               Box, that information needs to be provided.
                                                                        For Product 25 the ROUTE field (EU #25b) for ACT=                    Unnumbered/Descriptive addresses were excluded
                                                                        V & Z is optional however for Product 5 for the same                 from this abbrv order information for this candidate.
                                                                        ACT types this field is conditional. (c) For Product 25              UNE-P POTS was slightly different and appears to
                                                                        the STATE field (EU #27) for ACT= V & Z is required                  allow for the unnumbered/desc addresses.
                                                  AT&T                  however for Product 5 for the same ACT types this                    (c) Qwest is deriving the state for this product set.
 62 Closed     Followup           Q # 11          Consumer       9/3/04 field is optional.                                           9/17/04 STATE is, therefore, not required for LNP.

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 21 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                   Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                           Answered                  Resolution/Answer

                                                                                                                                                Qwest has always and still requires a range in
                                                                                                                                                APPTIME.
                                                                                                                                                The change you are asking about affected ABTIME
                                                                        Follow-up to Q&A Question #13            Answer stated                  and the change was concurrent with IMA 16.0
                                                                        "For TXTYP=D, the changes are to clarify already                        SCR012204-01RG (TRO BHC IMA Changes and
                                                                        existing rules only, f.i. ASQ11, ABTIME changes                         Appointment Scheduler). With the CR, Qwest
                                                                        from: HHMM-HHMM or HHMM to: If TXTYP=D                                  introduced a new TXTYP=C and cleaned up
                                                                        HHMM-HHMM If TXTYP=U HHMM This applies to                               existing appointment scheduling functionality to
                                                                        both PreOrder and Order."       It this really an existing              always return a range for TXTYP=D (D =
                                                                        rule (QWEST made a software change after event                          Appointment Scheduling non-UBL Products) so
                                                  AT&T                  notification #100996) or is this a change effective with                there is no need to convert a single time returned
 63 Closed     Followup           Q # 13          Consumer       9/3/04 IMA 16.0 ?
                                                                        Follow-up Q&A to question #45 Answer stated "For                9/10/04 in ABTIME to a range in APPTIME going forward.
                                                                        Pre-order, Qwest will provide Pending Disconnect
                                                                        information on the CSR Response as indicated
                                                                        below: VCSR eligible. When CSR date precedes the
                                                                        pending disconnect the disconnect order and due
                                                                        date will appear in the pending order tab on the CSR
                                                                        response, the account status will = DISC When
                                                                        CSR date post dates the pending disconnect the
                                                                        CSR is not returned Not VCSR eligible
                                                                        Functionality will not change. The CSR returned will
                                                                        always be a static CSR from BOSS/CARS and a
                                                                        pending disconnect will result in account status =
                                                                        DISC. "                                         When the
                                                                        CSR is not returned because the CSR post dates the
                                                                        pending disconnect, will we receive a unique error
                                                                        message so we can detect this? Today, since we pull                     There will be a new error message introduced.
                                                                        a static CSR we can detect this right away with the                     “Order <ordnumber> is disconnecting the account
                                                                        DISC status and alert the customer. Sometimes the                       on <CCYYMMDD> Order activity is not allowed for
                                                                        customer is unaware that they may have caused this                      requests that will complete after the account
                                                                        to happen if they told the old LSP to discontinue their                 disconnect has occurred.” Where <ordnumber> is
                                                                        service when they really wanted to keep their TN and                    the D order number and <CCYYMMDD> is the D
                                                  AT&T                  move their existing service to another LSP. I'm trying                  order‟s due date. Also the pending Dorder will be
 64 Closed     Followup           Q # 45          Consumer       9/3/04 to understand if we still have this option in the virtual       9/10/04 found in the Pending Orders section/tab.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 22 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                   Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                           Answered                  Resolution/Answer


                                                                        Is Parenthesis allowed or not allowed in the Listed
                                                                        Last Name (LNLN) field on the DL Form?
                                                                        The Disclosure Document contains conflicting
                                                                        information (see below):
                                                                        Appendix C states the following under the Valid
                                                                        Values column for the LNLN field (see pages 56 - 59)
                                                                        The following special characters are allowed: ( )
                                                                        (Parenthesis): - First letter following a parenthesis will
                                                                        be capitalized - Double Parenthesis is required for a
                                                                        single set of Parenthesis to appear in the LNFN -
                                                                        May not be used as the first or last character in the
                                                                        LNFN - Must be preceded and followed by an alpha
                                                                        or numeric character                                                    Parenthesis are allowed for LNLN. The Developer
                                                                        The following characters are NOT allowed in this                        Worksheet will be updated to remove the
                                                                        field: ;(Semicolon)...,(Comma)...= (Equal)...- -                        Parenthesis from the "Not Allowed" list. The
                                              AT&T                      (Consecutive hyphens)...?(Question mark)...$ (Dollar                    update will go into Addendum #1 publishing on
 65 Closed     App C: DL          DL: 44-LNLN Consumer           9/7/04 sign)...( )(Parenthesis)...+(Plus Sign)...@(At Sign)
                                                                        Follow-up to Question #49                                       9/10/04 11/1/04.
                                                                        IMA Data Conversion (see page 55) are discussed in
                                                                        the IMA 16.0 EDI Implementation Guide. Has
                                                                        QWEST identified any data conversions for IMA
                                                                        16.0? When we move from IMA 15.0 to IMA 16.0 are
                                                                        we required to convert or change any information on
                                                                        our in-flight IMA 15.0 orders?              During our
                                                                        IMA 13.0 to IMA 14.0 Conversion we ran into
                                                                        problems which were documented with event
                                                                        notifications 695258 & 701532.                   The
                                                                        problems seem to occur when data was sent
                                                                        differently than the previous IMA version. In the IMA
                                                                        13.0 to IMA 14.0 upgrade, our SUP orders ran into
                                                                        problems with: (1) blocking in the REMARKS field for
                                                                        IMA 13 vs the BLOCK field in IMA 14 (2) Conversion
                                                                        Indicator (CONVIND) field used in IMA 13 vs
                                                                        Migration Indicator (MI) field used in IMA 14.
                                                                        We want to ensure the successful completion of our                      Qwest does not forsee any conversion issues with
                                                                        in-flight orders and including any in-flight orders that                a migration from IMA EDI 15.0 to 16.0. Should
                                                                        may need to be SUP'D.          For example, effective                   unforseen issues arise post-migration, Qwest will
                                                                        with IMA 16.0 there is an additional CALA value and                     immediately pursue correction of those issues and
                                                  AT&T                  new business rules for the population of the RS #67                     notify all CLECs via the current Event Notification
 66 Closed     Followup           Q # 49          Consumer       9/7/04 PULSE field. Are there any CLEC conversion                      9/10/04 process.

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                   Page 23 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                         Answered                    Resolution/Answer

                                                                        This question was raised in the 16.0 walkthrough
                                                                        however I do not see it captured in the question log or
                                                                        comments. The PSON action value of R = Recap or
                                                                        Blank = Recap. Please provide the business rules as
                                                                        to when a CLEC will see an R in the Action field or
                                                                        when the action field will be blank. Clecs do have
                                  PSON: 16-                             automation that checks PSONs and need to define                       The question (and answer) appear as number 38 in
 67 Closed     App D: PSON        Action Code Eschelon           9/9/04 these rules for their automation.                             9/10/04 the response document and in this log.
                                                                                                                                              The URL in these product chapters will be updated
                                                                                                                                              with Addendum #1 posting on 11/1/04.
                                                                                                                                              The new URLs will be:
                                                                        According to product chapters 67, 68, 69 under                        For PN and BCN the descriptions are in the
                                                                        Business Description the URL is listed as: URL:                       Provisioning and Installation PCAT
                                                                        http://www.qwest.com/wholesale/clecs/ordering.html .                  (http://www.qwest.com/wholesale/clecs/provisionin
                                                                        However when visting this link there is no business                   g.html)
                                                                        description available for PN, BCN, or BCH. You can                    For BHC the description will be at
                                                                        not find any information regarding these three                        <http://www.qwest.com/wholesale/clecs/batchhotc
                                                                        activities in this link. Please indicate the correct URL              ut.html> however, it is a new pcat with this release
 68 Closed     PN, BCN, BHC       Bus Descr.      Eschelon      9/10/04 for these three statuses.                                     9/17/04 and has not yet published to the web.
                                                                        1) If you subscribe to the Provider Notification (PN)
                                                                        notices via EDI do you still receive the full Loss
                                                                        Report each month?            2) If you subscribe to the              1. If you subscribe to PN notices via EDI, you will
                                                                        Billing Completion Notices via EDI, is it correct that                continue to receive your daily Loss & Completion
                                                                        you will receive only the BCN for LSRs sent via EDI?                  reports. That is a daily, not monthly, report.
                                                                        Any LSRs sent via IMA GUI will continue to be sent                    2. You are correct. BCN by EDI will only be
 69 Closed     PN, BCN            General         Eschelon      9/10/04 via email?                                                    9/17/04 returned to you for EDI transactions.

                                                                                                                                                9/17/04: Sent to SME
                                                                        Follow-up to Q&A # 54                                                   9/24/04: Even though the PREMIS conversion to
                                                                        I still don't understand why the SANO field length was                  LFACS AN change that was dictated by the new
                                                                        only increased for the AVR Multiple and Near Match                      OSS only changed the SANO field length for this
                                                                        Address section (AVR59). Unlikely the CITY, TTA                         one field (AVR59) and not for all instances of the
                                                                        & CALA field, the SANO field was not updated                            SANO, this is not a problem for CLECs. Currently,
                                                                        everywhere SANO existed. It doesn't make sense                          Qwest is not aware of any SANO larger than 8
                                                                        for the SANO field to increase from 8 to 15 for the                     characters within the 14-state region. In the rare
                                                                        AVR Multiple and Near Match Address section and                         instance where there is a SANO larger than 8
                                                                        not for the others (AVQ11, AVR15, CSRQ14,                               characters, Qwest will manage the order and all
                                                  AT&T                  CSRQ41, CSRQ67, CSRR45, CSRR114, FAQ18,                                 other preorder transactions to ensure consistency.
 70 Closed     Followup           Q # 54          Consumer      9/10/04 LQQ18, RLDQ13, TNAQ13, EU13).                                 9/24/04


Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 24 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                      Resolution/Answer
                                                                                                                                           9/17/04: Sent to SME
                                                                        Follow-up to Q&A #66                                               9/24/04:
                                                                        How will the new CALA value be managed?                            CALA - LFACS AN will be rolled out by region/wire
                                                                        We currently store the validated address retrieved                 center after 16.0 deploys in October. A notification
                                                                        during the initial migration or new install order and              will be distributed to all CLECs with information
                                                                        use this address on subsequent order activity. For                 regarding the migration dates per region. In
                                                                        example, if we have an AT&T UNEP POTS end user                     addition, individual notification will be provided 48
                                                                        that resides in northern Idaho, do we have to convert              hours prior to each migration. This notification will
                                                                        their CALA from "IDO" to "NIDO" or will QWEST                      provide the details of the applicability of each new
                                                                        continue to accept a CALA value of "IDO" on our                    CALA to the CLECs. CLECs will be provided with
                                                                        orders (ie ACT=R)?                                                 information as to how to manage the CALA values
                                                                        How will the new PULSE rule be managed?                            going forward.
                                                                        For example, PULSE is now required for South                       This will only impact the border towns that are in a
                                                                        Dakota. When we convert from IMA 15.0 to IMA 16.0,                 list that will be provided to the CLEC's. For
                                                                        will our pending IMA 15 South Dakota orders reject                 example, if you have a customer who lives in one
                                                                        because they won't have PULSE information or will                  of these bordertowns with the CALA of IDO then
                                                                        QWEST assume a default value of touchtone on                       when you issue the new order you will need to put
                                                  AT&T                  these orders? Will our existing South Dakota end                   in ID for the CALA. The information will need to be
 71 Closed     Followup           Q # 66          Consumer      9/10/04 users be defaulted to touchtone?                           9/24/04 converted once the wire center for LFACS AN




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 25 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor                                     Issue/Question
                                                               Opened Bill Micou had asked the following R16 question and         Answered                  Resolution/Answer
                                                                        received a response via the Q&A R16 Log:
                                                                        Bill Micou, AT&T: While reviewing Appendix F
                                                                        "Appendices - Change Summary 15.0 - 16.0", I
                                                                        noticed a change to Appendix J "Product Family and
                                                                        Product Matrices" that is in conflict with our current
                                                                        use of ACT = "Z" and does not agree with any other
                                                                        definition of ACT = "Z in this Appendix. In Section
                                                                        1.2.2 for Local Number Portability (LNP), on page
                                                                        191, ACT = "Z" has a change that makes the wording
                                                                        the same as ACT = "V". The change replaces the
                                                                        text "retain the current listings" with the text "will
                                                                        discontinue the Listing(s) associated with the Port
                                                                        Activity (all listings are removed)." In all other
                                                                        instances of ACT = "Z" in Appendix J, the "retain the
                                                                        current listings" text is unchanged.
                                                                        Question: Is this truly a change in definition for                   With the posting of Final Disclosure on September
                                                                        REQTYP = "C", ACT = "Z" or is this a typographical                   3, 2004, Appendix J was updated to correct
                                                                        error?                                                               Section 1.2.2, as noted in the response to Bill's
                                                                        Answer: Qwest is revising Appendix J to reflect the                  question.
                                                                        difference between ACT=Z and ACT=V. Qwest will                       The changes from 15.0 FINAL to 16.0 DRAFT are
                                                                        retain the listings.                                                 on pages 1-355 of the document (The change you
                                                                        But when I review the R16 documentation posted on                    reference is on page 206). DRAFT to FINAL
                                                  AT&T                  the QWEST web site, I don't believe the                              changes begin on page 356. The change you are
 72 Closed     Followup           Q # 12          Business      9/10/04 documentation has been completely updated.                   9/17/04 looking for appears on page 366.
                                                                        With IMA 16.0 Qwest is introducing the capability to
                                                                        retrieve a Virtual CSR. Will SATE include one or                     SATE does have one CSR with pending service
                                                                        more CSR test cases whereby a CLEC can test this                     order section in the CSR response to let CLECs
                                                                        new functionality, i.e., retrieve a CSR with future in-              test the new CSRR 855 map. This is a new test
 73 Closed     App A: CSR         VCSR            MCI           9/13/04 progress service orders?                                     9/17/04 case with 16.0 and is CSR14.
                                                                        The new CSR Inquiry field CSR DATE is a required
                                                                        field. How far into the future can a CLEC populate
                                                                        the CSR DATE field? Is there a Qwest constraint of
                                  CSRQ: 7a-                             say 1 year or what? Not stated in Negotiated
 74 Closed     App A: CSR         CSR DATE        MCI           9/13/04 Business Rules.                                              9/17/04 You may populate a date up to 1 year in the future.
                                                                        Based on the Product Chapter Changes,
                                                                        N2*NAMEEU-9 should be added also along with
                                                                        N1*IT*LOC ACC in Chapter 17: LNP (EU.NAME),
                                  Mapping                               however I don‟t see it listed in the current chapter 17              You are correct. The product chapter 17 will be
 75 Closed     CSR                Example         Accenture     9/14/04 document?                                                    9/17/04 updated with Addendum #1 on 11/1/04.



Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 26 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                   Resolution/Answer

                                                                                                                                           Just the notes re: CIP, CSO1 and CSO2 not being
                                                                                                                                           valid on the 860 are changing. These segments
                                                                                                                                           were previously prohibited on the 860 transaction -
                                                                                                                                           so there was a note on the 850 mapping example
                                                                                                                                           and those segments were also noted in the
                                                                                                                                           differences information on the 860 mapping
                                                                                                                                           example. With 16.0, those segments are valid for
                                                                                                                                           860 transactions - therefore, the notes on the 850
                                                                                                                                           mapping example were removed and those
                                                                                                                                           segments were also removed from the 860
                                                                        UNEP (CIP, CSO1, CSO2). Based on the Product                       mapping example as they are no longer "different"
                                                                        Chapter Changes, only the note "(Prohibited on the                 than what was outlined for the 850. For 16.0 you
                                  Mapping                               860)" is being removed and not the segments? Is this               may send CIP, CSO1 and CSO2 setments on
 76 Closed     CSR                Example         Accenture     9/14/04 true?                                                              A: LSTR or preorder function
                                                                                                                                   9/17/04 either 850is a860 transactions. available via IMA
                                                                                                                                           GUI/EDI whereas DLIS is a separate application
                                                                                                                                           altogether. You need to request and obtain access
                                                                                                                                           to that DLIS application completely independent
                                                                                                                                           and separate from any IMA access processes
                                                                                                                                           (there is no IMA GUI or EDI interface into DLIS).
                                                                                                                                           DLIS is used to view listing information only. IMA
                                                                                                                                           LSTR provides the same functionality as DLIS,
                                                                                                                                           with the exception of viewing Caption Sets. IMA
                                                                                                                                           GUI and EDI both also allow the user to order
                                                                                                                                           listings electronically using FBDL – where DLIS is
                                                                                                                                           not an ordering system.
                                                                                                                                           B: As mentioned in (a) – general listing information
                                                                                                                                           is the same on both IMA LSTR and DLIS. DLIS is
                                                                        (a) What is the difference between the IMA GUI / IMA               a little more user friendly and allows a view of SLU
                                                                        EDI PreOrder Listing Reconciliation (LSTR) Query                   sets and Caption Sets.
                                                                        and Directory Listing Inquiry System (DLIS)? (b)                   C: Again, DLIS is only to view listings whereas
                                                                        Can we obtain the same level of FBDL information                   LSTR in IMA GUI/EDI allows viewing of the listing
                                                                        from both? (c) Or does one contain more listing                    and IMA GUI/EDI also allows order entry via FBDL.
                                                                        information than the other? In other words, is there               D: Since DLIS is only used to view listing
                                                                        any reasons/rules to use one over the other? (d) If a              information, it would never provide error detail.
                                                                        previous FBDL order was processed but contained                    Neither does IMA LSTR, since it is only a dip into
                                                                        an error, will the PreOrder LSTR and/or DLIS                       the Listing Database and provides a means to view
                                                                        response give us information about any outstanding                 listing information. Error Detail is ONLY available
                                                  AT&T                  DSRED error? (e) Will one contain more information                 on the DSRED which is generated in response to
 77 Closed     DLIS & LSTR        General         Consumer      9/14/04 about the DSRED error than another?                        9/17/04 an FBDL order.


Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 27 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened Question regardingIssue/Question diagram in
                                                                                               the Order Flow                   Answered                 Resolution/Answer
                                                                        Chapter 64 FBDL (see pages 3 thru 5)
                                                                        (1) Please confirm that the "855 DSRED"
                                                                        (Confirmation) in the Normal Order Flow diagram
                                                                        represent a DSRED response with an RT value of "L"
                                                                        for Accepted (AT - Confirmed Update On PON).
                                                                        (2) Noticed that the 855 FATAL is not referred to as
                                                                        the 855 DSRED FATAL, please confirm that the 855                   (1) The 855 DSRED response in the Normal Order
                                                                        Fatal illustrated in the diagram is a DSRED response               Flow could be either an L (AT).
                                                                        (not an LR response).                                              (2) The 855 FATAL is a LR response - it is a
                                                                        (3) There is a statement that "The Co-Provider,                    system reject returned from the BPL.
                                                                        having received the system generated 855 Fatal,                    (3) The 855 FATAL returned for FBDL orders is a
                                                                        needs to correct the 850 FBDL Listing order with the               system generated Fatal (Local Response). Once
                                                                        same or new PON, and transmit the 850 FBDL                         the order makes it into Qwest's OSS, you will
                                                                        Listing order as an original request." Are all 855                 receive DSRED responses. (Please note that for
                                                                        Fatals system generated?                                           other products, the 855 Fatal could either be
                                                                        (4) Please confirm that the 855 FATAL in the                       system- or manually-generated.)
                                                                        Exception Order Flow diagram represent a DSRED                     (4) The 855 FATAL is a LR response - it is a
                                                                        response with an RT value of "N" for Reject with                   system reject returned from the BPL which errors
                                                                        Cancel (RF - Subsequent Fatal Update On PON).                      out your order before it makes it into Qwest's
                                                                        (5) Please confirm that the 855 DSRED REJECT in                    systems. It is NOT a DSRED response. Once the
                                                                        the Exception Order Flow diagram represent a                       order makes it into Qwest's OSS, you will receive
                                                                        DSRED response with an RT value of "E" for Reject                  DSRED responses.
                                                                        with Exception Detail only (RF - Initial Fatal Update              (5) The 855 DSRED REJECT in the order flow
                                                                        On PON).                                                           diagram represents a DSRED with an RT value of
                                                  AT&T                  (6) Please confirm that the 855 DSRED ACCEPT                       E (RF) or N (RF).
 78 Closed     FBDL               Order Flow      Consumer      9/15/04 WITH OR WITHOUT CHANGE in the Exception                    9/17/04 (6) Correct.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                            Page 28 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                               Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                        Answered                Resolution/Answer

                                                                        From Pg 8 of the IMA Facility Based Directory
                                                                        Listings Corrective Procedures and
                                                                        Confirmation/Error Codes, Dated July 29, 2004,
                                                                        Version 2.03
                                                                        "Note: FBDL orders that receive an RF PON status
                                                                        will remain in a rejected status for 10 calendar days.
                                                                        This will allow you to analyze the confirmation/errors
                                                                        on the order, determine corrective procedures, and
                                                                        resend/resubmit the PON. If you attempt to
                                                                        resend/resubmit the request after the 10 calendar
                                                                        day timeframe, IMA will notify you that the PON has
                                                                        been cancelled."
                                                                        Does this 10 calendar rule apply to IMA EDI DSRED
                                                  AT&T                  FATAL and REJECT (as defined in Exception Order                     This applies to the 855 DSRED with an RF PON
 79 Closed     Errors List        FBDL            Consumer      9/16/04 Flow diagram in Chapter 64 - FBDL)?                         9/17/04 status.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                           Page 29 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                             Date
Q#   Status          Form             Name          Vendor                                  Issue/Question
                                                               Opened Scenario 2 on Page 11 of the IMA Facility Based                                      Resolution/Answer
                                                                                                                               Answered (a) The Subsequent DSRED would show an RF
                                                                        Directory Listings Corrective Procedures and                      status indicating the LOC could not process the
                                                                        Confirmation/Error Codes dated July 29, 2004,                     order.
                                                                        Version 2.03 states:      "Corrective Procedure: The              (b) It is not common for the Initial and Subsequent
                                                                        PON Level Confirmation/Error Code (ULAC0C)                        DSREDs to have the same outcome. In the
                                                                        indicates the PON partially processed to the listing              scenario where an Initial DSRED shows AC due to
                                                                        database, but may have errors that require Qwest                  an existing account, the Subsequent DSRED
                                                                        follow up. The Listing Level Confirmation/Error Code              would be an RF. We only send ACs on
                                                                        (UL495P) tells the Qwest LOC that there is already                Subsequent DSREDs when we are awaiting a Port
                                                                        an existing main listing record at that telephone                 Order completion and/or for some reason, we need
                                                                        number. The Qwest LOC removes the new LML from                    extra time to analyze the error condition.
                                                                        the database. On the Subsequent DSRED, Qwest                      (c) This is partially correct. A Subsequent DSRED
                                                                        LOC advises you that your new RTY LML listing is                  is always provided when the Initial DSRED had an
                                                                        not in the database. You must determine if the                    AC PON Status. The errors that resulted in the AC
                                                                        existing LML listing is correct, needs changes, or                required a LOC Order Specialist to analyze and
                                                                        needs to be removed, and issue a new PON if                       determine corrective procedures. In some cases,
                                                                        appropriate."                                                     the error may have been the result of our tables
                                                                        (a) Based on this example, how will the subsequent                not being updated in which case we can correct
                                                                        DSRED differ from the initial DSRED?                              the error and send an AT on the Subsequent
                                                                        (b) I don't understand the purpose of the subsequent              DSRED. If the problem is truly not on our side but
                                                                        DSRED since it had the same outcome as the initial                we still had to analyze the error to determine it, we
                                                                        DSRED response. Should we always expect the                       will send back the Subsequent DSRED with an RF
                                                                        same outcome on the subsequent DSRED?                             and explain what the Provider needs to do to
                                                                        (c) Is the purpose of the subsequent DSRED to try to              correct the condition. Or, we may send back an
                                                                        provide a resolution to the issue with the initial                AD which means we were able to resolve some of
                                                  AT&T                  DSRED or is it just a means to allow QWEST                        the listing discrepancies, but others require the
 80 Closed     FBDL Errors List   Scenario 2      Consumer      9/16/04 additional time to cleanup/prep the listing database      9/24/04 Provider to determine resolution.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 30 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor                                    Issue/Question
                                                               Opened Scenario 3 on Page 12 of the IMA Facility Based           Answered                     Resolution/Answer
                                                                        Directory Listings Corrective Procedures and
                                                                        Confirmation/Error Codes dated July 29, 2004,
                                                                        Version 2.03 states:         "Scenario: You submitted a
                                                                        PON with an ACT C to change a customer's listed
                                                                        name for the RTY LML and to add a new Local
                                                                        Additional Main Listing (LAM). An error was detected
                                                                        on the LML because the No Solicitation (NOSL) field
                                                                        was marked and is not allowed for the state in which
                                                                        this listing appears. There was also an error detected
                                                                        on the LAM record because the Listed Telephone
                                                                        Number (LTN) is the same as the Account Telephone
                                                                        Number (AN)."         "The PON Level
                                                                        Confirmation/Error Code (ULAD0C) indicates the
                                                                        PON was partially processed to the listing database,               (a) Yes, as stated in the Document.
                                                                        but may have errors that require Provider follow up.               (b) Yes, as stated in the Document.
                                                                        The LML listed name change was successfully                        (c) Correct
                                                                        processed, however the Listing Level                               (d) Correct, there is no follow-up on the Qwest side
                                                                        Confirmation/Error Code (UI046A) indicates there is                nor do we require a correcting order for the
                                                                        an advice error. The NOSL privacy indicator was                    LML/NOSL. However, there is work required for
                                                                        requested for this listing, but is not allowed because             the LAM. The intent of this example was to show
                                                                        the listing is not in a state that allows NOSL, and the            that the initial Provider Order was an ACT=N,
                                                                        NOSL was discarded. The Listing Level                              however, since the LML posted successfully, the
                                                                        Confirmation/Error Code (UI047F) on the LAM                        account has been established and when the
                                                                        record, indicates that the listing was not processed to            Provider corrects the LAM error, they will need to
                                                                        the database. An LAM record must have an LTN that                  issue an ACT=C to make a change to an existing
                                                                        is different from the AN. You must resubmit a new                  account.
                                                                        PON with an ACT C. The RTY LML must be                             (e) Likely, but each condition should be
                                                  AT&T                  recapped on the new PON using a LACT Z, since the                  viewed/analyzed. It would not be a safe
 81 Closed     FBDL Errors List   Scenario 3      Consumer      9/16/04 update on that record already successfully processed       9/24/04 assumption that all Advices can be ignored.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 31 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                Product or DWS      Field # or    Software     Date                                                              Date
Q#   Status          Form             Name         Vendor     Opened                     Issue/Question                        Answered                  Resolution/Answer


                                                                       Please explain the DSRED RT status of "N" and "E".
                                                                       The Developer Worksheet (DWS) for DSRD5 RT field
                                                                       on the DSRED Form states the following under valid
                                                                       values:
                                                                       E = Reject with Exception Detail only (RF - Initial
                                                                       Fatal Update On PON)
                                                                       N = Reject with Cancel (RF - Subsequent Fatal
                                                                       Update On PON)
                                                                       Based on the FDBL and DSRED DWS chapters, I
                                                                       originally thought RT = "N" was used for the DSRED
                                                                       FATAL Response (BAK01=01, BAK02=RF, PON                            The Initial RF that has a RT= E indicates they can
                                                                       LECODE=ULRF0F) and RT= "E" was used for the                        retrieve the PON and re-submit/re-send it (using
                                                                       DSRED REJECT Response (BAK01=44, BAK02=RF,                         the same PON) once they‟ve made the necessary
                                                                       PON LECODE=ULRF0F) however the refers to                           corrections – based on the error codes. A
                                                                       "initial" and "subsequent" fatal in the DWS appendix               Subsequent RF that has an RT=N indicates the
                                                                       description above seems to contradict my                           Initial DSRED was an AC status and after the LOC
                                                                       understanding.               Please explain :                      analyzed the errors, determine they could not
                                                                       (1) under what situations can we expect RT=E vs                    update the database and are subsequently
                                                                       RT=N on the DSRED                                                  Rejecting the PON. The Provider cannot re-use
                                             AT&T                      (2) what should we use to tell the difference between              the PON in this case, they need to issue a new
 82 Closed     App C: DL          DSRD: 5-RT Consumer          9/17/04 the initial DSRED vs the subsequent DSRED.                 9/24/04 PON with the correct/revised data entry.
                                                                                                                                          ACT=V on your LNP order will drop the existing
                                                                                                                                          listing. So, there is no listing to do a CLEC to
                                                                                                                                          CLEC conversion for. You would need to submit
                                                AT&T                   Is ACT=W valid for Product 14 (FBDL) if you use                    your FBDL order for that account as a New listing
 83 Closed     App J              Section 1.1.2 Consumer       9/17/04 ACT=V for Product 5 (LNP)?                                 9/24/04 (FBDL ACT=N).
                                                                                                                                          The LACT information for ACT=T will be corrected
                                                                       Conflict found in Appendix J, Section 1.1.2 Facility               (in 16.0 Disclosure Adddendum #1 posting on
                                                                       Based Directory Listings (FBDL)                                    11/1/04) to match the business rule. The new
                                                                       ACT=T (pg 5) states the valid LACT values are N, D,                LACT information will be :
                                                                       I, O.                                                              When RTY=LML, then LACT must = I, O or Z.
                                                AT&T                   LACT=Z (pg 6) states that this is allowed on ACT=T                 When RTY=anything but LML, then LACT must =
 84 Closed     App J              Section 1.1.2 Consumer       9/17/04 Which one is correct? Is LACT Z valid for ACT=T?           9/24/04 N, D, I, O or Z.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                            Page 32 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                         Answered                  Resolution/Answer

                                                                        On the DL form you will find the field LNFN #45.
                                                                        Under the valid values section you find the period                   The period can not be the first character.
                                                                        listed as “valid as a first character”, however                      The DL form (45-LNFN) will be updated with 16.0
                                                                        immediately follow that there is a rule stating that it              Disclosure Addendum #1 (posting on 11/1/04) to
                                                                        must be preceded by or followed by a character?                      read as follows…
                                                                        . (Period, dot, point)                                               . (Period, dot, point)
                                                                        - Valid as 1st character                                             – Must be preceded by and followed by a
 85 Closed     App C: DL          DL: 45-LNFN Accenture         9/17/04 – Must be preceded by and followed by a character            9/24/04 character
                                                                        Follow-up to Answer #78
                                                                        Answer #78 was very helpful
                                                                        (1) Can we update Exception Order Flow in Chapter
                                                                        64 to indicate "855 LR FATAL" instead of "855
                                                                        FATAL"?
                                                                        (2) Can we also update the Exception Order Flow in
                                                                        Chapter 64 to indicate all of the associated LR values
                                                                        as provided in answer #78 to help link this                          1 & 2: The Order Flows in Chapter 64 will be
                                                                        information to the other FBDL documentation.                         updated to clarify this information with Addendum
                                                  AT&T                  (3) Please confirm that the 855 LR FATAL will return                 #1 posting on 11/1/04.
 86 Closed     FBDL               Order Flow      Consumer      9/17/04 an RT value of "Z"?                                          9/24/04 3: The 855 Fatal (LR) will be an RT value of "Z"
                                                                        On the DL form, for field #44 (LNLN) under the valid
                                                                        values you find the following conditions listed for
                                                                        parenthesis: ( ) (Parenthesis)
                                                                        - First letter following a parenthesis will be
                                                                        capitalized
                                                                        - Double Parenthesis is required for a single set of
                                                                        Parenthesis to appear in the LNFN?
                                                                        - May not be used as the first or last character in the
                                                                        LNFN?
                                                                        - Must be preceded and followed by an alpha or
                                                                        numeric character                                                    The reference should read LNLN. This will be
                                                                        Should the reference to the LNFN field above be                      corrected with 16.0 Disclosure - Addendum #1
 87 Closed     App C: DL          DL: 44-LNLN Accenture         9/20/04 changed to read LNLN?                                        9/24/04 posting on 11/1/04.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 33 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                          Answered                  Resolution/Answer

                                                                        As we talked about on Thursday. The question I am
                                                                        trying to get more information on is number 67 on the
                                                                        question log.
                                                                        This question was raised in the 16.0 walkthrough
                                                                        however I do not see it captured in the question log or
                                                                        comments. The PSON action value of R = Recap or
                                                                        Blank = Recap. Please provide the business rules as
                                                                        to when a CLEC will see an R in the Action field or                   R or Blank will be consistent on a single
                                                                        when the action field will be blank. CLECs do have                    Completion or PSON. A single completion will not
                                                                        automation that checks PSONs and need to define                       have both R's and Blanks.
                                                                        these rules for their automation.                                     Whether a Recap is displayed as R or Blank
                                                                        The answer simply refers me back to the fact that we                  depends on the region:
                                                                        will see an R and a Blank. I need to find out if there                R = Recap (Eastern/Western region)
                                                                        is any way for us to determine in what instances we                   Not Populated (EDI Only), Blank = Recap (Central
                                                                        will see a blank vs an R. Example - If the order goes                 region)
                                                                        FT will it always be a blank vs if it falls to manual                 This will be clarified in the 16.0 Disclosure
 88 Closed     Followup           Q # 67, 38      Eschelon      9/20/04 handling it will always have an R.                            9/24/04 Addendum #1 posting on 11/1/04.
                                                                        Facility-Based CLECs and Reseller/Unbundled
                                                                        Network CLECs Directory Listing User Document
                                                                        (http://www.qwest.com/wholesale/downloads/2004/04
                                                                        0907/WPDL_User_Doc_V4_05.doc) page 3-18
                                                                        "General Rules for Punctuation, Capitalization and
                                                                        Symbols" implies that the normal capitalization rules
                                                                        will be applied to the listed name field unless
                                                                        specified otherwise using the special characters
                                                                        listed in this section.                                               In the future, for general FBDL capitalization and
                                                                        (a)Based on the normal capitalization rules, please                   other usage information, please contact your LRS
                                                                        confirm that if we send the Listed Name in the                        Account Manager. The referenced document is not
                                                                        following case format "JANE DOE", "jane doe" or                       an EDI document nor are the rules contained
                                                                        "jANe doE" we will always get the same result "Jane                   therein specific to EDI provisioning of FBDL.
                                                                        Doe" printed in the actual Directory.                                 (a) Yes
                                                                        (b)Does the normal capitalization rule apply for all                  (b) Yes, no exclusions in terms of the Listed Name
                                                                        products? If not, which products are excluded and                     fields. There may be some fields where the rules
                                                                        what is the rule?                                                     are different, such as DES. The first character is
                                                                        (c)Does the normal capitalization rules apply to more                 always lower case unless an asterisk is used.
                                                                        than the listed name field? For examples does it also                 (c) Each field has the same rules unless
                                                                        apply to the all listing related fields such as address,              otherwise documented.
                                                                        title of lineage, designation, etc?                                   (d) No – again, field specific rules are
                                                  AT&T                  (d)I've noticed that the X12 Mapping Examples for the                 documented.
 89 Closed     FBDL               General         Consumer      9/20/04 previous release, shows FBDL examples with all

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 34 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                         Answered                  Resolution/Answer


                                                                        (a) Please confirm that the following Account Number
                                                                        (AN) rule stated on the DWS LSR form should not
                                                                        include Product 14 (FBDL): "Note: When multiple
                                                                        CSR exists for a TN, and ACT = W, V or Z, customer
                                                                        code should be included as part of the AN"
                                                                        (b) If a customer has several lines and wants a listing              (a) Correct, since FBDL does not have CSR.
                                                                        for each line, can we establish separate FBDL                        (b) There should be one Account Number per
                                                                        Account Numbers for each TN at the same service                      Service Address. If an end user wants additional
                                                                        address?         (c) How are accounts defined in the                 lines, they can be established as Additional
                                                                        FBDL world?          (d) What are the rules, if any,                 Listings carrying the same AN and SA.
                                                                        regarding FBDL accounts? The only rule that I've                     (c) Per AN
                                                  AT&T                  found is that the LTN of the Main Listing must match                 (d) Need more info on what you are looking for.
 90 Closed     FBDL               General         Consumer      9/20/04 the Account Number (AN) on the LSR.                                  Regardless documented in the (FBDL v. Listings
                                                                                                                                     9/24/04 All rules are of the Product TypeLSOG and DWS.
                                                                                                                                             Only), the rules are the same.
                                                                                                                                             An LAM is considered a Main type listing and the
                                                                                                                                             Listed Telephone Number must always be
                                                                                                                                             different than the LML Listed Telephone Number.
                                                                                                                                             Generally, LAMs are used when there are different
                                                                                                                                             Mains billed to the same AN. For example, you
                                                                                                                                             may have two different names billed to the same
                                                                                                                                             account. For example:
                                                                                                                                             LML Jones Body Shop             896-6970
                                                                                                                                             LAM Mike‟s Mechanics              555-0000
                                                                                                                                             An LAM is treated similar to an LML, in that the
                                                                                                                                             LAM will be entitled to a complimentary Yellow
                                                                                                                                             Page listing and is also up for grabs for Dex Media
                                                                                                                                             Sales Reps to contact to sell Yellow Page
                                                                                                                                             advertising. An LAM will also receive a White
                                                                                                                                             Page directory. An LAM is considered a Primary
                                                                                                                                             listing and is not billable (via FBDL).
                                                                                                                                             An LAL usually has the same telephone number as
                                                                                                                                             the LML, but it is feasible to have a different
                                                                        Please explain the difference between an Additional                  number. Many SLUs are set us with an LML and
                                                                        Listing (RTY=LAL) and Additional Main Listing                        LAL, for example:
                                                                        (RTY=LAM).                                                           LML Jones, Mike ins agent            896-6970
                                                                        Under what conditions must a listing be defined as a                 LAL      Fax                              555-0000
                                                                        Additional Main Listing (RTY=LAM) vs an Additional                    An LAL is not entitled to a complimentary Yellow
                                                  AT&T                  Listing (RTY=LAL)?                                                   Page listing and will not receive a White Page
 91 Closed     FBDL               General         Consumer      9/21/04 Does the rule differ based on UNEP POTs vs FBDL ?            9/24/04 Directory. This is considered a Premium listing

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 35 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                 Resolution/Answer

                                                                        (1) Conflicting Answers for the PULSE field on the
                                                                        RS form - which one is it?
                                                                        Q#48 The PULSE change is a new requirement
                                                                        effective with the IMA 16.0
                                                                        Q#71 The following informational rule was corrected
                                                                        to match the PCAT and how the System was already
                                                                        working.
                                                                        (2) I still don't have an answer to my original
                                                                        conversion questions regarding the PULSE field (see
                                                                        below). If the system is already working this way and
                                                                        requires the PULSE information for South Dakota.
                                                                        How is QWEST handling our South Dakota orders
                                                                        today since we're not sending it?
                                                                        Original Conversion Question: For example, PULSE
                                                                        is now required for South Dakota. When we convert                  10/1/04:
                                                                        from IMA 15.0 to IMA 16.0, will our pending IMA 15                 (1) #71 was the correct response. The answer to
                                                                        South Dakota orders reject because they won't have                 #48 should have been corrected when the answer
                                                                        PULSE information or will QWEST assume a default                   to #71 was published. This has now been
                                                  AT&T                  value of touchtone on these orders? Will our existing              corrected. We apologize for the confusion.
 92 Closed     Followup           Q # 48, 71      Consumer      9/24/04 South Dakota end users be defaulted to touchtone?          10/1/04 (2) Touchtone is the default for provisioning.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                            Page 36 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                   Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                                                    Resolution/Answer
                                                                                                                                     Answered (1) You will continue to receive all notifications
                                                                                                                                              regarding the conversion from PREMIS to LFACs
                                                                                                                                              AN according to CMP agreed-upon timelines. Any
                                                                                                                                              code-impacting changes to you (ie: new CALA
                                                                                                                                              values) were identified in the 16.0 documents,
                                                                                                                                              although those won't actually go into effect until
                                                                        Followup to Question #71 (email attachment below)                     those regions/wire centers are converted.
                                                                        My question was about the "IDO" to "NIDO" CALA                        (2) The CALA values were disclosed with 16.0
                                                                        value change associated with IMA 16.0 The answer                      Disclosure Document, and will be updated with
                                                                        provided seems to talk about a totally different and                  Addendum #1 (NIDO will not be a final CALA
                                                                        NEW CALA requirement change from "IDO" to "ID"                        value). The new values will be implemented with
                                                                        associated with the LFACS rollout.                                    the LFACs AN rollout notification for each
                                                                        (1) We will need as much advance notice as possible                   region/wire center.
                                                                        regarding these new non-release related
                                                                        requirements so we can prepare, test and schedule                       (Original Question): The answer to the original
                                                                        the changes required for the LFACs rollout.                             question was: "CALA - LFACS AN will be rolled
                                                                        (2) Is the CALA change from "IDO" to "NIDO" going                       out by region/wire center after 16.0 deploys in
                                                                        to be implemented with IMA 16.0 as stated in the                        October. A notification will be distributed to all
                                                                        Disclosure Document or is it going to be implemented                    CLECs with information regarding the migration
                                                                        with the LFAC rollout notification? If it is truly part of              dates per region. In addition, individual notification
                                                                        the IMA 16.0 implementation then please answer my                       will be provided 48 hours prior to each migration.
                                                                        original questions.                                                     This notification will provide the details of the
                                                                        Original CALA question:        "We currently store the                  applicability of each new CALA to the CLECs.
                                                                        validated address retrieved during the initial migration                CLECs will be provided with information as to how
                                                                        or new install order and use this address on                            to manage the CALA values going forward.
                                                                        subsequent order activity. For example, if we have an                   This will only impact the border towns that are in a
                                                                        AT&T UNEP POTS end user that resides in northern                        list that will be provided to the CLEC's. For
                                                                        Idaho, do we have to convert their CALA from "IDO"                      example, if you have a customer who lives in one
                                                  AT&T                  to "NIDO" or will QWEST continue to accept a CALA                       of these bordertowns with the CALA of IDO then
 93 Closed     Followup           Q # 71          Consumer      9/24/04 value of "IDO" on our orders (ie ACT=R)? "                      10/1/04 when you issue the new order you will need to put




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                     Page 37 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                  Date
Q#   Status          Form             Name          Vendor     Opened                         Issue/Question                        Answered                   Resolution/Answer
                                                                        Follow-up to Q&A # 90           The previously Question
                                                                        asked "can we establish separate FBDL Account
                                                                        Numbers for each TN at the same service address?"
                                                                        The answer provided stated " There should be one
                                                                        Account Number per Service Address". The answer
                                                                        explained what one "SHOULD" do but the question
                                                                        was asking about what one "CAN" do. Just trying to                     There can only be one main listing (LML) for an
                                                                        understand all of our options.            (a) Can a                    account number. Qwest knows that there are
                                                                        service address have more than one FBDL account                        multiple TNs for a given account. So, if you had an
                                                                        number?           (b) If so, what are the                              account with two TNs and you attempted to submit
                                                                        rules/restrictions (if any)? (c) Is there anything                     an FBDL order for each TN as a LML, that would
                                                                        preventing a CLEC from establishing separate FBDL                      error out. You need to submit the second TN as an
                                  General         AT&T                  Account Numbers for each TN at the same service                        additional listing as outlined in the original
 94 Closed     FBDL               Order           Consumer      9/24/04 address?                                                       10/1/04 response to #90.

                                                                        Follow-up to Question #82                "A Subsequent
                                                                        RF that has an RT=N indicates the Initial DSRED
                                                                        was an AC status and after the LOC analyzed the
                                                                        errors, determine they could not update the database
                                                                        and are subsequently Rejecting the PON. The
                                                                        Provider cannot re-use the PON in this case, they                      (1) The only time you may reuse a PON (for FBDL
                                                                        need to issue a new PON with the correct/revised                       orders) is when the Initial response is an RF (RT=
                                                                        data entry."        (1) Please list all of the                         E). This indicates you can retrieve the PON and re-
                                                                        circumstances a Provider can not re-use the PON on                     submit/re-send it (using the same PON) once
                                                                        a FBDL order?            (2) Are all RT values valid                   you‟ve made the necessary corrections – based on
                                                                        on a subsequent DSRED if the initial DSRED was an                      the error codes.
                                  General         AT&T                  AC status? For example can we get another DSRED                        (2) Yes - you may get any of the RT values (except
 95 Closed     FBDL               Order           Consumer      9/24/04 with an AC status?                                             10/1/04 RT=E) following an AC.

                                                                          Per Chapter 69 'Batch Hot Cut Status Update' we are
                                                                          to refer to
                                                                          http://www.qwest.com/wholesale/clecs/ordering.html
                                                                          for the business description. I do not find any                      The Business Description for this chapter is being
                                                                          information on this transaction at this url. Can we get              updated with the publication of Addendum #1 on
                                                                          a process description of this transaction and rules as               11/1/04. The correct URL for Batch Hot Cut Status
                                                                          to when, why and what to do for this transaction? We                 For BHC the description will be at
                                                                          have reviewed the fields provided in the disclosure                  <http://www.qwest.com/wholesale/clecs/batchhotc
                                  General                                 document spreadsheet but it doesn't tell us much.                    ut.html> however, it is a new pcat with this release
 96 Closed     BHC                Order           McLeod        9/27/04                                                                10/1/04 and has not yet published to the web.



Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 38 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                            Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                    Answered                   Resolution/Answer
                                                                        New Rule added for products 1, 4, 7, 9, 14, 25:Note:
                                                                        When multiple CSR exists for a TN, and ACT = W, V
                                                                        or Z, customer code should be included as part of the
                                                                        AN.
                                                                        Why is product 14 listed for this rule? Per the AN
                                                                        valid values 'AN must be 12 characters. Dashes are
                                                                        required in positions 4 & 8. The remaining positions             The business rule will be updated with the
                                                                        must be numeric.'...so we would never be able to                 publication of Addendum #1 to remove product 14
 97 Closed     App B: LSR         LSR: 7-AN       McLeod        9/27/04 pass the customer code.                                  10/1/04 (FBDL) from the product listing.


                                                                        According to the Change Summary (Pg 7) the AAR18
                                                                        field COMPTIME valid values were to be changed to
                                                                        'If TXTYP=D then ' CCYYMMDD, HHMM-HHMM'. If
                                                                        TXTYP=U then 'CCYYMMDD, HHMM'.
                                                                        However I do not see this changed reflected in the               The change summary was incorrect. The change
                                  AAR: 18-                              disclosure doc (Pg 18) as the valid values listed are            noted was only applicable to the ABTIME field, not
 98 Closed     App A: AAQ         COMPTIME McLeod               9/27/04 HHMM or Blank, Not Populated (EDI only) = space.         10/1/04 to the COMPTIME field.


                                                                        Appendix D - General - Post Order - BCH Status
                                                                        Responses - Can the BCH responses be opted into
                                                                        at any time after the 16.0 release for EDI users or              You can add (or remove) any of the subscriber
                                                                        can they only be opted into when the CLEC moves to               post-order responses to (from) Production at any
                                                                        their next EDI Release? Example: CLEC moves to                   time. If adding the response to Production, you will
                                                                        16.0 EDI but does not select to receive the BCH. 2               need to test that transaction with the Qwest IMA
                                                                        months later they decide they would like to receive              EDI team (following the new implementation
                                                                        these transactions can they do this at that time or do           process) before it can be added to Production. If
                                                                        they have to wait until they move to 17.0 or 18.0 to             you contact Qwest to activate a subscriber post-
                                                                        start the transactions? Also to receive the new                  order transaction before testing it with Qwest and
                                                                        transactions at a later time not associated with an              before the tested configuration is moved into the
                                                                        EDI version move is this considered a new                        Production environment, you will not receive those
                                                                        implementation like a new product?                               responses for EDI transactions because they will
                                                                        Appendix D - General - Post Order - BCH Status                   not be configured to be transmitted to you via EDI.
                                                                        Responses - Can a CLEC test the BCH responses in                 To remove the subscriber response from
                                                                        SATE without having the BCH amendment already in                 Production, you should coordinate that with your
                                                                        place with their ICA?                                            Qwest IMA EDI contact. You may test these
                                                                        Appendix D - General -Post Order - Status Update                 transactions in SATE without an ammendment.
                                                                        Reponses - Can a CLEC opt out of the receiving the               You would need to coordinate configuration of the
                                  General                               status updates via at any time or can this only be               SATE environment with your Qwest IMA EDI
 99 Closed     BHC                Order           Eschelon      9/27/04 done when a CLEC moves to their next EDI release?        10/1/04 contact.

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                             Page 39 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                           Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                    Answered                    Resolution/Answer
                                                                        General - Post Order - LR19 and LR40B - PIA - Is
                                                                        FTS capable of assigning PIA values 4, 16, & 17? Or             In general, if a PIA'able condition can be identified
                                                                        will these values be used in a manual fashion only?             during flowthrough, IMA could return a flowthrough
                                                                        If these values can be used via FTS will the remarks            FOC with PIA values. For these specific PIA
                                  LR: 19-PIA                            clearly define what the change is to the LSR or                 values of 4, 16 and 17 - they are all manually
100 Closed     App D: LR          and 40B-PIA Eschelon          9/28/04 Order?                                                  10/1/04 generated.

                                                                        According to Appendix J, under FBDL LACT = Z,
                                                                        "The DL form must indicate the ALI code (if not a
                                                                        main listing) and RTY for the listing to remain the
                                                                        same, along with the listing name and text
                                                                        information to ensure the correct listing is
                                                                        referenced." We currently don't have the capability
                                                                        to recap the Main Listing on every FBDL Order.
                                                                        Before we make any additional design changes we
                                                                        would like to confirm whether we are required to
                                                                        specify all details of the recapped LML (LACT=Z) on
                                                                        the FBDL order.       (a) Why do we need to recap the                (a) YES. This is an OSS requirement and all
                                                                        main listing on every DL order? What purpose does it                 attributes of a Main Listing are always required.
                                                                        serve?       (b) Are we required to specify all details of           (b) OSS Requirement, it ensures that we are
                                                                        the recapped LML (LACT=Z) or Is there a minimum                      processing the correct listing on the account.
                                                                        subset of fields required such as LACT, ALI (if an                   (c) Whatever is documented is required – whatever
                                  General         AT&T                  additional listing), RTY, LTY, STYC, TOA, DOI, LTN,                  the listing attributes were when the listing was
101 Closed     FBDL               Order           Consumer      9/28/04 LNLN and LNFN .                                              10/1/04 established are required.
                                                                        According to the DL form, the listed address field are
                                                                        only used when the address to be shown in the
                                                                        directory and directory assistance is different from the
                                                                        service address on the EU otherwise this field should
                                                                        be left blank.
                                                                        (a) If we choose to always populate the listed address               (a) Absolutely, we do not do any compares. What
                                                                        even when it's the same as the service address on                    is sent is what is processed.
                                                                        the EU order, will QWEST accept and process our                      (b) This is a business decision you have to make.
                                                                        FBDL order?                                                          Whatever you send as the Listed Address will
                                  General         AT&T                  (b) Are we required to compare the listing address to                appear in a printed directory and Directory
102 Closed     FBDL               Order           Consumer      9/28/04 the service address?                                         10/1/04 Assistance products.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 40 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                         Answered                   Resolution/Answer

                                                                        For FBDL orders, please confirm if no delivery
                                                                        address is sent on the FBDL Order then the delivery                  AHNs are assigned by Qwest when there isn‟t a
                                                                        address is defaulted to the service address. If the                  house number available and used sort of as a
                                                                        delivery address is defaulted to the service address                 pseudo service address for Qwest to be able to
                                                                        then please explain how the delivery address is                      service. Since we don‟t service FBDL, an AHN
                                  General         AT&T                  handled when AHN, ROUTE and BOX fields are not                       would never apply. In terms of the Route and Box,
103 Closed     FBDL               Order           Consumer      9/28/04 supported on the EU Form for FBDL orders.                    10/1/04 that information can be included in the SASN.

                                                                                                                                             In general, if you are doing a number change only
                                                                                                                                             you don't have to do the Out & In routine. If you are
                                                                                                                                             doing any other change you must do an Out & In
                                                                                                                                             change.
                                                                        For FBDL Change TN it states "On a Change TN, if                     In your example, if there is a change to the service
                                                                        there are no other changes for the listings, enter a DL              address, but no change to the listing address, a
                                                                        LACT of Z and enter the new telephone number in                      Move Order (ACT=T) has the same requirements
                                                                        the LTN. There is no need to take the listings Out                   as a change of telephone number (ACT=C or T). If,
                                                                        and In for this situation"   Is this also true for Move              however, the change to the Service Address
                                                                        Order? Can we make the following similar statement                   affects the Listing Address then Out/In is required.
                                                                        for Move Orders? - On a service address change, if                   This is true ONLY for a Service Address Change.
                                                                        there are no other changes for the listing enter a DL                This is because, like the Account Number – it is at
                                  General         AT&T                  LACT of Z with the old or new LTN. There is no need                  an account level and as long as all of the listings
104 Closed     FBDL               Order           Consumer      9/28/04 to take the listing Out and In for this situation            10/1/04 are recapped and not changing, this is possible.


                                                                        The CSR Date is a new field on the CSR Query
                                                                        which can be future dated. So for example, if I were
                                                                        to submit a CSR Query today (9/29/04) and I
                                                                        populate that field with a date of 10/18/04, does that
                                                                        mean that I would not get a CSR Response UNTIL
                                                                        10/18/04 from Qwest? Or does that mean that I                        You will get the CSR response immediately, with
                                                                        should get a CSR response on the same day                            pending order activity indicated (if any exists) that
                                                                        (9/29/04) that reflects what the customer account will               would affect the account as of 10/18/04.
                                  CSRQ: 7a-                             look like on 10/18/04? Also, the date populated in                   You do not have to future date the CSR. You could
105 Closed     App A: CSR         CSR DATE        Cbeyond       9/29/04 this field does not have to be a future date, does it?       10/1/04 use "today's" date.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 41 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                               Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                        Answered                  Resolution/Answer

                                                                        Follow-up to Q#89
                                                                        "In the future, for general FBDL capitalization and
                                                                        other usage information, please contact your LRS                    Please continue to submit your questions to
                                                                        Account Manager."         I'm a little confused by the              EDIQLOG@qwest.com. If anything needs to be
                                                                        response above. Should I submit my FBDL question                    referred to the LRS Account Manager, you will be
                                                                        to the LRS Account Manager instead of using the                     notified immediately via email response (same
                                                  AT&T                  IMA 16.0 Q&A process? Under what conditions                         process as for questions referred to your
106 Closed     Followup           Q # 89          Consumer      9/29/04 should I contact my LRS Account Manager?                    10/1/04 Wholesale Service Manager).

                                                                                                                                            10/1: Still Researching
                                                                                                                                            10/8/04:
                                                                                                                                            (a) LACT=Z is appropriate when listings on an
                                                                                                                                            account are not changing, only the Service
                                                                                                                                            Address.
                                                                                                                                            (b) When a new listing is being added at the same
                                                                                                                                            time as the T order (change of address) or when a
                                                                        (a) On a FBDL Order, when is it appropriate to use an               listing is being deleted at the same time as the T
                                                                        ACT=T with LACT=Z instead of LACT= I & O?                           order. LACT of O/I is a change to an existing
                                  General         AT&T                  (b) On a FBDL Order, when is it appropriate to use an               listing where LACT=N is establishing a NEW listing
107 Closed     FBDL               Order           Consumer      9/29/04 ACT=T with LACT= N & D instead of LACT= I & O?              10/8/04 and LACT=D is removing an existing listing.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 42 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                  Date
Q#   Status          Form             Name          Vendor     Opened                        Issue/Question                         Answered                   Resolution/Answer


                                                                        The EDI Disclosure documents states for Product 14
                                                                        (FBDL) LSR #16 DDD field "DDD mustequal current
                                                                        (today's) date".
                                                                        The Standard Interval Guide (SIG) shows a 24 hour
                                                                        turnaround and states at the bottom of page 65 " Non-
                                                                        complex listings submitted as Facility Based
                                                                        Directory Listings (FBDL) must be submitted by 3:00
                                                                        PM Mountain Time.The terms Stand Alone Listing
                                                                        (SAL) and FBDL are synonymous. FBDL represent
                                                                        Directory Listings for Facility Based CLECs not
                                                                        ordering and provisioning other services from Qwest
                                                                        and ordering Directory Listings exclusively."
                                                                        Please confirm the IMA EDI rule for the Desired Due
                                                                        Date (DDD) field on the FBDL order.
                                                                        (a) Can we set the Due Date on the FBDL Order to a
                                                                        future date or must it always be set to the current
                                                                        date?
                                                                        (b) If we send a FBDL order over the weekend,                          a) DDD on FBDL Orders must be set to the
                                                                        should the due date still be set to the current date?                  current date.
                                  General         AT&T                  (c) If we send a FBDL after 3pm Mountain Time, what                    B) Yes
108 Closed     FBDL               Order           Consumer      9/30/04 should the due date be set to?                                 10/1/04 c) The FBDL order should be the current date.




                                                                        RESALE form LNUM (9) Rule on LNUM states that
                                                                        LNUM = 0001 should be the primary ANI – should                         10/1: Still Researching
                                                                        this have additional clarification that this is only true              10/8/04: Qwest will determine whether this
                                                                        on an inward order where ACT = N, V, Z or T.                           information is correct and if so, will take your
                                                                        Maintenance orders which add a feature to a non-                       suggested clarification under advisement for a
109 Closed     App C: Resale      RS: 9-LNUM MCI                9/30/04 primary AN will not include this number.                       10/8/04 future release of the Disclosure Document.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                   Page 43 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                  Resolution/Answer

                                                                                                                                           10/1: Still Researching
                                                                                                                                           10/8/04: On a Listings Only order, your only
                                                                                                                                           ACTchoice is ACT=R and your only LNA choice is
                                                                                                                                           LNA=R. "R" means "Record" and is the only
                                                                                                                                           option available for Listings Only orders. For
                                                                                                                                           Listings Only, you need to supply the LSR, EU, RS
                                                                        RESALE form LNA (12) For Product #13 would you                     and DL forms - so you do need to supply an LNA.
                                                                        ever send a resale form with LNA = R? What reason                  Also, there is a business rule for LNA, Product 13:
110 Closed     App C: Resale      RE: 12-LNA      MCI           9/30/04 would be valid on a Listings Only Product                  10/8/04 If ACT=R, LNA=R




                                                                        RESALE form MEGACENTNM (26a) states required
                                                                        if adding DSL to an existing line (FA = N). This
                                                                        implies that new USOCs are added to a line which
                                                                        has DSL – Not clear if these features are added                    10/1: Still Researching
                                                                        based on the completion of the DLEC loop order                     10/8/04: MEGACENTNM needs to be populated on
                                  RS: 26a-                              which adds the DSL or on a later order issued by the               an order if a line doesn't already have DSL and the
                                  MEGACENT                              VLEC. Also not clear what would be populated in the                DLEC is adding it or if the line has DSL and the
111 Closed     App C: Resale      NM       MCI                  9/30/04 MEGACENTNM field.                                          10/8/04 ISP is changing.




                                                                        RESALE form PIC (28) rule states that if other
                                                                        activity on the number change order LNA = X then
                                                                        should change LNA = C (this is also stated on the                  10/1: Still Researching
                                                                        LNA (12) field. Question arises as also on the                     10/8/04: For LNA=X, the only thing you can change
                                                                        PIC/LPIC fields and wondered if just these two fields              is the TN. If other changes are desired along with
                                                                        along with BA and FA or if LSCP were populated then                the TN change, use LNA=C.
112 Closed     App C: Resale      RS: 28-PIC      MCI           9/30/04 the LNA = X or P should be converted to LNA = C            10/8/04 See also the responses to Q #5 and 60, above.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 44 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                               Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                        Answered                   Resolution/Answer




                                                                        RESALE form PULSE (50) in IMA14 field was
                                                                        required in ID-north and AZ and now in IMA 16
                                                                        PULSE is required in SD. Today we add a feature
                                                                        TTS for three NPA/NXX values in SD for touchtone.                   10/1: Still Researching
                                  RE: 50-                               Should we continue to do this in addition to                        10/8/04: Please see the answers to Q #48, 71 and
113 Closed     App C: Resale      PULSE           MCI           9/30/04 populating PULSE or only populate PULSE = DMTF              10/8/04 92, above.
                                                                                                                                            10/1: Still Researching
                                                                                                                                            10/8/04: You need to always provide FA=C & T in
                                                                        RESALE form FA (63) states when Line level USOC                     conjunction with one another (they are change
                                                                        is changing use FA values (C&T); when non-line level                from and change to). For Conversion orders
                                                                        features changes use FA = N&D and what I would                      (ACT=V & Z), if you want to provide an "END-
                                                                        like to confirm is that the FA= T alone is used                     STATE" view of the account post-conversion, you
                                                                        whenever a Feature detail (FID) associated to any                   need to use FA=N and provide everything you want
114 Closed     App C: Resale      RE: 63-FA       MCI           9/30/04 USOC whether line or non-Line level is changing             10/8/04 on the account post-conversion.




                                                                        HUNT GROUP form HID (10) states that when ACT =
                                                                        V or Z and HA = N the HID is optional – question is if
                                                                        populate the HID on the HUNT GROUP with the                         10/1: Still Researching
                                                                        value on the CSR as migrating HUNT GROUP as is                      10/8/04: Out to SME for response.
                                                                        will that HID value be retained or will it be replaced              10/15/04: In the example when ACT= V or Z, if the
                                                                        because the HA value is now N and not E. Question                   HID is provided from the CSR, then it is retained
               App C: Hunt Group                                        arise because of the fact that Qwest allows the value               on the request. If it is not provided, a new HID will
115 Closed     Info              HGI: 10-HID MCI                9/30/04 to be sent?                                                10/15/04 be assigned for the CLEC.
                                                                                                                                            10/1: Still Researching
                                                                                                                                            10/8/04: Couldn't find the original question. Q #6 in
                                                                                                                                            this log is not a preorder question. So, trying to
                                                                                                                                            answer based on the information in this specific
                                                                                                                                            question.
                                                                                                                                            If you send the AVQ with an unnumbered address
                                                                                                                                            as: @.Taylor then Qwest will return to you the
                                                                        Follow-up to PreOrder answer to Question #6 for                     same info "@.Taylor" in your AVR.
                                                                        Unnumbered Address the SASN field shows                             Your subsequent order should also contain that
                                                                        @,Taylor – is the comma a typo or is it returned in                 same information as it was returned to you on the
                                                                        PreOrder and should be dropped when send out the                    AVR: "@.Taylor"
116 Closed     Followup           Q # ??          MCI           9/30/04 Order service address                                       10/8/04

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 45 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                         Answered                   Resolution/Answer



                                                                                                                                             10/1: Still Researching
                                                                                                                                             10/8/04: Couldn't find the original question. Q #6 in
                                                                                                                                             this log is not a preorder question. So, trying to
                                                                                                                                             answer based on the info in this specific question.
                                                                        Another Follow-up to PreOrder Question #6 as it                      The code-converted values (the 32 and 13 that you
                                                                        applies to the Order response – Qwest business                       identified in your question, for example) within the
                                                                        rules and the example indicate that the sub-location                 NX2 segments differentiate what type of item is
                                                                        values are always in the order UNIT, APT etc, then                   being returned/sent. For EDI transactions you may
                                                                        FLR and finally BLDG, WING etc. LD1 has valid                        have those NX2 segments in any order (and they
                                                                        values of APT UNIT etc and LD2 had valid value =                     might be returned to you in any order). You need to
                                                                        FLR and LD3 has value values for structure BLDG                      be able to send and recognize the differentiating
                                                                        WING PIER. Does Qwest always send the PreOrder                       code-converted values (32 v. 13, etc.).
                                                                        in this order and expect this order or sequence of sub-              So, you might get either order:
                                                                        location values on the order. I ask as LD/LV values                  NX2*32*1
                                                                        are passed in the NX2 segments with no reference to                  NX2*13*123
                                                                        the LD1, LD2 or LD3. Could the CLEC send                             or
                                                                        NX2*32*1 followed by NX2*13*123 or would it always                   NX2*13*123
117 Closed     Followup           Q # ??          MCI           9/30/04 be NX2*13*123 followed by NX2*32*1.                          10/8/04 NX2*32*1




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 46 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                       Answered                   Resolution/Answer

                                                                                                                                           10/1: Still Researching
                                                                                                                                           10/8/04: FBDL never uses the Service Address for
                                                                                                                                           Listed Address. If the Listed Address is the same
                                                                                                                                           as the Service Address and the end user wants it
                                                                                                                                           to appear in Directory Assistance and/or a
                                                                                                                                           Directory, the List Address fields must be
                                                                                                                                           completed. If the end user does not want their
                                                                                                                                           address printed, they must enter ADI=O to omit it.
                                                                                                                                           FBDL requires either ADI=O or at a minimum the
                                                                                                                                           LALOC.
                                                                                                                                           The DL form will be updated, with 160 Addendum
                                                                                                                                           #1 on 11/1/04, to remove Product 14 from the
                                                                                                                                           following business rule – for LANO.
                                                                                                                                           Products 1, 3, 4, 7, 8, 9, 9a, 10, 11, 12, 13, 14, 16,
                                                                                                                                           17, 18, 20, 21, 25, 28, 29, 30, 31, 33, 34, 35, 37,
                                                                                                                                           38, 39, 40, 41: This field is only used when the
                                                                         DL form LANO (62) & LASN (65) state that the                      address to be shown in the directory and directory
                                                                        Listed address fields should only be populated when                assistance is different from the service address on
                                                                        not the same as the service address fields. Question               the EU and there is a street number, otherwise this
                                  DL: 62-                               is – if the Address fields are sent and are the same               field should be left blank. If this field is present,
                                  LANO & 65-                            does Qwest reject the order or just ignore the fields              LASN must also be present. This field is required
118 Closed     App C: DL          LASN       MCI                9/30/04 sent.                                                      10/8/04 when LAPR or LASF are populated.

                                                                                                                                           10/1: Still Researching
                                                                                                                                           10/8/04: Out to SME to determine whether the
                                                                        DL form DDASN (87) In IMA14 had DDASN                              current rule is correct or whether correction is
                                                                        required when DDQTY = 1 or 2 and a note to                         required.
                                                                        populate the DDA fields when they are not the same                 10/15/04: The current business rules are correct as
                                                                        as the service address fields – In IMA 16 states only              is. This rule accommodates a DDQTY=1 without a
                                  DL: 87-                               required if DDQTY = 2? Would seem that some                        Delivery Address but with a DIRQTYNC and
119 Closed     App C: DL          DDASN           MCI           9/30/04 information might have been lost.                         10/15/04 DIRQTYA.
                                                                        What is the capitalization rule for the NICKNAME
                                  DL: 53-         AT&T                  field on the DL form (DL #53)? Is it the same as                   Yes, there are no special stylization rules. The first
120 Closed     App C: DL          NICKNAME        Consumer      9/30/04 TITLE1 & TL fields?                                        10/8/04 character is upper case and the rest lower case.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 47 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                Product or DWS      Field # or    Software     Date                                                              Date
Q#   Status          Form             Name         Vendor                                 Issue/Question
                                                              Opened In IMA 14 the Appendix D –Developer Worksheets –          Answered                   Resolution/Answer
                                                                     Post Order on page 17 for the LR19 PIA field lists the
                                                                     following values and their reason details:
                                                                     Blank, Not Populated (EDI only)=Space
                                                                     1 = ECCKT(s) change
                                                                     2 = Due date change
                                                                     3 = ECCKT and due date change
                                                                     4 = Other (clarify in remarks)                                       Qwest started returning multiple PIA values in
                                                                     5 = Service order number change                                      15.0. This change to PIA values came into play at
                                                                     6 = Route Index (RTI) change                                         that time. There are now two PIA values.
                                                                     7 = Change to TERS/HID                                               LR 19: PIA (for PIA info at LSR level) and the valid
                                                                     8 = Invalid PON characters                                           values are:
                                                                     9 = Telephone (SBN/BTN/MAN) number change                            4 = Other (clarify in LSR Level PIA remarks)
                                                                     10 = Verbal CFA/Slot change accepted                                 13 = BAN Change
                                                                     11 = Dispatch entry not valid                                        16 = Other 2 (clarify in LSR Level PIA remarks)
                                                                     12 = AN Change                                                       17 = Other 3 (clarify in LSR Level PIA remarks)
                                                                     13 = BAN Change                                                      4, 16, 17 are manual generated and only 13 is auto
                                                                     14 = Data portion not provisioned                                    generated.
                                                                     15 = Required USOC not provided on request but                       LR 40b: PIA (for PIA info at Order level) and the
                                                                     was added to Qwest service order                                     valid values here are:
                                                                                                                                          1 = ECCKT(s) change
                                                                       In the IMA 16 release, the Appendix D –Developer                   2 = Due date change by Qwest
                                                                       Worksheets – Post Order on page 22 gives this                      4 = Other 1 (clarify in remarks)
                                                                       abbreviated list:                                                  5 = Service order number change
                                                                       Blank, Not Populated (EDI only)=Space                              6 = Route Index (RTI) change
                                                                       4 = Other (clarify in LSR Level PIA remarks)                       7 = Change to TERS/HID
                                                                       13 = BAN Change                                                    9 = Telephone (SBN/BTN/MAN) number change
                                                                       16 = Other 2 (clarify in LSR Level PIA remarks)                    10 = Verbal CFA/Slot change accepted
                                                                       17 = Other 3 (clarify in LSR Level PIA remarks)                    11 = Dispatch entry not valid
                                                                                                                                          12 = AN Change
                                                                       Are the previous values no longer valid and Qwest                  16 = Other 2 (clarify in remarks)
                                  LR: 19-PIA                           will only be using 4, 13, 16, and 17? Can you give us              17 = Other 3 (clarify in remarks)
121 Closed     App D: LR          and 40B-PIA MCI              10/1/04 an actual example with a populated LSR Level PIA           10/8/04 18 = Verbal Due Date Change by CLEC




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                             Page 48 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                               Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                        Answered                    Resolution/Answer

                                                                                                                                            Both Reject (BPL Fatal and ISC Reject) Local
                                                                                                                                            Responses have the RT value = Z. However, you
                                                                                                                                            will receive different information in the LR 21 field,
                                                                                                                                            as outlined in the Developer Worksheet valid
                                                                                                                                            values section. The BPL Fatal - meaning the order
                                                                                                                                            did not make it into Qwest's processing systems -
                                                                                                                                            is a 14 character a/n response in that field. The
                                                                        How does can one differentiate between a Soft                       ISC Reject -meaning the order made it into
                                                                        Reject and a Fatal Reject. In the IMA 16 release, the               Qwest's processing systems, but was
                                                                        Appendix D –Developer Worksheets – Post Order on                    subsequently rejected - is a 3 character numeric
                                                                        page 22 gives the following in the Valid Values                     response in that field. They are both REJECTS.
                                                                        section:                                                            For the BPL Fatal - you may resubmit the LSR with
                                                                        3 character for rejects/error (post order).                         the same order type (850 or 860) and PON/VER.
                                                                        14 character code for fatal errors (integrity edits).               For the ISC Reject - you should resubmit as a
                                                                        The 14 char code is a fatal error code, while the 3                 supplemental order (860) using the Same PON
                                                                        char error code is used for post-submission rejects                 and Increment the VER.
                                                                        and errors.                                                         If you are considering something else a "soft"
                                                                        Does this mean that all Soft Rejects will have 3                    reject, please provide further clarification.
                                  LR: 21-                               character codes and all Fatal Rejects will have 14                  Other types of LR Responses are differentiated by
                                  ERROR/REJ                             character codes? If not, please tell us how to                      the RT value. These are: Non-Fatal, Jeopardy,
122 Closed     App D: LR          ECT CODE MCI                  10/1/04 differentiate between the two?                              10/8/04 FOC, etc.
                                                                                                                                            It is your responsibility to validate that the new
                                                                        What action (if any) is required for our FBDL Listings              Provider has migrated those listings over. If you
                                                                        when the TN associated with the listings has been                   don‟t, it is possible that you will continue to receive
                                                                        taken over by another provider? Are we required to                  charges for those listings. If the new Provider
                                  General         AT&T                  delete all listings when we lose the line to another                does not migrate the listing(s) – you should issue a
123 Closed     FBDL               Order           Consumer      10/1/04 provider (REQTYP=JB/ACT=D/LACT=D)?                          10/8/04 Disconnect (ACT=D).
                                                                                                                                            10/8/04: For IMA GUI, the DSRED is auto emailed
                                                                                                                                            to the FBDL order initiator, therefore, it is
                                                                                                                                            imperative that we have a correct email address to
                                                                                                                                            ensure the DSREDs are being sent to the right
                                                                        Please explain why the Initiator Email Address (LSR                 place/person. DSRED responses for EDI orders
                                                                        # 91 EMAIL) field is required on the IMA EDI FBDL                   are returned via EDI, not via email normally.
                                                                        Order.                                                              However, if Qwest ever needed to send a DSRED
                                                                        We need to understand QWEST's intent so we can                      manually for an EDI order, the Email address
                                  LSR: 91-        AT&T                  ensure that the email address of the appropriate                    would be necessary. So, it is required across the
124 Closed     App B: LSR         EMAIL           Consumer      10/1/04 team is provided.                                           10/8/04 board.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 49 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                         Answered                    Resolution/Answer
                                                                                                                                              There is a "Blank" response that is valid for both
                                                                                                                                              GUI or EDI. However, they manifest differently in
                                                                                                                                              the two interfaces, which results in the "Not
                                                                                                                                              Populated-EDI Only" statement to which you are
                                                                                                                                              referring.
                                                                                                                                              In the GUI interface, when the response is "Blank"
                                                                                                                                              you actually see a field that is "Blank".
                                                                                                                                              In the EDI interface, EDI does not return a
                                                                                                                                              segment with no value associated with it. So,
                                                                        Follow up Question - PSON                                             what actually happens when the respone from the
                                                                        In reference to question number 88. Per the LSOG                      back end is "Blank" is that the segment is not
                                                                        comments the value of Blank for recap on the PSON                     returned - resulting in the "Not Populated"
                                                                        is not solely limited to EDI. With the Addendum 1 will                response that is valid for EDI Only.
                                                                        the comment Not populated EDI ONLY be removed                         This is an accurate statement given how EDI
125 Closed     Followup           Q # 88          Eschelon      10/4/04 as this is not an accurate statement?                         10/8/04 works.


                                                                                                                                              This sounds like a VoIP issue. AT&T needs to
                                                                        QWEST FBDL Order question                                             negotiate a separate agreement for VoIP.
                                                                        If a end user moves from New York City to Denver
                                                                        and wants to keep their existing TN.                                  FBDL supports Qwest Territory. If an end user
                                                                        (a) Will we have any problems/issue establishing a                    wants to keep their existing NY TN, this could not
                                                                        directory listing in the local Denver directory via FBDL              be done in IMA. This request would need to go to
                                                                        order for this Verizon TN?                                            the Qwest Business Office and they will establish
                                                                        (b) What are the additional requirements (if any)                     an IFWPL (Independent Foreign White Page
                                                                        when sending an FBDL order for a TN with an                           Listing).
                                                                        NPA/NXX outside of the QWEST territory?                               (a) Again, we serve Qwest territory. A Verizon TN
                                                                        (c) What are the additional requirements (if any)                     needs to come in from Verizon, not FBDL.
                                  General         AT&T                  when sending an FBDL order with an AT&T TN (non-                      (b) IFWPL.
126 Closed     FBDL               Order           Consumer      10/5/04 ported TN) within the QWEST territory?                        10/8/04 (c) Not a problem.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 50 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                  Resolution/Answer
                                                                                                                                           This would error out if:
                                                                                                                                           First Order/Account
                                                                                                                                           ACT=N
                                                                                                                                           AN=3035551111
                                                                                                                                           LACT=N LTN=3035551111
                                                                                                                                           RTY=LML
                                                                                                                                           Second Order/Account
                                                                                                                                           ACT=N
                                                                                                                                           AN=3035551111
                                                                                                                                           LACT=N
                                                                                                                                           LTN=3035552222
                                                                                                                                           RTY=LML
                                                                        Follow-up to Question # 94 "There can only be one
                                                                        main listing (LML) for an account number. Qwest                    This would not error out if:
                                                                        knows that there are multiple TNs for a given                      First Order/Account
                                                                        account. So, if you had an account with two TNs and                ACT=N
                                                                        you attempted to submit an FBDL order for each TN                  AN=3035551111
                                                                        as a LML, that would error out. You need to submit                 LACT=N
                                                                        the second TN as an additional listing as outlined in              LTN=3035551111
                                                                        the original response to #90."        Just want to                 RTY=LML
                                                                        confirm our understanding, based on the answer                     Second Order/Account
                                                                        above. If we had an account with two TNs, is QWEST                 ACT=N
                                                                        stating that we can't send two new FBDL orders to                  AN=3035552222
                                                                        setup two separate FBDL account, one for each TN                   LACT=N
                                                  AT&T                  as an LML (ACT=N, LACT=N, AN = TN)? Would this                     LTN=3035552222
127 Closed     Followup           Q # 94          Consumer      10/5/04 actually error out?                                        10/8/04 RTY=LML




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                           Page 51 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                               Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                        Answered                  Resolution/Answer

                                                                                                                                            LACT=Z indicates there is no change to the
                                                                                                                                            listing. It is feasible to have LSR.ACT=C or T to
                                                                                                                                            change the Service Address for the Account and
                                                                                                                                            have no changes to the listings. If however, the
                                                                                                                                            Service Address was used in the Listed Address of
                                                                                                                                            a listing(s) and it has a direct impact on the
                                                                                                                                            Listing(s) Listed Address, then the Listing should
                                                                                                                                            be changed to update the Address.
                                                                        Follow-up to Question #102         "This is a business              For example:
                                                                        decision you have to make. Whatever you send as                     Existing SA = 123 Main Denver
                                                                        the Listed Address will appear in a printed directory               Existing LA = Denver
                                                                        and Directory Assistance products."             Just                New SA = 789 Sheridan Lakewood
                                                                        taking this a step further to understand the possible               New LA = Lakewood
                                                                        impacts of this business decision. Can we still                      In this case, the user would need to issue a DL
                                                                        execute an LACT=Z on Move and Change TN (see                        form with LACT=O to remove the LA of Denver
                                                                        answer to question # 104) if we make the business                   and a DL Form with LACT=I with the new Listed
                                                                        decision to always specify the listed address OR will               Address (City) of Lakewood. If LACT=Z was used,
                                                  AT&T                  we be required to always use LACT I & O because                     the Service Address would be changed, but the
128 Closed     Followup           Q # 102         Consumer      10/5/04 we are specifying the listed address?                       10/8/04 listed address would still „print‟ as Denver.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 52 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                        Answered                     Resolution/Answer
                                                                                                                                           (a) Qwest does not publish or deliver directories.
                                                                                                                                           We offer a product for Delivery List information to
                                                                        Follow-up to Question #103          "AHNs are                      our official publisher and to other publishers. This
                                                                        assigned by Qwest when there isn't a house number                  product actually has address information. Based
                                                                        available and used sort of as a pseudo service                     on what is on the Main Listing, is what we provide
                                                                        address for Qwest to be able to service. Since we                  on this product. If there is a Delivery Address, that
                                                                        don't service FBDL, an AHN would never apply. In                   is provided – if no Delivery Address, we provide the
                                                                        terms of the Route and Box, that information can be                Service Address.
                                                                        included in the SASN." (a) Does QWEST provide                      (b) Whatever the Provider enters in either the
                                                                        directory delivery to unnumbered addresses?                        Service Address or Delivery Address is used for
                                                                        (b) In question #103, we were trying to understand                 Directory Delivery products. The Service Address
                                                                        how the delivery address is determined for                         should not be used as the default Delivery Address
                                                                        unnumbered address since AHN, ROUTE & BOX are                      if it is in any way different – or the end user may
                                                                        not supported. Is QWEST stating that in order for the              not receive a Directory. End users and/or
                                                                        directory to be delivered for an unnumbered address,               Providers can always contact Dex Media to
                                                                        we need to supply the ROUTE and BOX in the SASN                    discuss this process.
                                                                        field in the Service Address when we want to use the               Dex Media Contacts
                                                                        service address as the default delivery address?                   Chris Peterson Voice: 402-384-3633 Fax: 402-
                                                                        (c) We normally use the validated address returned                 384-3651
                                                                        from PreOrder AVQ/AVR. Will QWEST have a                           The Directory Source 1-800-422-8793
                                                                        problem validating our service address if we replace               Customer Service 1-800-422-1234
                                                                        the SASN field value with ROUTE & BOX                              (c) Address Validation is NOT used for FBDL,
                                                                        information?                                                       since Qwest is not provisioning the service.
                                                  AT&T                  (d) Can we provide the ROUTE & BOX information in                  PreOrder AVQ/AVR is not used.
129 Closed     Followup           Q # 103         Consumer      10/5/04 the DDASN field ?                                          10/8/04 (d) Absolutely.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 53 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                         Answered The field lengthResolution/Answerlimited with the
                                                                                                                                                                 is 1000, but we are
                                                                                                                                              OSS and will send a maximum 60 characters in
                                                                                                                                              this field.
                                                                                                                                              (a) FBDL uses this field to provide PON level
                                                                                                                                              Confirmation or Error Code. The verbiage is
                                                                                                                                              consistent for each status. The following
                                                                                                                                              information can be found in the IMA Facility Based
                                                                                                                                              Directory Listings Corrective Procedures and
                                                                                                                                              Confirmation/Error Codes Document
                                                                                                                                              (http://www.qwest.com/wholesale/ima/edi/documen
                                                                                                                                              t.html)
                                                                                                                                              PON Level Confirmation/Errors
                                                                                                                                              The PON status will be identified on the DSRED
                                                                                                                                              with the following Confirmation/Error Codes:
                                                                                                                                              • ULAT0C – Confirmed Update on PON. The
                                                                                                                                              Listing Database was updated for all listings. No
                                                                                                                                              follow up is required by Qwest or the Provider.
                                                                                                                                              • ULAC0C –Processed With Changes/Errors –
                                                                                                                                              Qwest Follow Up. This is a partial update. The
                                                                                                                                              Listing Database was updated however, some or
                                                                                                                                              all of the listings may have an error condition.
                                                                                                                                              Qwest follow up is required.
                                                                                                                                              • ULADOC – Processed with Changes/Errors –
                                                                        Noticed that the LSR REMARKS field (DSRED #9c )                       Provider Follow Up. This is a partial update. The
                                                                        is 1000 characters long. We're trying to determine                    Listing Database was updated, however some or
                                                                        what to expect in this field and who needs to see this                all of the listings may have an error condition.
                                                                        data. (a) What has QWEST used this field in the past                  Provider follow up is required.
                                                                        to clarify? (b) Should we always expect this field to                 • ULRF0F – Fatal Update on PON. This entire
                                                                        be populated on particular scenarios/situations? If so,               PON is in error and no updates were processed to
                                                                        which scenarios/situations? (c) Are canned                            the Listing Database. Provider follow up is
                                  DSRD: 9-                              responses placed in this field based on Response                      required.
                                  LSR             AT&T                  Type (RT) or is each LSR Remark field unique to the                   Note: FBDL orders that receive an RF PON status
130 Closed     App D: DSRED       REMARKS         Consumer      10/6/04 particular FBDL order?                                        10/8/04 will remain in a rejected status for 10 calendar
                                                                        The EDI Disclosure Document shows fields DL #49a
                                                                        DESD, DL #50 TLD & DL #51 TITLE1D with a usage
                                                                        rule of "N" (Not Required) for FBDL (Product #14)
                                                                        however for all other products these fields are
                                  DL: 49-                               "O"(Optional).
                                  DESD, 50-                             I'm assuming that this is in error and that these fields
                                  TLD & 51-       AT&T                  should have a usage rule of optional for FBDL
131 Closed     App C: DL          TITLE1D         Consumer      10/7/04 (Product #14). Please confirm.                               10/15/04 No error, these fields are not supported by FBDL.


Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 54 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                  Reporting
                                                   CLEC,
                                                   Service
                                                  Bureau or
                Product or DWS      Field # or    Software     Date                                                              Date
Q#   Status          Form             Name         Vendor     Opened                         Issue/Question                    Answered                    Resolution/Answer
                                                                       How do we communicate Yellow Page Heading                          Qwest does not provide Yellow Page Heading
                                                                       information for a business listing on an FBDL Order                information, this is a Publisher function. Our
                                  DL: 110-YPH AT&T                     when DL#110 YPH and DL#111 YPHV are not                            official publisher, Dex Media determines the
132 Closed     App C: DL          & 111-YPHV Consumer          10/7/04 supported?
                                                                       The latest answer above conflicts with the EDI            10/15/04 appropriate YP Heading.
                                                                       Disclosure Document which states that we must use
                                                                       the address returned on AVR for our FBDL orders.
                                                                       The following statement is made for each of the
                                                                       service address fields in the EDI Disclosure
                                                                       Document for Product #14: "This field is part of the
                                                                       overall End User Address. This address information
                                                                       is validated for all orders against data in the Qwest
                                                                       Legacy systems. If data exists for this field in the
                                                                       Legacy system for the End User address, the field
                                                                       must be populated and must exactly match the data
                                                                       from the Qwest Legacy system as returned on an
                                                                       Address Validation Response."
                                                                       So going back to my original question on 9/28, how
                                                                       are unnumbered service addresses handled for
                                                                       directory delivery. Since the EDI Disclosure
                                                                       document states that the service address must
                                                                       match the address returned on AVR, it seems that
                                                                       the directory delivery address would always be
                                                                       required for unnumbered addresses since Route and                  Address Validation is not currently performed for
                                                                       Box are not supported in the Service address fields                FBDL orders. Qwest will review these statements
                                                                       on the FBDL Order however I can't seem to find any                 to determine whether to remove product 14 from
                                                                       documentation stating this requirement unless                      those business rules in a future release of the 16.0
                                                                       perhaps the publishers don't support unnumbered                    Disclosure Document.
                                               AT&T                    addresses on their Delivery List.                                  Route and Box information can be included in the
133 Closed     Followup           Q # 103, 129 Consumer        10/8/04 AT&T doesn't want to develop FBDL code to always          10/15/04 SASN, as you state in your question.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 55 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                                                    Resolution/Answer
                                                                                                                                  Answered You cannot do what you are asking to do.
                                                                                                                                             In your example, you have a multi-line account at
                                                                                                                                             LocationA. The AN is 303-555-1111 and the two
                                                                                                                                             TNs are 303-555-1111 and 303-555-2222, this
                                                                                                                                             would have to be submitted as a LML for 303-555-
                                                                                                                                             1111 and a LAL for 303-555-2222. You can not
                                                                                                                                             submit the listing for 303-555-2222 as a second
                                                                                                                                             LML with an AN of 303-555-1111 and a TN of 303-
                                                                                                                                             555-2222. This will error out as illustrated in the
                                                                                                                                             response to 127 (gave you example of what would
                                                                        I've tried asking this several different ways. The last              error and what would not). If you had two separate
                                                                        response only answered 1 of the 2 questions. The                     accounts at Location A, you would be allowed one
                                                                        question still remains "Is QWEST stating that we                     LML for each account. This means that if you had
                                                                        can't send two new FBDL orders to setup two                          AN=303-555-1111 with TN 303-555-1111 and a
                                                                        separate FBDL account, one for each TN as an LML                     second AN=303-555-2222 with TN 303-555-2222,
                                                                        (ACT=N, LACT=N, AN = TN)?" AT&T Consumer                             you would be allowed two main listings - one for
                                                                        wants to setup a separate account for each TN. It                    each Account.
                                                                        seems QWEST's preference is one account for each                     However, whether it will currently work and/or will
                                                                        service address which may have one or more TNs                       error out is somewhat irrelevant. In this case
                                                                        however I can't seem to confirm whether QWEST                        Qwest has stated this is something you should not
                                                                        has any rules preventing us from creating &                          be doing. Qwest doesn't currently have hard edits
                                                                        maintaining separate accounts for each TN. If there                  for everything that CLECs are told not to do. But,
                                                                        isn't such a rule then AT&T Consumer will go ahead                   Qwest could choose to enforce a given rule at a
                                                                        and build software to support the creation of separate               point in the future - which would then be
                                  Q # 90, 94,     AT&T                  FBDL accounts for each TN regardless of service                      problematic for you. So, we do not recommend
134 Closed     Followup           127             Consumer      10/8/04 address.                                                    10/15/04 that you code your systems based on the presence
                                                                        ON the DL form for the LASN field you find a condition
                                                                        for Product 14 that states “the field is Required when
                                                                        LANO is populated, otherwise not required”. How
                                                                        should this rule be interpreted? Is it the same as
                                                                        saying "otherwise prohited/not applicable" or should it              It should be treated as "otherwise optional" not as
135 Closed     App C: DL          DL: 65-LASN Accenture        10/19/04 be treated as "otherwise optional"?                         10/22/04 "otherwise prohibited/not applicable".




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 56 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                         Answered                   Resolution/Answer

                                                                        The rules for APPTIME seem to contradict each
                                                                        other. One rules states that with Product 4 the
                                                                        format must contain a single time and several others
                                                                        seem to imply that a range is ok: negotiated
                                                                        business rule - "Products 4, 7, 11, 12, 41, 42: Range
                                                                        not allowed." contradicts the valid value rule
                                                                        "Products 4, 7, 41, 42: The format is HHMM
                                                                        representing start time, or a range HHMM-HHMM
                                                                        representing after and before time" as well as another
                                                                        negotiated business rule that states "Product 4, 41:
                                                                        For ACT=V, if CHC=B, APPTIME must be HHMM-
                                                                        HHMM. For Information Only - When CHC=B                               As answered in Q# 37, Product 4, 7, 41, and 42
                                                                        APPTIME range is 0300-1100.".                                         will be removed from the rule "Range not allowed".
                                  LSR: 17-                              Please clarify when a range is allowed. I apologize if                This change will go into Addendum #1, which will
136 Closed     App B: LSR         APPTIME         Neustar      10/19/04 I have missed a notification that clarifies this.            10/22/04 publish on 11/1/04.
                                                                                                                                              No, this does not cause problems at Qwest.
                                                                        The TXTYP for an Appointment Reservation for                          Qwest's IMA EDI interface uses individual maps
                                                                        Batch Hot Cut is TXTYP = C.                                           (as dislosed in the individual product chapters) per
                                                                        I also noticed that the TXTYP for a CFA validation is                 product based on the GS value and type of
                                                                        TXTYP = C. This is causing us some problems. Is                       transaction (850 v 860). So, it is possible for Qwest
                                  Appt: many                            this correct? Is this not causing any problems at                     to use the same value for TXTYP for two different
137 Closed     App A: Appt        fields          Neustar      10/19/04 Qwest?                                                       10/22/04 products without any problems.
                                                                        Jane just wants to verify that we still need to continue
                                                                        to add the feature TTS for the three NPA/NXX values
                                                                        in SD for touchtone in addition to populating the
                                                                        PULSE field? Or do we only populate PULSE =
                                                                        DMTF?
                                                                        My take from the Touch Tone PCAT is that we still
                                                                        need to add TTS feature in SD for McIntosh,
                                                                        Morristown, and Timber Lake in addition to populating
                                                                        DMTF in PULSE field on Resale form.
                                                                        Jane just wants to verify because it seems duplicative
                                                                        to do both.
                                                                        However, the responses they are providing do not                      You are correct in that the TTS feature is still
                                                                        appear to specifically answer that question if we still               needed in the 3 exchanges in SD. The CLEC
                                                                        need to add TTS for 3 areas in SD in addition to                      should also be filling in the DTMF in the Pulse
138 Closed     Followup           Q # 113         MCI          10/22/04 populating the PULSE field.                                  10/29/04 field.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 57 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor     Opened                         Issue/Question                       Answered                   Resolution/Answer
                                                                        Have reviewed the 16.0 Disclosure Documentation
                                                                        and the questions #11 and 17 thru 30 on populating
                                                                        the EU Service address fields #9-28a. References
                                                                        are made to the TN/SANO rule and was wondering if
                                                                        there is separate documentation summarizing the                       This answer is for the UNE-P POTS product:
                                                                        rule or in lieu of that can we get confirmation of the                1. Correct (for the scenarios you mention as well
                                                                        following:                                                            as for ACT=V, EUMI=Y for Location1)- based on
                                                                        1.     If ACT = N or ACT = T and LOCNUM = 2 then                      their business rules (ie: SANO and ROUTE cannot
                                                                        address fields on customer CSR are required                           both be populated for a single location on an order)
                                                                        2.     For all other ACTs if Custcode is provided as                  2. Correct
                                                                        part of the AN field then the only EU_LOC field                       3. Correct
                                                                        required is STATE                                                     4. Correct based on the business rules for
                                                                        3.     For all other ACTs if no Custcode then if TN                   unnumbered addresses (ie: ROUTE and SANO
                                                                        field is part of the AN field and the Service address is              cannot both be populated for a single location on
                                                                        a numbered address then only SANO, STATE & ZIP                        an order).
                                                                        or CALA is required                                                   Additional information is in the CSR Matches by
                                                                        4.     For all other ACTs if no Custcode then if TN                   TN and SANO section of the Ordering Overview
                                  Full AN vs.                           field is part of the AN field and the Service address is              PCAT at:
                                  TN/SANO                               a non-numbered address (AHN, ROUTE or BOX                             http://www.qwest.com/wholesale/clecs/ordering.ht
139 Closed     General            rules           MCI          10/27/04 format) then all address fields required                     10/29/04 ml

                                                                                                                                              NIDO was originally published in Disclosure,
                                                                                                                                              however that value changed. This was notified in
                                                                                                                                              Event Notification #1287251 IMA EDI-GUI 101804
                                                                                                                                              Initial-Patch Pending 110104. The notification
                                                                        What is the Northern Idaho CALA? Per IMA 16.0                         was for the update to the Disclosure Document for
                                  EU: 28a-                              Idaho's CALAs are ID and IDO, but per EDI 16.0                        this value in Addendum #1. The corrected CALA
140 Closed     App B: EU          CALA            McLeod       10/28/04 disclosure the CALA shows as NIDO.                           10/29/04 information is contained in the notification.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 58 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                            Date
Q#   Status          Form             Name          Vendor     Opened                     Issue/Question                      Answered                    Resolution/Answer
                                                                                                                                         Please refer to the pre-order PCAT for more
                                                                                                                                         information on bordertowns.
                                                                                                                                         http://www.qwest.com/wholesale/clecs/preordering.
                                                                                                                                         html
                                                                                                                                         Release 16.0 allows LNP and LSNP bordertowns
                                                                                                                                         to be input into IMA.
                                                                                                                                         The TN that needs to be submitted is the CSR AN
                                                                                                                                         TN. This can either be the dialable number
                                                                                                                                         provided by the end user or billing number (csr an)
                                                                                                                                         Qwest has.
                                                                        Do we have to use the wire center TN when                        If the CLEC uses the pre-order CSR functionality to
                                                                        submitting an LS or LSNP order in a Bordertown                   pull the dialable number - and a response is
                                                                        area? In IMA 16.0 training documentation it says                 returned. That would be the TN to use. If the
                                                                        that the CLEC is able to submit the working TN. But              CLEC doesn't pull a match from the dailable
                                                                        we are receiving system errors when we attempt to                number they can find the corresponding NPA-NXX
141 Closed     General            Bordertown      McLeod       10/28/04 do that in IMA.                                         10/29/04 from the pcat to use to pull the CSR.
                                                                                                                                         Your CSR date does not have to "match" the LSR
                                                                                                                                         date for any validation purposes. You should,
                                                                                                                                         however, select a CSR date that works with the
                                                                                                                                         date of your LSR. For example, if you want your
                                                                                                                                         requested work to complete in 14 days, it would
                                                                                                                                         make sense to pull a CSR dated for that date, or
                                  CSRQ: 7a-                             Does the CSR date have to match the requested due                close to that date to be able to see pending activity
142 Closed     App A: CSR         CSR DATE        McLeod       10/29/04 date on our LSR, for EDI and/or IMA orders?              11/5/04 on the account.
                                                                                                                                         The descriptions for new CALAs and other
                                                                                                                                         information will be distributed with specific
                                                                                                                                         notifications when the affected LFACs AN
                                                                                                                                         Region/Wire Centers are rolled out. There is also a
                                                                        Can you send me the descriptions for the new CALAs               call scheduled for Tuesday, November 9 to review
                                  EU: 28a-                              that were disclosed on event notification 1287251.               the changed items in Addendum #1 - including the
143 Closed     App B: EU          CALA            McLeod        11/1/04 The Disclosure does not give a description.              11/5/04 updated CALA values.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                             Page 59 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                          Date
Q#   Status          Form             Name          Vendor     Opened                        Issue/Question                 Answered                    Resolution/Answer
                                                                        1. Please confirm when DACT is required – if it is
                                                                        only required when populate the DDA address fields
                                                                        are populated (DDASN is the key address field then
                                                                        DACT & DELNUM are populated)                                   1. Correct. DACT is only required when the user
                                                                        2. Please confirm when CLEC should send DDA                    is establishing, changing or removing the Delivery
                                                                        field – only when not the same as service address              address.
                                                                        3. Is it possible to have DACT = Z and have the DDA            2. Correct. Only when the end user has
                                                                        address fields null                                            requested that their phone book be delivered to an
                                                                        4. The response to question on DDQTY is answered               address different from their Service Address.
                                                                        in Question #119 - DDQTY can be populated with                 Otherwise, the DA fields should be left blank.
                                  DL: 80-                               DACT = null (I e DACT related to the DDA fields and            3. NO
144 Closed     App C: DL          DACT            MCI           11/3/04 DELNUM)                                                11/5/04 4. Correct.

                                                                        Question 118 on the log asked for DL 62-LANO and
                                                                        65 LASN . What is the Qwest process when Listed
                                                                        address fields are included on the LSR - the wording
                                                                        has not changed since IMA 14 and today we do not
                                                                        receive errors Both IMA 14 and IMA 16 have the
                                                                        following for LANO and similar wording for LASN
                                                                         “This field is only used when the address to be
                                                                        shown in the directory and directory assistance is
                                                                        different from the service address on the EU and                   There have been no changes between 14.0 and
                                                                        there is a street number, otherwise this field should              16.0 for these fields.
                                                                        be left blank. If this field is present, LASN must also            As stated in the previous answers to Q 118 and
                                                                        be present. This field is required when LAPR or LASF               102, if the listed address is the same as the
                                                                        are populated. The answer was the reference to the                 service address and you place it on your DL form,
                                                                        Addendum update for Product #14 on LANO but the                    the listed address will appear in Directory
                                                                        question on how Qwest will process was not                         Assistance and/or a Directory. The order will not
                                                                        answered. As both have the word should – not sure                  reject if the Listed Address information is the same
145 Closed     Followup           Q # 118         MCI           11/3/04 how Qwest will process – ignore if there or error .        11/5/04 as Service Address and appears on the order.

                                                                        The second Addendum question concerns the
                                                                        updated to SASN for Product #25 where apparently
                                                                        removes the requirement to populate SASN when                      11/5/04: Sent to SME
                                                                        UNE-P EU 16-SASN “This field is required when                      11/12/04:
                                                                        SASD, SATH, or SASS are populated. If AHN is                       1. This business rule is still valid for Product 25 -
                                                                        populated, the "@" symbol is required and must be                  that product number was removed in error and will
                                                                        the first character. Question is if have new address               be corrected in the 17.0 Draft release of the
                                                                        on an install account ACT = N which has AHN                        Disclosure document.
                                  EU: 16-                               ROUTE AND BOX values populated what will be                        2. SASN - is either @ or @, Community or @,
146 Closed     App B: EU          SASN            MCI           11/3/04 required on the SASN field for Product #25                11/12/04 HC## or @, HCR## but just @ works fine.

Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 60 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                 Date
Q#   Status          Form             Name          Vendor                                    Issue/Question
                                                               Opened Would like to confirm the use of ACT = W on the              Answered                   Resolution/Answer
                                                                        REQTYP = JB for the following scenarios.
                                                                        1. If CLEC-1 is porting native numbers from another
                                                                        CLEC-2 and the ported numbers have Listings
                                                                        (a) Confirm CLEC-1 could issue an FBDL order with
                                                                        REQTYP = JB and ACT = W and have the LACT on
                                                                        the listings = Z
                                                                        (b) As Follow-up to question #123 – if CLEC-2 had
                                                                        issued the ACT = D on the listings would CLEC-1 get
                                                                        reject and request to issue an ACT = N                                1 (a) Correct
                                                                        (c) Is it a matter of timing of the order – so if CLEC-1              1 (b) Correct
                                                                        migration ACT = W completed first and then CLEC-2                     1 (c) Correct
                                                                        issued the ACT = D the CLEC-2 order would reject                      1 (d) Qwest does not require CLEC2 to issue a
                                                                        (d) What is the suggested business policy that best                   Disconnect, we advise for CLEC 1 to issue a
                                                                        supports the customer?                                                Migration ACT=W. However, it is CLEC2
                                                                        2. If CLEC-1 is porting numbers from Qwest and if all                 responsibility to ensure the listing(s) have migrated
                                                                        the listings associated to the ported numbers are not                 over to CLEC1, and if not, they will continue to
                                                                        changing then confirm CLEC-1 would issue a                            receive a bill for any Premium listings and the
                                                                        REQTYP = CB order with ACT = Z and Qwest would                        listing wil remain there until CLEC1 or CLEC2
                                                                        establish the listing account.                                        issues an order.
                                                                        3. If CLEC-1 is porting numbers from Qwest and the                    2. Correct
                                                                        customer wants to change, add or delete one of the                    3. Correct - if porting to an FBDL. Suggestion is to
                                                                        listings then confirm that Qwest would require two                    always Migrate as Is and then do subsequent
                                                                        PONs – one for the ported TNs, REQTYP = CB and                        changes when migrating to FBDL.
                                                                        ACT = V and a second PON REQTYP = JB and ACT                          3 (a) Again, this depends on whether the migration
                                                                        = W for the listings.                                                 is to Resale/UNE or FBDL. For Resale/UNE, the
                                  General                               (a) In this same scenario – if the Main listing LML is                answer is YES, but the subsequent order wourld
147 Closed     FBDL               Order           MCI          11/12/04 not changing and has LACT = Z but customer is                11/19/04 be REQTYP=HB and FBDL would be JB.
                                                                        With the new version, ADR is no longer a valid value
                                                                        for the caption indent address. Will we receive a                     ADR will not be an option, so the OUT portion will
                                  DL: 56-                               system or manual reject if we attempt to send an                      need to have the indent in the Address Fields and
148 Closed     FBDL               LTXTY           McLeod       11/17/04 ADR on the out portion of our listing?                       11/19/04 no error will be received.
                                                                                                                                              ADR is not stored in our OSS, so there will
                                                                                                                                              never be a mismatch on the LTXTY value. All
                                                                                                                                              address indents are stored in the OSS in the
                                                                        Can we send ADR for an existing listing that has ADR
                                                                                                                                              address fields. Sending an LTXTY=ITX for an
                                                                        present in your system? If we send ITX in the out
                                                                        LTXTY field on a change order will you reject us                      indent that was previously entered as
149 Closed     Followup           Q # 148         McLeod       11/23/04 because the listing in your system still as ADR?             11/24/04 LTXTY=ADR will not create a reject.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                  Page 61 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                Date
Q#   Status          Form             Name          Vendor     Opened                Issue/Question               Answered                   Resolution/Answer



                                                                        I found an example of a Directory
                                                                        listing Test Case in the
                                                                        WholeSale/Local Service Ordering
                                                                        Guideline and IMA SATE EDI Examples do
                                                                        not match with the Business Rule in the              Yes. The equal sign is invalid. The DWS Section
                                                                        Qwest Network Disclosure 409 – Release               4.6 information will be corrected with the 17.0 Draft
                                                                        15.0 for CAPTION/SLU Indent Section.
                                                                                                                             Disclosure as follows:
                                                                        According to the Qwest Network
                                                                        Disclosure 409 Website
                                                                        http://www.qwest.com/disclosures/netdis              Change From:
                                                                        closure409.html   Release 15.0 - The                 The Caption/SLU Indent Section is a conditional
                                                                        Developer Work Sheet Appendix C – DL                 section necessary for defining indented listings
                                                                        Form – 4.6 Caption/SLU Indent Section                (required when STYC = CI or SI and DOI > 1). For
                                                                        "The Caption/SLU Indent Section is                   Products 9, 9a, 13, 30, 31, 40: This section is not
                                                                        required for all activities when DOI >=              allowed when LACT = D or Z. For Product 14: This
                                                                        1 and Product is Facility Base                       section is required for all activities when DOI >= 1.
                                                                        Directory Listing”                                   The following fields LVL through FANSTN repeat
                                                                        In the Whole Sale / Local Service                    as a group up to six times. (DOI minus 1 number of
                                                                        Ordering Guideline / DL Form includes                times).
                                                                        an example where DOI = 1 but there is
                                                                        no CAPTION/SLU Indent Section                        Change To:
                                                                        In the EDI X12 Example Test Case, when               The Caption/SLU Indent Section is a conditional
                                                                        REQTYP = JB, ACT = C, the Local
                                                                                                                             section necessary for defining indented listings
                                                                        Additional Main Listing (LML) has DOI
                                                                                                                             (required when STYC = CI or SI and DOI > 1). For
                                                                        = 1 but there is no CAPTION/SLU Indent
                                                                        Section                                              Products 9, 9a, 13, 30, 31, 40: This section is not
                                                                                                                             allowed when LACT = D or Z. For Product 14: This
                                                                        Question: Should the Equal sign be                   section is required for all activities when DOI >1.
                                                                        removed and change to “For Product 14:               The following fields LVL through FANSTN repeat
                                                                        This section is required for all                     as a group up to six times. (DOI minus 1 number of
150 Closed     App C: DL          Section 4.6     Wisor         12/7/04 acvities when DOI > 1                       12/10/04 times).




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                 Page 62 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                                                  Resolution/Answer
                                                                                                                                Answered 12/31/04: Sent to SME
                                                                                                                                         1/7/05:
                                                                                                                                         1. Qwest will accept LNP orders for accounts that
                                                                                                                                         have active DSL. However, when the number port
                                                                                                                                         is completed, that existing DSL service will be
                                                                                                                                         dropped. Since that number is no longer managed
                                                                                                                                         by Qwest - either as a Resale or UNE/QPP
                                                                                                                                         account - it is the new number owner's
                                                                                                                                         responsibility to provide features and services for
                                                                                                                                         the end-user. Qwest does offer a stand-alone DSL
                                                                                                                                         product, which would have to be ordered on a
                                                                                                                                         separate LSR.

                                                                                                                                            From the "Port In" PCAT: A subsequent service
                                                                                                                                            request is required when ordering the following
                                                                                                                                            products and services:
                                                                                                                                            Digital Subscriber Line (DSL)
                                                                                                                                            Design Services (e.g. Integrated Services Digital
                                                                                                                                            Network (ISDN) and Off Premise Extensions
                                                                                                                                            (OPX)

                                                                                                                                            From the "LNP" PCAT: Other activities to perform
                                                                                                                                            prior to submitting a service request to port a TN
                                                                                                                                            are:
                                                                                                                                            If your request for port activity only addresses the
                                                                                                                                            porting of TNs
                                                                        1. Does Qwest reject port requests if DSL is on the                 Review the end-users Customer Service Record
                                                                        account/line? If so, does Qwest always reject the                   (CSR) verifying all numbers to be ported, including
                                                                        order or are there circumstances where Qwest will                   custom ring numbers. All services including alarm
                                                                        accept a Port with DSL on the account/line?                         services or Exchange Service Extensions, (i.e. Off
                                                                        2. What are the timelines associated with a day of                  Premise Extension (OPX) or Different Premise
                                  General                               Install Cancel? Example, when is the latest possible                Address (DPA)). when associated with ported TNs,
151 Closed     LNP                Order           Accenture    12/29/04 time a cancel can be performed on the day of install?        1/7/05 will be disconnected. If you require rearrangement,

                                                                        XO has a question about the EU billing address
                                  EU: 46-FBI &                          section. If they populate FBI with E (existing) and
                                  48a-54                                then also include address fields in the EU billing
                                  Billing                               address section, will this cause problems? If these                 If FBI=E then you should not populate the following
                                  Address                               fields are present, must they be fomatted as a valid                address fields in the Billing Information section.
152 Closed     App B: EU          fields       Neustar         12/17/04 address (e.g. SASD only allowed with SASN, etc)?             1/7/05 Those fields are Required if FBI=D



Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 63 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                           Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                   Answered                    Resolution/Answer
                                                                        Could you tell me if there is a requirement for APOT
                                                                        and CFA that may not be documented concerning
                                                                        the state of 'IA' ?
                                                                         * APOT ( LSR)- Required when REQTYP= "AB"
                                                                        and (ACT = " N" or "V" ) and EU_LOC.STATE =
                                                                        "IA"(Iowa), else prohibited when REQTYP = "AB" and
                                LSR: 48-                                ACT = "C"or "D". Prohibited when REQTYP = BB,
                                APOT, LS:                               CB, HB, JB or MB.
                                18-CFA &                                * CFA (LS) - Required when ACT = C,else required
               App B: LSR & App LSNP: 22-         AT&T                  when ACT = N or V and EU_LOC.STATE = "IA"
153 Closed     C: LS            CFA               Business       1/3/05 (Iowa), else prohibited.                                 1/7/05 You have noted the relevant rules for Iowa.
                                                                                                                                        Apparently, we misunderstood your question. You
                                                                                                                                        were the one who provided the Iowa rules (as
                                                                                                                                        stated in your question) to us. We intended to
                                                                                                                                        respond that all relevant rules are documented in
                                                                                                                                        Developer Worksheets. There may be additional
                                                                                                                                        rules for Iowa & other states (specific ordering
                                                                                                                                        requirements, contractual requirements, USOCs,
                                                                        Your response to my first question below was You                etc.) that are located in the PCAT and/or
                                                                        have noted the relevant rules for Iowa. Where are               USOC/FID Finder.
                                                  AT&T                  these requirements documented ?? I could not find               From where did you get the rules you noted in your
154 Closed     Followup           Q #153          Business      1/10/05 them in the worksheets.                                 1/14/05 original question?




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                          Page 64 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                               Date
Q#   Status          Form             Name          Vendor     Opened                      Issue/Question                        Answered                     Resolution/Answer
                                                                                                                                            Your requested range must match what is returned
                                                                                                                                            to you for that approintment in IMA (either returned
                                                                                                                                            via EDI or GUI Appointment Reservation Query).
                                                                                                                                            Products 1, 3, 4, 7, 8, 9, 9a, 10, 21, 25, 28, 29, 30,
                                                                                                                                            31, 33, 37, 38, 40, 41, 42: This field goes with
                                                                                                                                            DDD.
                                                                                                                                            For Information Only - If an appointment was
                                                                                                                                            reserved for this CCNA/PON in pre-order either
                                                                                                                                            manually or using IMA (if this is the case, APT
                                                                                                                                            CON is populated with the confirmation
                                                                                                                                            number), then this field is required and must
                                                                                                                                            match the time of the appointment. The LSR
                                                                                                                                            must be received:
                                                                                                                                            a. within a pre-established time frame (e.g., 24
                                                                                                                                            business hours) after reserving the appt., or, b.
                                                                                                                                            Within a pre-established time frame before the
                                                                                                                                            start time of the appointment; whichever time is
                                                                        We are currently receiving rejects within our internal              earlier. This field can optionally be used to indicate
                                                                        MCI systems and I‟m trying to validate the correct                  a desired appointment time if Pre Order
                                                                        value when using an „All Day‟ timeframe. The IMA                    Appointment Scheduling is unavailable. The CLEC
                                                                        Gui is providing us a timeframe of 0800 – 1700 when                 can call for a manual appointment and put that info
                                                                        reserving an appointment time/confirmation number.                  on the LSR, OR put in a desired apptime and
                                                                         Should the „All Day‟ be sent as a range from 0800 to               submit the LSR without an appointment in which
                                                                        1700? ... Can you check to see if the appointment                   case the service center will reserve the
                                  LSR: 18-                              time values changed with the Qwest 16.0                             appointment. If Pre Order Appointment
155 Closed     App B: LSR         APPTIME         MCI           1/11/05 implementation?                                             1/14/05 Scheduling is working, manually populating




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 65 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                        Answered                  Resolution/Answer
                                                                        Attached is a document (Qwest note:document
                                                                        contained CEMR thoroughfare abbreviations) I
                                                                        recently downloaded from the Qwest web site that
                                                                        contains Qwest thoroughfare abbreviations. In the
                                                                        Qwest IMA EDI Appendix A Developers Guide there
                                                                        are no valid value references to Thoroughfare                        The list attached is for CEMR use. The list for IMA
                                                                        Values.                                                              provisioning follows LSOG rules. And, regarding a
                                                                        There is no urgency but I would appreciate it if you                 list of the standards for SATH, the LSOG
                                                                        could forward to the appropriate Qwest SME if the                    references the following: Recommended
                                                                        attachment would be considered an inclusive list                     abbreviations are contained in the United States
                                                                        applicable for IMA EDI type pre order and order                      Postal Service Publication 28, Postal Addressing
                                                                        transactions. I would also like to ask where there are               Standards, Street Suffix Abbreviations Section.
                                                                        regional differences, for example Base, would it be                  This government document can be found at:
                                                                        appropriate for a CLEC to use a regional abbreviation                http://pe.usps.gov/cpim/ftp/pubs/Pub28/Pub28.pdf
                                                                        in all regions or would we receive an error message                  Qwest will take your request (to add these values
                                                                        in the non applicable regions.                                       as valid values in the Developer Worksheet in a
                                                                        What I‟m looking to is if Qwest would make this                      future release) under advisement.
                                AVQ: 15-                                itemization a reference in the IMA EDI Developer                     As always stated, however, for the most accurate
                                SATH, AVR:                              Worksheets in the future like they do for other similar              address information, CLECs should pull Address
                                20-SATH, &                              fields such as SASD, SASS, LD(x), etc. Nothing we                    Validation queries and use the AVR response,
               App A: AVQ & App EU: 17-                                 have to do immediately but I believe it is worthy of                 exactly as returned, to populate the LSR address
156 Closed     B: EU            SATH       MCI                  1/27/05 future planning.                                             1/28/05 information.
                                                                                                                                             The DWS shows this as the current valid value
                                                                        The Developer worksheets show that for Product 4,                    information for Product 4: Products 4, 7, 41, 42:
                                                                        Unbundled Loop, a Range is not allowed in the                        The format is HHMM representing start
                                                                        APPTIME field according to the rules in the                          time, or a range HHMM-HHMM
                                                                        Negotiated Business Rules Column. However, in the                    representing after and before time.
                                                                        Valid Values Column for Product 4 it shows that the                  This information is in the Negotiated Business
                                                                        format is HHMM representing a start time, or a range                 Rules for Product 4: Product 4, 41:
                                                                        HHMM-HHMM. This information is conflicting - Is                      For ACT=V, if CHC=B, APPTIME must be HHMM-
                                  LSR: 17-                              the Range allowed in the APPTIME field for Product                   HHMM. For Information Only - When CHC=B
157 Closed     App B: LSR         APPTIME         Wisor         1/31/05 4?                                                            2/4/05 APPTIME range is 0300-1100.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                Page 66 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                        Answered                  Resolution/Answer
                                                                        Negotiated Business Rules column shows that LCON
                                                                        is required for ACT N, T, V and Optional for ACT C.
                                                                        However, the EDI Test case example labeled
                                                                        EEL/UNE-Combination ACT = M, on page 65 of the
                                                                        EDI order examples has an ACT M, but does not
                                                                        have the SECLOC populated. Please clarify the
                                                                        rules for SECLOC for ACT M. Is it always required,                   The Secondary Location LCON should be
                                                                        or like ACT C, required only if the SECLOC is                        populated on the Populated X12 Mapping
                                                                        impacted. Either the EDI example is incorrect, or the                examples as LCON (68) is required if the SECLOC
                                                                        Rule specified in the Developer worksheets and                       section is present. The Populated X12 Mapping
                                  RPL: 68-                              Requirements documentation needs to be corrected.                    Examples will be updated with the 17.0 publication
158 Closed     App C: RPL         LCON            Wisor         1/31/05 Please advise.                                                2/4/05 to reflect that field correctly.

                                                                        I've got some questions regarding business rules for
                                                                        multi-line accounts. The Migration Indicator field is
                                                                        not required for LNP transactions, so we will not                    1. On a multi-line account - the lines not ported
                                                                        specify if we are sending a full or partial migrate. 1.              remain with Qwest and active for the end-user. If
                                                                        If an account has two or more TNs but we are only                    the primary TN (the one that makes up the AN) is
                                                                        migrating one TN, do the remaining TNs get                           the one that is ported, another number on the
                                                                        disconnected or do these remain active with QST?                     account will be come the primary TN/AN.
                                                                        2. If the TN has a distinctive ring TN but we are only               2. Distinctive Ring is a feature on the TN. When
                                  General                               migrating the main TN, does the dist. ring TN get                    you port the TN, all features are dropped -
159 Closed     LNP                Order           Accenture     1/31/05 disconnected or does it remain active with QST?               2/4/05 including the distinctive ring number.

                                                                        There are contradictory rules for product 14 for LSR -
                                                                        PON field. Must be a minimum of 4 characters and a
                                                                        maximum of 11 characters. The last character must
                                                                        be numeric. Only numeric characters 0 through 9
                                                                        and alpha characters A through Z in upper case                       2/4/05: Hyphens are not allowed for Product 14.
                                                                        allowed And          Special characters (anything that               This will be corrected in an addendum for 15.0 and
                                                                        is not a letter or number) are not allowed, except                   16.0 and in the 17.0 Final.
                                             AT&T                       hyphen. Could you tell me if Hyphen is allowed or                    Change will remove product 14 from the business
160 Closed     App B: LSR         LSR: 2-PON Business            2/2/05 not for Product 14 ?                                          2/4/05 rule you note.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                               Page 67 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                                Date
Q#   Status          Form             Name          Vendor     Opened                       Issue/Question                        Answered                   Resolution/Answer
                                                                        1.) What is the cost and/or fees associated with a
                                                                        rush port request (e.g. an order with a due date that
                                                                        is three days out)?

                                                                        1a.)We need to deteremine if Qwest accepts multiple
                                                                        main listings per address for Directory Listing
                                                                        Transactions (for both hosted and ported TNs).
                                                                                                                                             1. All fees are outlined in the customer's individual
                                                                        1b.)Is it logical to consider allowing only one listing              Interconnect Services Agreements (Exhibit A of the
                                                                        per telephone number? We need to deteremine if                       SGAT, for example).
                                                                        Qwest allows CLECs to send one Directory Listing                     1a. As answered above in Q#94: "There can only
                                                                        transaction for each TN on an account as a main                      be one main listing (LML) for an account number.
                                                                        listing (even though the address is the same for each                Qwest knows that there are multiple TNs for a
                                                                        TN). For example:                                                    given account. So, if you had an account with two
                                                                        Account 1234 (same address for all TNs):                             TNs and you attempted to submit an FBDL order
                                                                        TN 1: (612) 300-0001 (main TN)                                       for each TN as a LML, that would error out. You
                                                                        TN 2: (612) 300-0002                                                 need to submit the second TN as an additional
                                                                        TN 3: (612) 300-0003                                                 listing as outlined in the original response to #90."
                                                                                                                                             So, if you ported one number and have a FBDL
                                                                        2.) Will Qwest allow a CLEC to send one Main Line                    listing for that number, there can also be a listing
                                                                        (LML) Directory Listing transaction for each of the                  for another POTS Resale or UNE-P POTS account
                                                                        TN's above?                                                          at that address, for example.
                                                                                                                                             1b. There is only one listing per Account Number.
                                                                        3.) Does Qwest mandate that a CLEC must send the                     If you want listings for each TN on the account -
                                                                        first TN's DL as the LML and the DL for each                         those would be Additional Listings.
                                  General                               subsequent TN on the account as an additional listing                2. NO
161 Closed     FBDL               Order           Accenture     2/14/05 (LAL)?                                                       2/18/05 3. Yes




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                                 Page 68 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                              Date
Q#   Status          Form             Name          Vendor                                 Issue/Question
                                                               Opened LPIC and PIC requirements are different. Why ??           Answered                  Resolution/Answer
                                                                      I've highlighted in yellow the differences.
                                                                      ACT          LNA         PIC LNA Requirements
                                                                      LPIC LNA Requirements

                                                                        N            N            = Required
                                                                        = Required                                                         Answering questions on the "RED" highlighted
                                                                        D            D            = Prohibited                             pieces from the summary provided:
                                                                        = Prohibited                                                       PIC
                                                                        Z            D            = ?                                      ACT=Z, LNA=D: Required
                                                                        = Required                                                         ACT=T, LNA=N: Required
                                                                                     N           = Required                                ACT=C, LNA=N: Optional
                                                                        = Required                                                         ACT=C, LNA=C: Required if PIC changing, else
                                                                                     V           = Required                                optional
                                                                        = Required                                                         ACT=C, LNA=D: Optional
                                                                        T            N            = Required                               ACT=C, LNA=P: Required if LPIC not populated,
                                                                        = ?                                                                else optional
                                                                                     D           = Optional                                ACT=C, LNA=X: TN Change only allowed under
                                                                        = Optional                                                         this LNA (if changing PIC - use LNA=C)
                                                                        C           N            = ?                                       LPIC
                                                                        =?                                                                 ACT=Z, LNA=D: Required
                                                                                    C            = Optional if PIC changing                ACT=T, LNA=N: Required
                                                                        =?                                                                 ACT=C, LNA=N: Optional
                                                                                     D           = ?                                       ACT=C, LNA=C: Required if PIC changing, else
                                                                        =?                                                                 optional
                                                                                    P           = Req if LPIC not populated                ACT=C, LNA=D: Optional
                                                                        else ?         = Req if PIC not populated else ?                   ACT=C, LNA=P: Required if PIC not populated,
                                                                                    X            = Req if TN change only                   else optional
                                  RS: 28-PIC      AT&T                  else ????         = ????                                           ACT=C, LNA=X: TN Change only allowed under
162 Closed     App C: RS          & 29-LPIC       Business      2/25/05 L                        = Prohibited                       3/4/05 this LNA (if changing PIC - use LNA=C)
                                                                        I'm responding to your response to #162 in the 16.0
                                                                        Log. Both LPIC and PIC have the same                               The response in #162 was to help clarify the "else"
                                                                        requirements. Why are the usage codes different for                requirements and your other questions. The usage
                                                  AT&T                  LPIC and PIC ? Are all of these clarifications going               rules could vary for those items based on state-to-
163 Closed     Followup           Q #162          Business       3/7/05 to be included in 17.0 documentation ?                     3/11/05 state v. in-state LD differences.
                                                                        I'm responding to your question in your response to
                                                                        question #154. The requirement that I was                          Qwest must defer to the rules documented in the
                                                                        questioning was in our code but I couldn't find it in              Developer Worksheets and any other rules as
                                                  AT&T                  ANY AT& T or Qwest documentation. That is why I                    noted in the PCAT and/or USOC/FID Finder for
164 Closed     Followup           Q #154          Business       3/7/05 was confirming it's accuracy.                              3/11/05 this item.



Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                              Page 69 of 70
Qwest IMA-EDI 16.0 Question Log
Post Date: 4/1/2005


                                                   Reporting
                                                    CLEC,
                                                    Service
                                                   Bureau or
                Product or DWS      Field # or     Software     Date                                                             Date
Q#   Status          Form             Name          Vendor     Opened                        Issue/Question                    Answered                  Resolution/Answer
                                                                        I need clarification to you response question #162. If
                                                                        LNA = X on ACT = C then PIC/LPIC is required if TN                For ACT=C, LNA=X : You can ONLY do a TN
                                                                        is changing and the PIC/LPIC is not. Yes or No.                   Change. If anything else changes on the account -
                                                  AT&T                  If TN is changing and PIC/LPIC is changing then LNA               including PIC/LPIC, you can't use LNA=X. You
165 Closed     Followup           Q #162          Business       3/8/05 = C.                                                      3/11/05 have to use LNA=C.




Send Questions to: EDIQLOG@qwest.com
Log is updated every Friday to:
http://www.qwest.com/wholesale/ima/edi/faq.html                                                                                                                            Page 70 of 70

				
DOCUMENT INFO
Description: Idaho Business Yellow Page Listings document sample