1. Copyright © 2010 Qwest. All rights reserved. Qwest Confidential & Proprietary QORA 17.0 - ASR Gateway ASOG 42 Release Effective March 21, 2011

2. Copyright © 2010 Qwest. All rights reserved. 2Qwest Confidential & Proprietary Qwest is a premier provider of full-service communications for people at work, at home or on the move. Qwest's competency reaches across America, drawing on the Spirit of Service TM at the heart of our heritage as we effectively steward our shareowners' investments and provide outstanding service to the customers we serve. As our dedicated professionals move and manage information, we do so with integrity, superior value and advanced products and services, assuming only those tasks we can do exceedingly well. Qwest Values The following values guide our decisions, both corporate and individual, as we transform Qwest into a premier telecommunications provider that delivers exceptional service to customers, creates pride among our employees, delivers value to our shareowners and earns high regard from our many constituents: Customers come first Our team is united We will grow profitably The Qwest Vision

3. Copyright © 2010 Qwest. All rights reserved. 3Qwest Confidential & Proprietary Release 17.0 – QORA ASR Gateway Qwest will implement the ASOG Version 42 Industry Standard changes to the ASR forms and fields decided upon at an industry level with participating members of the OBF Committees. Effective date for this release as dictated by the industry is March 21, 2011. For detailed information about the industry changes on the ASR – refer to the ATIS website: http://www.atis.org/http://www.atis.org/ Qwest will implement upfront validations in the QORA ASR Gateway that impact all ASRs being transmitted to Qwest electronically. This includes the web-based QORA (Qwest Online Request Application) GUI application, or through direct connections, such as NDM or UOM interfaces.

4. Copyright © 2010 Qwest. All rights reserved. 4Qwest Confidential & Proprietary Customer Impacts/Value How does implementation of Qwest up front editing add value for you, our customer?  The QORA GUI application is a superior alternative to paper ASR forms, offering on-line help as well as validations for accuracy.  Upfront edits streamline processing time for your request, by ensuring the data supplied by you is as accurate as possible.  Prior to the ASR being accepted into Qwest’s systems, you are notified of the errors on the ASR allowing corrections to be made, thereby reducing the need for costly supplemental ASRs.  An accurate ASR helps ensure the accurate provisioning of your request the first time.  Accurate entries also create accurate billing, reducing the possibility for errors on your monthly bill.  Reduced cycle time

5. Copyright © 2010 Qwest. All rights reserved. 5Qwest Confidential & Proprietary General Changes Pre-Order Validation Enhancement – QORA Gateway  There are no Pre-Order Validation changes or enhancements with this release. Report Enhancement – QORA GUI  There are no Report changes or enhancements with this release.

6. Copyright © 2010 Qwest. All rights reserved. 6Qwest Confidential & Proprietary ASOG 42 Industry Changes to QORA GUI and ASR Gateway ASR – Access Service Request – Form:  DSGCON (Design Contact) Field usage requirements changing from required to conditional. DSGCON is required when:  ACT = N, C, M, or T  The second position of the AFO field is populated (TSR form)  Otherwise prohibited  DSGCON Tel Field usage requirements changing from required to conditional. Required when DSGCON is populated, otherwise prohibited Transport Form:  Two new fields  IP Address  This field is conditional when the REQTYP on the ASR Form is "S", the ACT field on the ASR Form is "N" or "C", and the SECNCI field specifies an Ethernet switched port, otherwise prohibited

7. Copyright © 2010 Qwest. All rights reserved. 7Qwest Confidential & Proprietary ASOG 42 Industry Changes to QORA GUI and ASR Gateway (cont.)  IP Address (cont.)  QORA does not enforce these edits when the ASC-EC is populated with a non-Qwest value  QORA will not validate whether or not the content meets the Internet Engineering Task Force (IETF) Standards for an IPv4 address  IP Address can be populated only when the Transport Form's SECNCI is populated with switched Ethernet Ports values and ACT is N or C  Subnet Mask  This field is conditional when the REQTYP on the ASR Form is "S", the ACT field on the ASR Form is "N" or "C", and the SECNCI field specifies an Ethernet switched port, otherwise prohibited  QORA does not enforce these edits when the ASC-EC is populated with a non-Qwest value  QORA will not validate whether or not the content meets the Internet Engineering Task Force (IETF) Standards for an IPv4 address  IP Address can be populated only when the Transport Form's SECNCI is populated with switched Ethernet Ports values and ACT is N or C

8. Copyright © 2010 Qwest. All rights reserved. 8Qwest Confidential & Proprietary ASOG 42 Industry Changes to QORA GUI and ASR Gateway (cont.)  Switched Ethernet TRANS.SECNCI values are:  04CX9.10T  04CX9.1CT  08CX9.1GE  02CXF.1GE  Example of form with new fields:

