CORA ASR Gateway 19.0/ASOG 44 Release January 17, 2012 CORA ASR Gateway 19.0/ASOG 44 Release

ASOG 44/CORA ASR Gateway – 19.0 CenturyLink will implement the ASOG Version 44 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 19, 2012. For detailed information about the industry changes on the ASR – refer to the ATIS website: http://www.atis.org/ CenturyLink will implement upfront validations in the CORA ASR Gateway that impact all ASRs being transmitted through CORA electronically. This includes the web-based CORA (CenturyLink Online Request Application) GUI application, or through direct connections, such as NDM or UOM interfaces.

Customer Value and Impacts How does implementation of CenturyLink up front editing add value for you, our customer? The CORA 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 CORA, 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. Reduces cycle time

ASOG 44: Changes on the ASR Form A new field is being added to the Access Service Request (ASR) Form called JPR (Jointly Provided Rings). This field is optional when the first position of the REQTYP field is “S” or “E” and the ASC-EC field is populated, otherwise prohibited. If the ASC-EC is not populated with JPR a new edit is presented: ASR.ASC-EC is required when JPR is populated This field is conditional when the first position of the REQTYP is “S”, and: The CFA or SCFA field on the Transport or Additional Circuit Information (ACI) Forms contain the CFA of a jointly provided ring Any of the ICFA fields on the Network Assignment Information (NAI) Form contains the CFA of a jointly provided ring. This field is conditional when the first position of the REQTYP is “E”, and: The PRILOC CFA or the SECLOC CFA field on the End User Special Access (EUSA) Form contain the CFA of a jointly provided ring The CFA or SCFA field on the ACI Form contain the CFA of a jointly provided ring Any of the ICFA fields on the NAI Form contains a CFA of a jointly provided ring

ASOG 44: Changes on the ASR Form cont. A new field is being added to the ASR Form called EDA (Early Date Acceptance) to indicate that customers agree to accept an earlier due date on their confirmation notice than the desire due date requested if the provider is able to turn up the circuit at test. Valid entry of “Y” This field is conditional: Prohibited when the EXP field is populated. If EXP and EDA are both populated, CORA will present a new edit: Prohibited when ASR.EXP is populated Prohibited when the ASC-EC field is populated. If ASC-EC and EDA are both populated, CORA will present a new edit: Prohibited when ASR.ASC-EC is populated Otherwise optional CenturyLink will not be using this field in CORA at this time.

ASOG 44: Changes on the ASR Form cont.

ASOG 44: Changes on the ASR Form cont. The following fields on the ASR Form are prohibited when the ACT is D: LUP - If populated when ACT is D a new edit is presented: Prohibited when the ACT field is D FNI – CORA currently does not allow when ACT is D RFNI – If populated when ACT is D a new edit is presented: Optional when REQTYP is R, S or E, and ACT is not D, otherwise prohibited PSL – If populated when ACT is D a new edit is presented: Prohibited when the ACT field is D PSLI – If populated when ACT is D a new edit is presented: Prohibited when the ACT field is D PIU – If populated when ACT is D a new edit is presented: Prohibited when the ACT field is D PLU – Changing the CORA edit to: Prohibited when both CC and UNE fields are blank or the ACT is D ISTN – If populated when ACT is D a new edit is presented: Prohibited when the ACT field is D APOT – If populated when ACT is D a new edit is presented: Prohibited when the ACT field is D IWBAN – If populated when ACT is D a new edit is presented: Prohibited when the ACT field is D

ASOG 44: Confirmation Notice New Field A new field is being added to the Confirmation Notice (FOC) called NFR (Network Facility Requirement) to indicate that the customer’s desired due date (DDD) cannot be met because additional facilities are required to fulfill the request and the order is a delayed/held order. This field is required on the FOC when the due date (DD) is greater than the DDD due to facility issues. The NFR field does not replace the Clarification/Notification Request that is being sent to initially notify the customer of a Delayed Order. This new field will be populated on the FOC when a new due date is available. This new field is in the Administrative section of the Confirmation Notice Form, next to the DD field:

