Qwest has reviewed its current Single Location Routing Number (SLRN) process and is changing the SLRN process to Alternate Routing for Location Routing Number (ARLRN) process for CLECs and WSPs in order to be more closely aligned with industry guidelines. Those customers who currently have SLRN routing in place are NOT required to make any changes in their embedded network and all new routing requests will follow the ARLRN process.
Alternate Routing for Location Routing Number (ARLRN) is a process that enables Qwest to route Local Number Routing (LRN) traffic to new or existing Local Interconnect Services (LIS) trunks or Wireless Type 2 Interconnect Services (Type 2) trunks at the end office or local tandem, with a minimum of one LRN per switch, per Local Access and Transport Area (LATA). CLECs or WSPs may maintain existing SLRN arrangements or may request a transition from existing SLRN to ARLRN arrangements as a project, however new SLRN requests will not be offered.
Additional LIS and Type 2 trunk information is described in the following PCATs:
Background
In order to assign a LRN, you must obtain an NPA-NXX from the North American Numbering Plan Administrator (NANPA) for each LNP capable switch. Refer to Local Number Portability (LNP), Product Description Section, for additional LRN assignment information.
The industry LRN Assignment Practices were developed by the Industry Numbering Committee (INC) and issued by the Alliance for Telecommunications Industry Solutions (ATIS) on July 13, 1998, and Technical Requirements No. 2 prepared April, 1999 by the T1S1.6 Working Group on Number Portability and issued by ATIS.
Specifically, the INC practice states that a NXX will not be assigned to a service provider for the sole purpose of establishing a LRN unless that service provider's switch or Point of Interconnection (POI) does not yet have an LRN for the LATA where they intend to provide service. The T1S1.6 technical requirement state: "only one NPA-NXX is needed for the first 6-digits of an LRN per LATA to identify the switch LRN".
LRN
Qwest supports one LRN per LATA. Typically, LRNs will route the same as the NPA-NXX they are a part of, therefore, if the NPA-NXX of the LRN is outside of the local calling area of the end office, the traffic will route to the access tandem and then to you. The routing of local LRN traffic via the access tandem and toll trunks will occur even if you have LIS or Type 2 trunks in place at the end office or local tandem unless ARLRN is requested.
Alternate Routing for Location Routing Numbers (ARLRN)
Alternate Routing for Location Routing Numbers (ARLRN) allows one or more LRNs to be routed on a single trunk group at end offices or local tandem. When requesting ARLRN, you are directing Qwest, via an ASR or CORR form, to route your LRN on your new or existing LIS or Type 2 trunks at the end office for Qwest originated traffic or at the local tandem for un-queried non-Qwest originated traffic instead of routing the traffic to the access tandem and then on to you. Qwest will translate using a 6-digit (NPA-NXX) routing scheme.
Diagrams
The following diagrams provide examples of Qwest's Network Configuration for ARLRN , Default LRN and Embedded SLRN.
Example 1a; ARLRN routing with Local Tandem trunking when the NPA-NXX of the LRN is outside the local calling area:
Example 1b; ARLRN routing with Direct End Office Trunking (DEOT) when the NPA-NXX of the LRN is outside the local calling area:
Special Note regarding Direct End Office Trunk Groups with ARLRN routing:
When a call originates from Qwest telephone numbers that are presubscribed to Qwest LPIC 5123 and resides in that same end office as the DEOT group where ARLRN is requested on a LIS or Type 2 DEOT group, Intra-LATA toll calls dialed to the same NPA-NXX as your LRN will be routed like the LRN.
Default LRN Routing
If the Qwest switch recognizes the NPA-NXX of the LRN for the ported telephone number (TN) as being outside the local calling area, local calls will be routed via toll trunks to the Qwest Access Tandem. Calls are then delivered to your Point of Interface (POI) via LIS or Type 2 trunks connected to the access tandem.
Example 2a: Qwest or Non-Qwest queried calls with LRN outside of local calling area
Example 2b - Non-Qwest non-queried calls with LRN outside of local calling area when ARLRN is not requested:
Embedded SLRN Network (not available for new routing requests)
Example 3a – Qwest SLRN routing with Local Tandem trunking when the NPA-NXX of the LRN is outside the local calling area:
Example 3b – Non-Qwest un-queried SLRN routing with Local Tandem trunking when the NPA-NXX of the LRN is outside the local calling area:
Example 3c – Qwest SLRN routing with Direct End Office Trunking (DEOT) when the NPA-NXX of the LRN is outside the local calling area:
To determine LNP availability, refer to Network Disclosure.
Design requirements are specified in Technical Publication Qwest Common Channel Signaling (CCS) Network Interface Specification - 77342.
If you are a new CLEC and are ready to do business with Qwest, view Getting Started as a Facility-Based CLEC or Getting Started as a Reseller. If you are an existing CLEC wishing to amend your Interconnection Agreement or New Customer Questionnaire, additional information is located in the Interconnection Agreement.
Pre-Ordering
Pre-Ordering section does not apply to ARLRN.
Field entry requirements are described in the Access Service Request (ASR) Forms.
Requests to order ARLRN in conjunction with ordering LIS or Type 2 trunk groups are submitted populating the following on the ASR:
If you have existing LIS or Type 2 trunks use the following process to order ARLRN:
General provisioning and installation activities are described in the Provisioning and Installation Overview.
General maintenance and repair activities are described in the Maintenance and Repair Overview.
Local Qwest 101 "Doing Business With Qwest"
View additional Qwest courses by clicking on Course Catalog.
Qwest contact information is located in Wholesale Customer Contacts.
This section is being compiled based on your feedback.
Last Update: February 28, 2008