9. Copyright © 2010 Qwest. All rights reserved. 9Qwest Confidential & Proprietary ASOG 42 Industry Changes to QORA GUI and ASR Gateway (cont.) EVC - Ethernet Virtual Connection – Form  DSCP - Differentiated Services Code Point is changing to allow for ranging  DSCP must be populated with 6 or 12 numeric values of 0s or 1s  When populated for a single value, the first six positions must contain a “0” or a “1”.  When populated for ranging all 12 numeric characters must be populated with a “0” or a “1”.  Blank is considered not populated  This field is conditional  Optional when the associated LREF field is populated and the associated TOS field is not populated, otherwise prohibited.  Example of valid data:

10. Copyright © 2010 Qwest. All rights reserved. 10Qwest Confidential & Proprietary ASOG 42 Industry Changes to QORA GUI and ASR Gateway (cont.) EVC Form Continued BDW – Bandwidth field – is being modified to allow “UNI” as a value provided when bandwidth will be provided at the UNI level contingent upon customer/provider negotiations. This field is conditional - required when associated LOSACT field is “C” or “N”, otherwise optional. Examples of valid entries:

11. Copyright © 2010 Qwest. All rights reserved. 11Qwest Confidential & Proprietary In some cases the city name portion of CLLI Codes (the first 4 characters) is only 3 characters. When this occurs the correct format is to leave the 4 th position blank showing a space in the CLLI code. The system would reject these ASRs for an invalid CLLI Code. QORA will no longer reject when the 4 th position is a space/blank. Correcting edits from 16.0 release around the population of the ASR.ICSC field when ASC_EC is populated so that the system does not require only Qwest specific ICSC values Enhancing the PSL/PSLI/CSL validations to include REQTYP = M, ACT = C Currently there is an edit that requires the MUXLOC field on the Transport Form be populated for REQTYP = S, and CFA is populated on the Transport Form. Qwest is changing this to not require TRANS.MUXLOC when REQTYP = S, ACT = N, TRANS.CFA = NEW when ordering an OC- system where Qwest will name the CFA. Qwest Specific QORA GUI and ASR Gateway Field Level Validations

12. Copyright © 2010 Qwest. All rights reserved. 12Qwest Confidential & Proprietary Qwest Specific QORA GUI and ASR Gateway Field Level Validations (cont.) When the SCFA field is populated on the Transport form, the SMUXLOC field is required.  When REQTYP = S  ACT = N  Must be populated with a valid CLLI  New error message is: TRANS.SMUXLOC = Required when TRANS.SCFA is populated When the SCFA field is populated on the Additional Circuit (ACI) form, the SMUXLOC field on the Transport form is required and must be populated with a valid CLLI.  When REQTYP = S  ACT = N  Must be populated with a valid CLLI  New error message is: Required when the TRANS.SCFA or ACI.SCFA field is populated

13. Copyright © 2010 Qwest. All rights reserved. 13Qwest Confidential & Proprietary Qwest Specific QORA GUI and ASR Gateway Field Level Validations (cont.) When the ACT = N and RPON is populated the system will no longer reject for CCEA/SCCEA busy slots For all ACT Types, when the SUP is 3 or 4, the system will not allow the ACT or the REQTYP to be different than the previous version. The new error message is: Requires cancellation of this request and a new request issued The system will validate that the CFAU field is not populated when:  REQTYP = E, S, V, or X  ACT = N or C  NC Codes reflect Virtual Concatenation Service  If the CFAU is populated the ASR will be rejected  The reject message will be: Prohibited with Virtual Concatenation NC Codes

14. Copyright © 2010 Qwest. All rights reserved. 14Qwest Confidential & Proprietary Qwest Specific QORA GUI and ASR Gateway Field Level Validations (cont.) Transport Form (TRANS) and End User Special Access (EUSA) form – SECLOC fields  REQTYP = E or S  ACT = N  When the WACD1 field is populated on the ACI, TRANS, or EUSA form the system will first validate that the SECLOC field is populated.  If not the ASR will be rejected.  The new error message is: When WACD1 is populated the SECLOC must be populated.  Then the system will validate that when SECLOC field is populated and the WACD1 field is populated, the first character of the SECLOC field is a “C” and the CLLI Code is a valid Qwest CLLI Code  If not the ASR will be rejected.  The new error message is: When WACD1 is populated the SECLOC must start with C.

