QORA –ASR Gateway ASOG 37 Release

1. Effective September 22, 2008 QORA –ASR Gateway ASOG 37 Release

2. The Qwest Vision • 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 ServiceTM 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

3. Release 12.0 – QORA ASR Gateway • Qwest will implement the ASOG Version 37 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 September 22, 2008. For detailed information about the industry changes on the ASR – refer to the ATIS website: 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. 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 re-issues of the ASR (supplements). • 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 due to less re-work and supplements being required.

5. General Changes • Pre-Order GUI for Address Validation – QORA GUI • Enhancement to provide address validation using an existing working circuit ID. • Circuit ID must be a for a serialized point to point circuit (e.g. 34/HCGS/123456//MS) • Multipoint circuits are currently not supported. • Required entries are the circuit ID, and either the Serving Wire Center (SWC) CLLI code or the LSO of the end user address. • Address inquiries obtained during the ASR creation process in the GUI may also be imported directly onto the SALI form. • User Network Interface (UNI) associated with Ethernet Virtual Connection (EVC) • Qwest is implementing a process change on requests for User Network Interface (UNI) associated with Ethernet Virtual Connection (EVC). Effective with the ASOG 37 release, these requests need to be submitted using REQTYP ‘S’. Qwest has been using ‘X’ for the UNI with EVC. • For UNI orders submitted the QORA GUI, the appropriate selection in the Select Service Type drop down will now be “Special Access – Transport”.

6. Field Rules/Validation • LTP Field Validation: • A Qwest-specific edit will be implemented to require the LTP field to be populated with a valid entry when the REQTYP = ‘L’ and the ACT = ‘N’, ‘C’, or ‘D’. If the field is left blank, or the entry is not valid, the ASR is rejected. • LTP Field Validation: • Qwest will validate the entry in the LTP field when the REQTYP = ‘M’ or ‘L’ and ACT = ‘N’,’C’, or ‘D’. Data in the CFA, SCFA and the type of service being requested are considered to determine if the LTP is valid. If the field is not populated with a valid entry, the ASR will be rejected. • EXP Field Validation: • Qwest will enhance the validation to include REQTYP = ‘S’ for Voice Grade Private Line and REQTYP = ‘M’, that when the DDD is less than the standard interval, that the EXP field is populated with a ‘Y’. If the interval is less than standard and the EXP field is blank, the ASR will be rejected.

7. Field Rules/Validation • PSLI Field Validation: • Qwest is implementing an edit when the REQTYP = ‘M’ and the ACT = ‘N’ or ‘C’ and either the CC or the WST fields on the ASR are populated. When the CSL CLLI code and the PSL CLLI code are in the same LATA, that the PSLI is populated with an ‘F’. If the CSL and the PSL are in different LATAs, the system shall validate that the PSLI is populated with an ‘E’. If the PSLI is invalid, the ASR will be ejected. If the PSL and/or CSL are not populated, the PSLI field is not validated. • CFA Field Validation: • The system shall implement an enhancement to validate the CFA on all service specific forms when the ASE-EC is populated. When the ASC-EC is populated with a Qwest ICSC code, the system shall perform all existing availability CFA checks and the ASR will be rejected if the CFA is invalid or not available for assignment. When the ASE-EC is populated with a Non-Qwest ICSC code, the system shall attempt to validate the CFA. If the CFA is not found in the Qwest systems, the ASR will not be rejected. • TSC Field Validation: • When the ASR.REQTYP = M and the ASR.ACT=‘C’,’D’ or ‘R’, the system shall validate that the value populated in the TSC field is valid. If the TSC is not valid, the ASR will be rejected. • ECCKT Field Validation: • Qwest is implementing an edit when the ACT = ‘C’, ‘D’ or ‘R’, the system shall validate that the entry in the ECCKT field is formatted correctly. If the ECCKT is not formatted correctly according to the ASOG requirements, the ASR shall be rejected.

8. Field Rules/Validation • INTER AND INTRA Field Validation: • When the WST field or the CC field on the ASR form is populated, the INTRA and INTER fields on the Translation Questionnaire Trunking section are prohibited. • PIU Field Validation: • Qwest will validate the entry in the PIU field when the REQTYP = ‘M’ and ACT = ‘N’ and the CC field on the ASR form is populated or when the CCNA indicates a Wireless Provider, the PIU must equal 0 (zero) or the ASR will be rejected. • MUXLOC Field Validation: • Qwest is implementing an edit when the REQTYP = ‘M’ and the ACT = ‘N’ and the CFA field on the Trunking form is populated, the MUXLOC field is required. If the MUXLOC field is left blank, the ASR will be rejected.

9. Customer Responsibilities • Arrange to participate in the 30-day testing window prior to the release • Test for the ASOG 37 Industry changes per industry test plan. • Test for the new Qwest ASR Gateway upfront validations and rule edits • Ensure information on the release details is shared internally with those employees issuing ASRs to Qwest.

10. FAQs • Are manually transmitted ASRs impacted with this release? • Yes – the industry changes for ASOG Version 37 are applicable and the new forms must be used effective with ASRs transmitted to Qwest after 3:00 pm (MST) on Friday September 19, 2008. • 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.

11. 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