ASOG 44: Service Address Location Information Changes Several changes to SALI Form fields and edits are being made to accommodate ordering services to a location that does not have a standard E911. AFT (Address Format Type): a new valid entry of “E” is being added for the AFT field E = Remote Location with Assigned CLLI. A value of “E” indicates a service delivery location that has been assigned a CLLI code despite the lack of a postal or E-911 address (e.g. tower, hut, pole, billboard, mine, etc.). New ASOG rules are: A value of “A”, “B”, “C” or “D” is optional when the SASN field is populated. The CORA edit is changing to mirror this rule change: A value of A, B, C, or D is optional when the SASN field is populated otherwise prohibited A value of “E” is optional when the SASN field is blank. A new CORA edit will be presented to mirror this rule change: A value of E is optional when SASN field is blank, otherwise prohibited Otherwise optional CORA will not perform address validation when AFT = E

ASOG 44: SALI Changes continued The ASOG is expanding the character limit on the AAI (Additional Address Information) field from 60 to 150 characters. If AFT is E and AAI is not populated CORA will present a new edit: SALI.AAI: Required when SALI.AFT is E A new ASOG rule is being added for the SPOT (Secondary Point of Termination) field. The SPOT field is required when the AFT field is populated with “E” New CORA edit will be presented if AFT is E and SPOT is not populated: SALI.SPOT: Required when SALI.AFT is E

ASOG 44: SALI Changes continued – SI Field In lieu of the ASOG changes, CORA specific edits are being added for the SI (Secondary Point of Termination Indicator) and SPOT fields. If the SALI.AFT field is E, the SALI.SI field is required. If not populated, CORA will present a new edit: SALI.SI required when SALI.AFT is E Valid entries in the SI field are not changing: N = Narrative C = CLLI If the SI field is populated with an “N”, CORA will validate that the SALI.SPOT field is populated. If not a new error message is presented: SALI.SPOT: Required when SALI.SI is N

ASOG 44: SALI Changes continued – SI Field cont. If the SI field is populated with an “C”, CORA will validate that the SALI.SPOT field is populated. If not a new error message is presented: SALI.SPOT: Required when SALI.SI is C When the SI field is populated with a C, the ASOG states that the SPOT field is populated with a valid CLLI code. CORA will validate the CLLI code populated in the SPOT field is a valid CLLI code per the LERG: If the CLLI Code is not found in the LERG CORA will present the existing edit when an invalid CLLI is used: CLLI ‘xxxxxxxx’ is not valid If the CLLI Code provided is valid but is identified as a non-company CLLI Code, CORA will require that the ASC-EC field is populated: CLLI is not in CenturyLink (formerly Qwest) territory, ASC-EC is required CORA will capture the address associated with the CLLI code in the LERG and pass the address to the Wholesale Service Delivery Provisioning Center to be placed on your service order.

ASOG 44: SALI Changes – New Contact Fields Three new contact fields are being added to the SALI form: LCON EMAIL: Local Contact Electronic Mail Address 60 character field Optional when the LCON field is populated, otherwise prohibited CORA will present a new edit if the LCON EMAIL field is populated and the LCON field is blank: Prohibited when LCON is blank AALCON TEL: Additional Alternate Local Contact Telephone Number 14 character field including 3 pre-populated hyphens Optional when the ALCON field is populated, otherwise prohibited CORA will present a new edit if the AALCON field is populated and the ALCON field is blank: Prohibited when ALCON is blank ALCON EMAIL: Alternate Local Contact Electronic Mail Address 60 characters CORA will present a new edit if the ALCON EMAIL field is populated and the ALCON field is blank: Prohibited when ALCON is blank

ASOG 44: SALI Changes – New Contact Fields

ASOG 44: Ethernet Virtual Connection Form A new field is being added to the Ethernet Virtual Connection (EVC) Form called EVCMPID (EVC Meet Point ID) to specify the physical facility ID interconnecting two service providers in an EVC meet point arrangement. Valid entry is the CLFI Code of the other provider in the EVC Meet Point arrangement This field is conditional in the ASOG: Optional when the ASC-EC field on the ASR Form is populated, otherwise prohibited CenturyLink will not be using this field in CORA at this time.

ASOG 44: Address Validation Responses When CORA performs address validation a Service Address Number Range (SANOR) is provided when a near match or multiple matches are found (documented in ASR-UOM Vol. I). ASOG 44 is introducing a Service Address Number Range Type (SANORT) as part of the response. SANORT will indicate that an address range consists of all even, all odd, both, or undetermined street number ranges. The CORA UOM response will display the following: E – representing even numbered ranges O – representing odd numbered ranges B – representing both even and odd numbered ranges