15. Copyright © 2010 Qwest. All rights reserved. 15Qwest Confidential & Proprietary Qwest Specific QORA GUI and ASR Gateway Field Level Validations (cont.) When the REQTYP begins with S or E, the NC begins with HC (indicating a DS1), and the CFA on the Transport or Trunk Forms is populated (indicating the DS1 is riding a higher facility), or the CFA_PRILOC field on the End User Special Access Form is populated, the system will begin validating that the NCI on the End User Special Access, Transport or Trunking form is:  04DS6.44*  04QB6.33*  If not, the ASR will be rejected  The new reject message is: Invalid NCI when CFA is present and NC starts with HC  This is a current C/NR reason that is being moved to the “upfront” system for editing When the REQTYP begins with S or E, the NC begins with HC (indicating a DS1), and the NCI on the End User Special Access, Transport, or Trunking Form is one of the codes listed above, the CFA field on the Transport or Trunk Form must be populated, or the CFA_PRILOC field on the End User Special Acces field must be populated  If not, the ASR will be rejected.  The new reject message is: Must be present when NCI value is 04DS6.44* or 04QB6.33*  This is a current C/NR reason that is being moved to the “upfront” system for editing Note: The asterisk above represents a wildcard and can be any valid character or blank.

16. Copyright © 2010 Qwest. All rights reserved. 16Qwest Confidential & Proprietary Qwest Specific QORA GUI and ASR Gateway Field Level Validations (cont.) When the REQTYP begins with S or E, the NC begins with HC (indicating a DS1), and the SCFA on the Transport or Trunk Forms is populated (indicating the DS1 is riding a higher facility), or the CFA_SECLOC field on the End User Special Access Form is populated, the system will begin validating that the SECNCI on the End User Special Access or Transport Form is:  04DS6.44*  04QB6.33*  If not, the ASR will be rejected  The new reject message is: Invalid SECNCI when SCFA is present and NC starts with HC  This is a current C/NR reason that is being moved to the “upfront” system for editing When the REQTYP begins with S or E, the NC begins with HC (indicating a DS1), and the SECNCI on the End User Special Access or Transport Form is one of the codes listed above, the SCFA field on the Transport or Trunk Form must be populated, or the CFA_SECLOC field on the End User Special Acces field must be populated:  If not, the ASR will be rejected.  The new reject message is: Must be present when SECNCI value is 04DS6.44* or 04QB6.33*  This is a current C/NR reason that is being moved to the “upfront” system for editing Note: The asterisk above represents a wildcard and can be any valid character or blank.

17. Copyright © 2010 Qwest. All rights reserved. 17Qwest Confidential & Proprietary Qwest Specific QORA GUI and ASR Gateway Field Level Validations (cont.) If NC/NCI/SECNCI is provided on an ACT = D the system will validate the combination provided for validity. If the combination is not valid, the ASR will be rejected NOTE: NC/NCI/SECNCI is not a required entry with ACT = D per the ASOG. This is not changing, this validation will only be performed if provided The system will begin validating that the VTA and SPEC fields are populated when the REQTYP = E or S and the EVCI is blank or populated with a “B”. If the VTA and SPEC fields are not populated the ASR will be rejected

18. Copyright © 2010 Qwest. All rights reserved. 18Qwest Confidential & Proprietary Qwest Specific QORA GUI and ASR Gateway Field Level Validations (cont.) The Gateway will perform validations on the Trunking Form Customer Point Codes (TRK.CSPC) field when:  REQTYP = L or M  ACT = N or C  ACTI = A, B, or C  If the CSPC is blank, the ASR will be rejected  The new error message will be: CSPC must be populated  If CSPC cannot be validated, the ASR will fall to the center for manual validation and a C/NR may be sent back to you

19. Copyright © 2010 Qwest. All rights reserved. 19Qwest Confidential & Proprietary Customer Responsibilities Arrange to participate in the 30-day testing window prior to the release beginning.  Test for the ASOG 42 Industry changes.  Test for the new Qwest ASR Gateway upfront validations and rule edits Ensure release detail information is shared internally with those employees issuing ASRs to Qwest.

20. Copyright © 2010 Qwest. All rights reserved. 20Qwest Confidential & Proprietary FAQs Are manually transmitted ASRs impacted with this release?  Yes – the industry changes for ASOG Version 42 are applicable and the new forms must be used effective with ASRs transmitted to Qwest after 3:00 pm (MST) on Friday March 18, 2011. Do the QORA ASR Gateway upfront edits impact our company if we have our own ordering systems?  Yes, all ASRS electronically submitted to Qwest through direct connections, e.g., NDM or UOM are impacted with the new edits/validations.

21. Copyright © 2010 Qwest. All rights reserved. 21Qwest Confidential & Proprietary Contacts/Resources Contact your Qwest Service Management Representative for more information. Detailed information on all ASR related ordering and technical specifications can be viewed at this website: http://www.qwest.com/wholesale/systems/asr.html http://www.qwest.com/wholesale/systems/asr.html