ASOG 44: Address Validation Responses – CORA GUI When the CORA GUI Pre-Order Address Validation option is used, a new column will be displayed as part of the address response when a near match or multiple match is found. The SANORT column will indicate that an address range consists of all even, all odd, both street number ranges. The CORA GUI response will display the following: E – representing even numbered ranges O – representing odd numbered ranges B – representing both even and odd numbered ranges Blank – representing the SANORT is undetermined

CORA 19.0: Meet Point Ordering New edits are being introduced around the ICSC field in the Header (HDR) section, and ICSC and ASC-EC fields on the ASR Form when Meet Point is being requested. When the ASC-EC is populated with a CenturyLink (formerly Qwest) value, the value must match the value populated in the ASR.ICSC field. If not a new error is presented: When ASC-EC is populated with a CenturyLink (formerly Qwest) value it must match the Header ICSC When the ASC-EC field is blank/not populated the HDR.ICSC and the ASR.ICSC values must match. If not a new error is presented: When ASC-EC is blank, HDR.ICSC and ASR.ICSC must match When the ASC-EC field is populated the value must match the ASR.ICSC value. If not a new error is presented: When ASC-EC is populated it must match the ASR.ICSC Once an ASR is submitted with a value populated in the ASC-EC field, CORA will edit to ensure that value is the same on supplemental ASRs (SUPs). If the value changes a new error message will be presented: Cannot change ASR ASCEC after initial acknowledgement. To change, a cancel and reissue is required

CORA 19.0: Meet Point Ordering cont. Additional new edits are being added to the Multiple Exchange Carrier (MEC) Form in correlation with the ASC-EC field. When ASC-EC is populated the value must match the value in the MEC.ICSC (in the ASC section) field. If not a new error is presented: When ASC-EC is populated it must match the MEC.ICSC CORA is implementing new edits on the MEC Form in the OEC section. When CenturyLink is not in control there can be multiple ICSC values in the OEC section of the MEC Form. One legacy Qwest value must be present in the ICSC list. If not a new error message will be presented: CenturyLink (formerly Qwest) value must be among the OEC ICSCs when CenturyLink is not in control of the Meet Point. When CenturyLink is in control there can be multiple ICSC values in the OEC section of the MEC Form. A legacy Qwest value must not be present in the ICSC list. If so a new error message will be presented: CenturyLink (formerly Qwest) value must not be among the OEC ICSCs when CenturyLink is in control of the Meet Point.

CORA 19.0: CORA Specific Edits CORA will reject ASRs that contain invalid characters such as a tilde (~), brackets ([ ]), etc. The new error message is: This ASR contains an invalid character (xxxx). Only ASCII characters 0x20 through 0x7A, carriage returns ( 0x0D ) and line feeds ( 0x0A ) are allowed CORA will not validate CSPC on the following ASRs: REQTYP = L or M ACT = N or C ACTI = A, B or C NC Codes represent Feature Group B or D is being requested SB-B SD-B SB-D SD-D SDUA SH-D

CORA 19.0: CORA Specific Edits CORA will not validate due date intervals on ASRs with: REQTYP = L or M ACT = N, C, D Project ID ends in “CONV” The due date may be less than standard interval and the EXP field is not required. These ASRs represent company initiated Central Office Conversions. CORA will require that at least one CE-VLAN field is populated when: REQTYP = E or S ACT = N EVCI = B SPEC = SVCSP or SVCMUX New edit will be displayed: CE VLAN is required when REQTYP is E or S, ACT is N, EVCI is B, SPEC is either SVCSP or SVCMUX

CORA 19.0: CORA Specific Edits cont. CORA will require either the DIVCKT or DIVPON be populated when the SR field is populated on the Transport or End User Special Access form. If the SR is populated and the DIVPON or DIVCKT is blank, CORA will present new edits: DIVPON*: Required when TRANS.SR is populated and TRANS.DIVCKT is blank DIVCKT*: Required when TRANS SR is populated and TRANS DIVPON is blank If DIVCKT or DIVPON is populated and the SR field is blank, CORA will present a new edit: SR*: Required when TRANS DIVCKT or TRANS DIVPON are populated If DIVCKT and DIVPON are blank and the SR field is populated, CORA will present a new edit: SR*: Prohibited when TRANS DIVCKT and TRANS DIVPON are blank * The abbreviated form name will precede the form field name in the error messages as appropriate: e.g. EUSA.DIVPON, TRANS.DIVPON