Local Service Ordering Practices - Windstream Business Wholesale

Local Service Ordering 

Practices 

January 2011 

Version 5.0 

Revision 5 

If you have any questions or comments regarding the following documentation, please contact the Local Service 

Provider Access Center at 870-743-7893.

Local Service Ordering Practice 

TABLE OF CONTENTS 

LOCAL SERVICE ORDERING PRACTICE 5.0..................................................................... 5 

1.0 GENERAL INFORMATION..............................................................................................................5 

1.1 Purpose......................................................................................................................................5 

1.2 Definition of Terms...................................................................................................................6 

1.3 Definition of Request Types......................................................................................................8 

1.4 Definition of Field Usage..........................................................................................................9 

1.5 Definition of Forms/Practices....................................................................................................9 

1.6 Ordering Process .....................................................................................................................11 

1.6.1 Pre-Order......................................................................................................................................................... 11 

1.6.2 Order................................................................................................................................................................ 11 

2.0 LOCAL SERVICE REQUEST (LSR)..............................................................................................12 

2.1 LSR Form................................................................................................................................12 

2.2 LSR Form Fields .....................................................................................................................13 

2.2.1 Administrative Section ..................................................................................................................................... 13 

2.2.2 Bill Section....................................................................................................................................................... 49 

2.2.3 Contact Section ................................................................................................................................................ 59 

2.2.4 Hunt Group Identification Section ................................................................................................................... 69 

2.2.5 Hunt Detail Section.......................................................................................................................................... 73 

2.3 LSR Alphanumeric Glossary...................................................................................................75 

3.0 END USER INFORMATION (EU)..................................................................................................83 

3.1 EU Form..................................................................................................................................83 

3.2 EU Form Fields .......................................................................................................................84 

3.2.1 Administrative Section ..................................................................................................................................... 84 

3.2.2 Location and Access......................................................................................................................................... 87 

3.2.3 Inside Wire....................................................................................................................................................... 99 

3.2.4 Bill Section..................................................................................................................................................... 101 

3.2.5 Disconnect Information.................................................................................................................................. 106 

3.3 EU Alphanumeric Glossary...................................................................................................111 

4.0 LOOP SERVICE (LS)..................................................................................................................119 

4.1 LS Form.................................................................................................................................119 

4.2 LS Form Fields......................................................................................................................120 

4.2.1 Administrative Section ................................................................................................................................... 120 

4.2.2 Service Details Section................................................................................................................................... 123 

4.3 LS Alpha Numeric Glossary .................................................................................................139 

5.0 NUMBER PORTABILITY (NP)....................................................................................................144 

5.1 NP Form ................................................................................................................................144 

5.2 NP Form Fields .....................................................................................................................145 



5.3 NP Alphanumeric Glossary..........................................................................................................162 

6.0 LOOP SERVICE WITH NUMBER PORTABILITY (LSNP)..........................................................167 

6.1 LSNP Form ...........................................................................................................................167 

6.2 LSNP Form Fields.................................................................................................................168 


Version 5.0 January 2011 

ii



6.3 LSNP Alphanumeric Glossary ..............................................................................................192 

7.0 RESALE SERVICE (RS)..............................................................................................................198 

7.1 RS Form ................................................................................................................................198 

7.2 Resale Form Fields................................................................................................................199 



7.3 RS Alphanumeric Glossary...................................................................................................230 

8.0 DID RESALE SERVICE (DRS)...................................................................................................237 

8.1 DID Resale Form...................................................................................................................237 

8.2 DRS Form Fields...................................................................................................................238 

8.2.1 DRS Administrative Section ........................................................................................................................... 238 

8.2.2 DRS Service Details Section .......................................................................................................................... 241 

8.3 DRS Alphanumeric Glossary ................................................................................................252 

9.0 CENTREX RESALE SERVICE .....................................................................................................289 

9.1Centrex Resale Form .....................................................................................................................289 

10.0 RESALE FRAME RELAY SERVICE ............................................................................................290 

10.1Resale Frame Relay Form ...........................................................................................................290 

11.0 RESALE PRIVATE LINE SERVICE .............................................................................................291 

11.1Resale Private Line Form ............................................................................................................291 

12.0 PORT SERVICE...........................................................................................................................292 

12.1Port Service Form........................................................................................................................292 

13.0 DIRECTORY SERVICE REQUEST (DSR) ...................................................................................293 

13.1 Directory Service Request Form ...........................................................................................293 

13.2 DSR Form Fields...................................................................................................................294 

13.2.1 Administrative Section............................................................................................................................... 294 

13.2.2 Bill Section................................................................................................................................................. 312 

13.2.3 Contact Section.......................................................................................................................................... 320 

13.2.4 Service Address Section............................................................................................................................. 324 

13.3 DSR Alphanumeric Glossary ................................................................................................333 

14.0 DIRECTORY LISTING (DL) .......................................................................................................341 

14.1 Directory Listing Form..........................................................................................................341 

14.2 DL Form Fields .....................................................................................................................342 


14.2.2 Listing Control Section.............................................................................................................................. 347 

14.2.3 Listing Indicators Section .......................................................................................................................... 355 

14.2.4 Listing Instruction Section......................................................................................................................... 360 

14.2.5 Caption/SLU Indent Section ...................................................................................................................... 376 

14.2.6 Delivery Address/Information Section....................................................................................................... 380 

14.2.7 Advertising Section .................................................................................................................................... 392 

14.3 DL Alphanumeric Glossary...................................................................................................396 

15.0 LOCAL RESPONSE (LR) ............................................................................................................411 

15.1 Local Response Form............................................................................................................411 

15.2 LR Form Fields .....................................................................................................................412 


15.2.2 Hunt Group Section ................................................................................................................................... 429 

15.2.3 DID Section ............................................................................................................................................... 431 

15.2.4 Circuit Detail Section ................................................................................................................................ 434 

15.2.5 SECLOC Section........................................................................................................................................ 448 


iii


15.2.6 Directory Section....................................................................................................................................... 452 

15.3 LR Alphanumeric Glossary...................................................................................................462 

16.0 LOCAL SERVICE RESPONSE COMPLETION (LSRCM)............................................................471 

16.1 Local Service Response Completion Form ...........................................................................471 

16.2 LSRCM Form Fields.............................................................................................................472 


16.3 LSRCM Alphanumeric Glossary ..........................................................................................480 


iv

Local Service Ordering Practice 5.0 

1.0 GENERAL INFORMATION 

1.1 Purpose 

The purpose of this document is to aid and to assist the LSP in inquiring and requesting bundled 

services from Windstream Communications. The information resident in this document is adapted 

from the Ordering and Billing Forum’s (OBF) Local Service Ordering Guideline (LSOG) version 5. 

This document is titled the Windstream Local Service Ordering Practice (LSOP) and further adapts the 

OBF standards to the processes and practices employed by Windstream. 

Windstream reserves the right to update or discontinue this document at any time based on future 

needs such as changing usage or field additions and deletions. 

Note: 

The ordering forms found in the Windstream LSOP must be submitted to the Windstream 

LSPAC (Local Service Provider Access Center) via Windstream Express, the electronic 

interface between Windstream and the Local Service Provider (LSP). If the LSP has any 

questions, please call the LSPAC at (870) 743-7893. 


5


1.2 Definition of Terms 

Bundle Services 

Services ordered from the Local Service Provider (LSP), which include business lines, residential 

lines, and auxiliary services. 

Completion Notification 

Completion Notification is issued by the Network Service Provider upon completion of a request 

from the Local Service Provider. 

Customer 

Any end user which requests the services offered by the LSP to provide local telecommunications 

services. 

Customer Service Information 

Describes the customer's billing information, which includes the customer's address, 

features/services, and equipment. The Customer Service Information may be obtained during the 

Pre-Order process. 

Direct Inward Dialing (DID) 

The process by which calls are routed to the number dialed over a dedicated facility (trunk group, 

etc.) to the LSP’s switch instead of using central office translations. 

Jeopardy 

When a due date is provided on the Local Response (LR) Form and the Network Service Provider 

(NSP) is unable to make the due date that order is placed in jeopardy. 

Local Response (LR) 

Local Response (LR) is provided by the Network Service Provider upon receipt and processing of 

the request from the Local Service Provider. 

Local Service Provider (LSP) 

Any company that provides local telecommunications services to end users. 

Network Service Provider (NSP) 

Any company that sells bundled or unbundled services to the LSP. 

Number Portability 

The ability of users of telecommunications services to retain, at the same location, existing 

telecommunications numbers without impairment of quality, reliability or inconvenience when 

switching from one telecommunications carrier to another. 

Port Out is defined for Location Number Portability as a ten-digit number leaving the control of an 

old Network Service Provider (NSP) switch. 

Port In is defined for Location Number Portability as a ten-digit number being added to a new 

Network Service Provider (NSP) switch. 

Port 

The connection from the line side of the main distribution frame to the digital switch including 

dial tone. 

Remote Call Forwarding 

Accomplished when Windstream redirects telephone calls to the switch of the LSP to give the 

appearance of number portability, i.e. Interim Number Portability. 


6


1.2 Definition of Terms (continued) 

Resale Services 

Bundled services sold by the network provider to the LSP to be resold to end users where the LSP 

and the network provider are different. 

Retail Services 

Bundled services where the service provider is the same as the network provider. 

Route Index 

The process of the LSP’s switching equipment forwarding the telephone number to the LSP’s 

nonremote call forward trunk group. 

Service Configuration 

Contains what the components of the existing service are; e.g., Resale vs. Facility Based. 

Traffic 

Traffic between competitive companies is broken into three possible categories: 

• Originating Traffic (OT) is one-way trunking that originates at the ILEC and terminates to the 

CLEC. 

• Terminating Traffic (TT) is one-way trunking that originates at the CLEC and terminates to 

the ILEC. 

• Two Way Traffic (OT/TT) is two-way trunking between the ILEC and the CLEC. 

Unbundled Services (UNE) 

Any separate service ordered by the LSP from Windstream such as local loop, switching port, etc. 

Unbundled Local Switching (Port) 

Provides access to the functions and capabilities of the local switch, including: 

• Line supervision 

• Dial tone 

• Ringing 

• Digit reception and interpretation 

• Network address (the local directory number) billing recording 

• The ability to pre-subscribe to primary carrier of InterLATA 

• IntraLATA toll region to region calls 

Wholesale Services 

Those services that Resellers can order from Windstream. 


7


1.3 Definition of Request Types 

Disclaimer: Availability of any service listed is subject to the terms negotiated in the 

interconnection agreement. 

Loop Service (LS) 

The request by the LSP to lease the local loop (two-way transmission path connecting the Main 

Distribution Frame end office to the NID at the end user’s premise location) of the Windstream. 

Loop Service is classified as Unbundled Network Elements. 

Loop Service with Number Portability (LSNP) 

The request by the LSP to lease the local loop of the Windstream and porting the end user’s 

telephone number to the LSP’s switch. 

Number Portability (NP) 

The request by the NSP to have the end user’s telephone number, currently resident in the switch 

of Windstream, ported and become resident in the switch of the NSP. 

Resale Service (RS) 

The request of the LSP to completely resell the service of Windstream (local loop, switching, 

transport, directory, etc.) at an agreed upon rate. 

Port Service (PS) 

The request of the LSP to lease a port in the switch of Windstream to provide local switching for 

the purpose of processing calls for the LSP on behalf of the end user. Port Service is classified as 

an Unbundled Network Element. 

Directory Listing (DL) 

The request of the LSP that Windstream provide directory listing service for the end user. 

Resale Private Line Service (RPL) 

The request of the LSP to completely resell private line service, currently provided by 

Windstream, to the end user at an agreed upon rate. 

Resale Frame Relay Service (RFR) 

The request of the LSP to completely resell frame relay service, currently provided by 

Windstream, to the end user at an agreed upon rate. 

DID Resale Service (DRS) 

The request of the LSP that Windstream resell direct inward dialing service, currently provided by 

Windstream to the end user at an agreed upon rate. 

Centrex Resale Service (CSR) 

The request of the LSP that Windstream resell Centrex service, currently provided by Windstream 

to the end user at an agreed upon rate. 


8


1.4 Definition of Field Usage 

Required (R) 

The field/form is required based upon request type and/or activity code. 

Optional (O) 

The field/form is optional based upon request type and/or activity code. 

Conditional (C) 

The field/form is required or prohibited based upon the population of other data field(s). 

Prohibited (P) 

The field/form is prohibited based upon request type and/or activity code. 

Validated (V) (SPSR only) 

The field, when populated, will be utilized to verify end user account identification as mandated 

by FCC 07-188. 

Not Required (N) 

The field/form is not required based upon request type and/or activity code. 

1.5 Definition of Forms/Practices 

Local Service Request (LSR) 

Prepared by the LSP and submitted to Windstream to request a service be provided as specified in 

the interconnection agreements/tariffs/contracts. 

End User (EU) 

Used to communicate to Windstream the location and access information of the end user and other 

details necessary to provide the service requested by the LSP. 

Loop Service (LS) 

Prepared by the LSP and forwarded to Windstream to provide information concerning leasing a 

local loop (LS) (i.e. facility assignments, cross-connect assignments, etc.). 

Loop Service with Number Portability (LS/NP) 

Prepared by the LSP and forwarded to Windstream to provide information concerning leasing a 

local loop (i.e. facility assignments, cross-connect assignments, etc.) and porting a telephone 

number (LS/NP). 

Number Portability (NP) 

Completed by the NSP to send to Windstream for notification of a request to port the end user’s 

working telephone number from Windstream’s switch to the switch of the NSP. Number 

Portability can be ordered from Windstream with or without an unbundled loop. 

Resale Service (RS) 

The action of the LSP purchasing Windstream’s services and reselling them to the end user. 

Port Service (PS) 

Completed by the LSP and sent to Windstream for the purpose of communicating information 

necessary to order local switching for the purpose of providing telephone service to the end user. 


9


1.5 Definition of Forms (continued) 

Resale Private Line (RPL) 

Completed by the LSP and submitted to Windstream for the purpose of reselling private line 

service to the end user. 

Resale Frame Relay (RFR) 

Prepared by the LSP and submitted to Windstream for the purpose of reselling frame relay service 

to the end user. 

Centrex Resale Services (CRS) 

Prepared by the LSP and submitted to Windstream for the purpose of reselling CENTREX 

Services to the end user. 

DID Resale Services (DRS) 

Prepared by the LSP and submitted to Windstream for the purpose of reselling DID Services to the 

end user. 

Local Response (LR) 

Prepared by Windstream and is sent to the LSP/NSP to confirm the services as ordered. This form 

is often referred to as the FOC (Firm Order Confirmation). 

Local Service Response/Completion (LSRCM) 

Prepared by Windstream and submitted to the LSP/NSP to confirm the requested services have 

been completed. The form also communicates information regarding possible critical dates and 

other pertinent information associated with the LSP/NSP's request for service. 

Directory Service Request (DSR) 

Prepared by the LSP/NSP for the purpose of ordering directory services from Windstream. 


Prepared by the LSP/NSP and submitted to Windstream for the purpose of directory listings and 

assistance for the LSP/NSP’s end user. 


10


1.6 Ordering Process 

1.6.1 Pre-Order 

Pre-order takes place prior to the ordering of service and it is the attempt by the LSP to 

ascertain the type of service (facility based, unbundled network elements, resale, etc.) that 

Windstream currently provides to the end user. This request may or may not include LSP 

service information such as toll restrictions and features. The pre-order process also 

allows an LSP to validate an end user's street address. Pre-Order is defined by the 

Ordering and Billing Forum (OBF) as optional. 

1.6.2 Order 

Order is the process of the LSP sending a firm request to Windstream for the purpose of 

assuming the role of providing local telephone service to the end user. Every order 

request is to include the Local Service Request (LSR) form, End User (EU) form, and the 

form for the service being request, i.e., Loop Service (LS), Resale Service (RS), etc. 

Upon receipt of the request, Windstream validates it responds by sending the LSP a Local 

Response (LR) also known as an FOC (Firm Order Confirmation) if the request is 

deemed valid. Otherwise the request is rejected. Once the service is put into place by 

Windstream, the LSP is sent a Local Service Response/Completion (LSRCM) form to 

communicate to the LSP that their service request has been completed. All forms 

mentioned above are approved OBF forms. 


11


2.0 LOCAL SERVICE REQUEST (LSR) 

2.1 LSR Form 

The Local Service Request (LSR) form is required to be submitted with every request, regardless 

of the request type. The LSR contains five sections: 

• Administration 

• Bill 

• Contact 

• Hunt Group Identification 

• Hunt Detail 

All information required for administrative, billing, and contact details are provided for in the 

various fields contained within the LSR Form. 

The Administrative Section contains information pertaining to the service being ordered such as: 

purchase order number, requisition type, desired due date, etc. Account Telephone Number (ATN) 

and Account Number (AN) are also included in the administrative section. 

The Bill Section provides billing name and address information. 

The Contact Section contains initiator information, design contact name, address and telephone 

number as well as implementation contact name and telephone number. 

The associated End User Information Form contains the Existing Account Telephone Number 

(EATN) and Existing Account Number (EAN) fields. 

This section of the Windstream LSOP contains the fields, a description of each field, usage of the 

fields, and what type of entry the field requires, such as alphanumeric. The form is prepared by 

the LSP and submitted to the Windstream LSPAC (Local Service Provider Access Center) in 

Harrison, AR. 

Disclaimer: Availability of any service listed is subject to the terms negotiated in the 

interconnection agreement. 


12


2.2 LSR Form Fields 

2.2.1 Administrative Section 

1. CCNA - Customer Carrier Name Abbreviation 

Identifies the COMMON LANGUAGE IAC code for the customer submitting the LSR and 

receiving the Local Response. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

The format and structure of this field is defined by ATIS in document 

0300251, Codes for Identification of Service Providers for Information 

Exchange or by COMMON LANGUAGE in BR 751-100-112. 

For an occasional customer who has not and probably will not obtain a 

CCNA, enter “CUS” in this field. 

An entry of “CUS” requires an entry in the CC field. 

VALID ENTRIES: 

• IAC Code 

NOTE 1: 

USAGE: 

Valid IAC codes are outlined within Telcordia Technologies practice BR 

751-100-112. 

This field is required. 

DATA CHARACTERISTICS: 

3 alpha characters 

EXAMPLE: Z Y X 

2. PON - Purchase Order Number 

Identifies the customer's unique purchase order or requisition number that authorizes the 

issuance of this request or supplement. 

USAGE: 



16 alphanumeric characters 

EXAMPLE: 

8 2 4 Z 9 


13


3. VER - Version Identification 

Identifies the customer’s version number. 

NOTE 1: 

Any reissuance must use this entry to uniquely identify the local service 

request from any other version. 


00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 

This field is conditional. 

Required when the SUP field is populated, otherwise optional. 

When the SUP field is populated, the data in this field must be incremented 

by 1 for each subsequent version. 

This field is automatically populated by Windstream Express. 



EXAMPLE: A A 

4. LSRNO - Local Service Request Number 

Identifies the number that may be generated by the provider's mechanized systems, preassigned 

to the customer by the provider or manually assigned by the provider to identify a 

customer's request for service. 

USAGE: 

NOTE 1: 


Automatically assigned on all LSRs submitted via Windstream Express, 

otherwise optional. 



EXAMPLE: 

3 1 2 3 4 5 6 7 8 9 0 1 


14


5. LOCQTY - Location Quantity 

Identifies the number of service locations for the service requested. 

USAGE: 

This field is optional. 


3 numeric characters 

EXAMPLES: 0 0 1 

9 9 9 

6. HTQTY - Hunt Group Quantity 

Identifies the quantity of hunt groups associated with this service request. 

USAGE: 

NOTE 1: 


Required when requesting one or more hunt groups for this service request, 

otherwise prohibited. 



EXAMPLE: 1 0 

7. AN - Account Number 

Identifies the main account number assigned by the NSP. 

NOTE 1: 

NOTE 2: 

Identifies an account number assigned by the current Network Service 

Provider that may or may not be dialable. 

This field may be validated for simple port service requests as mandated in 

FCC Order 07-188 


Account Number 

N = New Account Number requested 

USAGE: 

NOTE 1: 


Required when either the EAN field on the EU Form or the ATN field is 

not populated, or when a new AN is requested, otherwise optional. 



EXAMPLE: 

N 

A B C D 1 2 3 


15


8. ATN - Account Telephone Number 

Identifies the account telephone number assigned by the NSP. 

NOTE 1: 

If a number is used, it may or may not be the same as the working 

telephone number. 


Account Telephone Number 

N = New Account Telephone Number requested 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 


Required when the first position of the REQTYP field is “C”, the request is 

a non-simple port, and either the EATN field on the EU Form or the AN 

field is not populated. 

Required when the first position of the REQTYP field is not “C” and either 

the EATN field on the EU Form or the AN field is not populated. 

Otherwise optional. 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 

9. SC - Service Center 

Identifies the code used to represent the organization or location that processes a customer’s 

request for service. 

NOTE 1: 

NOTE 2: 

USAGE: 

The providers may supply guidelines for choosing the appropriate 

provider’s service center. 

Service center codes are maintained by Telcordia Technologies. 

This field is prohibited. 



EXAMPLE: P T 0 2 


16


10. PG_of_ - Page _ of _ 

Identifies the page number and total number of pages contained in this request. 

NOTE 1: 

USAGE: 

NOTE 1: 

This field is only used when preparing a manual request 


Required on manual requests, otherwise prohibited. 



EXAMPLE: PG 1 of 2 

11. RESID - Response Identifier 

Identifies the response number assigned by the provider to relate associated activity. 

USAGE: 




EXAMPLE: 

1 1 0 6 1 1 9 6 1 0 L 


17


12. D/TSENT - Date and Time Sent 

Identifies the date and time the transaction is sent. 


U.S. Standard 

Metric Format 

Two Digit Month (01-12) Two Digit Century (00-99) 

Two Digit Day (01-31) Two Digit Year (00-99) 

Two Digit Century (00-99) Two Digit Month (01-12) 

Two Digit Year (00-99) Two Digit Day (01-31) 

Two Digit Hour (01-12) Two Digit Hour (01-12) 

Two Digit Minute (00-59) Two Digit Minute (00-59) 

AM or PM 

AM or PM 

NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 

Windstream requires the use of the U.S. Standard format. 



This data is automatically captured and logged by Windstream Express. 


17 alphanumeric characters (including 3 hyphens) 

EXAMPLE: 

0 5 - 2 2 - 1 9 9 6 - 1 1 1 5 A M 

13. DSPTCH - Dispatch Required 

Indicates a dispatch is required. 


Y = Yes 

USAGE: 

NOTE 1: 


Optional when the ACT field is “N,” “C,” or “T,” and the DSIND field on 

the POINQ response is returned, otherwise prohibited. 


1 alpha character 

EXAMPLE: 

Y 


18


14. DDD - Desired Due Date 

Identifies the customer's desired due date. 

NOTE 1: 

NOTE 2: 

On disconnect requests, this date represents the date billing is to stop on the 

involved service and can be no earlier than the date the provider receives 

the request. 

A separate order request is required for each different Desired Due Date 

(DDD). 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 





EXAMPLE: 0 3 - 2 2 - 1 9 9 6 

15. APPTIME(DDD) - Appointment Time 

Identifies the time period during which the end user's service will be established and/or a 

technician is scheduled to visit the end user's premises. 


AM or PM 

USAGE: 




EXAMPLE: A M 


19


16. DDDO - Desired Due Date Out 

Identifies the customer’s desired due date for suspension or disconnection of service. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 



Required when the service is to be suspended and the DDD field is 

populated with a restoral date. 

Required for short-term service (e.g., trade shows) and the DDD field is 

populated with an install date. 

Required for dual service, or when the DDDO is different from the DDD 

for an outside move. 




EXAMPLE: 0 3 - 2 2 - 1 9 9 6 


20


17. NOR - Number of Requests 

Identifies this local service request and the total quantity of local service requests within a 

related group of orders being submitted. 

NOTE 1: 

NOTE 2: 

In order to facilitate the process, at least the first related LSR should 

describe or list the total RPONs used when RPON is not the same for all 

such requests. For example, six LSRs are to be associated and individual 

PONs and RPONs are being used. 

All locations and due dates must be identical for such grouping of like 

orders. 


1 st Two Positions (Denotes a specific number assigned by the customer) 

1-99 

2 nd Two Positions (Denotes the total number of related requests). 

2-99 

USAGE: 



5 alphanumeric characters (including a hyphen) 

EXAMPLE: 1 - 6 

18. APPTIME(DDDO) – Appointment Time 

Identifies the time period during which the end user’s service will be established and/or a 

technician is scheduled to visit the end user’s premises. 


AM or PM 

USAGE: 




EXAMPLE: A M 


21


19. DFDT - Desired Frame Due Time 

Identifies desired frame cutover time. 


Two Digit Hour (01-12)/Two Digit Minute (00-59)/ 

AM or PM 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

Indicates the window for cutover time when the CHC field is not populated. 

When the CHC field is populated, indicates the desired specific cutover 

time. 

The time will reflect the local time of the end user location(s). 


Prohibited when the first position of the REQTYP field is "G", "H" or "J", 




EXAMPLE: 1 0 1 5 P M 

20. PROJECT - Project Identification 

Identifies the project to which the request is to be associated. 

NOTE 1: 

NOTE 2: 

USAGE: 

Examples of the use of this field would be relating multiple service 

requests, previously negotiated orders, etc. 

The provider may initiate the project identification and provide this to the 

customer who will populate the field when submitting a service request. 




EXAMPLE: 

M S 7 3 6 1 1 9 


22


21. LSCP - Local Service Provider Change Prohibited 

Identifies that the end user has requested the option of prohibiting the change of their current 

service provider or removing the option. 

NOTE 1: 

NOTE 2: 

Invoking this option may require additional authorization or written 

permission. 

This field is used to freeze the entire account. 


A = Prohibit a change of current local service provider 

B = Remove the prohibition 

USAGE: 




EXAMPLE: 

A 

22. CHC - Coordinated Hot Cut 

Identifies that the customer is requesting near seamless cutover activity. 

NOTE 1: 

This field may require manual intervention and coordination between the 

provider/customer. 


Y = Yes 

NOTE 1: 

USAGE: 

An entry in this field requires a single time entry in the DFDT field. 




EXAMPLE: 

Y 


23


23. REQTYP - Requisition Type and Status 

Identifies the type of service being requested. 

NOTE 1: 

NOTE 2: 

The first character of REQTYP specifies the type of service. 

The second character of REQTYP specifies a firm order. 


1 st Character 

A = Loop 

B = Loop with Number Portability 

C = Number Portability 

E = Resale 

F = Unbundled Local Switching (Port) 

G = Directory Assistance 

H = Directory Listing 

J = Directory Listing and Assistance 

K = Resale Private Line 

L = Resale Frame Relay 

M = Port/Loop Service and Unbundled Local Switching 

N = DID Resale 

P = CENTREX Resale 

NOTE 1: 

NOTE 2: 

NOTE 3: 

When directory services are ordered in combination with valid entries of 

“A”, “B”, “C”, “E”, “F” and “M”, the AFO field should be used to identify 

the type of directory request(s). 

REQTYP "M" may drive either the Resale Form or the Loop with the 

Unbundled Local Switching (PORT) Forms. 

Valid entries of “G”, “H”, and “J” should only be used when requesting 

stand-alone directory service(s). 

2 nd Character 

A = Service Inquiry 

B = Firm Order 

USAGE: 

NOTE 1: 


This field may not be changed via a SUP. A new LSR must be generated. 



EXAMPLE: A B 


24


24. ACT - Activity 

Identifies the activity involved in this service request. 

NOTE 1: 

On a supplement to a request, this field carries the original activity type. 


N = New installation and/or account 

C = Change an existing account, e.g., rearrangement, partial disconnect or 

addition 

D = Disconnection 

M = Inside move of the physical termination within a building 

T = Outside move of end user location 

R = Record activity is for ordering administrative changes 

V = Conversion of service to new LSP 

W = Conversion as is 

S = Suspend 

B = Restore 

L = Seasonal suspension 

Y = Deny 

H = Short term suspension 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 

NOTE 6: 

USAGE: 

"T" is prohibited when the first position of the REQTYP field is "B" and 

the move is outside of the original serving wire center. 

"T" is prohibited when the first position of the REQTYP field is "C", "F", 

"G", "H" or "J". 

"M" is prohibited when the first position of the REQTYP field is "C", "F", 

"G", "H" or "J". 

An entry of "W", "B", "S", "L", "Y", or "H" is only allowed when the first 

position of the REQTYP field is "E" or "F". 

When the 2 nd position of the TOS field is “N”, the ACT field entry must be 

“N”, “C”, “D” or “V”. 

Windstream does not support the usage of entries “L”, “Y”, or “H”. 




EXAMPLE: 

N 


25


25. SUP - Supplement Type 

A supplement is any new iteration of an LSR. The entry in the SUP field identifies the reason 

for which the supplement is being issued. 


1 = Cancel - Indicates that the pending order is to be canceled in its entirety. 

NOTE 1: 

NOTE 2: 

If the pending order was already completed as ordered, a separate 

request must be sent instead of the supplement. 

Valid for service inquiries and firm orders whether or not they have 

been through the response phase. 

2 = New Desired Due Date - Indicates that the pending order requires only a 

change of desired due date. 

NOTE 1: 

Indicates the pending order requires a change of due date. The new 

date is specified in the DDD field. If the request is to establish a due 

date less than the standard interval, the EXP field must be populated. 

3 = Other - Any other change to the request. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 

This may affect the previously agreed upon due date. 

Partial cancellations should also be entered with a "3" in the SUP 

field. 

A request for a change in desired due date in conjunction with other 

changes to a pending order should be submitted with a "3" in the 

SUP field. If the request is to establish a due date less than the 

standard interval, the EXP field must be populated. 

This entry is also to be used for supplements that are a result of 

provider changes. 

Requires an entry in the REMARKS field to identify the changes. In 

addition to the changed fields, the remainder of the request must be 

identical to the original request issued. 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 


Prohibited on initial requests. 

Prohibited when changing a service inquiry to a firm order. 

Prohibited when changing service type, which results in a change to the 

first position of the REQTYP field. 

NOTE 4: Required when the LSR version is greater than 0. 


1 numeric character 

EXAMPLE: 3 


26


26. EXP - Expedite 

Indicates that expedited treatment is requested and any charges generated in provisioning this 

request (e.g., additional engineering charges or labor charges if applicable) will be accepted. 


Y = Expedite Charges Authorized 

USAGE: 




EXAMPLE: 

N 

27. AFO - Additional Forms 

Indicates which additional forms are being submitted with this request. 

Character Position 1 





= End User Information Form 

= Directory Assistance 

= Directory Listings 

= Directory Listings Assistance 

= Reserved for Future Use 

NOTE 1: 

The customer should populate the appropriate character position(s) to 

indicate which additional form(s) is attached. 


Character Position Valid Entry Attached Form(s) 

1 Y End User Information Form 

2 Y Directory Assistance 

3 Y Directory Listings 

4 Y Directory Listings/ Assistance 

5 N/A 

USAGE: 




EXAMPLE: 

Y 


27


28. RTR - Response Type Requested 

Identifies the type of local response requested by the customer. 


C = Confirmation 

E = Errors only 

F = Facility Confirmation 

H = Confirmation and Errors 

N = No response requested 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

NOTE 2: 

“F” is not valid for Directory Services only orders. 

“E” and “H” are only valid on orders, which include Directory Service 

Requests. 

Windstream supports only a valid entry of “C”. 


Required when the first position of the REQTYP field is “C” and the 

request is a non-simple port. 

Required when the first position of the REQTYP field is not “C”. 



EXAMPLE: 

N 

29. CC - Company Code 

Identifies the exchange carrier initiating the transaction. 

NOTE 1: 



Exchange. 


• Operating Company Identifier – A four alphanumeric character code, which 

identifies providers in the United States and certain U.S. territories, maintained by 

NECA. 

NOTE 1: 

USAGE: 

Valid Operating Company Identifiers are available from NECA. 




EXAMPLE: 1 2 A 3 


28


30. NNSP - New Network Service Provider Identification 

Identifies the Number Portability Administration Center (NPAC) Service Provider Identifier 

(SPID) of the new Network Service Provider (NSP). 

NOTE 1: 



Exchange. 


• Operating Company Identifier – A four alphanumeric character code, which 

identifies providers in the United States and certain U.S. territories, maintained 

by NECA. 

NOTE 1: 

USAGE: 

NOTE 1: 

Valid Operating Company Identifiers are available from NECA. 


Required when the first position of the REQTYP field is “C” and the ACT 

field is “V”, otherwise optional. 





29


31. ONSP - Old Network Service Provider Identification 

Identifies the NPAC SPI of the current Network Service Provider. 

NOTE 1: 

The format and structure of this field is defined by ANSI in document 

T1.251, Identification of Telecommunications Service Provider Codes for 

the North American Telecommunications System. 


• COMMON LANGUAGE EC Code - A four alpha character code, which 

identifies providers in North America, maintained by Telcordia Technologies. 

• COMMON LANGUAGE EC Code - A two alpha character code, which 

identifies the former Bell companies maintained by Telcordia Technologies. 

• Company Code - A four alphanumeric character code, which identifies providers 

in the United States and certain U.S. territories, maintained by NECA. 

NOTE 1: Valid EC codes are outlined in Telcordia Technologies practice BR 751- 

100-112. 

NOTE 2: 

USAGE: 

NOTE 1: 

Valid Company Codes are available from NECA. 


Required when the first position of the REQTYP field is “E,” “F,” “M,” 

“N,” or “P,” and the NPI field is “C” or “D,” otherwise optional. 




32. AENG - Additional Engineering 

Indicates that if additional engineering is required, an estimate of the charges is to be 

forwarded to the initiator of the request. 

NOTE 1: 

This should be populated for DS3 type requests. 


Y = Engineering Requested 

USAGE: 




EXAMPLE: 

Y 


30


33. ALBR - Additional Labor 

Indicates that additional labor is requested and charges will be accepted in conjunction with 

this Service Request, (e.g., Sunday or out of normal business hour installation is being 

requested). 


Y = Additional labor is authorized 

USAGE: 




EXAMPLE: 

Y 

34. SCA - Special Construction Authorization 

Indicates pre-authorization for special construction. 


Y = Special construction is authorized 

USAGE: 




EXAMPLE: 

Y 

35. AGAUTH - Agency Authorization Status 

Indicates that the customer is acting as an end user's agent and has authorization on file. 


Y = Authorization on file 

USAGE: 

NOTE 1: 


Required when the ACT field is “V” or “W”, otherwise optional. 



EXAMPLE: 

Y 


31


36. DATED - Date of Agency Authorization 

Identifies the date appearing on the agency authorization that was previously submitted to the 

provider. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 



Optional when the AGAUTH field is "Y", otherwise prohibited. 



EXAMPLE: 0 6 - 2 0 - 1 9 9 6 

37. AUTHNM - Authorization Name 

Identifies the end user who signed the authorization. 

USAGE: 




EXAMPLE: E N D U S E R N A M E 

38. PORTTYP - Port Type 

Identifies the type of unbundled port ordered from the provider. 


L = Line Port 

T = Trunk Port 

USAGE: 

NOTE 1: 


Required when the first position of the REQTYP field is “F” or “M” and 

the 2 nd position of the TOS field is not “M” or “N” or the 2 nd position of the 

LTOS field on the PS Form is not “M” or “N”, otherwise prohibited. 



EXAMPLE: 

T 


32


39. ACTL - Access Customer Terminal Location 

Identifies the CLLI code of the customer facility terminal location or designated collocation 

area. The CLLI code will have been previously assigned. 

NOTE 1: 


T1.253, Identification of Location Entities for the North American 

Telecommunications System. The Location Identifier consists of the 

following elements: 

1. Geographical Code - A code that designates a single geographical locality 

within a state, province, territory, country, or distinct region of the world. Valid 

entries are outlined in Telcordia Technologies practice BR 795-100-050 (4 

alphanumeric characters). 

2. Geopolitical Code - A code that designates a state or territory of the United 

States, a province or territory of Canada, another country having a national 

federal government, or a unique designation. Valid entries are outlined in 

Telcordia Technologies practice BR 795-100-100 (variable length, 1-6 


3. Network Site Code - A code designating a structure within a geographical 

location where there is a need to identify one or more telecommunications 

equipment entities. Valid entries are outlined in Telcordia Technologies’ 

repository (2 alpha or 2 numeric characters). 

4. Network Site Entity Code - A functional category of equipment or work center 

contained within a structure. Equipment categories are associated network sites 

for purposes of maintaining equipment inventories and for identifying facility and 

circuit terminations and nodal locations. Valid entries are outlined in Telcordia 

Technologies practice BR 795-100-100 (3 alphanumeric characters). 

USAGE: 

NOTE 1: 

NOTE 2: 


Prohibited when the first position of the REQTYP field is "E." 

Required when the first position of the REQTYP field is "A," "B," "F," & 

"M." 



EXAMPLES: M I L N T N M A W 0 1 

M I L N T N M A X M D 


33


40. AI - Additional Point of Termination Indicator 

Identifies whether the APOT field contains a CLLI code or a narrative. 


C = CLLI code 

N = Narrative 

USAGE: 

NOTE 1: 


Required when the APOT field is populated, otherwise prohibited. 



EXAMPLE: 

C 

41. APOT - Additional Point of Termination 

Further identifies the physical Access Customer Terminal Location (ACTL) point of 

termination. 

NOTE 1: 

NOTE 2: 

This field may be a CLLI code or any other format to identify a termination 

location within an ACTL. For example, the customer may pre-assign 

cross-connect information for its service-to-service order coordination. 

When this field contains a CLLI code, the format and structure is defined 

by ANSI in document T1.253, Identification of Location Entities for the 

North American Telecommunications System, and consists of the following 

elements: 


within a state, province, territory, country, or distinct region of the world. Valid 

entries are outlined in Telcordia Technologies practice BR 795-100-050 (4 









equipment entities. Valid entries are outlined in Telcordia Technologies’ 

repository (2 alpha or 2 numeric characters). 







34


41. APOT - Additional Point of Termination (continued) 

USAGE: 

NOTE 1: 


Required when the ACTL field does not identify the specific physical 

termination point of the service, otherwise optional. 



EXAMPLES: M I L N T N M A F X X 

B 1 7 - P 5 - J K 2 4 

NOTE 1: 

The above example could indicate Bay 17, Panel 5 and Jack 24 as the 

APOT. 

42. LST - Local Service Termination 

Identifies the CLLI code of the end office switch from which service is being requested. 

NOTE 1: 






within a state, province, territory, country, or distinct region of the world (e.g., 

municipality). Valid entries are outlined in Telcordia Technologies practice BR 

795-100-050 (4 alphanumeric characters). 







location where there is a need to identify one more telecommunications 

equipment entities, facility terminations, nodal locations, or administrative 

operations. Valid entries are outlined in Telcordia Technologies’ repository (2 

alpha or 2 numeric characters). 







35


42. LST - Local Service Termination (continued) 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 


Required when the first position of the REQTYP field is "F" or "M" and the 

2 nd position of the TOS field is not “M” or “N” or the 2 nd position of the 

LTOS field on the PS Form is not “M” or “N”. 

Required when the first position of the REQTYP field is "E" and the entry 

is different than the end user's local serving office. 




EXAMPLE: S N F C C A M C W 0 1 

43. LSO - Local Service Office 

Identifies the NPA/NXX of the local or alternate serving central office of the customer 

location or primary location of the end user. 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 


Required when the RTR field is "C" the ACT field is "N" or "T" and the 

first position of the REQTYP field is "E". 

Prohibited when the first position of the REQTYP field is "K". 




EXAMPLE: 2 0 1 8 8 5 


36


44. TOS - Type of Service 

Identifies the type of service. 

NOTE 1: 

The type of service identifies the end user account as business, residential 

or government. 


1 st Character (type) 

1 = Business 

2 = Residence 

3 = Government 

4 = Coin 

5 = Home Office 

2 nd Character (product) 

A = Multi-line 

B = Single Line 

C = Coin 

D = Advanced Services 

E = CENTREX Resale 

H = ISDN (BRI) 

J = PBX (trunk) 

K = ISDN (PRI) 

L = xDSL 

M = AIN Record Management 

N = LIDB Record Management Service 

- = Not Applicable 

3 rd Character (class) 

M = Measured Rate 

F = Flat Rate 

G = Message 


4 th Character (characterization) 

F = FXS (Foreign Exchange Service) 

G = Semi-public 

N = Normal 

P = Prison/Inmate 

R = RCF 

S = 800 Service 

W = WATS 


NOTE 1: 

The use of “4” in the first position and “C” in the second position are 

mutually exclusive. 


37


44. TOS - Type of Service (continued) 

USAGE: 

NOTE 1: 


Required when the ACT field is “N”, “C”, “T”, “V” or “W” and the first 

position of the REQTYP field is “E”, “F” or “M” and the LTOS on the 

service specific form is not populated, otherwise optional. 



EXAMPLE: 1 A F - 

45. SPEC - Service and Product Enhancement Code 

Identifies a specific product or service offering. 

NOTE 1: 

SPEC may be applicable for circuit level features and options other than 

those already identified by the Network Channel (NC) and Network 

Channel Interface (NCI) codes. 


Positions 1-7 = any alpha character except "I" or any numeric character 

except "0" 

NOTE 1: 

USAGE: 

Valid entries are based on provider tariffs/ practices. 


DATA CHARACTERISTICS: 5 alphanumeric characters minimum and 7 

alphanumeric characters maximum 

EXAMPLE: B D 1 T 5 A B 


38


46. NC - Network Channel Code 

Identifies the network channel code for the circuit(s) involved. The network channel code 

describes the channel being requested. 

NOTE 1: 


T1.223, Structure and Representation of Network Channel (NC) and 

Network Channel Interface (NCI) Codes for the North American 

Telecommunications System. The Network Channel Code consists of the 


1. Channel Service Code – Positions 1 and 2 describe the channel service code in 

an encoded form. The channel service code will typically be specified as the 

service code of the special service circuit or the transmission grade of the 

message trunk circuit. (2 alpha or 2 alphanumeric characters). 

2. Optional Feature Code – Positions 3 and 4 represent the option codes available 

for each channel service code. Standard combinations of this code will allow 

the customer to enhance the technical performance of the requested channel, or 

to further identify the type of service. It is also used to specify options such as 

conditioning, effective 4-wire, multiplexing, etc. (2 alpha or 2 alphanumeric 

characters). 

NOTE 2: 

Channel codes may be used in lieu of NC/NCI codes. 


NC Code 

NOTE 1: NC codes are outlined in Telcordia Technologies practice BR 795-403-100. 

USAGE: 




EXAMPLE: L C - A 


39


47. PBT - Pot Bay Type 

Identifies the type of collocation arrangement for this service request. 

NOTE 1: 

A Pot Bay is the physical demarcation point between a physical collocation 

arrangement and the ILEC’s equipment. 


A = Pot Bay is located in the common area - ILEC provides, installs, and 

maintains equipment. 

B = Pot Bay is located in the common area - Collocator provides equipment and 

ILEC installs and maintains equipment. 

C = Pot Bay is located inside the cage - CLEC provides, installs, and maintains 

equipment. 

USAGE: 

NOTE 1: 


Optional when the ACT field is “N,” “C,” or “D” and the customer’s ACTL 

is a physical collocation arrangement, otherwise prohibited. 



EXAMPLE: 

A 

48. NCI - Network Channel Interface Code 

Identifies the electrical conditions on the circuit at the ACTL/Primary Location. 

NOTE 1: 




Telecommunications System. The Network Channel Code consist of the 


1. Total Conductors - Positions 1 and 2 identify the total number of physical 

conductors (e.g., wires) required at the interface (2 numeric characters). 

2. Protocol - Positions 3 and 4 identify the requirements for the interface regarding 

signaling and transmission (2 alpha characters). 

3. Impedance - Position 5 identifies the nominal reference impedance that will 

terminate the channel for the purpose of evaluating transmission performance (1 

alphanumeric character). 

4. Delimiter #1 - Position 6 identifies the start of the protocol option field if a 

protocol option code is assigned. 

5. Protocol Options - Positions 7, 8 and 9 identify additional features (e.g., bit 

rate, bandwidth, etc.) on the protocol to be used (3 alphanumeric characters). 

6. Delimiter #2 - Position 10 identifies the start of Transmission Level Points 

(TLP) field if a TLP is assigned. 


40


48. NCI - Network Channel Interface Code (continued) 

7. Transmission Level - Positions 11 and 12 identify the TLPs from either the 

Exchange Carrier (EC)/service provider or customer end 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

Position 11 identifies the TLP transmit signal level at the EC/service 

provider when transmitting to the customer. 

Position 12 identifies the TLP receive signal level at the EC/service 

provider when receiving from the customer. 

If TLP is entered in one character position only (transmit or receive), 

a hyphen or the letter “O” is required as a field filler in the associated 

TLP character position. 

If TLPs are not to be coded, default levels found in Telcordia 

Technologies Technical Publications will apply and the TLP 

character positions will be left blank. 

NOTE 2: 

NOTE 3: 

This field must also be compatible with the NC on the request. 

If the protocol option field is not coded and the TLP is coded, a double 

delimiter #1 and #2 will be placed after character position five (5). In this 

case, delimiter #1 will be in character position six (6), and delimiter #2 will 

be in character position seven (7). The TLP will be left justified into 

character positions eight (8) and nine (9) accordingly. 


NCI Code 

NOTE 1: NCI codes are outlined in Telcordia Technologies practice BR 795-403- 

100. 

USAGE: 

NOTE 1: 


Required when the NC field is populated, otherwise prohibited. 

DATA CHARACTERISTICS: 5 alphanumeric characters minimum, 12 


EXAMPLES: 0 4 Q C 2 . . O O E 

NOTE 1: 

This example indicates a central office termination (closed end of 

station) loop start circuit. 

0 2 Q A 2 . 1 0 

NOTE 1: 

This example indicates service is multiplexed at the serving wire center, 

DSO local loop to end user. 


41


48. NCI - Network Channel Interface Code (continued) 

0 2 Q C 2 . O O D 

NOTE 1: 

This example indicates open end of loop start circuit at central office. 

0 2 L S 2 

NOTE 1: 

This example indicates closed end of local loop at end user location. 

0 4 Q B 2 . 0 0 

NOTE 1: 

This example indicates a MDF cross connect for resale. 

49. CHANNEL - Channel Code 

Identifies the type of channel associated with this request. 

NOTE 1: 

USAGE: 

Codes for channel identification may include USOCs or customer/provider 

negotiated codes. 




EXAMPLE: 2 0 0 1 


42


50. SECNCI - Secondary Network Channel Interface Code 

Identifies the electrical conditions on the circuit at the secondary ACTL or end user location. 

NOTE 1: 




Telecommunications System. The Network Channel Code consists of the 


1. Total Conductors - Positions 1 and 2 identify the total number of physical 

conductors (e.g., wires) required at the interface (2 numeric characters). 

2. Protocol - Positions 3 and 4 identify the requirements for the interface 

regarding signaling and transmission (2 alpha characters). 

3. Impedance - Position 5 identifies the nominal reference impedance that will 

terminate the channel for the purpose of evaluating transmission performance 

(1 alphanumeric character). 

4. Delimiter #1 - Position 6 identifies the start of the protocol option field if a 

protocol option code is assigned. 

5. Protocol Options - Positions 7, 8 and 9 identify additional features (e.g., bit 

rate, bandwidth, etc.) on the protocol to be used (3 alphanumeric characters). 

6. Delimiter #2 - Position 10 identifies the start of the Transmission Level Points 

(TLP) field if a TLP is assigned. 

7. Transmission level - Positions 11 and 12 identify the TLPs from either the 

Exchange Carrier (EC)/service provider or customer end. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

Position 11 identifies the TLP transmit signal level at the 

EC/service provider when transmitting to the customer. 

Position 12 identifies the TLP receive signal level at the 

EC/service provider when receiving from the customer. 

If TLP is entered in one character position only (transmit or 

receive), a hyphen or the letter “O” is required as a field filler in 

the associated TLP character position. 

If TLPs are not to be coded, default levels found in Telcordia 

Technologies Technical Publications will apply and the TLP 

character positions will be left blank. 

NOTE 2: 

NOTE 3: 

A CO CENTREX is considered to be an end user location. 

If the protocol option field is not coded and the TLP is coded, a double 

delimiter #1 and #2 will be placed after character position five (5). In this 

case, delimiter #1 will be in character position six (6), and delimiter #2 will 

be in character position seven (7). The TLP will be left justified into 

character positions eight (8) and nine (9) accordingly. 


43


50. SECNCI - Secondary Network Channel Interface Code (continued) 


NCI Code 

NOTE 1: NCI codes are outlined in Telcordia Technologies practice BR 795-403- 

100. 

USAGE: 


DATA CHARACTERISTICS: 5 alphanumeric characters minimum, 12 


EXAMPLES: 0 2 L 0 2 

NOTE 1: 

This example indicates an open end of a loop start circuit at end user 

location. 

0 2 L S 2 

NOTE 1: 

This example indicates a closed end of a loop start circuit at end user 

location. 

51. RPON - Related Purchase Order Number 

Identifies the PON of a related service request. 

NOTE 1: 

USAGE: 

The RPON field may be used for relating connect and disconnect service 

requests, or multiple requests for the same location due date. 




EXAMPLE: 

8 2 4 Z 9 


44


52. RORD - Related Order Number 

Identifies a related provider order number 

USAGE: 

NOTE 1: 


Required when the provider has preassigned a related order number, 




EXAMPLE: 

C 4 5 6 8 9 5 

53. LSPAUTH - Local Service Provider Authorization 

Indicates the carrier code of the Local Service Provider that is providing existing service and 

has authorized the change to a new service provider. 

NOTE 1: 









• Company Code - A four alphanumeric character code, which identifies provider 



100-112. 

NOTE 2: 

USAGE: 







45


54. LSPAUTH DATE - Local Service Provider Authorization Date 

Identifies the date that appears on the LSP authorization previously provided to the new 

service provider. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 



Required when the LSP AUTH field is populated, otherwise optional. 



EXAMPLE: 0 5 - 1 2 - 1 9 9 6 

55. LSPAUTHNAME - Local Service Provider Authorization Name 

Identifies the name of the person who signed the authorization letter. 

USAGE: 

NOTE 1: 


Required when the LSP AUTH field is populated, otherwise optional. 



EXAMPLE: J A N E S M I T H 

56. LSPAN - LSP’s Authorization Number 

Identifies the LSP’s authorization number. 

NOTE 1: 

USAGE: 

This authorization number may be passed to the New LSP by the OLD LSP 

as part of transition information prior to the New LSP issuing the LSR. 




EXAMPLE: 

W T 2 3 5 4 7 8 3 0 3 1 1 6 7 3 


46


57. CIC - Carrier Identification Code 

Identifies the numeric code of the initiating local service provider. 

NOTE 1: 

NOTE 2: 

USAGE: 

This code is identical to the CIC code specified on local interconnection 

trunks. 

This code is separate and distinct from the ACNA, CCNA and CC codes 





58. CUST - Customer Name 

Identifies the name of the customer who originated this request when that customer has not 

been assigned a CCNA. 

USAGE: 




EXAMPLE: 

J O H N J . S M I T H C O R P . 

59. NPDI - Number Portability Direction Indicator 

Identifies the direction of LNP conversion activity and the Enhanced (E) 9-1-1 data base 

record activity requirements for this request. 


A = Wireless to Wireless 

B = Wireless to Wireline 

C = Wireline to Wireless 

D = Wireline to Wireline 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 


Required when the first position of the REQTYP field is “B” or “C”. 

Optional when the ACT field is “N”, “C”, or “V” and the first position of the 

REQTYP field is “E”, “F”, “M” or “P”. 

Otherwise prohibited. 



EXAMPLE: 

A 


47


59a. PSWD_PIN – Customer Passcode/PIN 

Identifies the end user’s personal passcode/PIN. 

NOTE 1: 

NOTE 2: 

USAGE: 

This field may be used when the end user’s account has been password 

protected 

This field will be validated for simple port service requests as mandated in 

FCC Order 07-188 




EXAMPLE: B L U E S O C K 


48


2.2.2 Bill Section 

60. BI1 - Billing Account Number Identifier 1 

Identifies the service type of the Billing Account Number 1 (BAN 1). 


A = All services on this request 

C = Directory Assistance listings and directory listings 

D = Directory listings 

L = Loop 

M = Combined loop and unbundled local switching (port) 

N = Number Portability (NP) 

O = Directory Assistance listings 

P = Port 

R = Resale 

U = Usage 

V = Loop with NP and usage 

W = Loop with NP 

X = CENTREX resale 

Z = NP with usage 

USAGE: 

NOTE 1: 


Required when the BAN1 and BAN2 fields are populated, otherwise 

optional. 



EXAMPLE: 

L 


49


61. BAN1 - Billing Account Number 1 

Identifies the billing account to which the recurring and non-recurring charges for this request 

will be billed. 

NOTE 1: 

The BAN1 entry appearing on this form must be for the provider identified 

in the SC field. 


Valid Billing Account Number 

N = New Billing Account Number Requested 

E = Existing 

USAGE: 




EXAMPLES: 2 0 1 - 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 


Identifies the service type of the Billing Account Number 2 (BAN2). 





L = Loop 




P = Port 

R = Resale 

U = Usage 





USAGE: 

NOTE 1: 


Required when the BAN2 field is populated, otherwise optional. 



EXAMPLE: 

L 


50





NOTE 1: 






E = Existing 

USAGE: 

NOTE 1: 


Required when the BI2 field is populated, otherwise prohibited. 



EXAMPLES: 2 0 1 - 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 


51


64. ACNA - Access Customer Name Abbreviation 

Identifies the COMMON LANGUAGE code of the customer to which the bill is to be 

rendered. 

NOTE 1: 

NOTE 2: 



Exchange or by COMMON LANGUAGE in BR 751-100-112. 

For an occasional customer who has not and probably will not obtain an 

ACNA, enter "ZZZ" in this field. 


• IAC Code 

NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 

Valid IAC codes are maintained by Telcordia Technologies. 


Not required when the first position of the REQTYP field is “C” and the 

request is a simple port. 

Optional when the first position of the REQTYP field is “C”, the request is 

a non-simple port, and the NPT field on the NP Form is “D” 

Otherwise required. 



EXAMPLE: Z Z Z 

65. EBD - Effective Bill Date 

Identifies the effective date to begin or cease billing when the billing date is different from the 

desired due date. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 





EXAMPLE: 0 4 - 0 2 - 1 9 9 7 


52


66. CNO - Case Number 

Identifies the Case Number assigned by the Provider in response to a Diversity Inquiry 

Request. 

USAGE: 




EXAMPLE: B S 0 6 1 1 9 6 - 0 0 2 

67. NRI - Negotiated Rate Indicator 

Indicates that the Customer has negotiated special billing arrangements for this service. 


Y = Negotiated rates apply 

NOTE 1: 

USAGE: 

If not populated, the tariff rates for the services or elements ordered are 

applicable. 




EXAMPLE: 

Y 

68. BILLNM - Billing Name 

Identifies the name of the person, office or company to whom the customer has designated 

that the bill be sent. 

USAGE: 

NOTE 1: 


Required when the BAN (i.e. BAN1 or BAN2) field is "N", otherwise 

optional. 



EXAMPLE: 

X Y Z C O R P O R A T I O N 


53


69. SBILLNM - Secondary Bill Name 

Identifies the name of a department or group within the designated BILLNM entry. May also 

be used to specify the end user customer as identified in field entry "SAN", Subscriber 

Authorization Number used by the customer in conjunction with billing its customer. 

USAGE: 




EXAMPLE: 

A C C O U N T S R E C E I V A B L E 

70. TE - Tax Exemption 

Indicates that the customer has submitted a tax exemption form to the provider. 


Entry Exempt From 

F Federal 

S State/Province 

C County or Local 

M Municipal 

A F & S 

B F & C 

K F & M 

D F & S & C 

E F & S & M 

G F & S & C & M 

H S & C 

I S & M 

J C & M 

L Letter on File 

N Non Exempt 

P S & C & M 

USAGE: 

NOTE 1: 


Required when the BAN (i.e., BAN1 or BAN2) field is "N", otherwise 

optional. 



EXAMPLE: 

B 


54


71. EBP - Extended Billing Plan 

Identifies the request for establishing or removing installment billing of non-recurring charges 

that may be offered by a provider. 

USAGE: 




EXAMPLES: 

Y 

I B 4 

72. STREET(BILLNM) - Street Address 

Identifies the street of the billing address associated with the billing name. 

USAGE: 

NOTE 1: 


Required when the BAN (i.e., BAN1 or BAN2) field is "N", otherwise 

optional. 



EXAMPLE: 

1 2 5 E M A I N S T R E E T 

73. FLOOR(BILLNM) - Floor 

Identifies the floor. 

NOTE 1: 

USAGE: 

This instance of the FLOOR field is used for the billing address. 




EXAMPLE: 3 2 


55


74. ROOM/MAILSTOP(BILLNM) - Room/Mail Stop 

Identifies the room or mail stop. 

NOTE 1: 

USAGE: 

This instance of the MAIL/ROOM STOP field is used for the billing 

address. 




EXAMPLE: 1 K 1 5 1 A 

75. CITY(BILLNM) - City 

Identifies the city, village, township, etc. 

NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the CITY field is used for the billing address. 


Required when the BAN (i.e. BAN1 or BAN2) field is "N" and a billing 

profile is not established, otherwise optional. 



EXAMPLE: 

L 

I V I N G S T O N 

76. STATE(BILLNM) - State/Province 

Identifies the abbreviation for the state or province. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

This instance of the STATE field is used for the billing address. 

Recommended abbreviations are contained in the United States Postal 

Service Publication 28, Postal Addressing Standards. 


Required when the BAN (i.e., BAN1 or BAN2) field is "N" and a billing 




EXAMPLE: N J 


56


77. ZIP(BILLNM) - ZIP/Postal Code 

Identifies the Zip code, ZIP code + extension or postal code. 

NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the ZIP field is used for the billing address. 


Required when the BAN (i.e., BAN1 or BAN2) field is "N" and a billing 




EXAMPLES: 0 7 0 3 9 

0 8 8 5 4 - 1 2 3 5 6 4 

M 5 A 1 X 7 

78. BILLCON - Billing Contact 

Identifies the name of the person or office to be contacted on billing matters. 

USAGE: 

NOTE 1: 



optional. 



EXAMPLE: J A N E T D O E 

79. TELNO(BILLNM) - Telephone Number 

Identifies the telephone number of the billing contact. 

USAGE: 

NOTE 1: 



optional. 


17 numeric characters (including 3 hyphens) 

EXAMPLE: 

2 0 1 - 5 5 5 - 3 4 0 0 - 2 2 2 


57


80. VTA - Variable Term Agreement 

Identifies the duration, identifying USOC, contract date or contract identification number of 

any variable term agreement that may be offered by a provider. 

USAGE: 




EXAMPLES: 

3 6 

V T P P P 

0 8 2 0 8 9 

C 1 2 3 4 5 

3 6 1 0 9 1 4 8 9 B L K H 0 0 0 1 


58


2.2.3 Contact Section 

81. INIT - Initiator Identification 

Identifies the customer's representative who originated this request. 

NOTE 1: 

USAGE: 

NOTE 1: 

This is the person who should be contacted if there are any questions 

regarding this request. Any authorizations of charges or changes are the 

responsibility of this person. 


Prohibited when the first position of the REQTYP field on the LSR Form is 

“C” and the order is for a simple port, otherwise required. 



EXAMPLE: J O H N S M I T H 

82. TELNO(INIT) - Telephone Number 

Identifies the telephone number of the initiator. 

USAGE: 




EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 0 0 - 2 2 6 2 

83. EMAIL(INIT) - Electronic Mail Address 

Identifies the electronic mail address of the initiator. 

USAGE: 




EXAMPLE: 

Z J O N E S @ N O T E S . B E L L C O M P A N Y . 

C O M 


59


84. FAXNO(INIT) - Facsimile Number 

Identifies the fax number of the initiator. 

USAGE: 




EXAMPLE: 9 0 8 - 3 3 6 - 2 9 8 0 

85. STREET(INIT) - Street Address 

Identifies the street address. 

NOTE 1: 

USAGE: 

This instance of the STREET field is used for the initiator’s address. 




EXAMPLE: 

1 3 2 E M A I N S T R E E T 

86. FLOOR(INIT) - Floor 


NOTE 1: 

USAGE: 

This instance of the FLOOR field is used for the initiator’s address. 




EXAMPLE: 3 2 

87. ROOM/MAILSTOP(INIT) - Room/Mail Stop 


NOTE 1: 

USAGE: 

This instance of the ROOM/MAIL STOP field is used for the initiator’s 

address. 






60


88. CITY(INIT) - City 


NOTE 1: 

USAGE: 

This instance of the CITY field is used for the initiator’s address. 




EXAMPLE: 

P I S C A T A W A Y 

89. STATE(INIT) - State/Province 


NOTE 1: 

NOTE 2: 

USAGE: 

This instance of the STATE field is used for the initiator’s address. 






EXAMPLE: N J 

90. ZIP(INIT) - Zip/Postal Code 

Identifies the ZIP code, ZIP code + extension or postal code. 

NOTE 1: 

USAGE: 

This instance of the ZIP field is used for the initiator’s address. 





0 8 8 5 4 - 1 2 3 5 6 4 

M 5 A 1 X 7 


61


91. IMPCON - Implementation Contact 

Identifies the customer's representative or office responsible for control of installation and 

completion. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

During installation, this is the customer contact who will be informed by 

the provider's installer when the end user requires activity other than that 

ordered by the customer (i.e., wants the circuit terminated in a room other 

than designated on the order). 

To facilitate the ordering process, the identification of the company may be 

included with the representative's name as shown below in the example. 

This is the contact to be used for completions, acceptance testing and other 

such related installation activity unless otherwise specified by 

provider/customer negotiations. 




EXAMPLE: J O H N S M I T H S P C 

92. TELNO(IMPCON) - Telephone Number 

Identifies the telephone number of the implementation contact. 

USAGE: 

NOTE 1: 


Required when the IMPCON field is populated, otherwise prohibited. 



EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 0 0 - 3 5 8 7 

93. PAGER(IMPCON) - Pager Number 

Identifies the pager number of the implementation contact. 

USAGE: 




EXAMPLE: 

1 - 8 0 0 - 2 2 2 - 1 2 3 4 - 0 0 0 0 


62


94. ALTIMPCON - Alternate Implementation Contact 

Identifies the customer's alternative representative or office responsible for control of 

installation and completion. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

During installation, this is the customer's representative who will be 

informed by the provider's installer when the end user requires activity 

other than that ordered by the customer (i.e., wants the circuit terminated in 

a room other than designated on the order). 

To facilitate the ordering process, the identification of the company may be 

included with the representative's name as shown below in the example. 

This is the contact to be used for completions, acceptance testing and other 

such related installation activity unless otherwise specified by 

provider/customer negotiations. 




EXAMPLE: A N N J O N E S M F S 

95. TELNO(ALTIMPCON) - Telephone Number 

Identifies the telephone number of the alternate implementation contact. 

USAGE: 

NOTE 1: 


Required when the ALT IMPCON field is populated, otherwise prohibited. 



EXAMPLE: 

2 0 1 - 9 6 8 - 7 4 6 3 - 1 2 3 4 

96. PAGER(ALTIMPCON) - Pager Number 

Identifies the pager number of the alternative implementation contact. 

USAGE: 




EXAMPLE: 

1 - 8 0 0 - 2 2 2 - 1 2 3 4 - 0 0 0 0 


63


97. DSGCON - Design/Engineering Contact 

Identifies the representative of the customer or agent that should be contacted on 

design/engineering matters. 

NOTE 1: 

USAGE: 

If DSGCON represents a customer different from the CCNA, the Design 

Routing Code (DRC) field may be populated for proper DLR distribution. 





98. DRC - Design Routing Code 

Identifies the customer location routing code for the transmission of the Design Layout Report 

for this request. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The routing code represents the following information: 

- Company 

- Street 

- Floor 

- Room 

- City 

- State/Province 

- Zip/Postal Code 

When populated, this will be the first choice for routing the DLR. 

The codes are assigned by the provider. 




EXAMPLE: A N 3 

99. TELNO(DSG) - Telephone Number 

Identifies the telephone number of the design/engineering contact. 

USAGE: 

NOTE 1: 


Required when the DSGCON field is populated, otherwise prohibited. 



EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 0 0 - 3 5 8 7 


64


100. FAXNO(DSG) - Facsimile Number 

Identifies the fax number of the design/engineering contact. 

USAGE: 




EXAMPLE: 9 0 8 - 3 3 6 - 2 9 8 0 

101. EMAIL(DSG) - Electronic Mail Address 

Identifies the electronic mail address of the design/engineering contact. 

USAGE: 




EXAMPLE: 


C O M 

102. STREET(DSG) - Street Address 


NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the STREET field is used for the design/engineering 

contact’s address. 


Required when the DSGCON field is populated, otherwise optional. 



EXAMPLE: 

1 3 2 E M A I N S T R E E T 


65


103. FLOOR(DSG) - Floor 


NOTE 1: 

USAGE: 

This instance of the FLOOR field is used for the design/engineering 





EXAMPLE: 3 2 

104. ROOM/MAILSTOP(DSG) – Room/Mail Stop 


NOTE 1: 

USAGE: 

This instance of the ROOM/MAIL STOP field is used for the 

design/engineering contact’s address. 




EXAMPLE: K - 1 5 1 A 

105. CITY(DSG) - City 


NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the CITY field is used for the design/engineering contact’s 

address. 





EXAMPLE: 



66


106. STATE(DSG) - State/Province 


NOTE 1: 

NOTE 2: 

USAGE: 

This instance of the STATE field is used for the design/engineering 







EXAMPLE: N J 

107. ZIP(DSG) - ZIP/Postal Code 


NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the ZIP field is used for the design/engineering contact’s 

address. 






0 8 8 5 4 - 1 2 3 4 4 4 

M G 6 3 Y 7 


67


108. REMARKS - Remarks 

Identifies a free flowing field, which can be used to expand upon and clarify other data on this 

form. 

USAGE: 




EXAMPLE: 

D I S C O F F I R S T C K T I N G R O U 

P 


68


2.2.4 Hunt Group Identification Section 

109. LOCNUM - Location Number 

Identifies the service location number for the service requested. 

NOTE 1: 

USAGE: 

NOTE 1: 

The Location Number is assigned by the customer and is retained until the 

service is disconnected. 


Required when the LOCQTY field is greater than 1 and the HTQTY field is 

greater than zero, otherwise prohibited. 




9 9 9 

110. HNUM - Hunt Number 

Identifies the Hunt Group as a unique number and each additional occurrence as a unique 

number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

The HNUM is customer assigned and is returned on the Local Response to 

the ordering customer. 

Once HNUM is generated it cannot be changed and is retained through 

completion of the request. 

The values are to be assigned consecutively and must be unique throughout 

the request at the LOCNUM level. 


Required when the HTQTY field is populated, otherwise prohibited. 



EXAMPLE: 0 0 0 0 1 


69


111. CB - Common Block 

Identifies the name/number of the CENTREX and the name/number of the grouping 

(customer Common Block). 

NOTE 1: 

There can be only one Common Block per CENTREX Resale Service 

Form. 


Position 1 through 4 

Position 5 through 8 

= CENTREX Name/Number 

= Customer Common Block Name/ Number 

USAGE: 

NOTE 1: 


Required when the REQTYP field is “P” and the HA field is populated, 




EXAMPLE: M C I 2 T E L 1 

112. HA - Hunt Group Activity 

Identifies the activity associated with the hunt group on this request. 


N = New 

E = Existing/No Change 

C = Change to Hunt Group Sequence 

D = Remove Hunt Group Arrangement 

USAGE: 

NOTE 1: 


Required when the HTQTY field is populated, otherwise optional. 



EXAMPLE: 

N 


70


113. HID - Hunt Group Identifier 

Identifies the hunt group. 


Hunt Group Identifier 

N = New Hunt Group Identifier 

USAGE: 





114. TLP - Telephone Line Identifier Type 

Identifies the type of entry in the TLI field. 


T = Telephone Number 

L = LNUM (Line Number) 

B = ISDN BRI Directory Number 

USAGE: 




EXAMPLES: 

T 

B 

115. TLI - Telephone Line Identifier 

Identifies the pilot number of a Multi-line hunt group. 


Telephone Number 

USAGE: 

NOTE 1: 


Required when the TLP field is populated, otherwise optional. 



EXAMPLES: 9 0 8 - 2 3 3 - 6 1 2 3 

0 0 1 0 


71


116. HNTYP - Hunting Type Code 

Identifies the type of hunting involved. 

NOTE 1: 

These forms of hunting are generic types and are offered by the provider 

using various or different names for the hunt type categories. 


1 = Preferential 

2 = Sequential 

3 = Circular 

4 = Multi-line-series completion with terminal or maintenance numbers. 

USAGE: 

NOTE 1: 


Required when the HA field is populated, otherwise optional. 



EXAMPLE: 4 


72


2.2.5 Hunt Detail Section 

117. HLA - Line Hunt Group Activity 

Identifies the activity associated with the hunt group on this request. 


N = New/Install 

E = Existing/No Change 

D = Disconnect/Delete 

USAGE: 

NOTE 1: 


Required when the HTQTY field is populated, otherwise optional. 



EXAMPLE: 

N 

118. HTSEQ - Hunting Sequence 

Identifies the desired hunting sequence or range of hunt sequence. 

USAGE: 

NOTE 1: 


Required when the HLA field is populated, otherwise optional. 



EXAMPLES: 1 - 1 1 1 

(Ranges are indicated by using a hyphen.) 

1 0 


73


119. NOTYP - Number Type 

Identifies the type of number entered in the HT field. 



R = LNUM (Line Number) 

L = Terminal Number 

M = Maintenance Number 

B = ISDN BRI Directory Number 

USAGE: 

NOTE 1: 





EXAMPLE: 

T 

120. HT - Hunting Telephone Number 

Identifies the hunting number for this sequence in the Hunt Group. 



USAGE: 

NOTE 1: 





EXAMPLE: 

3 1 4 - 2 3 5 - 8 0 0 0 - 8 1 0 0 

(Ranges are indicated by using hyphens.) 


74


2.3 LSR Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the Local Service Request 

Form fields. 

LSR FORM 

Field Abbreviation Field # Field Name 

ACNA 64 Access Customer Name Abbreviation 

ACT 24 Activity 

ACTL 39 Access Customer Terminal Location 

AENG 32 Additional Engineering 

AFO 27 Additional Forms 

AGAUTH 35 Agency Authorization Status 

AI 40 Additional Point of Termination Indicator 

ALBR 33 Additional Labor 

ALTIMPCON 94 Alternate Implementation Contact 

AN 7 Account Number 

APOT 41 Additional Point of Termination 

APPTIME(DDD) 15 Appointment Time 

APPTIME(DDDO) 18 Appointment Time 

ATN 8 Account Telephone Number 

AUTHNM 37 Authorization Name 

BAN1 61 Billing Account Number 1 


BI1 60 Billing Account Number Identifier 1 


BILLCON 78 Billing Contact 

BILLNM 68 Billing Name 

CB 111 Common Block 

CC 29 Company Code 

CCNA 1 Customer Carrier Name Abbreviation 

CHANNEL 49 Channel Code 

CHC 22 Coordinated Hot Cut 

CIC 57 Carrier Identification Code 

CITY(BILLNM) 75 City 

CITY(DSG) 105 City 

CITY(INIT) 88 City 

CNO 66 Case Number 

CUST 58 Customer Name 

DATED 36 Date of Agency Authorization 

DDD 14 Desired Due Date 

DDDO 16 Desired Due Date Out 

DFDT 19 Desired Frame Due Time 

DRC 98 Design Routing Code 

DSGCON 97 Design/Engineering Contact 

DSPTCH 13 Dispatch Required 

D/TSENT 12 Date and Time Sent 


75


2.3 LSR Alphanumeric Glossary (continued) 

LSR FORM 


EBD 65 Effective Bill Date 

EBP 71 Extended Billing Plan 

EMAIL(DSG) 101 Electronic Mail Address 

EMAIL(INIT) 83 Electronic Mail Address 

EXP 26 Expedite 

FAXNO(DSG) 100 Facsimile Number 

FAXNO(INIT) 84 Facsimile Number 

FLOOR(BILLNM) 73 Floor 

FLOOR(DSG) 103 Floor 

FLOOR(INIT) 86 Floor 

HA 112 Hunt Group Activity 

HID 113 Hunt Group Identifier 

HLA 117 Line Hunt Group Activity 

HNTYP 116 Hunting Type Code 

HNUM 110 Hunt Number 

HT 120 Hunting Telephone Number 

HTQTY 6 Hunt Group Quantity 

HTSEQ 118 Hunting Sequence 

IMPCON 91 Implementation Contact 

INIT 81 Initiator Identification 

LOCNUM 109 Location Number 

LOCQTY 5 Location Quantitiy 

LSCP 21 Local Service Provider Change Prohbited 

LSO 43 Local Service Office 

LSPAUTH 53 Local Service Provider Authorization 

LSPAUTHDATE 54 Local Service Provider Authorization Date 

LSPAUTHNAME 55 Local Service Provider Authorization Name 

LSPAN 56 LSP’s Authorization Number 

LSRNO 4 Local Service Request Number 

LST 42 Local Service Termination 

NC 46 Network Channel Code 

NCI 48 Network Channel Interface Code 

NNSP 30 New Network Service Provider Identification 

NOR 17 Number of Requests 

NOTYP 119 Number Type 

NPDI 59 Number Portability Direction Indicator 

NRI 67 Negotiated Rate Indicator 

ONSP 31 Old Network Service Provider Identification 

PAGER 

96 Pager Number 

(ALTIMPCON) 

PAGER(IMPCON) 93 Pager Number 

PBT 47 Pot Bay Type 


76


2.3 LSR Alphanumeric Glossary (continued) 

LSR FORM 


PG_of_ 10 Page_of_ 

PON 2 Purchase Order Number 

PORTTYP 38 Port Type 

PROJECT 20 Project Identification 

PSWD_PIN 59a Password/PIN 

REMARKS 108 Remarks 

REQTYP 23 Requisition Type and Status 

RESID 11 Response Identifier 

ROOM/MAIL 74 Room/Mail Stop 

STOP(BILLNM) 


STOP (DSG) 


STOP (INIT) 

RORD 52 Related Order Number 

RPON 51 Related Purchase Order Number 

RTR 28 Response Type Requested 

SBILLNM 69 Secondary Bill Name 

SC 9 Service Center 

SCA 34 Special Construction Authorization 

SECNCI 50 Secondary Network Channel Interface Code 

SPEC 45 Service and Product Enhancement Code 

STATE(BILLNM) 76 State/Province 

STATE(DSG) 106 State/Province 

STATE(INIT) 89 State/Province 

STREET(BILLNM) 72 Street Address 

STREET(DSG) 102 Street Address 

STREET(INIT) 85 Street Address 

SUP 25 Supplement Type 

TE 70 Tax Exemption 

TELNO 

95 Telephone Number 

(ALTIMPCON) 

TELNO(BILLNM) 79 Telephone Number 

TELNO(DSG) 99 Telephone Number 

TELNO(IMPCON) 92 Telephone Number 

TELNO (INIT) 82 Telephone Number 

TLI 115 Telephone Line Identifier 

TLP 114 Telephone Line Identifier Type 

TOS 44 Type of Service 

VER 3 Version Identification 

VTA 80 Variable Term Agreement 

ZIP(BILLNM) 77 ZIP/Postal Code 

ZIP(DSG) 107 ZIP/Postal Code 

ZIP(INIT) 90 ZIP/Postal Code 


77

(Insert Your Company Logo) 

Administrative Section 

AN 

ATN 

7 8 

- - 

D/TSENT 

1 2 

NOR 

1 7 

ONSP 

3 1 

LST 

4 2 

- 

RPON 

5 1 

LSPAN 

5 6 

APPTIME 

1 8 

AENG 

32 

ALBR 

33 

SCA 

34 

LSO 

4 3 

CCNA 

1 

AGAUTH 

35 

PON 

2 

DSPTCH 

13 

RORD 

5 2 

CIC 

5 7 

DFDT 

1 9 

DATED 

3 6 

TOS 

4 4 

DDD 

1 4 

CUST 

5 8 

PROJECT 

2 0 

SPEC 

4 5 

Local Service Request 

AUTHNM 

3 7 

SC PG _of_ 

9 1 0 

APPTIME 

1 5 

VER 

3 

NC PBT 

4 6 47 

LSR N0 

4 

NCI 

4 8 

LSP AUTH 

5 3 

LSCP 

21 

RESID 

1 1 

DDDO 

1 6 

CHC 

22 

REQTYP 

2 3 

PORTTYP 

38 

LSP AUTH DATE 

5 4 

NPDI 

59 

ACT 

24 

ACTL 

3 9 

CHANNEL 

4 9 

SUP 

25 

LOCQTY 

5 

EXP 

26 

SECNCI 

5 0 

LSP AUTH NAME 

5 5 

AFO 

2 7 

HTQTY 

6 

AI 

40 

APOT 

4 1 

RTR 

28 

CC 

2 9 

NNSP 

3 0 

V5 

8/00 

Bill Section 

BILLNM 

6 8 

STREET 

7 2 

STATE 

7 6 

EMAIL 

ZIP 

7 7 

BILLCON 

SBILLNM 

6 9 

FLOOR 

ROOM/MAIL STOP 

7 3 7 4 

TEL NO 

7 8 7 9 

- - 

8 3 8 4 

- - 

STREET 

8 5 

ZIP 

9 0 

ALT IMPCON 

IMPCON 

9 4 9 5 

- - 

1 0 1 

STREET 

STATE 

1 0 6 

ZIP 

1 0 7 

REMARKS 

1 0 8 

BI1 

60 

Contact Section 

STATE 

8 9 

DSGCON 

9 7 

EMAIL 

BAN1 

6 1 

INIT 

FLOOR 

8 6 

TEL NO 

ROOM/MAILSTOP 

8 7 

9 1 9 2 

- - 

TEL NO 

BI2 

62 

- 

FLOOR 

BAN2 

6 3 

TEL NO 

8 1 8 2 

- - 

DRC 

TEL NO 

1 0 2 1 0 3 

PAGER 

9 6 

- 

FAX NO 

ACNA 

6 4 

9 8 9 9 - - - 

1 0 0 - - 


1 0 4 

- 

- 

EBD 

6 5 

CITY 

7 5 

CITY 

8 8 

CITY 

1 0 5 

TE 

70 

VTA 

8 0 

PAGER 

9 3 

EBP 

7 1 

CNO 

6 6 

FAX NO 

NRI 

67 

This Form may not be reproduced, distributed, or used without the express written permission of the Alliance for Telecommunications Industry Solutions. 

Permission may be obtained by contacting Mike Nichols, OBF Manager, c/o ATIS 1200 G Street NW, Suite 500, Washington, DC 20005. 

Telephone number: 202-434-8822; e-mail: mnichol@atis.org


Local Service Request Hunt Group Information 

V5 

8/00 


PON 

2 

VER 

3 

AN 

ATN 

7 8 

- - 

PG _of_ 

1 0 

Hunt Group 

Identification 

LOCNUM 

1 0 9 

HNUM 

1 1 0 

CB 

1 1 1 

HA 

112 

HID 

1 1 3 

TLP 

114 

TLI 

1 1 5 

HNTYP 

116 

Hunt Detail Section 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 

HLA 

117 

HTSEQ 

1 1 8 

NOTYP 

119 

HT 

1 2 0 






AN 

ATN 

D/TSENT 

DSPTCH DDD 

NOR 

- 

- - 

Local Service Request 

CCNA PON VER LSR N0 LOCQTY HTQTY 

APPTIME 

DFDT PROJECT 

SC PG _of_ RESID 

APPTIME 

DDDO 

LSCP CHC REQTYP ACT SUP EXP AFO RTR CC 

ONSP AENG ALBR SCA AGAUTH DATED 

AUTHNM 

PORTTYP ACTL AI APOT 

NNSP 

V5 

8/00 

LST LSO TOS SPEC NC PBT NCI CHANNEL SECNCI 

RPON 

RORD 

LSP AUTH LSP AUTH DATE LSP AUTH NAME 

LSPAN 

CIC 

CUST 

NPDI 

Bill Section 

BI1 BAN1 BI2 BAN2 ACNA EBD CNO 

BILLNM SBILLNM TE EBP 

NRI 

STREET FLOOR ROOM/MAIL STOP 

CITY 

STATE ZIP 

Contact Section 

EMAIL 

STREET 

INIT 

BILLCON 

FLOOR 

TEL NO 

- - 

TEL NO 

- - 

- 

ROOM/MAILSTOP 

- 

CITY 

VTA 

FAX NO 

- - 

STATE ZIP 

ALT IMPCON 

DSGCON 

EMAIL 

IMPCON 

TEL NO 

- - 

DRC 

TEL NO 

- - 

- 

TEL NO 

- - 

PAGER 

FAX NO 

- - - 

- 

PAGER 

STREET 

FLOOR 


CITY 

STATE ZIP 

REMARKS 





Local Service Request Hunt Group Information 

V5 

8/00 

Administrative Section PON VER AN ATN 

- - 

PG _of_ 

Hunt Group 

Identification 

Hunt Detail Section 

LOCNUM HNUM CB HA HID TLP 

HLA HTSEQ NOTYP HT HLA HTSEQ NOTYP HT 

TLI 

HNTYP 















+ 


3.0 END USER INFORMATION (EU) 

3.1 EU Form 

The End User (EU) Information form is required to be submitted with every request, regardless of 

the request type. The EU form contains five sections: 

• Administrative 

• Location and Access 

• Inside Wire 

• Billing 

• Disconnect Information 

The Administrative section is brief on this particular form and only summarizes key information 

from the LSR form for cross-reference from form to form. 

The Location and Access section provides specific information on the location of the end user as 

well As any LSP premise equipment and its location. 

The Inside Wire section indicates if an inside wire agreement is requested and the name and 

Telephone number for the billing questions. 

The Billing section provides all necessary billing account type information if the end user is to 

receive the bill for the requested service. 

The Disconnect Information section provides the telephone number(s) that are to be disconnected 

and any transfer options that would predominately apply to Interim Number Portability. 



the LSP and submitted to the Windstream LSPAC in Harrison, AR. 


83


3.2 EU Form Fields 



Identifies the customer's unique purchase-order or requisition number that authorizes the 


USAGE: 




EXAMPLE: 

8 2 4 Z 9 



NOTE 1: 

Any reissuance can use this entry to uniquely identify the form from any 

other version. 


00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 

NOTE 2: 


Required when the SUP field on the LSR Form is populated, otherwise 

optional. 

This field is automatically populated by Windstream Express. 



EXAMPLE: A A 


84




NOTE 1: 

The entry in this field must be identical to the AN field on the LSR Form. 



N = New Account Number 

USAGE: 

NOTE 1: 


This field is automatically populated by Windstream Express with the value 

entered on the LSR Form. 



EXAMPLE: 

N 



NOTE 1: 

NOTE 2: 

The entry in this field must be identical to the ATN field on the LSR Form. 






USAGE: 

NOTE 1: 


This field is automatically populated by Windstream Express with the value 

entered on the LSR Form 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


85


5. DQTY - Disconnect Quantity 

Identifies the quantity of telephone numbers affected by this service request. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

Indicates the quantity of telephone numbers to be disconnected with this 

request. 

Indicates the quantity of telephone numbers affecting call transfer 

information. 


Required when the DISC NBR field is populated, otherwise optional. 



EXAMPLE: 8 0 0 



USAGE: 

NOTE 1: 







86


3.2.2 Location and Access 


Identifies this service location number for the service requested. 

NOTE 1: 

USAGE: 

NOTE 1: 

The location number is assigned by the customer and is retained until the 




“C” and the request is for a simple port, otherwise required. 




9 9 9 

8. NAME - End User Name 

Identifies the name of the end user. 

NOTE 1: 

USAGE: 

NOTE 1: 

The name in this field is not intended to be used for directory services. 



“C” and the order is for a simple port, otherwise required. 



EXAMPLE: 

O L Y M P I C C O R P 


87


9. AFT – Address Format Type 

Identifies the format of the address being supplied. 

NOTE 1: 

This instance of the AFT field is used for the service address. 


A = Rural Route and/or Box Number 

B = Unnumbered 

C = Provider Assigned House Number 

D = Descriptive 

USAGE: 

NOTE 1: 

A value of "C" indicates a valid address where no house number 

exists; therefore, the provider has assigned an internal house number 

to facilitate provisioning. 




EXAMPLE: 

A 

10. SAPR - Service Address Number Prefix 

Identifies the prefix for the address number of the service address. 

USAGE: 




EXAMPLE: 2 5 W 

NOTE 1: 

Where 25W is the address number prefix for the following address 

example: 25W 450 1/2 SW Camino Ramon Lane NW, Floor 12, Wing 2, 

Suite 23A. 

11. SANO - Service Address Number 

Identifies the number of the service address. 

NOTE 1: 

USAGE: 

NOTE 1: 

This field may contain a provider assigned house number. 


Required when the AFT field is “C”, otherwise optional. 




NOTE 1: 

Where 450 is the address number for the following address example: 25W 

450 1/2 SW Camino Ramon Lane NW, Floor 12, Wing 2, Suite 23A. 


88


12. SASF - Service Address Number Suffix 

Identifies the suffix for the address number of the service address. 

USAGE: 

NOTE 1: 


Optional when the SANO field is populated otherwise prohibited. 



EXAMPLE: 1 / 2 

NOTE 1: 

Where 1/2 is the address number suffix for the following address example: 

25W 450 1/2 SW Camino Ramon Lane NW, Floor 12, Wing 2, Suite 23A. 

13. SASD - Service Address Street Directional Prefix 

Identifies the street directional prefix for the service address. 


N = North 

S = South 

E = East 

W = West 

NE = Northeast 

NW = Northwest 

SE = Southeast 

SW = Southwest 

USAGE: 




EXAMPLE: S W 

NOTE 1: 

Where SW is the street directional prefix for the following address 


Suite 23A. 


89


14. SASN - Service Address Street Name 

Identifies the street name of the service address. 

NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 

If no street name exists, this entry may be a rural route, general delivery or 

other description for this service location. 


Prohibited when the REQTYP on the LSR Form is “C” and the request is 

for a simple port. 

Optional when NPDI field on the LSR Form is populated with an “A” or 

“C", otherwise required. 



EXAMPLES: 

C a m i n o R a m o n 

NOTE 1: 

Where Camino Ramon is the address street name for the following address 


Suite 23A. 

O n e C i t y C e n t e r 

15. SATH - Service Address Street Type 

Identifies the thoroughfare portion of the street name of the service address. 

NOTE 1: 

USAGE: 


Service Publication 28, Postal Addressing Standards, Street Suffix 

Abbreviations Section. 




EXAMPLE: L N 

NOTE 1: 

Where LN is the address street name type for the following address 


Suite 23A. 


90


16. SASS - Service Address Street Directional Suffix 

Identifies the street directional suffix for the service address. 


N = North 

S = South 

E = East 

W = West 





USAGE: 




EXAMPLE: N W 

NOTE 1: 

Where NW is the street directional suffix for the following address 


Suite 23A. 

17. LD1 – Location Designator 1 

Identifies additional specific information related to the address (e.g., building, floor, room). 

NOTE 1: 

NOTE 2: 

USAGE: 

This instance of the LD1 field is used for the service address. 

Recommended abbreviations are contained in United States Postal Service 

Publication 28, Postal Addressing Standards, Secondary Unit Designators 

Section. 




EXAMPLE: F L 

NOTE 1: 

Where FL is the first location designator for the following address example: 

25W 450 1/2 SW Camino Ramon Lane NW, FL 12, Wing 2, Suite 23A. 


91


18. LV1 – Location Value 1 

Identifies the value associated with the first location designator of the address. 

NOTE 1: 

USAGE: 

This instance of the LV1 field is used for the service address. 




EXAMPLE: 1 2 

NOTE 1: 

Where 12 is the first location value for the following address example: 




NOTE 1: 

NOTE 2: 

USAGE: 




Section. 




EXAMPLE: W I N G 

NOTE 1: 

Where WING is the second location designator for the following address 


Suite 23A. 


Identifies the value associated with the second location designator of the address. 

NOTE 1: 

USAGE: 





EXAMPLE: 2 

NOTE 1: 

Where 2 is the second location value for the following address example: 



92




NOTE 1: 

NOTE 2: 

USAGE: 




Section. 




EXAMPLE: S U I T E 

NOTE 1: 

Where SUITE is the third location designator for the following address 


Suite 23A. 


Identifies the value associated with the third location designator of the address. 

NOTE 1: 

USAGE: 





EXAMPLE: 2 3 A 

NOTE 1: 

Where 23A is the third location value for the following address example: 



93


23. AAI – Additional Address Information 

Identifies additional location information about the address. 

NOTE 1: 

USAGE: 

This instance of the AAI field is used for the service address. 




EXAMPLE: 

T R A I L E R B E H I N D G A S S T A T I O 

N N E X T T O P O S T O F F I C E 

24. CITY - City 


NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 

This instance of the CITY field is used for the service address. 


Not required when the request is for a simple port. 


“C", otherwise required. 



EXAMPLE: 



94


25. STATE - State/Province 


NOTE 1: 

NOTE 2: 

USAGE: 

This instance of the STATE field is used for the service address. 






EXAMPLE: N J 

26. ZIP - ZIP/Postal Code 


NOTE 1: 

USAGE: 

This instance of the ZIP field is used for the service address. 





27. COUNTY - County 

Identifies the county. 

USAGE: 




EXAMPLE: J E F F E R S O N 

28. TEL NO - Telephone Number 

Identifies the telephone number of the local contact for the service location. 

USAGE: 




EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 8 7 - 


95


29. EUMI - End User Moving Indicator 

Indicates when the end user location is changing. 

NOTE 1: 

End user address information may be required to ensure the telephone 

number is eligible for portability. 


Y = End user is moving 

USAGE: 




EXAMPLE: 

Y 

30. ACC - Access Information 

Indicates the access instructions at the end user location. 

USAGE: 




EXAMPLE: 

A F T E R 

3 P M 

31. WSOP - Working Service on Premises 

Indicates if there is a working service at the end user location. 


A = Additional line request 

V = Validate status of existing service 

USAGE: 




EXAMPLE: 

A 


96


32. CPE MFR - Customer Premises Equipment Manufacturer 

Identifies the manufacturer of the CPE. 

USAGE: 




EXAMPLE: 

M O T O R O L A 

33. CPE MOD - Customer Premises Equipment Model Number 

Identifies the model number of the CPE. 

USAGE: 




EXAMPLE: 

B I T S U R F E R 

34. ERL - End User Retaining Listing 

Identifies the desire of the end user to have no changes made to their listings when changing 

Local Service Providers. 


Y = Retain end user listings for this account “as is” in both directory and/or 

directory assistance. 

N = Do not retain listings. 

USAGE: 

NOTE 1: 

NOTE 2: 


Not required if the request is for a simple port. 

Required when the ACT field on the LSR Form is “V”, otherwise 

prohibited. 



EXAMPLE: 

Y 


97


35. IBT - ISDN BRI Type 

Indicates the type of National ISDN BRI. 


1 = NI-1 

2 = NI-2 

3 = NI-3 

USAGE: 




EXAMPLE: 2 


98


3.2.3 Inside Wire 

36. IWO - Inside Wire Options 

Identifies the requirement for inside wire services. 


R = Referral for inside wiring (provider will negotiate with the end user) 

S = Provide inside wire repair plan and bill the customer 

T = Provide inside wire repair plan and bill the end user 

U = Provide inside wiring and repair plan and bill the customer 

V = Provide inside wiring and repair plan and bill the end user 

W = Provide inside wiring and bill the customer 

Y = Provide inside wiring and bill the end user 

USAGE: 




EXAMPLE: 

R 

37. IWBAN - Inside Wire Bill Account Number 

Identifies the billing account number for charges associated with inside wire. 


Billing Account Number 

E = Existing Customer Billing Account Number 


USAGE: 




EXAMPLE: 2 0 1 9 8 8 - 7 3 0 0 

38. IWCON - Inside Wire Contact 

Identifies the name of the person to be contacted for inside wire. 

USAGE: 

NOTE 1: 


Required when the IWO field is populated, otherwise optional. 



EXAMPLE: 

T O M 

J O N E S 


99


39. TEL NO - Inside Wire Contact Telephone Number 

Identifies the telephone number of the inside wire contact. 

USAGE: 

NOTE 1: 


Required when the IWCON field is populated, otherwise prohibited. 



EXAMPLE: 

2 0 1 - 9 8 8 - 7 6 2 3 - 1 0 1 2 


100



40. EAN - Existing Account Number 

Identifies the end user’s existing account number assigned by the current NSP. 

NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 






Required when the ACT field on the LSR Form is “V” or “W” and the 

EATN field is not populated, otherwise optional. 



EXAMPLE: 

2 0 1 M 8 1 - 3 5 8 2 

41. EATN - Existing Account Telephone Number 

Identifies the end user’s existing account telephone number. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

NOTE 2: 

The EATN as assigned by either the current LSP or NSP. 






Required when the ACT field on the LSR Form is “V” or “W” and the 

EAN field is not populated, otherwise optional. 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


101


42. FBI - Final Bill Information Indicator 

Indicates whether a final bill should be sent to either the existing billing address or a different 

address. 


D = Different 

E = Existing 

NOTE 1: 

USAGE: 

When the valid entry is “D”, the BILLNM, STREET, CITY, STATE and 

ZIP fields must be populated. 




EXAMPLE: 

D 

43. BILLNM - Bill Name 

Identifies the end user bill name. 

USAGE: 

NOTE 1: 


Required when the FBI field is "D", otherwise optional. 



EXAMPLE: 

A B C 

C O 

44. SBILLNM - Secondary Bill Name 

Identifies the name of a department or group within the designated BILLNM entry. 

NOTE 1: 

USAGE: 

May also be used to specify the end user as identified in the SAN field on 

the LSR Form, used by the customer in conjunction with billing its end 

user. 




EXAMPLE: 

A C C O U N T S R E C E I V A B L E 


102


45. STREET - Street Address 


NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the STREET field is used for the billing address. 


Required when the FBI field is "D", otherwise optional. 



EXAMPLE: 

1 2 5 E M A I N S T R E E T 

46. FLOOR - Floor 


NOTE 1: 

USAGE: 

This instance of the FLOOR field is used for the billing address. 




EXAMPLE: 3 2 

47. ROOM/MAIL STOP - Room/Mail Stop 

Identifies the room. 

NOTE 1: 

USAGE: 

This instance of the ROOM field is used for the billing address. 






103




NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the CITY field is used for the billing address. 



“C" otherwise required. 



EXAMPLE: 

L 

I V I N G S T O N 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

This instance of the STATE field is used for the billing address. 





“C” otherwise required. 



EXAMPLE: N J 



NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the ZIP field is used for the billing address. 



“C" otherwise required. 




0 8 8 5 4 - 1 2 3 4 3 4 

M 5 A 1 X 7 


104


51. BILLCON - Billing Contact 


USAGE: 

NOTE 1: 


Required when the FBI field is populated and/or this entry is different from 

the BILLNM field, otherwise optional. 



EXAMPLE: J A N E T D O E 



USAGE: 

NOTE 1: 


Required when the BILLCON field is populated, otherwise optional. 



EXAMPLE: 

2 0 1 - 5 5 5 - 3 4 0 0 - 2 2 2 

53. SSN - Social Security Number 

Identifies the social security number of the end user in the BILLNM field. 

USAGE: 




EXAMPLE: 9 9 9 - 9 9 - 9 9 9 9 


105


3.2.5 Disconnect Information 

54. DNUM - Disconnect Line Number 

Identifies the line as a unique number and each additional occurrence as a unique number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The DNUM is customer assigned and is returned on the Local Response to 


Once DNUM is generated it cannot be changed and is retained through 







EXAMPLE: 0 0 0 0 1 

55. DISC NBR - Disconnect Telephone Number 

Identifies the end user telephone number to be disconnected. 

USAGE: 




EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 

56. TER - Terminal Number 

Identifies a non-lead line in a multi-line hunt group. 

NOTE 1: 

USAGE: 

This entry may represent the maintenance number assigned to a member of 

a multi-line hunt group. 




EXAMPLES: 0 0 0 5 

7 1 8 - 1 0 0 0 


106


57. TC OPT - Transfer of Call Options 

Identifies the type of transfer of call option the end user has requested. 

NOTE 1: 

Where available, Windstream Intercept service is used. 


Custom Code Identifier 

N = None 

S = Standard 

USAGE: 




EXAMPLES: 

S 

T 

58. TC TO PRI - Transfer of Calls To Primary Number 

Identifies the telephone number to which calls are to be referred. 

USAGE: 

NOTE 1: 


Required when the TC OPT field is not blank or “N”, otherwise optional. 



EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 

59. TC TO SEC - Transfer of Calls To Secondary Number 

Identifies the secondary telephone number to which calls are to be referred. 

NOTE 1: 

Not Applicable to Windstream. 

60. TCID - Transfer of Calls To Identifier 

Identifies the sequence of telephone numbers and names associated with split transfer of calls. 

NOTE 1: 



107


61. TC NAME - Transfer of Calls To Name 

Identifies the name(s) associated with TC TO PRI and TC TO SEC fields to which calls are to 

be referred when split transfer of calls is requested. 

NOTE 1: 


62. TC PER - Transfer of Calls Period 

Indicates the requested date that the transfer of calls, specified in the TC TO PRI, is to be 

removed and the standard recorded announcement is to be provided. 

NOTE 1: 

When the standard period of transfer (provided by the provider) is 

acceptable, the field is to be left blank. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 



Optional when the TC TO PRI field is populated otherwise prohibited. 

DATA CHARACTERISTICS: 10 alphanumeric characters (including 2 

hyphens) 

EXAMPLE: 0 8 - 1 0 - 1 9 9 7 


108




form. 

USAGE: 




EXAMPLE: 

C U S T L I V E S 2 M I L E S W E S T 

O F P O L I C E S T A T I O N 

64. TCMI - Transfer of Call Message Indicator 

Associates the transfer of call message with the TCID of the telephone number for which the 

message is being requested. 

USAGE: 

NOTE 1: 


Prohibited when the TC OPT field is blank, “N” or contains a custom code 

identifier which is equivalent to none, otherwise optional. 




3 


109


65. TCMESS - Transfer of Calls Message 

Allows for a personalized message when requesting the transfer of calls option. 

NOTE 1: 

Not Applicable to Windstream 


110


3.3 EU Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the End User Information 

Form. 

EU FORM 


ACC 30 Access Information 

AFT 9 Address Format Type 



BILLCON 51 Billing Contact 

BILLNM 43 Bill Name 

CITY 

48 City 

(BILLNM) 

CITY (END 24 City 

USER) 

COUNTY 27 County 

CPE MFR 32 Customer Premises Equipment Manufacturer 

CPE MOD 33 Customer Premises Equipment Model Number 

DISC NBR 55 Disconnect Telephone Number 

DNUM 54 Disconnect Line Number 

DQTY 5 Disconnect Quantity 

EAN 40 Existing Account Number 

EATN 41 Existing Account Telephone Number 

ERL 34 End User Retaining Listing 

EUMI 29 End User Moving Indicator 

FBI 42 Final Bill Information Indicator 

FLOOR 

46 Floor 

(BILLNM) 

IBT 35 ISDN BRI Type 

IWBAN 37 Inside Wire Bill Account Number 

IWCON 38 Inside Wire Contact 

IWO 36 Inside Wire Options 

LD1 17 Location Designator 1 



LV1 18 Location Value 1 




NAME 8 End User Name 

PG_of_ 6 Page _ of _ 




111


3.3 EU Alphanumeric Glossary (continued) 

EU FORM 


SANO 11 Service Address Number 

SAPR 10 Service Address Number Prefix 

SASD 13 Service Address Street Directional Prefix 

SASF 12 Service Address Number Suffix 

SASN 14 Service Address Street Name 

SASS 16 Service Address Street Directional Suffix 

SATH 15 Service Address Street Type 

SBILLNM 44 Secondary Bill Name 

SSN 53 Social Security Number 

STATE 

49 State/Province 

(BILLNM) 

STATE (END 25 State/Province 

USER) 

STREET 

45 Street Address 

(BILLNM) 

TCID 60 Transfer of Calls To Identifier 

TCMESS 65 Transfer of Calls Message 

TCMI 64 Transfer of Call Message Indicator 

TC NAME 61 Transfer of Calls To Name 

TC OPT 57 Transfer of Call Options 

TC PER 62 Transfer of Calls Period 

TC TO PRI 58 Transfer of Calls To Primary Number 

TC TO SEC 59 Transfer of Calls To Secondary Number 

TEL NO 


(BILLCON) 

TEL NO 

39 Inside Wire Contact Telephone Number 

(IWCON) 

TEL NO 


(LCON) 

TER 56 Terminal Number 


WSOP 31 Working Service on Premises 

ZIP (BILLNM) 50 ZIP/Postal Code 

ZIP (END 

USER) 

26 ZIP/Postal Code 


112



End User Information 

V5 

8/00 

PON 

1 

VER AN 

3 

ATN 

2 4 

- - 

DQTY 

5 

PG_of_ 

6 

Location and Access 

LOCNUM 

7 

NAME 

8 

AFT 

9 

SAPR 

1 0 

SANO 

SASF 

1 1 1 2 

SASD 

1 

3 

SASN 

1 4 

SATH 

1 5 

SASS 

1 6 

LD1 

1 7 

LV1 

1 8 

LD2 

1 9 

LV2 

2 0 

LD3 

2 1 

LV3 

2 2 

AAI 

2 3 

CITY 

2 4 

STATE ZIP 

2 5 2 6 

LCON 

2 7 

TEL NO 

2 8 

ACC 

3 0 

- - 

ACC (continued) 

- 

EUMI 

29 

WSOP 

31 

CPE MFR 

3 2 

CPE MOD 

3 3 

ERL 

34 

IBT 

35 

Inside Wire 

IWO 

36 

IWBAN 

3 7 

IWCON 

TEL NO 

3 8 3 9 

- - 

- 

Bill Section 

EAN 

EATN 

4 0 4 1 

- - 

FBI 

42 

BILLNM 

4 3 

SBILLNM 

4 4 

STREET 

4 5 

FLOOR 

4 6 

ROOM 

4 7 

CITY 

4 8 

STATE 

4 9 

ZIP 

5 0 

BILLCON 

5 1 

TEL NO 

5 

SSN 

2 5 3 

- - - 

- - 






PON 

1 

Disconnect Information 

DNUM 

DISC NBR 

5 4 5 5 

- - 

TCID 

6 0 

TC NAME 

6 1 

End User Information (continued) 

VER AN 

ATN 

2 3 

4 

TER 

5 6 

TC OPT 

TC TO PRI 

- - 

TC TO SEC 

5 7 5 8 

- - 

5 9 

- - 

DQTY 

5 

PG_of_ 

6 

V5 

8/00 

TCID 

6 0 

TC NAME 

6 1 

TC PER 

6 2 

DNUM 

DISC NBR 

5 4 5 5 

- - 

TCID 

6 0 

TC NAME 

6 1 

TER 

5 6 

TC OPT 

TC TO PRI 

TC TO SEC 

5 7 5 8 

- - 

5 9 

- - 

TCID 

6 0 

TC NAME 

6 1 

TC PER 

6 2 

DNUM 

DISC NBR 

5 4 5 5 

- - 

TCID 

6 0 

TC NAME 

6 1 

TER 

5 6 

TC OPT 

TC TO PRI 

TC TO SEC 

5 7 5 8 

- - 

5 9 

- - 

TCID 

6 0 

TC NAME 

6 1 

TC PER 

6 2 

DNUM 

DISC NBR 

5 4 5 5 

- - 

TCID 

6 0 

TC NAME 

6 1 

TER 

5 6 

TC OPT 

TC TO PRI 

TC TO SEC 

5 7 5 8 

- - 

5 9 

- - 

TCID 

6 0 

TC NAME 

6 1 

TC PER 

6 2 

DNUM 

5 4 5 5 

- - 

TCID 

6 0 

TCID 

6 0 

TC NAME 

6 1 

TC NAME 

6 1 

REMARKS 

6 3 

DISC NBR 

TER 

5 6 

TC OPT 

TC TO PRI 

TC TO SEC 

5 7 5 8 

- - 

5 9 

- - 

TC PER 

6 2 






PON 

1 



VER AN 

ATN 

2 3 

4 

- - 

DQTY 

5 

PG_of_ 

6 

V5 

8/00 

TCMI 

6 4 

TCMESS 

6 5 






End User Information 

V5 

8/00 

PON 

VER 

AN 

ATN 

- - 

DQTY 

PG_of_ 

Location and Access 

LOCNUM 

NAME 

AFT SAPR 

SANO 

SASF 

SASD 

SASN 

SATH 

SASS 

LD1 LV1 LD2 LV2 LD3 LV3 

AAI 

CITY 

STATE 

ZIP 

LCON 

TEL NO 

- - 

ACC 

- 

EUMI 

ACC (continued) 

WSOP CPE MFR CPE MOD ERL IBT 

Inside Wire IWO IWBAN IWCON 

Bill Section 

TEL NO 

- - 

- 

EAN 

EATN FBI BILLNM 

- - 

SBILLNM 

STREET 

FLOOR 

ROOM 

CITY STATE ZIP 

BILLCON 

TEL NO 

- - 

SSN 

- - - 






PON 


DNUM 

TCID 

TC NAME 

VER 

DISC NBR TER TC OPT 

- - 

AN 


TC TO PRI 

- - 

ATN 

- - 

TC TO SEC 

- - 

DQTY 

PG_of_ 

V5 

8/00 

TCID 

TC NAME 

TC PER 

DNUM 

TCID 

TC NAME 


- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TC PER 

DNUM 

TCID 

TC NAME 


- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TC PER 

DNUM 

TCID 

TC NAME 


- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TC PER 

DNUM 

TCID 

TC NAME 


- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TC PER 

REMARKS 







V5 

8/00 

PON 

VER 

AN 

ATN 

- - 

DQTY 

PG_of_ 


TCMI 

TCMESS 





4.0 LOOP SERVICE (LS) 

4.1 LS Form 

The LS Form must always be associated with LSR and EU Forms, which contain administrative 

and bill detail necessary for the provisioning of this request. 

The Loop Service Form is required when the LSP is requesting to utilize a portion of 

Windstream’s current network facilities, i.e. UNE Local Loop, in order to deliver the end user 

with their own dial tone and feature services. The LS form contains two sections: 

• Administrative Section 

• Service Details Section 



The Service Details provides all the necessary facility detail to complete the provisioning of the 

telephone service for the LSP on behalf of the end user. 




It is recognized that there may be fields in the Administrative Section of this practice that are based 

on LSR Activity (ACT) values. For documentation purposes the usage strips in this practice reflect 

only the applicable line level activities (LNAs) for Loop Service. The applicable LNAs are as 

follows: 


C = Change an existing account, e.g., rearrangement, partial disconnect or addition 







119


4.2 LS Form Fields 





USAGE: 




EXAMPLE: 

8 2 4 Z 9 



NOTE 1: 




00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 



optional. 



EXAMPLE: A A 


120




NOTE 1: 

NOTE 2: 

Identifies a non-standard account number. 

Identifies an account number that is not a dialable number. 




USAGE: 

NOTE 1: 






EXAMPLES: 

N 

A B 3 2 2 1 4 7 



NOTE 1: 




ATN 

N = New ATN requested 

USAGE: 

NOTE 1: 


Required when either the EATN field on the EU Form or the AN field is 

not populated, or when a new ATN is requested, otherwise optional. 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


121


5. LQTY - Loop Quantity 

Identifies the quantity of loops involved in this service request. 

USAGE: 







USAGE: 






122


4.2.2 Service Details Section 


Identifies the service location number for the service requested 

NOTE 1: 

USAGE: 

The Location Number is assigned by the Customer and is retained until the 






9 9 9 

8. LNUM - Line Number 

Identifies the line as a unique number and each additional occurrence as a unique number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The LNUM is customer assigned and is returned on the Local Response to 


Once LNUM is generated it cannot be changed and is retained through 







EXAMPLE: 0 0 0 0 1 


123


9. LNA - Line Activity 

Identifies the activity involved at the line level. 




addition 






USAGE: 




EXAMPLE: 

N 

10. CKR - Customer Circuit Reference 

Identifies the circuit number assigned by the customer. 

NOTE 1: 

USAGE: 

CKR is used by the customer as a cross reference to the provider circuit ID 

and in many cases to identify the customer’s end-to-end service. 




EXAMPLES: 

L 0 0 0 2 

2 9 3 3 2 1 8 1 


124


11. TSP - Telecommunication Service Priority 

Indicates the provisioning and restoration priority as defined under the TSP Service Vendor 

Handbook. 

NOTE 1: 

These codes are assigned by the TSP Program Office. 


Nine Character TSP Control Identifier 

One Character Provisioning Priority Level (E, 0-5) 

One Digit Restoration Priority Level (0-5) 

NOTE 1: 

USAGE: 

A TSP code ending in “00” indicates “revocation”, the removal of a 

previously assigned TSP code. 



hyphen) 

EXAMPLE: T S P 1 2 3 4 5 C - E 1 

12. SAN - Subscriber Authorization Number 

Identifies a number equivalent to the end user Purchase Order Number. 

NOTE 1: 

USAGE: 

This may, at the option of the customer, be a requirement when providing 

service to some governmental agencies. 




EXAMPLE: 

A B 1 2 3 4 5 6 7 8 


125


13. ECCKT - Exchange Company Circuit ID 

Identifies a provider’s circuit identification. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 

The format of the field is defined by the provider. 

All components within the ID should be delimited by either virgules or 

periods. 

The layout of the field may be defined by the COMMON LANGUAGE 

standards. 

When a component of CLT, CLS and CLF is purposely omitted, the 

component should still be delimited and compressed to eliminate any 

spaces. 

If all positions in a component of CLT, CLS and CLF are not populated, 

the component should be compressed to eliminate any spaces. 


TELEPHONE NUMBER FORMAT: 

Prefix/Service Code and Modifier/NPA/NXX/XXXX/Terminal Number (if applicable) 

This format may be up to 30 characters in length. 

EXAMPLES: 

A2/SBFS/201/981/3500 

//800/123/4567 

SERIAL NUMBER FORMAT: 

Prefix/Service Code and Modifier/Serial Number/Suffix Code/AP Code/segment name (if 

applicable) 


EXAMPLE: 

A2/LBFS/032719/001/NY 

FACILITY ID FORMAT: 

Facility Designation/Facility Type/office A location/office Z location 


EXAMPLE: 

USAGE: 

NOTE 1: 

101/T1/NYCMNY50/NYCMNY54W01 


Required when the LNA field on the LS Form is “C”, “D”, “M” , “T” or 

“R”, otherwise optional. 




126


14. CFA - Connecting Facility Assignment 

Identifies the provider carrier system and channel to be used. 

NOTE 1: 


T1.238, Identification of Telecommunication Facilities for the North 

American Telecommunications System. The Facility Identifier consists of 

the following elements: 

1. Facility Designation – A code that, for a specific type of facility, uniquely 

identifies a path between two network nodes (variable length, 1-5 


2. Facility Type – A code that describes a type of facility when it is other than 

a single baseband channel on cable. Valid entries are outlined in Telcordia 

Technologies practice BR-795-450-100 (variable length, 1-6 alphanumeric 

characters). 

3. Channel/Pair/Time Slot – A code that identifies a specific assignable 

portion of a facility (variable length, 1-5 alphanumeric characters). 

4. Location A – A standardized code that uniquely identifies the location of 

facility terminal A, which has the lower in alphanumeric sequence of the two 

facility location codes. Valid values are outlined in Telcordia Technologies 

practice BR-795-100-100 (8 or 11 alphanumeric characters). 

5. Location Z – A standardized code that uniquely identifies the location of 

facility terminal Z, which has the higher in alphanumeric sequence of the 

two facility location codes. Valid values are outlined in Telcordia 

Technologies practice BR-795-100-100 (8 or 11 alphanumeric characters). 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 

USAGE: 

Either virgules (/) or periods (.) are used consistently as delimiters to 

separate all elements of the CFA. 

All element entries of the CFA are left justified with no trailing spaces. 

When multiple levels of CFA are being provided, the highest level of CFA 

is populated in the CFA field and the lower level CFA is populated in the 

SCFA field. 

Applicable when utilizing Hi-Cap facilities and the customer has 

assignment control. 




EXAMPLES: 

1 0 1 / T 1 / 3 / B S T N M A G T C G O / B S T N 

M A M T C G O 

1 0 1 . T 1 . 3 . B S T N M A G T C G O . B S T N 

M A M T C G O 


127


15. CCEA – Cross Connect Equipment Assignment 

Identifies the physical point of termination at a collocation cage. 

NOTE 1: 

NOTE 2: 

USAGE: 

This information is provided by the customer when they have assignment 

control. 

When the CCEA field is populated, the information will identify the tiedown 

assignment at the ACTL. 




EXAMPLE: 

A B C / 0 1 / 2 4 - N L / 1 2 0 8 - 1 2 1 0 / O K 

L D C A 0 3 / O K L D C A 0 3 

16. SYSTEM ID - System Identification 

Identifies the customer's system to be used in a collocation arrangement. 

NOTE 1: 

USAGE: 

Applicable when the customer has assignment control in a collocation 

arrangement. 




EXAMPLE: A A 

17. CABLE ID - Cable Identification 

Identifies the provider's central office cable to be connected to the customer's collocated 

equipment 

NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: X X X 0 1 


128


18. SHELF - Shelf 

Identifies the number assigned to the customer's shelf to be used in a collocation arrangement. 

NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 2 0 

19. SLOT - Slot 

Identifies the customer's specific connection slot to be used in a collocation arrangement. 

NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 0 7 

20. RELAY RACK – Relay Rack 

A code that identifies the customer's bay/cabinet in a collocation arrangement and may also 

include the floor and aisle where the specific piece of equipment is located. 

NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 1 0 0 0 5 2 - 0 3 


129


21. CHAN/PAIR - Channel/Pair 

Identifies the specific channel or pair within the provider's cable to be used for connection. 

NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 2 4 

22. UNIT – Unit 

Identifies the number assigned to a panel, shelf or case within the customer’s bay/cabinet 

indicated in the RELAY RACK field. 

USAGE: 

NOTE 1: 


Required when the customer has assignment control in a collocation 

arrangement, otherwise optional. 



EXAMPLES: 2 4 

2 4 - 4 8 

23. JK CODE - Jack Code 

Indicates the standard code for the particular registered or non-registered jack used to 

terminate the service. 

NOTE 1: 

USAGE: 

NOTE 1: 

Familiarization with the FCC's registration rules is requisite for all parties 

involved for the determination of the proper jack code for a given registered 

service. Registered jacks used to terminate category 1 and 3 services begin 

with the designation "RJ". 


Required when the JR field is populated, otherwise prohibited. 



EXAMPLE: R J 2 1 X 


130


24. JK NUM - Jack Number 

Identifies the number of the jack used on end user connections. 

NOTE 1: 

USAGE: 

NOTE 1: 

When the jack identification is unknown, enter 99 in this field. 


Required when the JK CODE field is populated, otherwise optional. 



EXAMPLE: B 2 

25. JK POS - Jack Position 

Identifies the position in the jack that a particular service will occupy. 

NOTE 1: 

USAGE: 

NOTE 1: 

When the jack position is unknown, enter 99 in this field to specify next 

available position. 





EXAMPLE: 9 9 

26. JR - Jack Request 

Indicates a request for a new jack. 


Y = YES 

USAGE: 

NOTE 1: 


Optional when the LNA is “N”, “C”, “M”, “T” or “V”, otherwise 

prohibited. 



EXAMPLE: 

Y 


131


27. NIDR - NID Request 

Indicates a request for a new network interface device (NID). 


Y = Yes 

USAGE: 




EXAMPLE: 

Y 

28. IWJK - Inside Wire Jack Code 

Indicates the standard code for the type of jack requested for inside wiring. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 





When multiple lines are terminating in one multi-line jack, the IWJK and 

IWJQ fields should only be populated for the first line. Jacks may be 

ordered on a line by line basis. 


Required when the IWJQ field is populated, otherwise prohibited. 




29. IWJQ - Inside Wire Jack Quantity 

Indicates the number of jacks requested for inside wiring. 

NOTE 1: 





01-99 

USAGE: 

NOTE 1: 





EXAMPLE: 0 1 


132




NOTE 1: 

USAGE: 

An entry in this field requests the disconnection of the telephone number of 

the associated bundled service. 




EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 

31. TER - Terminal Number 

Identifies a non-lead line in a multi-line hunt group. 

NOTE 1: 

USAGE: 

This entry may represent the maintenance number assigned to a member of 

a multi-line hunt group. 





7 1 8 - 1 0 0 0 





N = None 

S = Standard 

USAGE: 




EXAMPLES: 

S 

T 


133




USAGE: 

NOTE 1: 


Required when the TC OPT field is “S” or a custom code identifier, 




EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 



USAGE: 

NOTE 1: 


Windstream does not support this service. 



USAGE: 

NOTE 1: 




Identifies the name(s) associated with TC TO PRI and TC TO SEC fields to which calls are 

referred when split transfer of calls is requested. 

USAGE: 

NOTE 1: 




134



Indicates the requested date that the transfer of calls, specified in the TC TO PRI field, is to be 


NOTE 1: 




U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 



Optional when the TC TO PRI field is populated, otherwise prohibited. 



EXAMPLE: 0 8 - 1 0 - 1 9 9 7 

38. LEAN - Line Existing Account Number 

Identifies the end user’s existing account number assigned by the current NSP and/or LSP. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

Supports consolidating working telephone numbers that reside in old LSP 

existing account(s) to a single account telephone number. 

Supports one end user’s multiple accounts at one end user location. 


Optional when the ACT field on the LSR Form is “V” and the EAN or 

EATN field on the EU Form or the LEATN field is not populated, 




EXAMPLE: 

2 0 1 M 8 1 - 3 5 8 2 


135


39. LEATN - Line Existing Account Telephone Number 

Identifies the end user’s existing account telephone number assigned by the old LSP. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 






EATN field on the EU Form or the LEAN field is not populated, otherwise 

prohibited. 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


136



Identifies a free flowing field which can be used to expand upon and clarify other data on this 

form. 

USAGE: 




EXAMPLE: 

I N S T A L L 2 W I R E A N A L O G L O O 

P 


137


41. TCMI – Transfer of Call Message Indicator 



USAGE: 

NOTE 1: 







0 0 3 

42. TCMESS – Transfer of Calls Message 


USAGE: 

NOTE 1: 




138


4.3 LS Alpha Numeric Glossary 

The following table is an alphanumeric cross-reference glossary of the Loop Service Form fields. 

LS FORM 



CABLE ID 17 Cable Identification 

CCEA 15 Cross Connect Equipment Assignment 

CFA 14 Connecting Facility Assignment 

CHAN/PAIR 21 Channel/Pair 

CKR 10 Customer Circuit Reference 


ECCKT 13 Exchange Company Circuit ID 

IWJK 28 Inside Wire Jack Code 

IWJQ 29 Inside Wire Jack Quantity 

JK CODE 23 Jack Code 

JK NUM 24 Jack Number 

JK POS 25 Jack Position 

JR 26 Jack Request 

LEAN 38 Line Existing Account Number 

LEATN 39 Line Existing Account Telephone Number 

LNA 9 Line Activity 

LNUM 8 Line Number 


LQTY 5 Loop Quantity 

NIDR 27 NID Request 



RELAY RACK 20 Relay Rack 


SAN 12 Subscriber Authorization Number 

SHELF 18 Shelf 

SLOT 19 Slot 

SYSTEM ID 16 System Identification 









TER 31 Terminal Number 

TSP 11 Telecommunications Service Priority 

UNIT 22 Unit 



139



Loop Service 

V5 

8/00 

PON 

1 

Service Details 

VER AN 

3 

ATN 

2 4 

- - 

LQTY PG_of_ 

5 6 

LOCNUM 

7 

LNUM 

8 

LNA 

9 

CKR 

TSP 

1 0 1 1 

- 

SAN 

1 2 

ECCKT 

1 3 

CFA 

1 4 

CCEA 

1 5 

SYSTEM ID 

1 6 

CABLE ID 

1 7 

SHELF 

1 8 

SLOT 

1 9 

RELAY RACK 

2 0 

CHAN/PAIR 

2 1 

UNIT 

2 2 

JK CODE 

2 3 

JK NUM 

2 4 

JK POS 

2 5 

JR 

26 

NIDR 

27 

IWJK 

2 8 

IWJQ 

2 9 

IWJK 

2 8 

IWJQ 

2 9 

IWJK 

2 8 

IWJQ 

DISC NBR 

2 9 3 0 

- - 

TER 

3 1 

TC OPT 

TC TO PRI 

TC TO SEC 

3 2 3 3 

- - 

3 4 

- - 

TCID 

3 5 

TC NAME 

3 6 

TCID 

3 5 

TC NAME 

3 6 

TC PER 

3 7 

LEAN 

3 8 

LEATN 

3 9 

- - 

LOCNUM 

7 

LNUM 

8 

LNA 

9 

CKR 

TSP 

1 0 1 1 

- 

SAN 

1 2 

ECCKT 

1 3 

CFA 

1 4 

CCEA 

1 5 

SYSTEM ID 

1 6 

CABLE ID 

1 7 

SHELF 

1 8 

SLOT 

1 9 

RELAY RACK 

2 0 

CHAN/PAIR 

2 1 

UNIT 

2 2 

JK CODE 

2 3 

JK NUM 

2 4 

JK POS 

2 5 

JR 

26 

NIDR 

27 

IWJK 

2 8 

IWJQ 

2 9 

IWJK 

2 8 

IWJQ 

2 9 

IWJK 

2 8 

IWJQ 

DISC NBR 

2 9 3 0 

- - 

TER 

3 1 

TC OPT 

TC TO PRI 

TC TO SEC 

3 2 3 3 

- - 

3 4 

- - 

TCID 

3 5 

TC NAME 

3 6 

TCID 

3 5 

TC NAME 

3 6 

TC PER 

3 7 

LEAN 

3 8 

LEATN 

3 9 

- - 






Loop Service (continued) 

V5 

8/00 

PON 

1 


VER AN 

3 

ATN 

2 4 

- - 

LQTY PG_of_ 

5 6 

LOCNUM 

7 

LNUM 

8 

LNA 

9 

CKR 

TSP 

1 0 1 1 

- 

SAN 

1 2 

ECCKT 

1 3 

CFA 

1 4 

CCEA 

1 5 

SYSTEM ID 

1 6 

CABLE ID 

1 7 

SHELF 

1 8 

SLOT 

1 9 

RELAY RACK 

2 0 

CHAN/PAIR 

2 1 

UNIT 

2 2 

JK CODE 

2 3 

JK NUM 

2 4 

JK POS 

2 5 

JR 

26 

NIDR 

27 

IWJK 

2 8 

IWJQ 

2 9 

IWJK 

2 8 

IWJQ 

2 9 

IWJK 

2 8 

IWJQ 

DISC NBR 

2 9 3 0 

- - 

TER 

3 1 

TC OPT 

TC TO PRI 

TC TO SEC 

3 2 3 3 

- - 

3 4 

- - 

TCID 

3 5 

TC NAME 

3 6 

TCID 

3 5 

TC NAME 

3 6 

TC PER 

3 7 

LEAN 

3 8 

LEATN 

3 9 

- - 

REMARKS 

4 0 

TCMI 

4 1 

TCMESS 

4 2 






Loop Service 

V5 

8/00 

PON 

VER 

AN 

ATN 

- - 

LQTY 

PG_of_ 


LOCNUM 

SAN 

LNUM LNA CKR TSP 

ECCKT 

- 

CFA 

CCEA 

SYSTEM ID 

CABLE ID 

SHELF SLOT RELAY RACK CHAN/PAIR UNIT JK CODE JK NUM JK POS JR NIDR IWJK IWJQ 

IWJK IWJQ IWJK IWJQ 


- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

LEAN 

LEATN 

- - 

LOCNUM 

SAN 


ECCKT 

- 

CFA 

CCEA 

SYSTEM ID 

CABLE ID 




- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

LEAN 

LEATN 

- - 






Loop Service (continued) 

V5 

8/00 

PON 

VER 

AN 

ATN 

- - 

LQTY 

PG_of_ 


LOCNUM 

SAN 


ECCKT 

- 

CFA 

CCEA 

SYSTEM ID 

CABLE ID 




- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

REMARKS 

LEAN 

LEATN 

- - 

TCMI 

TCMESS 





5.0 NUMBER PORTABILITY (NP) 

5.1 NP Form 

The NP Form must always be associated with LSR and EU Forms, which contain administrative 

and bill detail necessary for the provisioning of this request. 

The NP Form is required when the LSP is requesting the end user’s telephone number(s) to be 

ported (i.e. Local Number Portability or Interim Number Portability). The NP form contains two 

sections: 


• Service Details 



The Service Details section provides all information pertinent to the porting of the telephone 

number including the ported telephone number and the remote call forward number. 




It is recognized that there may be fields in the Administrative Section of this practice that are 

based on LSR Activity (ACT) values. For documentation purposes the usage strips in this practice 

reflect only the applicable line level activities (LNAs) for Number Portability. The applicable 

LNAs are as follows: 

N 

C 

D 

M 

T 

R 

V 

= New installation and/or account 

= Change and existing account, e.g., rearrangement, partial disconnect or additions 

= Disconnection 

= Inside move of the physical termination within a building 

= Outside move of end user location 

= Record activity for ordering administrative changes 

= Conversion of service to new LSP 


144


5.2 NP Form Fields 





USAGE: 




EXAMPLE: 8 2 4 Z 9 



NOTE 1: 




00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 



optional. 



EXAMPLE: A A 


145


3. AN- Account Number 


NOTE 1: 

NOTE 2: 






USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 


For requests submitted in Windstream Express, the value in this field is 

populated by the system based on the entry in the AN field on the LSR 

Form. 

Required when the ATN field is not populated. 

Required when the EAN field on the EU Form is blank or when a new AN 

is required. 




EXAMPLES: 

N 

A B 3 2 2 1 4 7 


146




NOTE 1: 




ATN 


USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 


For requests submitted in Windstream Express, the value in this field is 

populated by the system based on the entry in the ATN field on the LSR 

Form. 

Required when the AN field is not populated. 

Required when the EATN field on the EU Form is blank or when a new 

ATN is required. 




EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 

5. NPQTY - Number Portability Quantity 

Identifies the quantity of ported numbers involved in this service. 

USAGE: 





9 9 9 



USAGE: 






147





NOTE 1: 

USAGE: 

NOTE 1: 




Required when the request is for a non-simple port. 




9 9 9 


Identifies the line or trunk as a unique number and each additional occurrence as a unique 

number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 











EXAMPLE: 0 0 0 0 1 


148


9. NPI - Number Portability Indicator 

Identifies the status of the telephone number being ported. 


A = Port Out Reserved TN 

B = Port Out Working TN 

C = Port in Working TN 

D = Port in Reserved TN 

NOTE 1: 

USAGE: 

Reserved numbers can only be ported when associated with an active 

account. 




EXAMPLE: 

A 






addition 






USAGE: 

NOTE 1: 





EXAMPLE: 

N 


149



Identifies the circuit number assigned by the customer 

NOTE 1: 

USAGE: 


and in many cases to identify the customer’s end-to-end service. 




EXAMPLES: 

L 0 0 0 2 

2 9 3 3 2 1 8 1 

12. LRN - Location Routing Number 

Identifies a number used to uniquely identify a switch that has ported numbers and is used to 

route a call to the switch that owns the NPA-NXX portion of the LRN. 


NPA-NXX-XXXX 

NOTE 1: 

USAGE: 

An LRN is a 10 digit number in the form of NPA-NXX-XXXX. 




EXAMPLE: 2 1 4 - 3 3 3 - 0 0 0 1 


150


13. TDT - Ten Digit Trigger 

Indicates the request for the activation of a ten digit trigger for local routing number 

portability. 


Y = Yes 

USAGE: 

NOTE 1: 


Required when the first position of the REQTYP field on the LSR Form is 

“C” and the NPT field is “D”, otherwise prohibited. 



EXAMPLE: 

Y 



NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 



periods. 


standards. 



spaces. 







EXAMPLES: 

A2/SBFS/201/981/3500 

//800/123/4567 


Prefix/Service Code and Modifier/Serial Number/Suffix Code/AP code/segment name (if 

applicable) 


EXAMPLE: 

A2/LBFS/032719/001/NY 


151


14. ECCKT - Exchange Company Circuit ID (continued) 

VALID ENTRIES (continued) 




EXAMPLE: 

USAGE: 

101/T1/NYCYMNY50/NYCMNY54W01 




15. PORTED NBR - Ported Telephone Number 

Identifies the telephone number (TN) and/or consecutive range of TNs residing in the same 

switch, that are to be ported. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

USAGE: 

A single number or the first number of the range may also be used to 

identify the billing account number. 

May include two or three hyphens as delimiters between the telephone 

number components and range. 

When the NPT field is “B”, a number range may only be specified when all 

numbers within the range are Remote Call Forwarding to the same TN. 

A range of numbers can be presented as a block of numbers or multiple 

iterations. 




EXAMPLE: 

9 0 8 - 6 9 9 - 7 0 0 0 - 7 0 2 0 


152


16. TNP - Total Number of Paths 

Identifies the total number of talk paths, including the initial path, associated with the ported 

number. 


001-999 

USAGE: 

NOTE 1: 


Required when the LNA field is "N", “T” or "V" and the NPT field is "A", 

“B" or "C", otherwise optional. 




17. CFTN - Call Forward To Number 

Identifies the telephone number to which calls will be directed. 

USAGE: 

NOTE 1: 


Required when the NPT field is “B”, otherwise optional. 



EXAMPLES: 1 4 0 8 - 5 5 5 - 1 2 3 4 

4 0 8 - 5 5 5 - 1 2 3 4 

5 5 5 - 1 2 3 4 

18. NPT - Number Portability Type 

Indicates the type of number portability for this request. 


A = DID 

B = RCF 

C = Route Index 

D = Local Routing Number 

USAGE: 

NOTE 1: 


Required when the LNA field is “N”, “T” or “V”, otherwise optional. 



EXAMPLE: 

A 


153


19. RTI - Route Index 

Identifies the routing index to be used by the provider's switching equipment to forward/port 

the provider's telephone number to the customer's non-RCF trunk group. 

USAGE: 





20. NPTG - Number Portability Trunk Group 

Identifies the two six code (TSC) of a dedicated trunk group, from the porting switch to the 

customer's point of interface (POI), used to complete NP calls. 

USAGE: 




EXAMPLE: A K 1 2 3 4 5 6 

21. LSCP – Local Service Provider Change Prohibited 



NOTE 1: 

NOTE 2: 


permission. 

This field is used to freeze this line only. 


A = Prohibit a change of current local service provider. 

B = Removed the prohibition. 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 


Prohibited when the LSCP field is populated on the LSR Form. 

Prohibited when NPT field is “D”. 




EXAMPLE: 

A 


154


22. BA - Blocking Activity 

Indicates the activity for the blocking of calls. 


A = Add 

D = Delete 

N = No change 

Z = Remove all blocking 

USAGE: 




EXAMPLE: 

D 

23. BLOCK - Block 

Identifies the type of blocking on the telephone number. 


A = No collect and third party 

B = No third party 

C = No collect call 

D = No 1+ 

E = No 0+ Local 

F = No 1+ and 0+ Local 

G = No 011 (International) 

H = No Directory Assistance Call Completion (DACC) 

J = No 700 

K = No 976 

L = No 915 

M = No 900 

N = No casual calling 

P = No N11 (except 911 and 411) 

Q = No 411 

R = No incoming (CENTREX) 

S = No 976, 900-303, 900-505 

T = No 900-303 

W = No 7 digit toll (CENTREX) 

Y = No 500 

Z = All 

NOTE 1: 

USAGE: 

NOTE 1: 

Valid Entry of “Z” may not include the same types of blocking by all 

providers. 


Required when the BA field is “A” or “D”. 


155


23. BLOCK – Block (continued) 

NOTE 2: 

NOTE 3: 

Prohibited when the BA field is blank. 




EXAMPLES: 

A F H J K 

Z 

24. FPI - Freeze PIC Indicator 

Indicates the customer's requested freeze option for the LPIC. 


A = Freeze Intra 

S = Remove Intra Freeze 

USAGE: 




EXAMPLE: 

A 

25. LPIC - IntraLATA Pre-subscription Indicator Code 

Identifies the Pre-subscription Indicator Code (PIC) of the carrier the customer has selected 

for IntraLATA traffic for the ported telephone number. 


Valid PIC code 

NONE 

NC = No change 

NOTE 1: 

NOTE 2: 

USAGE: 

NONE - Customer does not want to pre-subscribe. 

NC - Used in a conversion as is activity scenario or change activity when 

the LPIC is not impacted. 






156






N = None 

S = Standard 

USAGE: 




EXAMPLES: 

S 

T 



USAGE: 

NOTE 1: 






EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 



USAGE: 

NOTE 1: 





USAGE: 

NOTE 1: 




157





USAGE: 

NOTE 1: 






NOTE 1: 




U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 



Optional when the TC TO PRI field is populated otherwise prohibited. 



EXAMPLE: 0 8 - 1 0 - 1 9 9 7 


158




NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 










EXAMPLE: 

2 0 1 M 8 1 - 3 5 8 2 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 







prohibited. 



EXAMPLE: 

2 0 1 - 5 5 5 - 1 2 1 2 


159




form. 

USAGE: 




EXAMPLE: 

P O R T I N G A L L L I N E S E X C E P T 

5 5 5 - 5 5 5 5 




USAGE: 

NOTE 1: 







0 0 3 


160




USAGE: 

NOTE 1: 




161


5.3 NP Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the Number Portability 

Form fields. 

NP FORM 



BA 22 Blocking Activity 

BLOCK 23 Block 

CFTN 17 Call Forward To Number 



FPI 24 Freeze PIC Indicator 






LPIC 25 IntraLATA Pre-subscription Indicator Code 

LRN 12 Location Routing Number 

LSCP 21 Local Service Provider Change Prohibited 

NPI 9 Number Portability Indicator 

NPQTY 5 Number Portability Quantity 

NPT 18 Number Portability Type 

NPTG 20 Number Portability Trunk Group 



PORTED NBR 15 Ported Telephone Number 


RTI 19 Route Index 









TDT 13 Ten Digit Trigger 

TNP 16 Total Number of Paths 



162




V5 

8/00 

PON 

1 


VER 

2 

AN 

ATN 

NPQTY PG_of_ 

3 4 

5 

6 

- - 

LOCNUM 

7 

LNUM 

8 

NPI 

9 

LNA 

10 

CKR 

1 1 1 2 

- - 

LRN 

TDT 

13 

ECCKT 

1 4 

PORTED NBR 

1 5 

LSCP 

21 

BA 

22 

- - 

BLOCK 

2 3 

TNP 

1 6 

BA 

22 

CFTN 

1 7 

BLOCK 

2 3 

NPT 

18 

FPI 

24 

RTI 

1 9 

LPIC 

2 5 

NPTG 

2 0 

TC OPT 

TC TO PRI 

TC TO SEC 

2 6 2 7 

- - 

2 8 

- - 

TCID 

2 9 

TC NAME 

3 0 

TCID 

2 9 

TC NAME 

3 0 

TC PER 

3 1 

LEAN 

3 2 

LEATN 

3 3 

- - 

LOCNUM 

7 

LNUM 

8 

NPI 

9 

LNA 

10 

CKR 

1 1 1 2 

- - 

LRN 

TDT 

13 

ECCKT 

1 4 

PORTED NBR 

1 5 

LSCP 

21 

BA 

22 

- - 

BLOCK 

2 3 

TNP 

1 6 

BA 

22 

CFTN 

1 7 

BLOCK 

2 3 

NPT 

18 

FPI 

24 

RTI 

1 9 

LPIC 

2 5 

NPTG 

2 0 

TC OPT 

TC TO PRI 

TC TO SEC 

2 6 2 7 

- - 

2 8 

- - 

TCID 

2 9 

TC NAME 

3 0 

TCID 

2 9 

TC NAME 

3 0 

TC PER 

3 1 

LEAN 

3 2 

LEATN 

3 3 

- - 






Number Portability (continued) 

V5 

8/00 

PON 

1 


VER 

2 

AN 

ATN 

NPQTY PG_of_ 

3 4 

5 

6 

- - 

LOCNUM 

7 

LNUM 

8 

NPI 

9 

LNA 

10 

CKR 

1 1 1 2 

- - 

LRN 

TDT 

13 

ECCKT 

1 4 

PORTED NBR 

1 5 

LSCP 

21 

BA 

22 

- - 

BLOCK 

2 3 

TNP 

1 6 

BA 

22 

CFTN 

1 7 

BLOCK 

2 3 

NPT 

18 

FPI 

24 

RTI 

1 9 

LPIC 

2 5 

NPTG 

2 0 

TC OPT 

TC TO PRI 

TC TO SEC 

2 6 2 7 

- - 

2 8 

- - 

TCID 

2 9 

TC NAME 

3 0 

TCID 

2 9 

TC NAME 

3 0 

TC PER 

3 1 

LEAN 

3 2 

LEATN 

3 3 

- - 

LOCNUM 

7 

LNUM 

8 

NPI 

9 

LNA 

10 

CKR 

1 1 1 2 

- - 

LRN 

TDT 

13 

ECCKT 

1 4 

PORTED NBR 

1 5 

LSCP 

21 

BA 

22 

- - 

BLOCK 

2 3 

TNP 

1 6 

BA 

22 

CFTN 

1 7 

BLOCK 

2 3 

NPT 

18 

FPI 

24 

RTI 

1 9 

LPIC 

2 5 

NPTG 

2 0 

TC OPT 

TC TO PRI 

TC TO SEC 

2 6 2 7 

- - 

2 8 

- - 

TCID 

2 9 

TC NAME 

3 0 

TCID 

2 9 

TC NAME 

3 0 

TC PER 

3 1 

REMARKS 

3 4 

LEAN 

3 2 

LEATN 

3 3 

- - 

TCMI 

3 5 

TCMESS 

3 6 







V5 

8/00 

PON VER AN 

ATN 

NPQTY 


- - 

PG_of_ 

LOCNUM 

LNUM 

NPI 

LNA 

CKR 

LRN 

- - 

TDT 

ECCKT 

PORTED NBR 

- - 

TNP CFTN NPT 

RTI 

NPTG 

LSCP 

BA 

BLOCK 

BA 

BLOCK 

FPI 

LPIC 

TC OPT 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

LEAN 

LEATN 

- - 

LOCNUM 

LNUM 

NPI 

LNA 

CKR 

LRN 

- - 

TDT 

ECCKT 

PORTED NBR 

- - 

TNP CFTN NPT 

RTI 

NPTG 

LSCP BA 

BLOCK 

BA 

BLOCK 

FPI 

LPIC 

TC OPT 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

LEAN 

LEATN 

- - 






Number Portability (continued) 

V5 

8/00 

PON VER AN 

ATN 

NPQTY 


- - 

PG_of_ 

LOCNUM 

LNUM 

NPI 

LNA 

CKR 

LRN 

- - 

TDT 

ECCKT 

PORTED NBR 

- - 

LSCP 

BA 

BLOCK 

TNP CFTN NPT RTI 

BA BLOCK 

FPI LPIC 

NPTG 

TC OPT 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

LEAN 

LEATN 

- - 

LOCNUM 

LNUM 

NPI 

LNA 

CKR 

LRN 

- - 

TDT 

ECCKT 

PORTED NBR 

- - 

LSCP 

BA 

BLOCK 


BA BLOCK 

FPI LPIC 

NPTG 

TC OPT 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

REMARKS 

LEAN 

LEATN 

- - 

TCMI 

TCMESS 





6.0 LOOP SERVICE WITH NUMBER PORTABILITY (LSNP) 

6.1 LSNP Form 

The LSNP Form must always be associated with LSR and EU Forms, which contain 

administrative and bill detail necessary for the provisioning of this request. 

The Loop Service with Number Portability Form is required when the LSP is requesting to utilize 

a portion of Windstream’s current network facilities, i.e. UNE Local Loop, in order to deliver the 

end user with their dial tone and feature services, and the end user also wants to retain their current 

telephone number. The LSNP form contains two sections: 

• Administrative Section 

• Service Details Section 



The Service Details provides all the necessary facility detail to complete the provisioning of the 

telephone service for the LSP on behalf of the end user. 

This section of the Wndstream LSOP contains the fields, a description of each field, usage of the 




based on LSR Activity (ACT) values. For documentation purposes, the usage strips in this 

practice reflect only the applicable line level activities (LNAs) for Loop Service with Number 

Portability. The applicable LNAs are as follows: 


C = Change an existing account, e.g., rearrangement, partial disconnect or addition 







167


6.2 LSNP Form Fields 



Identifies the customer’s unique purchase-order or requisition number that authorizes the 

issuance of this request. 

USAGE: 







NOTE 1: 




00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 



optional. 



EXAMPLE: A A 


168




NOTE 1: 

NOTE 2: 






USAGE: 

NOTE 1: 






EXAMPLES: 

N 

A B 3 2 2 1 4 7 



NOTE 1: 




ATN 


USAGE: 

NOTE 1: 


Required when either the EATN field on the EU Form or the AN field is 

not populated, or when a new ATN is requested, otherwise optional. 


12 numeric characters (including 2 pre-printed 

hyphens) 

EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


169


5. LQTY - Loop Quantity 

Identifies the quantity of loops involved in this service request. 

USAGE: 





6. NPQTY - Number Portability Quantity 

Identifies the quantity of ported numbers involved in this service request. 

USAGE: 







USAGE: 






170





NOTE 1: 

USAGE: 







9 9 9 



number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 










EXAMPLE: 0 0 0 0 1 


171









NOTE 1: 

NOTE 2: 

USAGE: 


account. 

When the first position of the REQTYP field on the LSR Form is “B”, the 

only valid entry is “A” or “B”. 




EXAMPLE: 

A 






addition 






USAGE: 




EXAMPLE: 

N 


172




NOTE 1: 

USAGE: 


and in many cases to identify the customer’s end-to end service. 




EXAMPLES: 

L 0 0 0 2 

2 9 3 3 2 1 8 1 

13. TSP - Telecommunications Service Priority 


Handbook. 

NOTE 1: 






NOTE 1: 

USAGE: 





hyphen) 

EXAMPLE: T S P 1 2 3 4 5 C - E 1 


173


14. LRN - Location Routing Number 

Identifies a number used to uniquely identify a switch that has ported numbers and is used to 

route a call to the switch that owns the NPA-NXX portion of the LRN. 


NPA-NXX-XXXX 

NOTE 1: 

USAGE: 

An LRN is a 10 digit number in the form of NPA-NXX-XXXX. 




EXAMPLE: 2 1 4 - 3 3 3 - 0 0 0 1 

15. TDT - Ten Digit Trigger 

Indicates the request for the activation of a ten-digit trigger for local routing number 

portability. 


Y = Yes 

USAGE: 

NOTE 1: 



“B” and the NPT field is “D”, otherwise prohibited. 



EXAMPLE: 

Y 



NOTE 1: 

USAGE: 






EXAMPLE: 

A B 1 2 3 4 5 6 7 8 


174




NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 



periods. 


standards. 



spaces. 







EXAMPLES: 

A2/SBFS/201/981/3500 

//800/123/4567 


Prefix/Service Code and Modifier/Serial Number/Suffix Code/AP code/segment name (if 

applicable) 


EXAMPLE: 

A2/LBFS/032719/001/NY 




EXAMPLE: 

USAGE: 

NOTE 1: 

101/T1/NYCYMNY50/NYCMNY54W01 


Required when the LNA field on the NP Form is “C”, “D”, “M”, “T” or 

“R”, otherwise optional. 




175




NOTE 1: 



American Telecommunications System. The Facility identifier consists of 


1. Facility Designation – A code that, for a specific type of facility, uniquely 



2. Facility Type – A code that describes a type of facility when it is other than 

a single baseband channel on cable. Valid entries are outlined in Telcordia 

Technologies practice BR 795-450-100 (variable length, 1-6 alphanumeric 

characters). 

3. Channel/Pair/Time Slot – A code that identifies a specific assignable 


4. Location A – A standardized code that uniquely identifies the location of 



practice BR-795-100-100 (8 or 11 alphanumeric characters). 

5. Location Z – A standardized code that uniquely identifies the location of 

facility terminal Z, which has the higher in alphanumeric sequence of the two 


practice BR 795-100-100 (8 or 11 alphanumeric characters). 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 

USAGE: 






SCFA field. 







176


18. CFA - Connecting Facility Assignment (continued) 

EXAMPLES: 

1 0 1 / T 1 / 3 / B S T N M A G T C G 0 / B S T N 

M A M T K 3 1 

1 0 1 / T 1 / 1 - 2 4 / B S T N M A G T C G 0 / B 

S T N M A M T K 3 1 

1 0 1 . T 1 . 3 . B S T N M A G T C G 0 . B S T N 

M A M T K 3 1 

NOTE 1: 

The second example shows the proper format for ranging channel 

assignments. 

19. CCEA – Cross Connect Equipment Assignment 

Identifies the physical point of termination at a collocation cage. 

NOTE 1: 

NOTE 2: 

USAGE: 

This information is provided by the customer when they have assignment 

control. 

When the CCEA field is populated, the information will identify the tiedown 

assignment at the ACTL. 




EXAMPLE: 

A B C / 0 1 / 2 4 - N L / 1 2 0 8 - 1 2 1 0 / O K 

L D C A 0 3 / O K L D C A 0 3 


177




NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: A A 


Identifies the provider's central office cable to be connected to the customer's collocated 

equipment 

NOTE 1: 

USAGE: 


arrangement. 







NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 2 0 


178




NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 0 7 

24. RELAY RACK – Relay Rack 

A code that identifies the customer's bay/cabinet in a collocation arrangement and may also 

include the floor and aisle where the specific piece of equipment is located. 

NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 1 0 0 0 5 2 . 0 3 



NOTE 1: 

USAGE: 


arrangement. 




EXAMPLE: 2 4 


179


26. UNIT - Unit 

Identifies the number assigned to a panel, shelf or case within the customer’s bay/cabinet 

indicated in the RELAY RACK field. 

USAGE: 

NOTE 1: 


Required when the customer has assignment control in a collocation 




EXAMPLES: 2 4 

2 4 - 4 8 




NOTE 1: 

USAGE: 

NOTE 1: 










28. JK NUM – Jack Number 


NOTE 1: 

USAGE: 

NOTE 1: 






EXAMPLE: B 2 


180




NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 



When the TNS field is ranged, the entry in this field indicates the first 

position in a sequential arrangement. 





EXAMPLE: 9 9 




Y = Yes 

USAGE: 

NOTE 1: 


Optional when the LNA is “N”, “C”, “M”, “T” or “V”, otherwise 

prohibited. 



EXAMPLE: 

Y 




Y = Yes 

USAGE: 




EXAMPLE: 

Y 


181




NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 















NOTE 1: 





01-99 

USAGE: 

NOTE 1: 


Required when the IWJK field is populated, otherwise prohibited. 



EXAMPLE: 0 1 


182


34. PORTED NBR – Ported Telephone Number 

Identifies the telephone number (TN) and/or consecutive range of TNs residing in the same 

switch, that are to be ported. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

USAGE: 

A single number or the first number of the range may also be used to 





numbers within the range are Remote Call Forwarding to the same TN. 


iterations. 



hyphens) 

EXAMPLES: 

9 0 8 - 6 9 9 - 7 0 0 0 

9 0 8 - 6 9 9 - 7 0 0 0 - 7 0 2 0 

35. TNP - Total Number of Paths 

Identifies the total number of talk paths, including the initial path, associated with the ported 

number. 


001-999 

USAGE: 

NOTE 1: 


Required when the LNA field is “N”, “T” or “V” and the NPT field is “A”, 

“B” or “C”, otherwise optional. 





183


36. CFTN - Call Forward To Number 

Identifies the telephone number to which calls will be directed. 

USAGE: 

NOTE 1: 


Required when the NPT field is “B”, otherwise prohibited. 



EXAMPLES: 1 4 0 8 - 5 5 5 - 1 2 3 4 

4 0 8 - 5 5 5 - 1 2 3 4 

5 5 5 - 1 2 3 4 

37. NPT - Number Portability Type 

Indicates the type of number portability for this request. 


A = DID 

B = RCF 

C = Route Index 

D = Local Routing Number 

USAGE: 

NOTE 1: 


Required when the LNA field is “N”, “T” or “V”, otherwise optional. 



EXAMPLE: 

A 




USAGE: 






184


39. NPTG - Number Portability Trunk Group 

Identifies the two six code (TSC) of a dedicated trunk group, from the porting switch to the 

customer's point of interface (POI), used to complete NP calls. 

USAGE: 




EXAMPLE: A K 1 2 3 4 5 6 




NOTE 1: 

NOTE 2: 


permission. 





USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 


Prohibited when the LSCP field is populated on the LSR Form. 

Prohibited when NPT field is “D”. 




EXAMPLE: 

A 

41. BA – Blocking Activity 



A = Add 

D = Delete 

N = No change 


USAGE: 




EXAMPLE: 

D 


185








D = No 1+ 





J = No 700 

K = No 976 

L = No 915 

M = No 900 



Q = No 411 


S = No 976, 900-303, 900-505 

T = No 900-303 


Y = No 500 

Z = All 

NOTE 1: Valid Entry of “Z” may not include the same type of blocking by all 

providers. 

USAGE: 

NOTE 1: 


Required when the BA field is “A”, “D” or “N”, otherwise prohibited. 



EXAMPLES: 

A F H J K 

Z 


Indicates the customer's requested freeze option for the LPIC. 


A = Freeze Intra 

S = Remove Intra Freeze 

USAGE: 




EXAMPLE: 

A 


186




for IntraLATA traffic for the ported telephone number. 



NONE 


NOTE 1: 

NOTE 2: 

USAGE: 












N = None 

S = Standard 

USAGE: 




EXAMPLE: 

S 



USAGE: 

NOTE 1: 






EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 


187




USAGE: 

NOTE 1: 





USAGE: 

NOTE 1: 






USAGE: 

NOTE 1: 






NOTE 1: 




U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 





hyphens) 

EXAMPLE: 0 8 - 1 0 - 1 9 9 7 


188




NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 










EXAMPLE: 

2 0 1 M 8 1 - 3 5 8 2 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 







prohibited. 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


189




form. 

USAGE: 




EXAMPLE: 

T E R M I N A T E T O D E M A R C 




USAGE: 

NOTE 1: 







0 0 3 


190




USAGE: 

NOTE 1: 




191


6.3 LSNP Alphanumeric Glossary 

The following table is an alphanumeric cross-reference glossary of the Loop Service with Number 

Portability Form fields. 

LSNP FORM 


ATN 4 Acccount Telephone Number 




CCEA 19 Cross Connect Equipment Assignment 


CFTN 36 Call Forward To Number 

















LQTY 5 Loop Quantity 

LRN 14 Location Routing Number 




NPQTY 6 Number Portability Quantity 

NPT 37 Number Portability Type 

NPTG 39 Number Portability Trunk Group 










192


6.3 LSNP Alphanumeric Glossary (continued) 

LSNP FORM 



TCID 48 Transfer of Calls to Identifier 



TC NAME 49 Transfer of Calls to Name 



TC TO PRI 46 Transfer of Calls to Primary Number 

TC TO SEC 47 Transfer of Calls to Secondary Number 

TDT 15 Ten Digit Trigger 

TNP 35 Total Number of Paths 


UNIT 26 Unit 



193



Loop Service with Number Portability 

V5 

8/00 

PON 

1 

VER 

2 

AN 

3 

ATN 

4 

- - 

LQTY 

5 

NPQTY 

6 

PG _of_ 

7 


LOCNUM 

8 

LNUM 

9 

NPI 

10 

LNA 

11 

CKR 

TSP 

1 2 1 3 

- 

LRN 

1 4 

ECCKT 

1 7 

CFA 

1 8 

- - 

TDT 

15 

SAN 

1 6 

CCEA 

1 9 

SYSTEM ID 

2 0 

CABLE ID 

2 1 

SHELF 

2 2 

SLOT 

2 3 

RELAY RACK 

2 4 

CHAN/PAIR 

2 5 

UNIT 

2 6 

JK CODE 

2 7 

JK NUM 

2 8 

JK POS 

2 9 

JR 

30 

NIDR 

31 

IWJK 

3 2 

IWJQ 

3 3 

IWJK 

3 2 

IWJQ 

3 3 

IWJK 

3 2 

IWJQ 

3 3 

PORTED NBR 

3 4 

- - 

TNP 

3 5 

CFTN 

3 6 

NPT 

37 

RTI 

3 8 

NPTG 

3 9 

LSCP 

40 

BA 

41 

BLOCK 

4 2 

BA 

41 

BLOCK 

4 2 

FPI 

43 

LPIC 

4 4 

TC OPT 

TC TO PRI 

4 5 4 6 

- - 

TC TO SEC 

4 7 

- - 

TCID 

4 8 

TC NAME 

4 9 

TCID 

4 8 

TC NAME 

4 9 

TC PER 

5 0 

LEAN 

5 1 

LEATN 

5 2 

- - 




(Insert Your Company Logo) Loop Service with Number Portability (continued) 


V5 

8/00 

PON 

1 

VER AN 

3 

ATN 

2 4 

- - 

LQTY 

5 

NPQTY 

6 

PG _of_ 

7 


LOCNUM 

8 

LNUM 

9 

NPI 

10 

LNA 

11 

CKR 

TSP 

1 2 1 3 

- 

LRN 

1 4 

ECCKT 

1 7 

CFA 

1 8 

- - 

TDT 

15 

SAN 

1 6 

CCEA 

1 9 

SYSTEM ID 

2 0 

CABLE ID 

2 1 

SHELF 

2 2 

SLOT 

2 3 

RELAY RACK 

2 4 

CHAN/PAIR 

2 5 

UNIT 

2 6 

JK CODE 

2 7 

JK NUM 

2 8 

JK POS 

2 9 

JR 

30 

NIDR 

31 

IWJK 

3 2 

IWJQ 

3 3 

IWJK 

3 2 

IWJQ 

3 3 

IWJK 

3 2 

IWJQ 

3 3 

PORTED NBR 

3 4 

- - 

TNP 

3 5 

CFTN 

3 6 

NPT 

37 

RTI 

3 8 

NPTG 

3 9 

LSCP 

40 

BA 

41 

BLOCK 

4 2 

BA 

41 

BLOCK 

4 2 

FPI 

43 

LPIC 

4 4 

TC OPT 

TC TO PRI 

4 5 4 6 

- - 

TC TO SEC 

4 7 

- - 

TCID 

4 8 

TC NAME 

4 9 

TCID 

4 8 

TC NAME 

4 9 

TC PER 

5 0 

LEAN 

5 1 

LEATN 

5 2 

- - 

REMARKS 

5 3 

TCMI 

5 4 

TCMESS 

5 5 





Loop Service with Number Portability 

V5 

8/00 


PON VER AN 

ATN 

- - 

LQTY 

NPQTY 

PG _of_ 


LOCNUM 

LNUM 

NPI 

LNA CKR 

TSP 

- 

LRN 

- - 

TDT 

SAN 

ECCKT 

CFA 

CCEA 

SYSTEM ID CABLE ID SHELF SLOT RELAY RACK CHAN/PAIR UNIT JK CODE JK NUM JK POS JR NIDR 

IWJK 

IWJQ 

IWJK 

3 2 

IWJQ IWJK IWJQ 

PORTED NBR 

- - 


NPTG 

LSCP 

BA BLOCK 

BA 

BLOCK 

FPI 

LPIC 

TC OPT 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

LEAN 

LEATN 

- - 




(Insert Your Company Logo) Loop Service with Number Portability (continued) 


V5 

8/00 

PON 

VER 

AN 

ATN 

- - 

LQTY 

NPQTY 

PG _of_ 


LOCNUM 

LNUM 

NPI 

LNA CKR 

TSP 

- 

LRN 

- - 

TDT 

SAN 

ECCKT 

CFA 

CCEA 

SYSTEM ID CABLE ID SHELF SLOT RELAY RACK CHAN/PAIR UNIT JK CODE JK NUM JK POS JR NIDR 

IWJK 

IWJQ 


PORTED NBR 

- - 


NPTG 

LSCP 

BA BLOCK 

BA 

BLOCK 

FPI 

LPIC 

TC OPT 

TC TO PRI 

- - 

TC TO SEC 

- - 

TCID 

TC NAME 

TCID 

TC NAME 

TC PER 

LEAN 

LEATN 

- - 

REMARKS 

TCMI 

TCMESS 





7.0 RESALE SERVICE (RS) 

7.1 RS Form 

The Resale Form is required when the LSP is requesting the reuse of Windstream’s current 

facilities, operating systems, and databases for the sole purpose of reselling local telephone service 

to the end user. The RS form contains two sections: 





The Service Details provides all the necessary feature detail for the provisioning of the telephone 

service for the LSP on behalf of the end user. 





based on LSR Activity (ACT) values. For documentation purposes the usage strips in this practice 

reflect only the applicable line level activities (LNAs) for Resale Service. The applicable LNAs 

are as follows: 


C = Change an existing account, e.g., rearrangement, feature activity 





S = Suspend 

B = Restore 

X = Telephone number change 

P = PIC change 

L = Seasonal 

Y = Deny 

H = Short term 


198


7.2 Resale Form Fields 




issuance of this request 

USAGE: 







NOTE 1: 




00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 



optional. 



EXAMPLE: A A 


199




NOTE 1: 

NOTE 2: 






USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 




is required. 




EXAMPLES: 

N 

A B 3 2 2 1 4 7 



NOTE 1: 






USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 








EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


200


5. RSQTY - Resale Quantity 

Identifies the quantity of Resale Services (e.g., lines, circuits, trunks, etc.) involved in this 

service request. 

USAGE: 




EXAMPLE: 8 

6. ORD - Order Number 

Identifies the provider's order number for the service requested. 

NOTE 1: 

USAGE: 

This number may be pre-assigned to the 

customer by the provider. 




EXAMPLE: 

C 2 3 4 5 6 



USAGE: 






201





NOTE 1: 

USAGE: 







9 9 9 



number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 










EXAMPLE: 0 0 0 0 1 


202


10. LNEX - Line Number Extension Number 

Identifies the additional telephone number, virtual circuit or related virtual circuit as a unique 

number and each additional occurrence as a unique number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 

NOTE 6: 

USAGE: 

NOTE 1: 

Provides an extension to the Line Number (LNUM) field when multiple 

ISDN BRI Directory Telephone Numbers (TNS) are assigned to a single 

ISDN BRI line for one service order, purchase order number or LNUM. 

LNEX can only be used for new order types if the ISDN BRI Directory 

Telephone Numbers (TNS) are obtained via a pre-order process. 

LNEX is customer assigned and is returned on the Local Response (LR) to 

the customer. 

Once LNEX is generated, it cannot be changed and is retained through 



the request at the LNUM level. 

There may be multiple LNEXs per LNUM. 


Optional when the ACT field on the LSR Form is “C”, “D”, “R”, “V”, “B”, 

“X”, “P”, “L”, “Y” or “H” and the 2 nd character of the TOS field on the 

LSR Form is “H” or the 2 nd character of the LTOS field is “H”, otherwise 

prohibited. 



EXAMPLE: 0 0 0 0 1 


203









NOTE 1: 

NOTE 2: 

USAGE: 


account. 

When the first position of the REQTYP field on the LSR Form is “E”, the 

only valid entry is “C” or “D”. 




EXAMPLE: 

A 





C = Change, e.g., rearrangement, feature activity 



V = Conversion of service to new LSP as specified 


S = Suspend 

B = Restore 

X = Telephone number change 

P = PIC change 

L = Seasonal 

Y = Deny 

H = Short term 

USAGE: 




EXAMPLE: 

N 


204


13. LTOS - Line Type of Service 

Identifies the type of service at the line level. 




2 = Residence 


4 = Coin 



A = Individual line of a multi-line 


C = Coin 






L = xDSL 





F = Flat Rate 

G = Message 




N = Normal 


R = RCF 


W = WATS 


NOTE 1: 

USAGE: 






EXAMPLE: 1 A F - 


205



Identifies the type of telephone number entered in the TNS or OTN fields. 




B = ISDN BRI Telephone Number 

USAGE: 

NOTE 1: 


Required when the TNS or OTN field is populated, otherwise prohibited. 



EXAMPLE: 

T 

15. TNS - Telephone Numbers 

Identifies the telephone number or consecutive range of telephone numbers for this request. 


N = New telephone number requested 


Maintenance Number 

ISDN BRI Telephone Number 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

When the LNA field is “X”, the entry in this field indicates the new 

telephone number or request for a new telephone number. The out 

telephone number is shown in the OTN field. 

There may be one or more ISDN telephone numbers assigned per ISDN 

BRI line. 


number components and ranges. 



hyphens) 

EXAMPLES: 

2 0 1 - 5 5 5 - 1 1 1 1 

9 0 8 - 5 5 5 - 1 0 0 0 - 1 9 9 9 


206


16. S - Suspend Activity Indicator 

Indicates type of suspend activity being requested. 


C = Suspend Both 

USAGE: 




EXAMPLE: 

B 

17. SPLD - State Primary Line Designator 

Indicates whether the residential resale line is the Primary Line or a Non-Primary line at the 

same address for the purpose of tracking State High-Cost fund qualification. 


A = Primary 

B = Non-Primary 

C = Pending 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

Primary - Indicates that the line is the customer’s first line. 

Non-Primary - Indicates that the line is an additional line for a customer 

who already has a primary line or is ordering the non-primary line at the 

same time as the primary line at the same address. 

Pending - Indicates the primary/non-primary line status has not been 

determined. 




EXAMPLE: 

A 


207


18. TERS - Terminal Numbers 

Identifies the number for a non-lead line in a multi-line hunt group or consecutive range of 

terminal numbers associated with the TNS field for this request. 


N = New terminal number requested 

Terminal number(s) 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

A pilot (lead) telephone number in the TNS field must accompany this 

field. 

When this field is populated, the TNS field must not be ranged. 

The first position is reserved for a terminal number indicator. 




EXAMPLES: 

T 0 0 0 1 

S 0 0 0 1 

T 0 0 4 

T 0 0 0 0 

S 0 0 0 1 - 0 0 2 0 

19. OTN - Out Telephone Number 

Identifies the existing telephone number that is being changed. 

USAGE: 

NOTE 1: 


Required when the LNA field is "X", otherwise prohibited. 



EXAMPLE: 2 0 1 - 6 9 9 - 0 0 0 1 


208


20. PRIBD - ISDN PRI “B” and “D” Channel Configuration 

Identifies the ISDN PRI B and D channel configuration per DS-1. The field consists of 7 

character codes where the: 

1. First two numeric characters (positions 1 and 2) identifies the sequencing of 

the first and all subsequent ISDN PRI DS-1s. 

2. Next two numeric characters (positions 3 and 4) are required and represent the 

quantity of B channels ordered per DS-1 - between 1 and 24. 

3. Next two numeric characters (positions 5 and 6) are required and represent the 

number of D channels ordered per DS-1 - between 0 and 2. 

4. Next alpha character (position 7) is required to designate Non-Facility 

Associated Signaling (NFAS), allowing multiple PRIs to share a single D 

channel. This allows all 24 channels (after the first PRI) to be traffic bearing 

and/or the ability to designate a back-up D channel on a subsequent PRI. 


Positions 1 and 2 

Sequentially populated starting with 01 


01 through 24 


00 through 02 

Position 7 

Y = NFAS 

N = No NFAS 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

The sum of the second code designating the number of B channels 

(positions 3 and 4), and the third code designating the number of D 

channels (position 5 and 6) must be less than or equal to 24 channels per 

DS-1. 

When ordering in increments of 24 lines, the D channel is normally 

associated with the 24th channel. 


Required when the 2 nd position of the TOS field on the LSR Form is "K" or 

the 2 nd position of the LTOS field is “K”, otherwise prohibited. 



EXAMPLE: 0 1 2 3 0 1 Y 


209


21. ISPID - ISDN Service Profile Identification 

Provides a code that must be programmed into the ISDN BRI Customer Premise Equipment 

(CPE). This code is transmitted from the CPE over the ISDN BRI “D” channel to the LSO 

switch. It must be present in order for the BRI to become active. 

USAGE: 

NOTE 1: 


Required when the 2 nd position of the TOS field on the LSR Form is “H” or 

the 2 nd position of the LTOS field is “H”, otherwise optional. 



EXAMPLE: 7 0 3 5 0 6 6 3 5 5 0 1 0 1 

22. PTKTYP - PBX Trunk Type 

Identifies the type of PBX trunk being ordered. 


C = Custom 

USAGE: 




EXAMPLE: 

C 

23. PTLI - PBX Lead Telephone Line 

Identifies the lead telephone line identifier assigned to the Trunk Group. 



USAGE: 




EXAMPLE: 4 1 5 - 5 4 2 - 7 0 0 0 


210


24. PTKCON - PBX Trunk Configuration 

Identifies the directional configuration of the PBX trunk being ordered. 


T = Two Way 

I = In Only 

O = Out Only 

USAGE: 


NOTE 1: Required when the LNA field is “N” and the 2 nd position of the TOS field 

on the LSR Form is “J” (PBX) or the 2 nd position of the LTOS field is “J”, 




EXAMPLE: 

T 

25. TSP - Telecommunications Service Priority 


Handbook 

NOTE 1: 






NOTE 1: 

USAGE: 





hyphen) 

EXAMPLE: T S P 1 2 3 4 5 C - E 1 


211




NOTE 1: 

USAGE: 






EXAMPLE: 

A B 1 2 3 4 5 6 7 8 


Identifies the circuit number or sequential range of circuit numbers assigned by the customer 

NOTE 1: 

USAGE: 

CKR is used by the customer as a cross reference to the provider’s circuit 

ID(s), and in many cases to identify the customer’s end-to-end service. 




EXAMPLES: 

L 0 0 0 2 - 0 0 2 4 

2 9 3 3 2 1 8 1 


212



Identifies a provider’s circuit identification 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 



periods. 


standards. 



spaces. 





Prefix/Service Code and modifier/NPA/NXX/XXXX/Terminal Number (if applicable) 


EXAMPLES: 

A2/SBFS/201/981/3500 

//800/123/4567 



applicable) 


EXAMPLE: 

A2/LBFS/032719/001/NY 




EXAMPLE: 

USAGE: 






213



Indicates the LSP’s or the LSP End User customer’s freeze option for the PIC and LPIC. 


E = Freeze LSP’s InterLATA PIC 

A = Freeze LSP’s IntraLATA PIC 

B = Freeze LSP’s Inter & IntraLATA PIC 

J = Freeze LSP End User Customer’s InterLATA PIC 

K = Freeze LSP End User Customer’s IntraLATA PIC 

L = Freeze LSP End User Customer’s Inter & IntraLATA PICs 

R = Remove InterLATA freeze 

S = Remove IntraLATA freeze 

T = Remove Inter & IntraLATA freezes 

USAGE: 




EXAMPLE: 

A 

30. PIC - InterLATA Pre-subscription Indicator Code 


for InterLATA traffic. 



NONE 


NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 



the PIC is not impacted. 


Required when the LNA field is “N” or “P”, otherwise optional. 





214



Identifies the Presubscription Indicator Code (PIC) of the carrier the customer has selected for 

IntraLATA traffic. 



NONE 


NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 





Required when the LNA field is “N” or “P”, otherwise optional. 




32. IPIC - International Pre-subscription Indicator Code 


for International traffic. 

NOTE 1: 

NOTE 2: 

This field may be used for a response for customer service information 

when authorized to provide transition information. 

Windstream does not support a 3-PIC process 



NONE 


NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

None - Customer does not want to pre-subscribe. 


the PIC is not impacted. 


Windstream does not recognize an entry in this field. 





215


33. SDI - Switched Data Identifier 

Identifies type of switched data for ISDN BRI in instances of multiple IXC selection, e.g., one 

IXC is requested as the PIC for one B channel providing voice and data and another IXC is 

requested as the PIC for the second B channel providing just data, etc.. 


E = Circuit Switched Data and Voice 

F = Packet Switched Data 

G = Packet Switched Data and Voice 

H = Circuit Switched Data, Packet Switched Data and Voice 

I = Circuit Switched Data, Packet Switched Data 

J = Packet Switched Data on D Channel 

K = Switched Data on B Channel 56 Kbps 

L = Switched Data on B Channel 65 Kbps 

M = Voice Only 

USAGE: 




EXAMPLE: 

E 

34. MATN - Main/Alternate Telephone Number 

Indicates the dialable telephone number(s) assigned to the ISDN BRI line. If the same 

number cannot be used for both B channels, then the main number will be assigned to B- 

channel 1, and the alternate number will be assigned to B-channel 2. 


M = Main Telephone Number 

A = Alternate Telephone Number(s) 

NOTE 1: 

USAGE: 

There can only be one main telephone number, but multiple alternate 

telephone numbers may exist. 




EXAMPLE: 

M 


216


35. TCOPT - Transfer of Call Options 




N = None 

S = Standard 

USAGE: 




EXAMPLES: 

S 

T 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 





Optional when the ACT field on the LSR Form is “V” or “W”, and the 

EAN or EATN fields on the EU Form or the LEATN field is not populated, 




EXAMPLE: 

2 0 1 M 8 1 - 3 5 8 2 


217




NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 





Optional when the ACT field on the LSR Form is “V” or “W” and the EAN 

or EATN field on the EU Form or the LEAN field is not populated, 




EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 



USAGE: 

NOTE 1: 






EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 



USAGE: 

NOTE 1: 


Prohibited from use because this is not applicable to Windstream. 


218





NOTE 1: 




U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 






EXAMPLE: 0 8 - 1 0 - 1 9 9 6 



USAGE: 

NOTE 1: 






USAGE: 

NOTE 1: 


Windstream does not support this service 


219





NOTE 1: 

USAGE: 

NOTE 1: 










44. JK NUM - Jack Number 


NOTE 1: 

USAGE: 

NOTE 1: 






EXAMPLE: B 2 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 



When the TNS field is ranged, the entry in this field indicates the first 

position in a sequential arrangement. 





EXAMPLE: 9 9 


220





Y = YES 

USAGE: 




EXAMPLE: 

Y 




Y = YES 

USAGE: 




EXAMPLE: 

Y 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 














221




NOTE 1: 





01-99 

USAGE: 

NOTE 1: 


Required when the IWJK field is populated, otherwise prohibited. 



EXAMPLE: 0 1 

50. SGNL - Signaling 

Identifies the type of signaling requested. 


LP = Loop 

USAGE: 




EXAMPLE: L P 

51. SSIG - Start Signaling 

Identifies the type of start signaling requested. 


LS = Loop Start 

GS = Ground Start 

NOTE 1: 

USAGE: 

Only entries of “LS” or “GS” are allowed when SGNL is “LP”. 




EXAMPLE: D D 


222


52. PULSE - Type of Pulsing 

Identifies the type of pulsing requested for the service. 


DP = Dial Pulse 

MF = Multi Frequency 

DTMF Dual-tone Multi-Frequency 

USAGE: 




EXAMPLE: D P 

53. LSCP - Local Service Provider Change Prohibited 



NOTE 1: 

NOTE 2: 


permission. 





USAGE: 

NOTE 1: 


Prohibited when the LSCP field is populated on the LSR Form, otherwise 

optional. 



EXAMPLE: 

A 




A = Add 

D = Delete 

N = No change 


USAGE: 




EXAMPLE: 

D 


223








D = No 1+ 





J = No 700 

K = No 976 

L = No 915 

M = No 900 



Q = No 411 


S = No 976, 900-303, 900-505 

T = No 900-303 


Y = No 500 

Z = All 

NOTE 1: 

USAGE: 

NOTE 1: 

Valid Entry of “Z” may not include the same types of blocking by all 

providers. 


Required when the BA field is “A” or “D”, otherwise prohibited. 



EXAMPLES: 

A F H J K 

Z 


224


56. CNAM - Calling Name 

Identifies the end user name that the customer wants stored in the provider’s Line Information 

Database (LIDB). 

NOTE 1: 

NOTE 2: 

USAGE: 

This field specifies the calling name that may appear on a suitably equipped 

caller ID display when the end user places a call to a telephone number that 

is provisioned with the calling name feature. 

This field must contain a legitimate version of the end user name. 




EXAMPLE: 

A F W H I T A K E R I N C 


Identifies the provider’s carrier system and channel to be used. 

NOTE 1: 





1. Facility Designation - A code that, for a specific type of facility, uniquely 



2. Facility Type - A code that describes a type of facility when it is other than a 

single baseband channel on cable. Valid entries are outlined in Telcordia 


characters). 

3. Channel/Pair /Time Slot - A code that identifies a specific assignable 


4. Location A - A standardized code that uniquely identifies the location of 




5. Location Z - A standardized code that uniquely identifies the location of 





225



NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 

USAGE: 






SCFA field. 






EXAMPLES: 


M A M T K 3 1 

1 0 1 / T 1 / 1 - 2 4 / B S T N M A G T C G 0 / B 



M A M T K 3 1 

NOTE 1: 


assignments. 


226


58. FA - Feature Activity 

Indicates the activity type for the feature. 


N = Add/Install 

C = Change to feature detail 

D = Disconnect 

I = Insert listing/data 

O = Delete listing/data 

V = Conversion to new LSP as specified 


USAGE: 




EXAMPLE: 

V 

59. FEATURE - Feature Codes 

Identifies the type of feature associated with the line. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

Codes for feature identification may include: USOCs, FIDs, TCIF 

maintained EDI codes or ISDN ordering codes (IOCs). 

When ordering ISDN BRI using ISDN ordering codes (IOCs) as described 

in Telcordia Technologies SR-3622, the first two characters equal "IC" and 

the third through sixth characters are the IOC. 


Required when the FA field is populated, otherwise prohibited. 



EXAMPLE: I C A 


227


60. FEATURE DETAIL - Feature Detail 

Identifies additional information for the type of feature associated with the line. 

USAGE: 

NOTE 1: 


Optional when the FEATURE field is populated, otherwise prohibited. 



EXAMPLES: 

T N 2 1 2 5 3 5 - 1 2 3 4 / T I I D 4 3 / A 

S A 0 C L E C A B T 1 / A S A 1 S R T G / A 

S S P 2 A B C 1 2 3 

C A L L W A I T I N G 


228


61. TCMI - Transfer of Call Message Indicator 



USAGE: 

NOTE 1: 







0 0 3 

62. TCMESS - Transfer of Calls Message 


USAGE: 

NOTE 1: 




229


7.3 RS Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the Resale Services Form. 

RS FORM 







CNAM 56 Calling Name 


FA 58 Feature Activity 

FEATURE 59 Feature Codes 

FEATURE 60 Feature Detail 

DETAIL 


IPIC 32 International Pre-subscription Indicator Code 

ISPID 21 ISDN Service Profile Identification 










LNEX 10 Line Number Extension Number 





LTOS 13 Line Type of Service 

MATN 34 Main/Alternate Telephone Number 




ORD 6 Order Number 

OTN 19 Out Telephone Number 


PIC 30 InterLATA Pre-subscription Indicator Code 


PRIBD 20 ISDN PRI “B” & “D” Channel Configuration 


230


7.3 RS Alphanumeric Glossary (continued) 

RS FORM 


PTKTYP 22 PBX Trunk Type 

PTLI 23 PBX Lead Telephone Line 

PULSE 52 Type of Pulsing 

RSQTY 5 Resale Quantity 

S 16 Suspend Activity Indicator 


SDI 33 Switched Data Identifier 

SGNL 50 Signaling 

SPLD 17 State Primary Line Designator 

SSIG 51 Start Signaling 

TCID 41 Transfer of Calls to Identifier 



TC NAME 42 Transfer of Calls to Name 


TC TO PRI 38 Transfer of Calls to Primary Number 

TC TO SEC 39 Transfer of Calls to Secondary Number 

TCOPT 35 Transfer of Call Options 

TERS 18 Terminal Numbers 

TNS 15 Telephone Numbers 




231


Resale Service 

V5 

8/00 


PON 

1 

VER AN 

3 

ATN 

2 4 

- - 

RSQTY 

5 

ORD 

6 

PG_of_ 

7 


LOCNUM 

8 

LNUM 

9 

LNEX 

1 0 

NPI 

11 

LNA 

12 

LTOS 

NOTYP 

TNS 

1 3 14 1 5 

- - 

S 

16 

SPLD 

17 

TERS 

1 8 

OTN 

1 9 

- - 

PRIBD 

2 0 

ISPID 

2 1 

PTKTYP 

PTLI 

22 2 3 

- - 

PTKCON 

24 

TSP 

2 5 

- 

SAN 

2 6 

CKR 

2 7 

ECCKT 

2 8 

FPI 

29 

PIC 

3 0 

LPIC 

3 1 

IPIC 

3 2 

SDI 

33 

MATN 

34 

TC OPT 

3 5 

LEAN 

3 6 

LEATN 

3 7 

- - 

TC TO PRI 

3 

8 

- - 

TC TO SEC 

3 9 

- - 

TC PER 

4 0 

TCID 

4 1 

TC NAME 

4 2 

TCID 

4 1 

TC NAME 

4 2 

JK CODE 

4 3 

JK NUM 

4 4 

JK POS 

4 5 

JR 

46 

NIDR 

47 

IWJK 

4 8 

IWJQ 

4 9 

SGNL 

5 0 

SSIG 

5 1 

PULSE 

5 2 

LSCP 

53 

BA 

54 

BLOCK 

5 5 

BA 

54 

BLOCK 

5 5 

CNAM 

5 6 

CFA 

5 7 

FA 

58 

FEATURE 

5 9 

FEATURE DETAIL 

6 0 

FA 

58 

FEATURE 

5 9 


6 0 





Resale Service (continued) 

V5 

8/00 


PON 

1 

VER AN 

3 

ATN 

2 4 

- - 

RSQTY 

5 

ORD 

6 

PG_of_ 

7 

Service Details (continued) 

FA 

58 

FEATURE 

5 9 


6 0 

FA 

58 

FEATURE 

5 9 


6 0 

FA 

58 

FEATURE 

5 9 


6 0 

FA 

58 

FEATURE 

5 9 


6 0 

FA 

58 

FEATURE 

5 9 


6 0 

FA 

58 

FEATURE 

5 9 


6 0 

TCMI 

6 1 

TCMESS 

6 2 





Resale Service 

V5 

8/00 


PON 

VER 

AN 

ATN 

- - 

RSQTY 

ORD 

PG_of_ 


LOCNUM LNUM LNEX 

NPI 

LNA 

LTOS 

NOTYP 

TNS 

- - 

S 

SPLD 

TERS 

OTN PRIBD ISPID PTKTYP 

- - 

PTLI 

- - 

PTKCON 

TSP 

- 

SAN 

CKR 

ECCKT FPI PIC LPIC IPIC SDI MATN TC OPT 

LEAN 

LEATN 

- - 

TC TO PRI 

- - 

TC TO SEC 

- - 

TC PER 

TCID 

TC NAME 

TCID 

TC NAME 

JK CODE JK NUM JK POS JR NIDR IWJK IWJQ SGNL 

SSIG 

PULSE LSCP BA BLOCK 

BA BLOCK 

CNAM 

CFA 

FA 

FEATURE 


FA 

FEATURE 






Resale Service (continued) 

V5 

8/00 


PON 

VER 

AN 

ATN 

- - 

RSQTY 

ORD 

PG_of_ 

Service Details (continued) 

FA 

FEATURE 


FA 

FEATURE 


FA 

FEATURE 


FA 

FEATURE 


FA 

FEATURE 


FA 

FEATURE 


TCMI 

TCMESS 





8.0 DID RESALE SERVICE (DRS) 

8.1 DID Resale Form 

This guide describes the DID Resale Service (DRS) Ordering Form entries. The DRS Form must 

always be associated with an administrative Local Service Request (LSR) Form and an End User 

(EU) Form. The DRS form contains two sections: 





The Service Details provides all the necessary feature detail for the provisioning of the telephone 

service for the LSP on behalf of the end user. 





237


8.2 DRS Form Fields 

8.2.1 DRS Administrative Section 




USAGE: 




EXAMPLE: 

8 2 4 Z 9 


Identifies the customer's version number. 

NOTE 1: 




00 – 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 



optional. 



EXAMPLE: A A 


238



Identifies the main account number assigned by the Network Service Provider (NSP). 

NOTE 1: 






USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 




is required. 




EXAMPLE: 

N 


Identifies the account telephone number assigned by the Network Service Provider (NSP). 

NOTE 1: 




ATN 


USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 








EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


239



Identifies the provider’s order number for the service requested. 

NOTE 1: 

USAGE: 

This number may be pre-assigned to the customer by the provider. 




EXAMPLE: 

C 2 3 4 5 6 

6. PG_of_ 


USAGE: 






240


8.2.2 DRS Service Details Section 



NOTE 1: 

USAGE: 

NOTE 1: 




Required when the ACT field is not "V" or "W" and the LNA field is 

populated, otherwise optional. 




9 9 9 

8. DIDNUM - DID Reference Number 

Identifies each DID group as a unique number and each additional DID group as a unique 

number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The DIDNUM is customer assigned and is returned on the Local Response 

to the ordering customer. 

Once DIDNUM is generated it cannot be changed and is retained through 



the request at the PON level. 






241






B = Port Out Working TN without Loop 

C = Port In Working TN 

D = Port In Reserved TN 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

USAGE: 


account. 

When the first position of the REQTYP field on the LSR Form is “C,” the 

only valid entry is “A.” 

When the first position of the REQTYP field on the LSR Form is “B,” the 

only valid entry is “A” or “B.” 

When the first position of the REQTYP field on the LSR Form is “E,” “F,” 

“M,” “N,” or “P,” the only valid entry is “C” or “D.” 




EXAMPLE: 

A 


Identifies the circuit number or sequential range of circuit numbers assigned by the customer. 

NOTE 1: 

USAGE: 

CKR is used by the customer as a cross reference to the provider's circuit 

ID(s) and in many cases to identify the customer's end-to-end service. 




EXAMPLES: 

L 0 0 0 2 - 0 0 2 4 

2 9 3 3 2 1 8 1 


242


11. DTNRACT - DID Telephone Number Activity 

Identifies the activity involved at the DID telephone number (TN) level. 


N = Add new TN Blocks 

D = Remove TN Blocks 

V = Convert existing TN Blocks as specified 

USAGE: 

NOTE 1: 


Required when the DTNRQ is populated, otherwise prohibited. 



EXAMPLE: 

N 

12. DTNRQ - DID Telephone Number Quantity 

Identifies the quantity of DID telephone numbers requested. 


1-9999 

USAGE: 





13. DTNR - DID Telephone Number Range 

Identifies the range of DID telephone numbers within the same switch. 

NOTE 1: 

USAGE: 

NOTE 1: 

If the blocks of DID numbers are not consecutive, additional appearances 

of DTNR must be populated. 


Required when DTNRACT field is populated, otherwise prohibited. 



EXAMPLE: 

2 0 3 - 5 2 2 - 1 2 0 0 - 1 2 5 9 


243


14. DSTNACT - Disassociated Telephone Number Activity 

Identifies the activity involved against the disassociated telephone number. 


X = Exclude 

I = Include 

USAGE: 

NOTE 1: 


Required when the DSTN field is populated, otherwise prohibited. 



EXAMPLE: 

X 

15. DSTNQ - Disassociated Telephone Number Quantity 

Identifies the quantity of disassociated telephone numbers. 

USAGE: 




EXAMPLE: 2 

16. DSTN - Disassociated Telephone Number 

Identifies the telephone number disassociated from the DID Telephone Number Range. 

USAGE: 




EXAMPLE: 2 0 3 - 5 2 2 - 1 2 3 5 


244


17. DTKACT - DID Trunk Activity 

Identifies the activity involved at the DID trunk level. 


N = Add new Trunks 

C = Change to existing Trunks 

D = Remove Trunks 

V = Convert existing Trunks as specified 

USAGE: 

NOTE 1: 


Required when the DTK field is populated, otherwise prohibited. 



EXAMPLE: 

N 

18. DTK - DID Trunk Quantity 

Identifies the quantity of trunks being requested. 

USAGE: 




EXAMPLE: 1 0 

19. DTGN - Trunk Group Number 

Identifies the DID Trunk Group Number which has been assigned by the provider. 

NOTE 1: 

USAGE: 

This field should be populated when previously provided. 



3 numeric characters minimum, 4 numeric 

characters maximum 


4 5 6 


245


20. DRTI - DID Route Index Number 

Identifies the Route Index Number assigned to the DID Trunk Group. 

NOTE 1: 

USAGE: 







2 4 6 

21. DTLI - DID Telephone Line Identifier 

The lead telephone line identifier assigned to the DID Trunk Group. 

NOTE 1: 

USAGE: 





EXAMPLE: 2 0 1 - 5 5 5 - 5 3 8 0 

22. DTKID - DID Trunk ID 

Identifies the trunk ID of the existing DID service. 

NOTE 1: 

USAGE: 





EXAMPLES: D 1 - 1 0 

D 1 0 1 - 1 1 0 

D 5 0 0 0 - 5 9 9 9 


246


23. DGOUT - DID Digits Out 

Identifies the number of digits outpulsed from the central office to the customer’s equipment. 

USAGE: 

NOTE 1: 


Required when the DTKACT field is “N”, otherwise optional. 



EXAMPLE: 4 

24. DPULSE - DID Type of Pulsing 

Identifies the type of pulsing requested for the DID service. 


DP = Dial Pulse 

MF = Multi Frequency 

DTMF = Dual-Tone Multi Frequency 

USAGE: 

NOTE 1: 





EXAMPLE: D P 

25. DSGNL - DID Signaling 

Identifies the type of signaling requested for the DID service. 


DST = Delay Dial Start 

IST = Immediate Start 

WST = Wink Start 

USAGE: 

NOTE 1: 





EXAMPLE: I S T 


247








USAGE: 

NOTE 1: 


Prohibited when the LSCP field is populated on the LSR Form, otherwise 

optional. 



EXAMPLE: 

A 


Identifies the activity for the blocking of calls. 


A = Add 

D = Delete 

N = No change 


USAGE: 

NOTE 1: 


Required when the BLOCK field is populated, otherwise prohibited. 



EXAMPLE: 

D 


248








D = No 1+ 

E = No 0+ 

F = No 1+ and 0+ 



J = No 700 

K = No 976 

L = No 915 

M = No 900 

N = No Casual Calling 


Q = No 411 

R = No Incoming (CENTREX) 

S = No 976, 900-303, 900-505 

T = No 900-303 

W = No 7 Digit Toll (CENTREX) 

Y = No 500 

Z = All 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

NOTE 2: 

Within this practice, the valid entries are “A”, “B” and “C”. 

Valid entry of “Z” may not include the same types of blocking by all 

providers. 


Required when the BA field is “A” or “D”. 




EXAMPLE: 

A 


249




NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 






or EATN field on the EU Form or the LEATN field is not populated, 




EXAMPLE: 

2 0 1 M 8 1 - 3 5 8 2 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 






or EATN field on the EU Form or the LEAN field is not populated, 




EXAMPLE: 

2 0 1 - 5 5 5 - 1 2 1 2 


250


31. REMARKS 


form. 

USAGE: 




EXAMPLE: 

D I S C O F F I R S T D I D I N G R O U 

P 


251


8.3 DRS Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the DID Resale Service Form 

fields. 

DRS FORM 






DGOUT 23 DID Digits Out 

DIDNUM 8 DID Reference Number 

DPULSE 24 DID Type of Pulsing 

DRTI 20 DID Route Index Number 

DSGNL 25 DID Signaling 

DSTN 16 Disassociated Telephone Number 

DSTNACT 14 Disassociated Telephone Number Activity 

DSTNQ 15 Disassociated Telephone Number Quantity 

DTGN 19 Trunk Group Number 

DTK 18 DID Trunk Quantity 

DTKACT 17 DID Trunk Activity 

DTKID 22 DID Trunk ID 

DTLI 21 DID Telephone Line Identifier 

DTNR 13 DID Telephone Number Range 

DTNRACT 11 DID Telephone Number Activity 

DTNRQ 12 DID Telephone Number Quantity 












252


DID Resale Service 

V5 

8/00 


PON 

1 

VER 

2 

AN 

ATN 

3 4 

- - 

ORD 

5 

PG _of_ 

6 


LOCNUM 

7 

DIDNUM 

8 

NPI 

9 

CKR 

1 0 

DTNRACT 

11 

DTNRQ 

1 2 

DTNR 

1 3 

- - 

- 

DSTNACT 

14 

DSTNQ 

DSTN 

1 5 1 6 

- - 

DSTN 

1 

DSTN 

6 - - 

1 6 

- - 

DTKACT 

17 

DTK 

1 8 

DTGN 

1 9 

DRTI 

2 0 

DTLI 

2 1 

DTKID 

2 2 

DGOUT 

2 3 

DPULSE 

2 4 

DSGNL 

2 5 

LSCP 

26 

BA 

27 

BLOCK 

2 8 

BA 

27 

BLOCK 

2 8 

LEAN 

LEATN 

2 9 3 0 

- - 


LOCNUM 

7 

DIDNUM 

8 

NPI 

9 

CKR 

1 0 

DTNRACT 

11 

DTNRQ 

1 2 

DTNR 

1 3 

- - 

- 

DSTNACT 

14 

DSTNQ 

DSTN 

1 5 1 6 

- - 

DSTN 

1 

DSTN 

6 - - 

1 6 

- - 

DTKACT 

17 

DTK 

1 8 

DTGN 

1 9 

DRTI 

2 0 

DTLI 

2 1 

DTKID 

2 2 

DGOUT 

2 3 

DPULSE 

2 4 

DSGNL 

2 5 

LSCP 

26 

BA 

27 

BLOCK 

2 8 

BA 

27 

BLOCK 

2 8 

LEAN 

LEATN 

2 9 3 0 

- - 

REMARKS 

3 1 





DID Resale Service 

V5 

8/00 


ORD 

PON VER AN 

PG _of_ 

ATN 

- - 


LOCNUM 

DIDNUM 

NPI 

CKR 

DTNRACT 

DTNRQ 

DTNR 

- - 

- 

DSTNACT 

DSTNQ 

DSTN 

- - 

DSTN 

- - 

DSTN 

- - 

DTKACT 

DTK 

DTGN DRTI DTLI DTKID 

DGOUT DPULSE DSGNL LSCP BA 

BLOCK 

BA BLOCK LEAN 

LEATN 

- - 


LOCNUM 

DIDNUM 

NPI 

CKR 

DTNRACT 

DTNRQ 

DTNR 

- - 

- 

DSTNACT 

DSTNQ 

DSTN 

- - 

DSTN 

- - 

DSTN 

- - 

DTKACT 

DTK 

DTGN DRTI DTLI DTKID 

DGOUT DPULSE DSGNL LSCP BA 

BLOCK 

BA BLOCK LEAN 

LEATN 

- - 

REMARKS 





9.0 CENTREX RESALE SERVICE 

9.1Centrex Resale Form 

To be completed. 


289


10.0 RESALE FRAME RELAY SERVICE 

10.1Resale Frame Relay Form 



290


11.0 RESALE PRIVATE LINE SERVICE 

11.1Resale Private Line Form 



291


12.0 PORT SERVICE 

12.1Port Service Form 



292


13.0 DIRECTORY SERVICE REQUEST (DSR) 

13.1 Directory Service Request Form 

This guide describes the Directory Service Request (DSR) Form entries. The DSR Form will 

always be associated with the Directory Listing Form. The DSR Form may also be associated 

with a Local Service Request (LSR) Form, an End User Information (EU) Form and a service 

specific form containing loop and location detail necessary for the provisioning of the request 

or it may be transmitted as a stand alone request. 

All information required for administrative, billing, and contact details are provided for in the 

various fields contained within page 1 of the DSR Form. 

The Administrative Section contains information pertaining to the directory listings and/or 

directory assistance listings being requested such as: purchase order number, version number, 

expected due date, requisition type, class of service, etc. 

The Bill Section provides billing account, billing name and address information. 

The Contact Section contains initiator information. 

The second page of this form is identified as Service Address Information. The first line of 

administrative entries is repeated. These fields provide identification linking the second page 

with the first page having identical entries (Fields 1 through 8). 


293


13.2 DSR Form Fields 



Identifies the COMMON LANGUAGE IAC code for the customer submitting the DSR and 


NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 







CCNA is not necessarily the customer to be billed for the service. The 

billed party should be specified in the ACNA field. 

If combined request, this entry must match the CCNA field on the LSR 

Form. 


• IAC Code 

NOTE 1: 

USAGE: 


751-100-112. 






294





NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The Purchase Order Number may be reused after two years from the due 

date of the original request. 

A unique number must be used for requests for listings of different end 

users or for subsequent requests for the same end user. 

If combined request, this entry must match the PON field on the LSR Form. 




EXAMPLE: 

8 2 4 Z 9 



NOTE 1: 

NOTE 2: 

Any reissuance of the request can use this entry to uniquely identify the 

form from any other version. 

If combined request, this entry must match the VER field on the LSR Form. 


00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 


Required when the SUP field on the LSR Form or the DSUP field is 




EXAMPLE: A A 


295


4. DSR NO - Directory Service Request Number 




NOTE 1: 

USAGE: 

NOTE 1: 

If combined request, this entry must match the DSR NO field on the LSR 

Form. 


Required on all supplements when furnished by the provider, otherwise 

optional. 


18 alphanumeric characters maximum 

EXAMPLE: 

3 1 2 3 4 5 6 7 8 9 0 1 

5. LOCQTY - Location Quantity 

Identifies the number of service locations for the service requested. 

USAGE: 





9 9 9 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 




Required when the ATN field is not populated, otherwise prohibited. 



EXAMPLE: 

1 2 3 - M O O - 4 9 9 9 


296




NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

USAGE: 

NOTE 1: 

It may or may not be the same as the working telephone number. 

If combined request, this entry must match the ATN field on the LSR 

Form. 

An ATN is a dialable number. 

Normally the primary number in the account. 


Required when the AN field is not populated, otherwise prohibited. 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 



NOTE 1: 

USAGE: 

NOTE 1: 




Required for conversion of end user accounts when the EATN field is not 




EXAMPLE: 

2 0 1 - M 8 1 - 3 5 8 2 


297



Identifies the end user’s existing account telephone number assigned by the current NSP. 

NOTE 1: 

USAGE: 

NOTE 1: 




Required for conversion of an end user account when the EAN field is not 




EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 

10. SC1 - Service Center 1 

Identifies the code used to represent the organization which processes a customer’s request for 

service. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

USAGE: 

NOTE 1: 

The providers will supply guidelines for choosing the appropriate 



The SC2 field will be supplied when the provider’s service center for 

processing Directory Assistance (DA) listings is different from the SC1 

field. 

When a DSR is submitted in conjunction with a LSR and the entry in this 

field is different than the SC field on the LSR Form, this field is used to 

communicate the provider's internal routing information. 


Required when it is a stand alone request or if different from the SC field 

on the LSR Form, otherwise optional. 





298




Directory Assistance (DA) listings. 

NOTE 1: 

NOTE 2: 

USAGE: 










USAGE: 






Identifies the date and time that the Directory Service Request is sent by the customer. 


U.S. Standard 

Metric Format 







AM or PM 

AM or PM 

NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 

0 5 - 2 2 - 1 9 9 6 - 1 1 1 5 A M 


299


14. EDD - Expected Due Date 

Identifies the customer's expected due date. 

NOTE 1: 

NOTE 2: 

On disconnect requests, this date represents the date billing is to stop on the 

involved service and can be no earlier than the date the request is received 

by the provider. 

When different expected due dates (EDD) are required these dates are 

stipulated using a separate request for each expected due date (EDD). 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

Windstream only uses the standard date format. 



hyphens) 

EXAMPLE: 0 3 - 2 2 - 1 9 9 6 

15. SCD - Service Completion Date 

Identifies the date dial tone is completed and listing information can be released to directory 

assistance and white pages systems for a post complete request. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 0 3 - 2 2 - 1 9 9 6 


300


16. PROJECT - Project Identification 

Identifies the project to which the request is to be associated. 

NOTE 1: 

NOTE 2: 

USAGE: 

Examples of the use of this field would be relating multiple service 

requests, previously negotiated orders, etc.. 

The provider may initiate the project identification and provide this to the 

customer who will populate the field when submitting a service request. 




EXAMPLE: 

M S 7 3 6 1 1 9 

17. DCHC - Directory Assistance Coordinated Hot Cut 

Indicates that the customer is requesting near seamless cutover activity. 

NOTE 1: 




Y = Yes 

NOTE 1: 

USAGE: 

An entry in this field requires a single time entry in the DADT field. 




EXAMPLE: 

Y 

18. DADT - Directory Assistance Due Time 

Identifies directory assistance due time. 

USAGE: 

NOTE 1: 


Windstream does provide a due time for directory assistance. 


301


19. REQTYP - Requisition Type and Status 

Identifies the type of service being requested and the status of the request. 

NOTE 1: 

NOTE 2: 

The first character of REQTYP specifies the type of service. 

The second character of REQTYP specifies the status of the request. 


1 st Character 

A = Loop 

B = Loop with NP 

C = Number Portability 

D = Retail/Bundled 

E = Resale 

F = Unbundled Local Switching (Port) 

G = Directory Assistance 

H = Directory Listings 

J = Directory Listings and Assistance 

K = Resale Private Line 

L = Resale Frame Relay 

M = Combined Loop and Unbundled Local Switching (Port) 

N = DID Resale 

P = CENTREX 

NOTE 1: 

NOTE 2: 

When directory services are ordered in combination with valid entries of 

“A”, “B”, “C”, “D”, “E” and “F”, the AFO field on the LSR Form should 

be used to identify the type of directory form request(s). 

Valid entries of “G”, “H” and “J” should only be used when requesting 

stand alone directory service(s). 

2 nd Character 

A = Service Inquiry 

B = Firm Order 

NOTE 1: 

USAGE: 

Firm order (B) is the only valid entry for stand alone directory service(s) 

requests. 




EXAMPLE: A B 


302


20. ACT - Activity 

Identifies the activity involved in this service request. 

NOTE 1: 

On a supplement to a request this field carries the original activity type. 



C = Change to an existing account, e.g., rearrangement, partial disconnect or 

addition 



V = Conversion of service to new LSP as specified 

W = Conversion of service to new LSP as is 


USAGE: 




EXAMPLE: 

N 

21. DSUP - Directory Supplement Type 

A supplement is any new iteration of a DSR. The entry in the DSUP field identifies the 

reason for which the supplement is being issued. 

NOTE 1: 

If combined request, this entry must match the SUP field on the LSR 

Form. 


1 = Cancel - Indicates that the pending order is to be cancelled in its entirety. 

NOTE 1: 

If the pending order was already completed as ordered, a 

separate request must be sent instead of the supplement. 

2 = Date Change - Indicates that only a change in the expected due date (EDD) is 

required. 

3 = Other - Any other change to the request. 

NOTE 1: 

NOTE 2: 

This may affect the previously requested EDD. 

Partial cancellations should also be entered with a "3" in 

the DSUP field. 

USAGE: 

NOTE 1: 


Prohibited on initial requests, otherwise required. 



EXAMPLE: 2 


303


22. EXP - Expedite 

Indicates that expedited treatment is requested for Directory Assistance (DA) purposes. This 

is known as special handling or online treatment. 


Y = This request should be expedited as a temporary update for Directory 

Assistance. An order with this field set to "F" must be submitted. 

F = This indicates that this is the follow up request for a request that was 

submitted with this field set to a value of "Y" or a follow up to a 

manual/verbal request. 

USAGE: 




EXAMPLE: 

Y 

23. RTR - Response Type Requested 

Identifies the type of Local Response requested by the customer. 


C = Confirmation 

E = Errors only (directory) 


H = Confirmation and Errors 

N = No response requested 

NOTE 1: 

NOTE 2: 

USAGE: 

“F” is not valid for stand-alone Directory Services orders. 

“E” and “H” are only valid on orders, which include Directory Service 

Requests. 




EXAMPLE: 

N 


304



Identifies the Exchange Carrier requesting service. 

NOTE 1: 












100-112. 

NOTE 2: 

USAGE: 






25. AGAUTH - Agency Authorization Status 

Indicates that the customer is acting as an end user's agent and has authorization on file. 


Y = Authorization on file 

USAGE: 

NOTE 1: 


Required when the customer is acting as an end user agent, otherwise 

optional. 



EXAMPLE: 

Y 


305


26. DATED - Date of Agency Authorization 

Identifies the date appearing on the agency authorization that was previously submitted to the 

provider. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 



Required when the AGAUTH field is “Y”, otherwise prohibited. 


hyphens) 

EXAMPLE: 0 6 - 2 0 - 1 9 9 6 

27. AUTHNM - Authorization Name 

Identifies the end user who signed the authorization. 

USAGE: 

NOTE 1: 


Required when the AGAUTH field is “Y”, otherwise prohibited. 



EXAMPLE: E N D U S E R N A M E 


306


28. TOS - Type of Service 

Identifies the type of service for the line ordered. 

NOTE 1: 

The type of service identifies the end user account as business, residential 

or government. 




2 = Residence 


4 = Coin 



A = Multi-line 


C = Coin 






L = xDSL 





F = Flat Rate 

G = Message 




N = Normal 


R = RCF 


W = WATS 


NOTE 1: 




307


28. TOS - Type of Service (continued) 

USAGE: 

NOTE 1: 


Required when the ACT field is “N”, “C”, “V” or “T” and the first position 

of the REQTYP field is “E”, otherwise optional. 



EXAMPLE: 1 A F F 

29. DLORD - Directory Listing Order Number 

Identifies the order number assigned by the provider. 

USAGE: 




EXAMPLE: 

N 0 6 2 2 0 0 1 1 

30. DAORD - Directory Assistance Order Number 

Identifies the order number assigned by the provider for directory assistance. 

NOTE 1: 

USAGE: 

May be used when a different order number is used for directory listings. 




EXAMPLE: 

N 0 6 2 2 0 0 1 1 

31. DRPON - Directory Related Purchase Order Number 

Identifies the PON of a related directory request. 

NOTE 1: 

USAGE: 

The DRPON field may be used for relating connect and disconnect service 

requests, or multiple requests for the same location and due date. 




EXAMPLE: 

8 2 4 Z 9 


308


32. DLRORD - Directory Related Order Number 

Identifies a related directory provider order number. 

USAGE: 

NOTE 1: 


Optional when the provider has preassigned a related order number, 




EXAMPLE: 

C 4 5 6 8 9 5 

33. DARORD - Directory Assistance Related Order Number 

Identifies the order number assigned by the provider receiving the request when a separate 

order number is assigned for directory assistance listings. 

USAGE: 

NOTE 1: 


Optional when the provider has preassigned a related order number for 

directory assistance listings, otherwise optional. 



EXAMPLE: 

N 0 6 2 2 0 0 1 1 


309


34. LSP AUTH - Local Service Provider Authorization 

Indicates the carrier code of the Local Service Provider that is providing existing service and 

has authorized the change to a new service provider. 

NOTE 1: 










in the United States and certain U.S. Territories, maintained by NECA. 


100-112. 

NOTE 2: 

USAGE: 






35. LSP AUTH DATE - Local Service Provider Authorization Date 

Identifies the date that appears on the LSP authorization previously provided to the new 

service provider. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLES: 0 5 - 1 2 - 1 9 9 6 

1 9 9 6 - 0 8 - 0 2 


310


36. LSP AUTH NAME - Local Service Provider Authorization Name 

Identifies the name of the person who signed the authorization letter. 

USAGE: 




EXAMPLE: J a n e S m i t h 

37. CUST - Customer Name 

Identifies the name of the customer who originated this request when that customer has not 

been assigned a CCNA. 

USAGE: 

NOTE 1: 


Required when the CCNA field is “CUS”, and the CC field is not 




EXAMPLE: 

A B C 

T E L C O 

38 DLQTY - Number of Listings 

Identifies the number of listing detail sections (control, instructions and indicators) in the 


NOTE 1: 

USAGE: 

DLQTY should be zero when the ACT field is populated with “W” for 

migrate as is, and the receiving company allows the listing to be retained. 




EXAMPLE: 1 2 


311



39. DBI1 - Directory Billing Account Number Identifier 1 

Identifies the service type of the Directory Billing Account Number 1 (DBAN1). 





L = Loop 



P = Port 

R = Resale 

U = Usage 





NOTE 1: 

USAGE: 

NOTE 1: 

The only valid entries for this practice are “C”, “D” and “O”. 


Required when the DBAN1 and DBAN2 fields are populated, otherwise 

optional. 



EXAMPLE: 

C 


312


40. DBAN1 - Directory Billing Account Number 1 



NOTE 1: 

The DBAN1 entry appearing on this form must be for the provider 

identified in the SC1 or SC2 field. 


Valid Directory Billing Account Number 

N = New Directory Billing Account Number Requested 

E = Existing 

USAGE: 

NOTE 1: 


Required when a new directory billing account number is requested, 




EXAMPLES: 2 0 1 - 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 







L = Loop 



P = Port 

R = Resale 

U = Usage 





NOTE 1: 

USAGE: 

NOTE 1: 



Required when the DBAN2 field is populated, otherwise optional. 



EXAMPLE: 

C 


313





NOTE 1: 





N = New Directory Billing Account Number Requested 

E = Existing 

USAGE: 

NOTE 1: 


Required when the DBI2 field is populated, otherwise optional. 



EXAMPLES: 2 0 1 - 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 

43. ACNA - Access Customer Name Abbreviation 

Identifies the COMMON LANGUAGE code of the customer to which the bill is to be 

rendered. 

NOTE 1: 

NOTE 2: 




For an occasional customer who has not and probably will not obtain an 

ACNA, enter “ZZZ” in this field. 


• IAC Code 

NOTE 1: 

USAGE: 


751-100-112. 




EXAMPLE: Z Z Z 


314


44. DEBD - Directory Effective Bill Date 


expected due date. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 0 4 - 0 2 - 1 9 9 7 

45. DBILLNM - Directory Billing Name 

Identifies the name of the person, office or company to whom the customer has designated 

that the bill be sent. 

USAGE: 

NOTE 1: 


Required when the DBAN1 or DBAN2 field is "N" and a billing profile is 

not established, otherwise optional. 



EXAMPLE: 

X Y Z C o r p o r a t i o n 

46. DSBILLNM - Directory Secondary Bill Name 

Identifies the name of a department or group within the designated DBILLNM entry. May 

also be used to specify the end user customer. 

USAGE: 




EXAMPLE: 

A c c o u n t s R e c e i v a b l e 


315


47. DTE - Directory Tax Exemption 

Indicates that the customer has submitted a tax exemption form to the provider. 


Entry Exempt From 

F Federal 

S State/Province 

C County or Local 

M Municipal 

A F & S 

B F & C 

K F & M 

D F & S & C 

E F & S & M 

G F & S & C & M 

H S & C 

I S & M 

J C & M 

L Letter on File 

N Non Exempt 

P S & C & M 

USAGE: 

NOTE 1: 






EXAMPLE: 

B 



NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the STREET field is used for the directory billing address. 






EXAMPLE: 

1 2 5 E M a i n S t r e e t 


316




NOTE 1: 

USAGE: 

This instance of the FLOOR field is used for the directory billing address. 




EXAMPLE: 3 2 



NOTE 1: 

USAGE: 

This instance of the ROOM/MAIL STOP field is used for the directory 

billing address. 




EXAMPLE: 1 K 1 5 1 A B C 2 0 


Identifies the city, village, township, etc.. 

NOTE 1: 

This instance of the CITY field is used for the directory billing address. 

USAGE: 

NOTE 1: 






EXAMPLE: 

L i v i n g s t o n 


317




NOTE 1: 

This instance of the STATE field is used for the directory billing address. 

NOTE 2: 



USAGE: 

NOTE 1: 






EXAMPLE: N J 



NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the ZIP field is used for the directory billing address. 







0 8 8 5 4 - 1 2 3 4 

M 5 A 1 X 7 

54. DBILLCON - Directory Billing Contact 


USAGE: 

NOTE 1: 






EXAMPLE: J a n e T D o e 


318


55. DTEL NO - Directory Telephone Number 


USAGE: 

NOTE 1: 






EXAMPLE: 

2 0 1 - 5 5 5 - 3 4 0 0 - 2 2 2 


319


13.2.3 Contact Section 

56. DINIT - Directory Initiator Identification 

Identifies the customer's representative who originated this request. 

NOTE 1: 

USAGE: 

This is the person who should be contacted if there are any questions 

regarding this request. Any authorizations of charges or changes are the 

responsibility of this person. 




EXAMPLE: J o h n S m i t h 

57. DTEL NO - Directory Telephone Number 

Identifies the telephone number of the initiator. 

USAGE: 




EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 0 0 - 2 2 6 2 

58. DEMAIL - Directory Electronic Mail Address 

Identifies the electronic mail address of the initiator. 

USAGE: 




EXAMPLE: 


C O M 


320


59. DFAX NO - Directory Facsimile Number 

Identifies the fax number of the initiator. 

USAGE: 




EXAMPLE: 9 0 8 - 3 3 6 - 2 9 8 0 



NOTE 1: 

This instance of the STREET field is used for the directory initiator’s 

address. 

USAGE: 

NOTE 1: 


Required when a customer does not have a customer initiator contact 

address profile, otherwise optional. 



EXAMPLE: 

1 3 2 E M a i n S t r e e t 



NOTE 1: 

This instance of the FLOOR field is used for the directory initiator’s 

address. 

USAGE: 




EXAMPLE: 3 2 


321




NOTE 1: 

This instance of the ROOM/MAIL STOP field is used for the directory 

initiator’s address. 

USAGE: 







NOTE 1: 

This instance of the CITY field is used for the directory initiator’s address. 

USAGE: 

NOTE 1: 






EXAMPLE: 

P i s c a t a w a y 



NOTE 1: 

NOTE 2: 

This instance of the STATE field is used for the directory initiator’s 

address. 



USAGE: 

NOTE 1: 






EXAMPLE: N J 


322




NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the ZIP field is used for the directory initiator’s address. 


Required when the customer does not have a customer initiator contact 





0 8 8 5 4 - 1 2 3 4 



form. 

USAGE: 




EXAMPLE: 

C U S T W A N T S T O A D D N O N - P U B 

T O M A I N L I N E 


323


13.2.4 Service Address Section 

67. AACT - Address Activity 

Identifies the address activity for this request. 


N = New service 

D = Delete service 

I = Insert new address 

O = Delete old address 

Z = No change to address 

NOTE 1: 

USAGE: 

When changing a service or delivery address, two transactions are 

recommended, the first transaction would have an AACT of "O" to specify 

the data to be deleted. The second transaction would have an AACT of "I" 

to specify the new data. 




EXAMPLE: 

N 



NOTE 1: 

USAGE: 







9 9 9 

- 


324



Identifies the name of the end user. 

NOTE 1: 

NOTE 2: 

USAGE: 

Name should be the same as End User Name field on the End User 

Information Form. 

Name in this field is not intended to be used for directory listings or 





EXAMPLE: 

J o e S m i t h 

70. AFT - Address Format Type 

Identifies the format of the address being supplied. 

NOTE 1: 

This instance of the AFT field is used for the service address. 


A = Rural route and / or box number 

B = Unnumbered 

C = Provider assigned house number 

D = Descriptive 

NOTE 1: 

USAGE: 

A value of “C” indicates a valid address where no house number exists; 

therefore, the provider has assigned an internal house number to facilitate 

provisioning. 




EXAMPLE: 

A 


325


71. SAPR - Service Address Number Prefix 

Identifies the prefix for the address number of the service address. 

USAGE: 

NOTE 1: 


Optional when the SANO field is populated, otherwise prohibited. 




NOTE 1: 



Suite 23A. 

72. SANO - Service Address House Number 

Identifies the number of the service address. 

NOTE 1: 

USAGE: 

NOTE 1: 

This field may contain a provider assigned house number. 


Required when the AFT field is “C”, otherwise optional. 




NOTE 1: 



73. SASF - Service Address Number Suffix 

Identifies the suffix for the address number of the service address. 

USAGE: 

NOTE 1: 


Optional when the SANO field is populated, otherwise prohibited. 




NOTE 1: 




326


74. SASD - Service Address Street Directional Prefix 

Identifies the street directional prefix for the service address. 


N = North 

S = South 

E = East 

W = West 





USAGE: 




EXAMPLE: S W 

NOTE 1: 



Suite 23A. 

75. SASN - Service Address Street Name 

Identifies the street name of the service address. 

NOTE 1: 

USAGE: 


other description for this service location. 




EXAMPLES: 


NOTE 1: 



Suite 23A. 



327


76. SATH - Service Address Street Type 

Identifies the thoroughfare portion of the street name of the service address. 

NOTE 1: 

USAGE: 







EXAMPLE: L N 

NOTE 1: 



Suite 23A. 

77. SASS - Service Address Street Directional Suffix 

Identifies the street directional suffix for the service address. 


N = North 

S = South 

E = East 

W = West 





USAGE: 




EXAMPLE: N W 

NOTE 1: 



Suite 23A. 


328


78. LD1 - Location Designator 1 


NOTE 1: 

NOTE 2: 

USAGE: 




Section. 




EXAMPLE: F l o o r 

NOTE 1: 



79. LV1 - Location Value 1 


NOTE 1: 

USAGE: 





EXAMPLE: 1 2 

NOTE 1: 




329




NOTE 1: 

NOTE 2: 

USAGE: 




Section. 




EXAMPLE: W i n g 

NOTE 1: 



Suite 23A. 



NOTE 1: 

USAGE: 





EXAMPLE: 2 

NOTE 1: 




330



Identifies additional specific information related to the address (e.g., building., floor, room). 

NOTE1: 

NOTE 2: 

USAGE: 




Section. 




EXAMPLE: S u i t e 

NOTE 1: 

Where STE is the third location designator for the following address 


Suite 23A. 



NOTE 1: 

USAGE: 






NOTE 1: 





NOTE 1: 

USAGE: 

This instance of the CITY field is used for the service address. 




EXAMPLE: 

C o n c o r d 


331


85. SAST - Service Address State/Province 


NOTE 1: 

NOTE 2: 

USAGE: 

This instance of the STATE field is used for the service address. 






EXAMPLE: C A 


Identifies the ZIP code, ZIP code + extension or postal code of the service address. 

NOTE 1: 

USAGE: 

This instance of the ZIP field is used for the service address. 





9 4 5 8 3 - 4 1 8 2 

M 5 A 1 X 7 

87. AAI - Additional Address Information 


NOTE 1: 

USAGE: 

This instance of the AAI field is used for the service address. 




EXAMPLE: 




332


13.3 DSR Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the Directory Service 

Request Form fields. 

DSR FORM 


AACT 67 Address Activity 

AAI 87 Additional Address Information 

ACNA 43 Access Customer Name Abbreviation 

ACT 20 Activity 

AFT 70 Address Format Type 

AGAUTH 25 Agency Authorization Status 



AUTHNM 27 Authorization Name 



CITY 51 City 

CITY 63 City 

CITY 84 City 

CUST 37 Customer Name 


DADT 18 Directory Assistance Due Time 

DAORD 30 Directory Assistance Order Number 

DARORD 33 Directory Assistance Related Order Number 

DATED 26 Date of Agency Authorization 

DBAN1 40 Directory Billing Account Number 1 


DBI1 39 Directory Billing Account Number Identifier 1 


DBILLCON 54 Directory Billing Contact 

DBILLNM 45 Directory Billing Name 

DCHC 17 Directory Assistance Coordinated Hot Cut 

DEBD 44 Directory Effective Bill Date 

DEMAIL 58 Directory Electronic Mail Address 

DFAX NO 59 Directory Facsimile Number 

DINIT 56 Directory Initiator Identification 

DLORD 29 Directory Listing Order Number 

DLQTY 38 Number of Listings 

DLRORD 32 Directory Related Order Number 

DRPON 31 Directory Related Purchase Order Number 

DSBILLNM 46 Directory Secondary Bill Name 

DSR NO 4 Directory Service Request Number 

DSUP 21 Directory Supplement Type 

DTE 47 Directory Tax Exemption 

DTEL NO 55 Directory Telephone Number 

DTEL NO 57 Directory Telephone Number 


333


13.3 DSR Alphanumeric Glossary (Continued) 

DSR FORM 




EDD 14 Expected Due Date 

EXP 22 Expedite 

FLOOR 49 Floor 

FLOOR 61 Floor 





LOCQTY 5 Location Quantity 

LSP AUTH 34 Local Service Provider Authorization 

LSP AUTH DATE 35 Local Service Provider Authorization Date 

LSP AUTH NAME 36 Local Service Provider Authorization Name 







PROJECT 16 Project Identification 


REQTYP 19 Requisition Type and Status 

ROOM/MAIL STOP 50 Room/Mail Stop 

ROOM/MAIL STOP 62 Room/Mail Stop 

RTR 23 Response Type Requested 

SANO 72 Service Address House Number 

SAPR 71 Service Address Number Prefix 

SASD 74 Service Address Street Directional Prefix 

SASF 73 Service Address Number Suffix 

SASN 75 Service Address Street Name 

SASS 77 Service Address Street Directional Suffix 

SAST 85 Service Address State/Province 

SATH 76 Service Address Street Type 

SC1 10 Service Center 1 


SCD 15 Service Completion Date 

STATE 52 State/Province 


STREET 48 Street Address 


334


13.3 DSR Alphanumeric Glossary (Continued) 

DSR FORM 


STREET 60 Street Address 

TOS 28 Type of Service 


ZIP 53 ZIP/Postal Code 




335



Directory Service Request 

V5 

8/00 

CCNA 

1 

PON 

2 

VER 

3 

DSR NO 

4 

LOCQTY 

5 

AN 

6 

ATN 

7 

- - 

EAN 

EATN 

8 9 

- - 

SC1 

1 0 

SC2 PG _of_ 

1 1 1 2 

D/TSENT 

1 3 

EDD 

1 4 

SCD 

1 5 

PROJECT 

1 6 

DCHC 

17 

DADT REQTYP ACT 

1 8 1 9 20 

DSUP 

21 

EXP 

22 

RTR 

23 

CC 

2 4 

AGAUTH 

25 

DATED 

2 6 

AUTHNUM 

2 7 

TOS 

2 8 

DLORD 

2 9 

DAORD 

3 0 

DRPON 

3 1 

DLRORD 

3 2 

DARORD 

3 3 

LSP AUTH 

3 4 

LSP AUTH DATE 

3 5 

LSP AUTH NAME 

3 6 

CUST 

3 7 

DLQTY 

3 8 

Bill Section 

DBI1 

39 

DBAN1 

4 0 

DBI2 

41 

DBAN2 

4 2 

ACNA 

4 3 

DEBD 

4 4 

DBILLNM 

4 5 

DSBILLNM 

4 6 

DTE 

47 

STREET 

4 8 

FLOOR 

4 9 


5 0 

CITY 

5 1 

STATE 

5 2 

ZIP 

5 3 

DBILLCON 

5 4 

DTEL NO 

5 5 

- - 

Contact Session 

- 

DINIT 

DTEL NO 

5 6 5 7 

- - 

- 

DEMAIL 

5 8 

DEMAIL (continued) 

DFAX NO 

5 9 

- - 

STREET 

6 0 

FLOOR 

6 1 


6 2 

CITY 

6 3 

STATE 

6 4 

ZIP 

6 5 

REMARKS 

6 6 






CCNA 

1 

ATN 

7 

PON 

2 

- - 

EAN 

Service Address Section 

AACT 

67 

LOCNUM 

6 8 

NAME 

6 9 

Directory Service Request (continued) 

VER 

3 

DSR NO 

4 

EATN 

8 9 

- - 

AFT 

70 

SAPR 

7 1 

LOCQTY 

5 

SANO 

7 2 

AN 

6 

SC1 

1 0 

CITY 

8 4 

SC2 PG _of_ 

1 1 1 2 

SASN 

SATH 

SASS 

7 5 7 6 

7 7 

LD1 

7 8 

SAST ZIP 

8 5 8 6 

LV1 

7 9 

LD2 

8 0 

AAI 

8 7 

LV2 

8 1 

LD3 

8 2 

LV3 

8 3 

SASF 

7 3 

SASD 

7 4 

V5 

8/00 


AACT 

67 

LOCNUM 

6 8 

NAME 

6 9 

AFT 

70 

SASN 

SATH 

SASS 

7 5 7 6 

7 7 

LD1 

7 8 

SAST ZIP 

8 5 8 6 

LV1 

7 9 


AACT 

67 

LOCNUM 

6 8 

NAME 

6 9 

LD2 

8 0 

AAI 

8 7 

LV2 

8 1 

LD3 

8 2 

SASN 

SATH 

SASS 

7 5 7 6 

7 7 

LD1 

7 8 

SAST ZIP 

8 5 8 6 

LV1 

7 9 

LD2 

8 0 

AAI 

8 7 

LV2 

8 1 

LD3 

8 2 

AFT 

70 

SAPR 

7 1 

LV3 

8 3 

SAPR 

7 1 

LV3 

8 3 

SANO 

7 2 

SANO 

7 2 

CITY 

8 4 

CITY 

8 4 

SASF 

7 3 

SASF 

7 3 

SASD 

7 4 

SASD 

7 4 






Directory Service Request 

V5 

8/00 

CCNA PON VER DSR NO LOCQTY AN 

ATN 

- - 

EAN 

EATN SC1 SC2 

- - 

D/TSENT EDD SCD PROJECT DCHC DADT REQTYP ACT DSUP 

PG _of_ 

EXP RTR CC AGAUTH 

DATED AUTHNUM TOS DLORD 

DAORD 

DRPON DLRORD DARORD 

LSP AUTH 

LSP AUTH DATE 

LSP AUTH NAME CUST DLQTY 

Bill Section 

DBI1 DBAN1 DBI2 DBAN2 ACNA DEBD DBILLNM 

DSBILLNM DTE STREET FLOOR ROOM/MAIL STOP 

CITY 

STATE 

ZIP 

DBILLCON 

DTEL NO 

- - 

Contact Session 

- 

DINIT 

DTEL NO 

- - 

- 

DEMAIL 

DEMAIL (continued) DFAX NO 

STREET 

FLOOR ROOM/MAIL STOP 

- - 

CITY STATE ZIP 

REMARKS 






Directory Service Request (continued) 

CCNA PON VER DSR NO LOCQTY AN 

V5 

8/00 

ATN 

- - 

EAN 

EATN SC1 SC2 PG _of_ 

- - 


AACT LOCNUM NAME AFT SAPR SANO SASF SASD 

SASN 

SATH 

SASS 


CITY 

SAST 

ZIP 

AAI 



SASN 

SATH 

SASS 


CITY 

SAST 

ZIP 

AAI 



SASN 

SATH 

SASS 


CITY 

SAST 

ZIP 

AAI 





14.0 DIRECTORY LISTING (DL) 

14.1 Directory Listing Form 

The Directory Listing (DL) Form is prepared by the LSP and is forwarded to the provider. 

This form provides the administrative and listing information associated with the customer's 

request. It is always associated with a DSR. 

All information required for ordering listings is provided in the various fields contained 

within the DL Form. 

The Listing Control Section provides entries for the type of activity and listing involved, the 

type of account for which the listing is being requested, etc. 

The Listing Instruction Section provides specific listing details. 

The Delivery Section contains information pertaining to the quantity and address for directory 

delivery. 

The Advertising Section contains information for the Yellow Pages. 


341


14.2 DL Form Fields 



Identifies the COMMON LANGUAGE IAC code for the customer submitting the DSR and 


NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 







CCNA is not necessarily the customer to be billed for the service. The 

billed party should be specified in the ACNA field. 

If combined request, this entry must match the CCNA field on the LSR 

Form. 


• IAC Code 

NOTE 1: 

USAGE: 


751-100-112. 






342





NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The Purchase Order Number may be reused after two years from the due 

date of the original request. 

A unique number must be used for requests for listings of different end 

users or for subsequent requests for the same end user. 

If combined request, this entry must match the PON field on the LSR Form. 




EXAMPLE: 

8 2 4 Z 9 



NOTE 1: 

NOTE 2: 



If combined request, this entry must match the VER field on the LSR Form. 


00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 


Required when the SUP field on the LSR Form or the DSUP field on the 

DSR Form is populated, otherwise optional. 



EXAMPLE: A A 


343


4. DSR NO - Directory Service Request Number 




NOTE 1: 

USAGE: 

NOTE 1: 

If combined entry, this entry must match the DSR NO field on the LSR 

Form. 


Required on all supplements when furnished by the provider, otherwise 

optional. 



EXAMPLE: 

3 1 2 3 4 5 6 7 8 9 0 1 



NOTE 1: 

NOTE 2: 

If combined request, this entry must match the ATN field on the LSR 

Form. 

This entry may or may not be the same as the working telephone number. 



USAGE: 


NOTE 1: Required when the AN field is not populated, otherwise prohibited. 



EXAMPLE: 2 0 1 - 9 8 1 - 3 5 0 0 


344



Identifies an account number that may be provided by the NSP. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

This entry must match the AN field on the LSR Form. 





USAGE: 

NOTE 1: 


Required when the ATN field is not populated, otherwise prohibited. 



EXAMPLE: 

A B 3 2 2 1 4 7 



service. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 




The SC2 field will be supplied when the provider’s service center for 

processing Directory Assistance (DA) listings is different from the SC1 

field. 






345



Identifies the code used to represent the organization, which processes a customer’s request 

for Directory Assistance (DA) listings. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 





Required when the SC2 field is different from the SC1 field, otherwise 

optional. 






USAGE: 






346


14.2.2 Listing Control Section 

10. LACT - Listing Activity Indicator 

Identifies the activity involved for this listing request. 


N = New listing 

D = Delete listing 

I = Change listing (new data to be inserted) 

O = Change listing (old data) 

Z = No change to listing 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1 

NOTE 2 

When changing a listing, two transactions are recommended. The first 

transaction would have a LACT entry of "O" to specify the data to be 

deleted. The second transaction would have a LACT entry of "I" to specify 

the new data. 

LACT of “Z” is used: 

When listing is migrate as-is 

Delivery Section only request. 


LACT of “Z” may not be used if the ACT field on the LSR Form is a “T”. 

When LACT is “D” or “Z” all other fields on the DL form are optional. 



EXAMPLE: 

N 

11. ALI - Alphanumeric Listing Identifier Code 

Identifier assigned to each listing to uniquely identify each listing for a Main Telephone 

Number (MTN) from a customer. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

Allows for multiple listings for the same MTN from a single customer. 

Unique for life of listings and spans requests. 

Used to relate listing request to confirmation and error detail. 




EXAMPLE: A 4 


347


12. RTY - Record Type 

Identifies the type of listing being submitted with respect to pricing and tariffs. 

NOTE 1: 

A cross-reference listing specifies the referral name. The LTXTY field 

must contain the value of “CR” and the LTEXT field contains the name 

being referenced. The OMTN and ADI fields must be populated if the 

address and/or telephone number is to be omitted. 


1 st Character (Area) 

F = Foreign 

L = Local 

S = Secondary Listing 

2 nd & 3 rd Characters (Type of Listing) 

AL = Additional listing 

AM = Additional main 

AS = Answer service 

AU = Alternate user listing 

CM = Client main 

CR = Cross reference listing 

EN = Enterprise 

ML = Main listing 

USAGE: 

NOTE 1: 

NOTE 2: 


Required when LACT is “N”, “I”, or “O”, otherwise optional. 

Windstream does not support the use of “AM” as a valid entry in this field. 



EXAMPLE: L M L 


348


13. LTY - Listing Type 

Identifies the type of listing with respect to publication and Directory Assistance (DA) 

appearance rules. 


1 = Listed - appears in DA and the directory 

2 = Non Listed - appears only in DA 

3 = Non Pub - does not appear in the directory and telephone number does not 

appear in DA 

4 = Non Pub Emergency - does not appear in the directory, customer may be 

contacted in an emergency 

5 = Non Pub Special - does not appear in the directory nor DA, customer never 

wants to be contacted 

6 = Omit DA - listing only appears in the published directory 

7 = No Appearance - primary telephone number has no listing in the directory 

or DA, but additional station numbers may be listed 

8 = Temporary Listing - appears only in DA for a short interval 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

Valid entries are generic and may have different interpretations in different 

jurisdictions. 

Valid entries “3” and “4” will not display the number in DA. The listing 

may not appear at all based on local tariffs/practices. 

Valid entry “7” may not have charges based on local tariffs. 





EXAMPLE: 2 

14. EOS - End User’s Other Service 

Identifies an end user’s listed or non-published service. 

NOTE 1: 

USAGE: 

For some types of non listed services, an end user may be required to have 

other listed or non published service 




EXAMPLE: 3 0 3 - 5 5 5 - 1 2 3 4 


349


15. STYC - Style Code 

Identifies whether the listing is a straight line, Straight Line Under (SLU) header, etc.. 


CI = Caption indent 

SH = SLU header 

SI = SLU indent 

SL = Straight line 

USAGE: 

NOTE 1: 





EXAMPLE: S L 

16. TOA - Type of Account 

Identifies the type of account for this listing. 

NOTE 1: 

Determines placement in split directories and directory assistance. 


B = Business 

C = County Government 

F = Federal Government 

L = Local or City Government 

R = Residence 

S = State Government 

BP = Business class, person name 

MI = Military 

PO = Port 

RE = Regional 

RP = Residence class, business name 

SC = School 

SD = Special District 

TR = Tribal 

TW = Township 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

TOA valid entries are generic and may have different interpretations in 

different jurisdictions. 

A valid entry of "BP" or "RP" may cause listings to appear in both business 

and residence sections of split directories and directory assistance. 





EXAMPLE: 

F 


350


17. DOI - Degree of Indent 

Identifies the degree of indentation for this listing. 


0-7 

NOTE 1: Straight-line listings, SLU headers and caption headers are always zero (0). 

NOTE 2: 

USAGE: 

NOTE 1: 

SLU indents, caption indents and caption sub-headers must be greater than 

zero (0). 





EXAMPLE: 1 

18. WPP - White Page Products 

Identifies information about the White Page Products, Signature Listings, Personality Logo 

and Lines of Distinction. 


Specified local negotiations, e.g.: 

LGOO1-LGOO9, 

LGOA1-LGOZ9 = Logo 

SB = Signature Bold 

SS = Signature Script 

ZL1-ZL8 = Line of Distinction (place text in LTEXT field) 

NOTE 1: 

USAGE: 

Multiple values may be supplied separated by commas. 




EXAMPLES: S S 

S B , Z L 1 


351



Identifies the service location address/segment and each additional service address/segment 

with a unique number. 

NOTE 1: 

NOTE 2: 

USAGE: 



This number refers back to the LOCNUM field on the DSR or EU Form. 





20. DLNUM - Directory Listing Number 

Identifies each listing within a request with a unique number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The DLNUM is customer assigned. 

Once DLNUM is generated, it cannot be changed and is retained through 









352


21. MTN - Main Telephone Number 

Identifies the main telephone number used to link the main listing with any other associated 

listings. 




NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 

The MTN of a main listing and the MTN on any associated listings is the 

LTN of the main listing. 


Prohibited when REQTYP field on the LSR Form is “C” and the request is 



“C”, the request is for a non-simple port, and the LACT is “N”, “I”, “O” or 

blank. 




EXAMPLE: 2 0 1 - 9 8 1 - 3 5 0 0 

22. PPTN - Previous Provider Telephone Number 

Identifies the end user's previous listed telephone number if the user is changing providers and 

telephone numbers. 

NOTE 1: 

USAGE: 

This field may useful to associate advertising with a migrate and telephone 

number change. 




EXAMPLE: 2 0 1 - 9 8 1 - 3 5 0 1 


353


23. DDQTY - Number of Delivery Segments 

Identifies the number of delivery address/information segments in this service request. 

USAGE: 

NOTE 1: 


Required when any delivery address/information segments are different 

from the service address or when directories are to be delivered to multiple 

addresses, otherwise optional. 



EXAMPLE: 2 

24. LTXQTY - Number of Listing Text Segments 

Identifies the number of listing text segments in this service request. 

NOTE 1: 

USAGE: 

NOTE 1: 

The listing text segments contain the LTXTY, LTXNUM and LTEXT 

elements. 


Required when any listing text segments are populated, otherwise optional. 



EXAMPLE: 2 


354


14.2.3 Listing Indicators Section 

25. DML - Direct Mail List 

Indicates whether this listing is to be omitted from any direct mail lists. 


O = Omit 

USAGE: 




EXAMPLE: 

O 

26. NOSL - No Solicitation Indicator 

Indicates that this listing is not to be used for solicitation purposes. 

NOTE 1: 

NOTE 2: 

May cause an identifying mark to be shown in published directory. 

May not prevent listing from being included in telemarketing lists. 


Y = Print indicator 

USAGE: 




EXAMPLE: 

Y 

27. TMKT - Telemarketing 

Indicates that this listing is to be omitted from any telemarketing lists. 


O = Omit 

USAGE: 




EXAMPLE: 

O 


355


28. BRO - Business/Residence Placement Override 

Identifies an override of the normal placement of business or residence listings. 

NOTE 1: 

Overrides placement that would normally happen based on the value of the 

TOA field. 


A = Place listing in both business and residence sections in directory and DA 

B = Place listing only in the business section in directory and DA 

R = Place listing only in the residence section in directory and DA 

USAGE: 




EXAMPLE: 

A 

29. ADV - Advance to Directory Indicator 

Indicates a request that the listing be advanced to the directory publisher in order to meet a 

book close. 

NOTE 1: 

NOTE 2: 

This is a generic definition. Based on local practices, additional orders may 

be required for DA listing and/or permanent inclusion in the directory. 

Local practices will determine date range during which ADV will be 

accepted. 


Y = Yes 

USAGE: 




EXAMPLE: 

Y 

30. STR - Street Address Directory 

Identifies whether this listing is to be omitted from the street address (reverse) directory. 


O = Omit 

USAGE: 




EXAMPLE: 

O 


356


31. DLNM - Dual Name Listing 

Indicates that this listing contains multiple first names, e.g., Smith Betty & John and that in 

Directory Assistance (DA) the listing should retrieve with a request for Smith John or Smith 

Betty. 


Y = Yes 

USAGE: 

NOTE 1: 


Required when the LNFN field is a dual name, otherwise prohibited. 



EXAMPLE: 

Y 

32. PROF - Professional Identifier 

Indicates that this is a professional listing. 


Y = Yes 

USAGE: 




EXAMPLE: 

Y 

33. DIRIDL - Directory Identifier 

Identifies the directory in which to place the listing. 


YPPA Code 

NOTE 1: 

USAGE: 

NOTE 1: 

May be alphanumeric when assigned by the local provider where YPPA 

code does not exist or is ambiguous. 


Required when the first position of the RTY field is “F” or “S”, otherwise 

optional. 



EXAMPLE: 3 4 5 6 7 8 


357


34. DIRNAME - Directory Name 

Identifies the name of a directory in which to place the listing. 


Directory name 

USAGE: 

NOTE 1: 


Required when the first position of the RTY field is “F” and the DIRIDL 

field is not populated, otherwise optional. 



EXAMPLE: 

G r a n d J u n c t i o n N E 

35. DIRSUB - Directory Subsection 

Identifies the subsection of a directory in which to place the listing. 


Directory subsection name 

USAGE: 

NOTE 1: 


Required when the valid entry in the DIRIDL field or the DIRNAME field 

specifies a sectionalized book, otherwise optional. 



EXAMPLE: 

F r e s n o 

36. LID1 - Scoping Zip 

Identifies the zip code or postal code which will aid in identifying the directory in which to 

place the listing. 

NOTE 1: 

USAGE: 

May not be used for foreign listings. 




EXAMPLE: 9 4 5 6 5 - 6 2 5 7 


358


37. LID2 - Additional Scoping Information 

Identifies additional descriptive scoping information required to identify the directory in 

which to place the listing, e.g., tax area rate (TAR) code. 

NOTE 1: 

USAGE: 

May be specified for all listings. 




EXAMPLE: W E S T S I D E 

38. OMSD - Omit From Secondary Directory 

Indicates in which secondary directory or directories this listing is not to appear. 


YPPA code 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 


code does not exist or is not unique. 

Optionally followed by the sub-directory name. 

Up to four of these identifiers may be supplied, separated by commas. 




EXAMPLE: 

1 2 3 4 5 6 , 3 4 8 7 6 2 F R E S N O , 9 8 7 7 7 

8 


359


14.2.4 Listing Instruction Section 

39. LTN - Listed Telephone Number 

Identifies the telephone number that may be included in the directory and/or quoted in 

Directory Assistance (DA). 




NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 1: 

The usage is based on the LTY, RTY and STYC field entries. 


Prohibited when the REQTYP field on the LSR Form is “C” and the 

request is for a simple port. 

Required when the NSTN field is not populated and there is to be a 

published or non-pub telephone number, otherwise optional. 



EXAMPLE: 2 0 1 - 9 8 1 - 3 5 0 0 

40. NSTN - Non Standard Telephone Number 

Identifies a telephone number which is not in the standard North American Numbering Plan 

format, e.g., vanity numbers, Enterprise, 911. 

NOTE 1: 

USAGE: 

NOTE 1: 

When NSTN is a vanity number, the numeric equivalent is required in the 

LTN field. 


Required when the LTN field is not populated, otherwise optional. 



EXAMPLES: 

E n t e r p r i s e 4 - 1 2 3 4 

4 1 4 2 2 7 H E L P 


360


41. OMTN - Omit TN 

Indicates whether or not the telephone number is to be omitted from the listing. 

NOTE 1: 

This field should be set when LTXTY is “XL” or “CR” with LTEXT 

containing the See “verbiage”. 


O = Omit 

USAGE: 




EXAMPLE: 

O 

42. LEX - Local Exchange 

Indicates the provider's local NPA and NXX. 

NOTE 1: 

USAGE: 

The telephone number being listed is not local to the service address 



7 numeric characters (including 1 hyphen) 

EXAMPLE: 5 1 0 - 4 7 5 

43. DNA - Do Not Abbreviate 

Indicates data in supplied fields must not be abbreviated. 


1 = Do not abbreviate listed name 

2 = Do not abbreviate thoroughfare 

3 = Do not abbreviate locality (community) 

4 = Do not abbreviate listed name and thoroughfare 

5 = Do not abbreviate listed name and locality 

6 = Do not abbreviate thoroughfare and locality 

7 = Do not abbreviate name, thoroughfare and locality. 

NOTE 1: 

USAGE: 

If field is not supplied, or if prohibited by publisher, listed appearance will 

default to publisher’s rules. 




EXAMPLE: 1 


361


44. LNPL - Letter Name Placement 

Identifies the alphabetic placement of the listing based on the LNLN field. 


L = Letter placement 

NOTE 1: 

USAGE: 

Listing placement will default to word placement unless "L" (letter 

placement) is specified. LNLN = ABC with letter placement would file as 

A B C. LNLN = ABC without letter placement would file as Abc. Both 

would print as ABC. 




EXAMPLE: 

L 

45. LNLN - Listed Name Last 

Indicates the first word for business listings or the complete last name for residence listings. 

USAGE: 




EXAMPLES: 

A m e r i c a n 

S a i n t J a m e s 

K i l e y - S m i t h 


362


46. LNFN - Listed Name First 

Identifies the continuation of the name for Business and Government listings. For residence 

listings it identifies the first name(s), middle name(s) and initials. 

USAGE: 

NOTE 1: 


Required when the TOA field is “R”, otherwise optional. 



EXAMPLES: 

R e d C r o s s 

M a r y & J o h n 

47. DES - Designation 

Indicates the professional designation phrase of a business listing. Typically prints in the 

white pages and is used to identify the type of business when it is not inherently obvious from 

the name. (e.g., Bob Smith and Daughters plmbr) 


Designation abbreviations 

NOTE 1: 

USAGE: 

Providers will supply customers with a list of allowable values, (e.g., atty, 

plmbr). 




EXAMPLES: 

p l m b r 

M F S C 


363


48. TL - Title of Lineage 

Indicates a phrase used to designate lineage of a listed person, e.g., Jr, Sr, III, etc.. 

NOTE 1: 

USAGE: 

Used for listed name or first name in a dual name listing. 




EXAMPLE: J r 

49. TITLE1 - Title of Address 1 

Indicates a phrase used to address a listed person, e.g., Mr, Dr, Rev, Ms. 

NOTE 1: 

NOTE 2: 

USAGE: 


May also contain academic degree abbreviations, military rank, etc.. 




EXAMPLES: D r 

P h D 

M a j 

50. TITLE2 - Title of Address 2 

Indicates additional phrases used to further identify the individual, e.g., degrees, military rank. 

NOTE 1: 

USAGE: 

NOTE 1: 



Optional when the TITLE1 field is populated, otherwise prohibited. 



EXAMPLE: U S M C R e t 


364


51. TLD - Title of Lineage for Dual Name 

Indicates a phrase used to designate lineage for the second name of a dual name listing, e.g., 

Jr, Sr, III, etc.. 

USAGE: 




EXAMPLE: J r 

52. TITLE1D - Title of Address 1 for Dual Name 

Indicates a phrase used to address the second name of a dual name listing, e.g., Mr, Dr, Rev, 

Ms. 

NOTE 1: 

USAGE: 

May also contain academic degree abbreviations, military rank, etc.. 




EXAMPLES: D r 

P h D 

M a j 

53. TITLE2D - Title of Address 2 for Dual Name 

Indicates additional phrases used to further identify the second name of the dual name listing, 

e.g., degrees, military rank. 

USAGE: 

NOTE 1: 


Optional when the TITLE1D field is populated, otherwise prohibited. 



EXAMPLE: U S M C R e t 


365


54. NICK - Nickname 

Indicates the listed person’s nickname. 

NOTE 1: 

USAGE: 

This is in addition to the Listed Name fields (LNLN, LNFN). 




EXAMPLE: G o m e r 

55. PLA - Place Listing As 

Identifies the special filing words that should be used instead of the listed name if the 

customer wishes to override the normal alphabetizing. 

NOTE 1: 

NOTE 2: 

USAGE: 

This is used, in particular, for words that are numeric, e.g., 1040 Tax could 

file as One Zero Forty Tax, Ten Forty Tax, One Zero Four Zero Tax. 

May be in upper or lower case. The result will be the same. 




EXAMPLE: 

T E N F O R T Y T A X 


366


56. LTXNUM - Line of Text Reference Number 

Identifies each line of information for a listing with a unique number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

The LTXNUM is customer assigned. 


the request at the DLNUM level. 

When multiple lines of text are requested for a single LTXTY type, this 

field indicates the sequence in which the text for that LTXTY type is 

requested to appear. 


Required when the LTEXT field is populated, otherwise optional. 



EXAMPLE: 0 1 

57. LTXTY - Listing Text Type 

Identifies the type of the associated text that will appear in the directory to assist the end user. 

NOTE 1: 

This is associated with an LTEXT or LPHRASE field. 


AC = Alternate Call 

ADR = Address only indent 

CR = Cross Reference 

EM = E-Mail text 

ITD = Indent text designation 

ITX = Indent text 

LOI = Line of information 

OP = Other predefined phrase 

TNC = TN text centered 

TNL = TN text left 

TNR = TN text right 

TT = TT text 

URL = Internet address 

WPP = White Page Product Text 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

“CR” is valid only if positions 2 and 3 of the RTY field are “CR”. 

“WPP” is only valid if the WPP field is populated. 

“TNC”, “TNL” and “TNR” are only valid if associated with a listing that 

has a telephone number and the OMTN field is not “O”. 

There may be character restrictions based upon local practices and Internet 

standards for E-mail and Internet text. 


367


57. LTXTY - Listing Text Type (continued) 

NOTE 5: 

NOTE 6: 

NOTE 7: 

NOTE 8: 

USAGE: 

NOTE 1: 

“ITX” and “ITD” are only valid if the DOI field is not “0”, and if a listing 

has an “ITD” entry, it must immediately follow an “ITX” entry. 

“TT” is only valid if positions 2 and 3 of the RTY field are “XL” or “AL”. 

“OP” is used to reference company specific phrases that are defined in the 

LPHRASE field. 

“ADR” is only valid if the DOI field is not zero. Address information is 

supplied in the listed address fields. 


Required when positions 2 and 3 of the RTY field are “CR”, otherwise 

optional. 



EXAMPLE: W P P 

58. LPHRASE - Listing Phrase 

Identifies a pre-defined phrase associated with a listing. 


1 = TDD (Telecommunication Device for the Deaf) only 

2 = TTY (Teletypewriter) only 

3 = TTY-TDD only 

4 = TDD-TTY only 

5 = Voice and TTY 

6 = Voice and TDD 

7 = TTY and voice 

8 = TDD and voice 

9 = TT (Text Telephone) only 

10 = TT and voice 

11 = Voice and TT 

A0-Z9 = Company specific defined phrase 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

Valid entries 1-11 are used when the LTXTY field is “TT”. 

Valid entries A0-Z9 are used when the LTXTY field is “OP”. 

For those valid entries that list two communication choices, the end user’s 

preference is listed first. 


Required when LTXTY field is “TT” or “OP”, otherwise prohibited. 



EXAMPLE: 2 2 


368


59. LTEXT - Line of Text 

Identifies the descriptive or informative text that will appear in the directory and directory 

assistance. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

This is associated with a listing line. 

Contains the text for listing text types defined in the LTXTY field. 

Required when an indent has text other than address and/or telephone 

number. 


Required when the LTXTY field is “AC”, “CR”, “EM”, “ITD”, “ITX”, 

“LOI”, “TNC”, “TNL”, “TNR”, “URL” or “WPP”, otherwise prohibited. 



EXAMPLE: 

C a l l b e t w e e n 9 a n d 5 


369


60. ACA - Alternate Call Authorization 

Indicates authorization has been obtained to list the alternate call number, when the requester 

is not the LSP owning the telephone number listing. 


Y = Alternate Call/Answering Service Listing is authorized 

USAGE: 

NOTE 1: 


Optional when the LTXTY field is “AC” or “AS”, otherwise prohibited. 



EXAMPLE: 

Y 

61. ADI - Address Indicator 

Identifies that listing address elements should be omitted from Directory Assistance and 

published directories. 

NOTE 1: 

This field should only be used when omitting the entire address from 

directory assistance and published directories. 


O = Omit address in DA and Directory 

USAGE: 

NOTE 1: 


Required when positions 2 and 3 of the RTY field are “CR”, otherwise 

optional. 



EXAMPLE: 

O 

62. LAPR - Listed Address Number Prefix 

Identifies the prefix for the address number of the listed address. 

USAGE: 

NOTE 1: 


Optional when the LANO field is populated, otherwise prohibited. 




NOTE 1: 



Suite 23A. 


370


63. LANO - Listed Address Number 

Identifies the number of the listed address. 

USAGE: 

NOTE 1: 


Optional when the LASN field is populated, otherwise prohibited. 




NOTE 1: 



64. LASF - Listed Address Number Suffix 

Identifies the suffix for the address number of the listed address. 

USAGE: 

NOTE 1: 


Optional when the LANO field is populated, otherwise prohibited. 




NOTE 1: 




371


65. LASD - Listed Address Street Directional Prefix 

Identifies the street directional prefix for the listed address. 


N = North 

S = South 

E = East 

W = West 





USAGE: 

NOTE 1: 





EXAMPLE: S W 

NOTE 1: 



Suite 23A. 

66. LASN - Listed Address Street Name 

Identifies the street name of the listed address. 

USAGE: 




EXAMPLES: 


NOTE 1: 



Suite 23A. 

C o r n e r o f M a i n a n d F i r s t 


372


67. LATH - Listed Address Street Type 

Identifies the thoroughfare portion of the street name of the listed address. 

NOTE 1: 

USAGE: 

NOTE 1: 








EXAMPLE: L N 

NOTE 1: 



Suite 23A. 

68. LASS - Listed Address Street Directional Suffix 

Identifies the street directional suffix for the listed address. 


N = North 

S = South 

E = East 

W = West 





USAGE: 

NOTE 1: 





EXAMPLE: N W 

NOTE 1: 


example: 25W 450 ½ SW Camino Ramon Lane NW, Floor 12, Wing 2, 

Suite 23A. 


373


69. LALO - Listed Address Location 

Identifies additional location information about the listed address such as an apartment 

number, floor, room, suite, etc.. 

USAGE: 




EXAMPLE: 

S u i t e 2 3 

NOTE 1: Where Suite 23 is the location for the following address example: 25W 450 

1/2 SW Camino Ramon Lane NW Suite 23. 

70. LALOC - Listed Address Locality 

Identifies the locality or community to be listed. 

NOTE 1: 

NOTE 2: 

USAGE: 

The locality name must be spelled out in full. 

Publishing appearance of the locality is determined by local practices. 




EXAMPLE: 

C o n c o r d 

71. LAST - Listed Address State/Province 

Identifies the abbreviation for the state or province of the listed address. 

NOTE 1: 

USAGE: 






EXAMPLE: C A 


374


72. LAZC - Listed Address ZIP/Postal Code 

Identifies the ZIP code, ZIP code + extension or postal code of the listed address. 

USAGE: 





9 4 5 8 3 - 4 1 8 2 

M 5 A 1 X 7 


375


14.2.5 Caption/SLU Indent Section 

73. LVL - Level of Indent 

Identifies the degree of indent of the prior level being recapped or the level of the sub-caption 

header being established. 


1 - 6 

USAGE: 

NOTE 1: 


Required when the DOI field is “2” or greater, otherwise prohibited. 



EXAMPLE: 2 

74. PLS - Prior Level Status 

Identifies whether the prior level is new or is a recap of an existing indent or sub-caption 

header supplied to define placement within the caption set. 


E = Existing indent or sub-caption header 

N = New sub-caption header 

USAGE: 

NOTE 1: 





EXAMPLE: 

N 


376


75. PLINFO - Prior Level Information 

Identifies the first 100 characters of the information on the prior level. 

NOTE 1: 

USAGE: 

NOTE 1: 

This may be text, or where no text is present, the indent address. 





EXAMPLES: 

1 2 5 M a i n W a l n u t G r o v e 

E l e c t r o n i c s D e p a r t m e n t 


377


76. PLTN - Prior Level Telephone Number 

Identifies a telephone number on the prior level. 

USAGE: 

NOTE 1: 


Required when the prior level has a telephone number, otherwise 

prohibited. 


20 alphanumeric characters (may include hyphens) 

EXAMPLES: 

5 6 2 1 2 3 4 3 2 1 

Z E N I T H 1 2 3 4 

77. SO - Sequence Override 

Identifies that normal sequencing in captions should be overridden for this listing. 

NOTE 1: 

In most cases, normal sequencing is alphabetic. 


A = File after 

F = File first 

USAGE: 




EXAMPLE: 

A 


378


78. FAINFO - File After Information 

Identifies the first 100 characters of the text on the indent or sub-caption header being filed 

after at the same level. 

NOTE 1: 

USAGE: 

NOTE 1: 

This may be text, or where no text is present, the indent address. 


Required when the SO field is “A”, otherwise prohibited. 



EXAMPLE: 

1 2 5 M a i n W a l n u t G r o v e 

79. FATN - File After Telephone Number 

Identifies a telephone number on the file after indent. 

USAGE: 

NOTE 1: 


Required when file after indent has a telephone number, otherwise 

prohibited. 


20 alphanumeric characters (may include hyphens) 

EXAMPLES: 

5 6 2 1 2 3 4 3 2 1 

Z E N I T H 1 2 3 4 

5 6 2 - 1 2 3 - 4 3 2 1 


379


14.2.6 Delivery Address/Information Section 

Note: This section is used whenever specific delivery data needs to be supplied. It is required if 

anything other than negotiated defaults are needed. 

80. DELNUM - Delivery Reference Number 

Identifies the delivery address/information segment and each additional delivery 

address/information segment with a unique number. 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

NOTE 2: 

The DELNUM is customer assigned. 




Required when the Delivery Section is populated. 

Optional when the RTY field is “LML”, otherwise prohibited. 



EXAMPLE: 0 0 

81. DACT - Delivery Activity 

Identifies the delivery activity for this request. 


N = New delivery section 

D = Delete delivery section 

I = Change new delivery section (new data to be inserted) 

O = Change old delivery section (old data) 

NOTE 1: 

USAGE: 

NOTE 1: 

When changing a delivery section, two transactions are required, the first 

transaction would have a DACT of "O" to specify the data to be deleted. 

The second transaction would have a DACT of "I" to specify the new data. 


Required when establishing, deleting or changing data in the Delivery 

Sections, otherwise prohibited. 



EXAMPLE: 

N 


380


82. DATY - Delivery Address Type 

Identifies a delivery address segment as being valid for hand delivery, postal delivery or both. 

NOTE 1: 

This only indicates the validity of an address for a particular delivery 

method and cannot be used to request a specific delivery method. 


1 = Both - (Address is valid for either hand or postal delivery) 

2 = Hand delivery address 

3 = Postal delivery address 

NOTE 1: 

USAGE: 

If this field is not populated a default value of “1” is implied. 




EXAMPLE: 2 


Identifies the name of the end user to which the directory is to be delivered. 

NOTE 1: 

USAGE: 

NOTE 1: 

The name in this field is not intended to be used for directory listings or 



Required when the delivery address is different from the service address, 




EXAMPLE: 

J O E S M I T H 

84. DDAPR - Delivery Address Number Prefix 

Identifies the prefix for the address number of the directory delivery address. 

USAGE: 

NOTE 1: 


Optional when the DDANO field is populated, otherwise prohibited. 




NOTE 1: 



Suite 23A. 


381


85. DDANO - Delivery Address Number 

Identifies the number of the directory delivery address. 

USAGE: 

NOTE 1: 


Optional when the DDASN field is populated, otherwise prohibited. 




NOTE 1: Where 450 is the address number for the following address example: 450 

1/2 SW Camino Ramon Lane NW, Floor 12, Wing 2, Suite 23A. 

86. DDASF - Delivery Address Number Suffix 

Identifies the suffix for the address number of the directory delivery address. 

USAGE: 

NOTE 1: 


Optional when the DDANO field is populated, otherwise prohibited. 




NOTE 1: 




382


87. DDASD - Delivery Address Street Directional Prefix 

Identifies the street directional prefix for the directory delivery address. 


N = North 

S = South 

E = East 

W = West 





USAGE: 

NOTE 1: 





EXAMPLE: S W 

NOTE 1: 


example: 450 1/2 SW Camino Ramon Lane NW, Floor 12, Wing 2, Suite 

23A. 

88. DDASN - Delivery Address Street Name 

Identifies the street name of the delivery address. 

NOTE 1: 

USAGE: 

NOTE 1: 


other description for this directory delivery address. 


Required when the delivery address differs from the service address, 




EXAMPLES: 


NOTE 1: 



Suite 23A. 



383


89. DDATH - Delivery Address Street Type 

Identifies the thoroughfare portion of the street name of the delivery address. 

NOTE 1: 

USAGE: 

NOTE 1: 








EXAMPLE: L N 

NOTE 1: 


example: 25W450 1/2 SW Camino Ramon Lane NW, Floor 12, Wing 2, 

Suite 23A. 

90. DDASS - Delivery Address Street Directional Suffix 

Identifies the street directional suffix for the directory delivery address. 


N = North 

S = South 

E = East 

W = West 





USAGE: 




EXAMPLE: N W 

NOTE 1: 



Suite 23A. 


384




NOTE 1: 

NOTE 2: 

USAGE: 

This instance of the LD1 field is used for the directory delivery address. 



Section. 




EXAMPLE: F l o o r 

NOTE 1: 





NOTE 1: 

USAGE: 

This instance of the LV1 field is used for the directory delivery address. 




EXAMPLE: 1 2 

NOTE 1: 




385




NOTE 1: 

NOTE 2: 

USAGE: 




Section. 




EXAMPLE: W i n g 

NOTE 1: 



Suite 23A. 



NOTE 1: 

USAGE: 





EXAMPLE: 2 

NOTE 1: 




386




NOTE 1: 

NOTE 2: 

USAGE: 




Section. 




EXAMPLE: S u i t e 

NOTE 1: 

Where STE is the third location designator for the following address 


Suite 23A. 



NOTE 1: 

USAGE: 






NOTE 1: 



97. AAI - Additional Address Information 


NOTE 1: 

USAGE: 

This instance of the AAI field is used for the directory delivery address. 




EXAMPLE: 




387




NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

This instance of the CITY field is used for the directory delivery address. 

The community name must be spelled out in full. 






EXAMPLE: 

C o n c o r d 



NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

This instance of the STATE field is used for the directory delivery address. 








EXAMPLE: C A 


388




NOTE 1: 

USAGE: 

NOTE 1: 

This instance of the ZIP field is used for the directory delivery address. 







9 4 5 8 3 - 4 1 8 2 

M 5 A 1 X 7 

101. DIRQTY - Number of Directory Type Segments 

Identifies the number of directory type segments in this delivery address section. 

NOTE 1: 

USAGE: 

NOTE 1: 

The directory type segments contain the DIRTYP, DIRID, DIRQTYA, 

DIRQTYNC and DIRNAME elements. 


Required when any directory type segments are populated, otherwise 

optional. 



EXAMPLE: 2 


389


102. DIRTYP - Directory ID Type 

Identifies the type of the directory (e.g., white pages, yellow pages) to be delivered. 


W = White Pages or Cobound 

Y = Yellow Pages 

B = Business to Business 

O = Other 

NOTE 1: 

USAGE: 

NOTE 1: 

Additional values may be company defined. 


Required when the DIRQTYA or DIRQTYNC field is populated, otherwise 

prohibited. 



EXAMPLE: 

W 

103. DIRQTYA - Number of Directories for Annual Delivery 

Identifies the number of directories to be delivered on an annual basis. 

NOTE 1: 

USAGE: 

NOTE 1: 

This quantity refers to the directory type identified in the previous DIRTYP 

field. 


Required when the DIRTYP field is populated, otherwise prohibited. 



EXAMPLE: 2 

104. DIRQTYNC - Number of Directories Delivered New Connect 

Identifies the number of directories to be delivered at the time of new connect. 

NOTE 1: 

USAGE: 

NOTE 1: 

This quantity refers to the directory type identified in the previous DIRTYP 

field. 


Optional when the ACT field on the DSR Form is "N" or "T" and the 

DIRTYP field is populated, otherwise prohibited. 



EXAMPLE: 1 


390


105. DIRID - Directory ID for Directory Delivery 

Identifies the directory code of the book to be delivered. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

May identify the White Page or cobound directory. 

May identify the primary yellow page directory that a customer is 

requesting when there are separate white and yellow page directories and/or 

multiple yellow page directories. 

May identify the Business to Business directory. 

May identify the Other Book directory. 


YPPA Code 

NOTE 1: 

USAGE: 


code does not exist or is ambiguous. 




EXAMPLE: 0 6 9 8 0 1 

106. DIRNAME - Directory Name 

Identifies the name of a directory that a customer is requesting. 


Directory name 

USAGE: 

This field is optional 



EXAMPLE: 

G r a n d J u n c t i o n N E 


391


14.2.7 Advertising Section 

107. EA - Existing Advertising 

Identifies the end user’s advertising status. 

NOTE 1: 

An indicator to advise the publishing company as to the status of 

advertising of the end user. 


Y = End user has existing advertising 

N = End user does not have existing advertising 

U = Unknown 

USAGE: 

NOTE 1: 

NOTE 2: 


Required if ACT on LSR form is “N” or “T” and the REQTYP on the LSR 

form is “E”, “B”, or “C”. 

Required if ACT on LSR form is “V” or “T”, the REQTYP on the LSR 

form is “E”, “B”, or “C”, and ERL on the EU form is “N” and LACT is 

“N”, “I”, or “O”. 



EXAMPLE: 

N 

108. ADVCONT - Advertising Contact 

Identifies the name of the person to contact to discuss the advertising. 

USAGE: 

NOTE 1: 


Required when the EA field is "Y", otherwise optional. 



EXAMPLE: 

J o h n D o e 


392


109. ADVCONT TN - Advertising Contact Telephone Number 

Identifies the telephone number of the advertising contact, including an extension if 

applicable. 

USAGE: 

NOTE 1: 


Required when the EA field is "Y", otherwise optional. 



EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 0 0 - 2 2 6 2 

110. SIC - Standard Industry Classification 

This code identifies the primary function of a customer’s business. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

The U.S. Government establishes the codes. The standard industrial 

classification codes are assigned to businesses as it relates to their type of 

primary business involvement. 

May also appear on some residential listings. 

This field affects directory publishing only and not directory assistance. 




EXAMPLE: 8 4 3 7 0 0 

111. YPH - Yellow Page Heading Code 

Identifies the code for the heading under which a listing will appear in the Yellow Pages. 

NOTE 1: 

Only applies if listing is a main or alternate (joint) user listing. 


Company specified Yellow Page Heading Codes 

USAGE: 






393


112. YPHV - Yellow Page Heading Verbiage 

Identifies the heading under which a listing will appear in the Yellow Pages. 

NOTE 1: 

USAGE: 

NOTE 1: 

Only applies if listing is a main or alternate-user (joint) business listing. 


Required when first position of TOS on the LSR Form is populated with 

“1”. 



EXAMPLE: 

A u t o m o b i l e s - U s e d C a r D e a l 

e r s 


394



Identifies remarks pertaining to the listing on this service request. 

NOTE 1: 

USAGE: 

Only used in manual mode. Not retained in a mechanized database. 




EXAMPLE: 

T H I S I S A R E S I D E N C E O N L Y 

W I T H A S E C O N D L I N E 


395


14.3 DL Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the Directory Listing Form 

fields. 

DL FORM 


AAI 97 Additional Address Information 

ACA 60 Alternate Call Authorization 

ADI 61 Address Indicator 

ADV 29 Advance to Directory Indicator 

ADVCONT 108 Advertising Contact 

ADVCONT TN 109 Advertising Contact Telephone Number 

ALI 11 Alphanumeric Listing Identifier Code 



BRO 28 Business/Residence Placement Override 


CITY 98 City 

DACT 81 Delivery Activity 

DATY 82 Delivery Address Type 

DDANO 85 Delivery Address Number 

DDAPR 84 Delivery Address Number Prefix 

DDASD 87 Delivery Address Street Directional Prefix 

DDASF 86 Delivery Address Number Suffix 

DDASN 88 Delivery Address Street Name 

DDASS 90 Delivery Address Street Directional Suffix 

DDATH 89 Delivery Address Street Type 

DDQTY 23 Number of Delivery Segments 

DELNUM 80 Delivery Reference Number 

DES 47 Designation 

DIRID 105 Directory ID for Directory Delivery 

DIRIDL 33 Directory Identifier 

DIRNAME 34 Directory Name 

DIRNAME 106 Directory Name 

DIRQTY 101 Number of Directory Type Segments 

DIRQTYA 103 Number of Directories for Annual Delivery 

DIRQTYNC 104 Number of Directories Delivered on New Connect 

DIRSUB 35 Directory Subsection 

DIRTYP 102 Directory ID Type 

DLNM 31 Dual Name Listing 

DLNUM 20 Directory Listing Number 

DML 25 Direct Mail List 

DNA 43 Do Not Abbreviate 

DOI 17 Degree of Indent 

DSR NO 4 Directory Service Request Number 

EA 107 Existing Advertising 

EOS 14 End User’s Other Service 


396


14.3 DL Alphanumeric Glossary (continued) 

DL FORM 


FAINFO 78 File After Information 

FATN 79 File After Telephone Number 

LACT 10 Listing Activity Indicator 

LALO 69 Listed Address Location 

LALOC 70 Listed Address Locality 

LANO 63 Listed Address Number 

LAPR 62 Listed Address Number Prefix 

LASD 65 Listed Address Street Directional Prefix 

LASF 64 Listed Address Number Suffix 

LASN 66 Listed Address Street Name 

LASS 68 Listed Address Street Directional Suffix 

LAST 71 Listed Address State/Province 

LATH 67 Listed Address Street Type 

LAZC 72 Listed Address ZIP/Postal Code 



LD3 95 Locatoin Designator 3 

LEX 42 Local Exchange 

LID1 36 Scoping Zip 

LID2 37 Additional Scoping Information 

LNFN 46 Listed Name First 

LNLN 45 Listed Name Last 

LNPL 44 Letter Name Placement 


LPHRASE 58 Listing Phrase 

LTEXT 59 Line of Text 

LTN 39 Listed Telephone Number 

LTXNUM 56 Line of Text Reference Number 

LTXQTY 24 Number of Listing Text Segments 

LTXTY 57 Listing Text Type 

LTY 13 Listing Type 



LV3 96 Locatoin Value 3 

LVL 73 Level of Indent 

MTN 21 Main Telephone Number 


NICK 54 Nickname 

NOSL 26 No Solicitation Indicator 

NSTN 40 Non Standard Telephone Number 

OMSD 38 Omit From Secondary Directory 

OMTN 41 Omit TN 


PLA 55 Place Listing As 


397


14.3 DL Alphanumeric Glossary (continued) 

DL FORM 


PLINFO 75 Prior Level Information 

PLS 74 Prior Level Status 

PLTN 76 Prior Level Telephone Number 


PPTN 22 Previous Provider Telephone Number 

PROF 32 Professional Identifier 


RTY 12 Record Type 


SO 77 Sequence Override 


SIC 110 Standard Industry Classification 


STR 30 Street Address Directory 

STYC 15 Style Code 

TITLE1 49 Title of Address 1 

TITLE1D 52 Title of Address 1 for Dual Name 

TITLE2 50 Title of Address 2 

TITLE2D 53 Title of Address 2 for Dual Name 

TL 48 Title of Lineage 

TLD 51 Title of Lineage for Dual Name 

TMKT 27 Telemarketing 

TOA 16 Type of Account 


WPP 18 White Page Products 

YPH 111 Yellow Page Heading Code 

YPHV 112 Yellow Page Heading Verbiage 



398

(Insert Your Company Logo ) 


CCNA 

1 

SC1 

7 

PON 

2 

SC2 PG _of_ 

8 9 

VER 

3 

DSR NO 


ATN 

4 5 

- - 

AN 

6 

V5 

8/00 

Listing Control Section 

LACT 

10 

PPTN 

2 2 

ALI 

1 1 

- - 

RTY 

1 2 

LTY 

13 

DDQTY 

2 3 

EOS 

1 4 

LTXQTY 

2 4 

STYC 

1 5 

TOA 

DOI WPP 

LOCNUM 

DLNUM 

MTN 

1 6 17 1 8 

1 9 2 0 2 1 

- - 

Listing Indicators Section 

DML 

25 

NOSL 

26 

TMKT 

27 

BRO 

28 

ADV 

29 

STR 

30 

DLNM 

31 

PROF 

32 

DIRIDL 

3 3 

DIRNAME 

3 4 

DIRSUB 

3 5 

OMSD (continued) 

LID1 

3 6 

LID2 

3 7 

OMSD 

3 8 

Listing Instruction Section 

LTN 

3 9 

- - 

LNLN (continued) 

NSTN 

4 0 

LNFN 

4 6 

OMTN 

41 

LEX 

4 2 

- 

DNA 

43 

LNPL 

44 

LNLN 

4 5 

LNFN (continued) 

DES 

4 7 

TL 

4 8 

NICK 

5 4 

TITLE1 

4 9 

PLA 

5 5 

TITLE2 

5 0 

TLD 

5 1 

TITLE1D 

5 2 

TITLE2D 

5 3 

PLA (continued) 

LTXNUM 

5 6 

LTXTY 

5 7 

LPHRASE 

5 8 

LTEXT 

5 9 

LTEXT (continued) 



ACA 

60 

ADI 

61 

LAPR 

6 2 

LANO 

6 3 

LASF 

6 4 

LASD 

6 5 

LASN 

6 6 

LATH 

6 7 

LALOC 

7 0 

LASS 

6 8 

LALO 

6 9 

LAST 

7 1 

LAZC 

7 2 






CCNA 

1 

SC1 

7 

PON 

2 

SC2 PG _of_ 

8 9 

VER 

3 

Directory Listing (DL) (continued) 

DSR NO 

ATN 

4 5 

- - 

AN 

6 

V5 

8/00 

Caption/SLU Indent Section 

LVL 

73 

PLS 

74 

PLINFO 

7 5 

PLINFO (continued) 

PLTN 

7 6 

FAINFO (continued) 

LVL 

73 

PLS 

74 

PLINFO 

7 5 


PLTN 

7 6 


LVL 

73 

PLS 

74 

PLINFO 

7 5 


PLTN 

7 6 


LVL 

73 

PLS 

74 

PLINFO 

7 5 


PLTN 

7 6 


LVL 

73 

PLS 

74 

PLINFO 

7 5 


PLTN 

7 6 


SO FAINFO 

77 7 8 

SO FAINFO 

77 7 8 

SO FAINFO 

77 7 8 

SO FAINFO 

77 7 8 

SO FAINFO 

77 7 8 

FATN 

7 9 

FATN 

7 9 

FATN 

7 9 

FATN 

7 9 

FATN 

7 9 






CCNA 

1 

SC1 

7 

PON 

2 

SC2 PG _of_ 

8 9 

VER 

3 


DSR NO 

ATN 

4 5 

- - 

AN 

6 

V5 

8/00 

Delivery Address/Information Section - use if delivery address different than listed or service address 

DELNUM 

8 0 

DDASN 

8 8 

LD1 

9 1 

AAI 

9 7 

CITY 

9 8 

DACT 

81 

LV1 

9 2 

DATY 

82 

NAME 

8 3 

LD2 

9 3 

LV2 

9 4 

LD3 

9 5 

STATE 

9 9 

DDAPR 

8 4 

LV3 

9 6 

ZIP 

1 0 0 

DDANO 

8 5 

DIRQTY 

1 01 

DDASF 

8 6 

DDASD 

8 7 

DDATH 

8 9 

DDASS 

9 0 

DIRTYP 

102 

DIRQTYA 

1 03 

DIRQTYNC 

1 04 

DIRID 

1 05 

DIRNAME 

1 06 

DIRTYP 

102 

DIRQTYA 

1 03 

DIRQTYNC 

1 04 

DIRID 

1 05 

DIRNAME 

1 06 

DIRTYP 

102 

DIRQTYA 

1 03 

DIRQTYNC 

04 

DIRID 

1 05 1 

DIRNAME 

1 06 

Advertising Section 

EA 

107 

YPHV 

1 12 

ADVCONT 

ADVCONT TN 

1 08 1 09 

- - 

- 

SIC 

1 10 

YPH 

1 11 

YPHV (continued) 


REMARKS 

1 13 






CCNA PON VER DSR NO 

SC1 SC2 PG _of_ 


ATN 

- - 

AN 

V5 

8/00 

Listing Control Section 

LACT ALI RTY LTY EOS 

STYC TOA DOI WPP LOCNUM DLNUM 

PPTN 

- - 

Listing Indicators Section 

DDQTY LTXQTY 

DML NOSL TMKT BRO ADV STR DLNM PROF DIRIDL DIRNAME 

MTN 

- - 

DIRSUB 

LID1 

LID2 

OMSD 

OMSD (continued) 

Listing Instruction Section 

LTN 

- - 

LNLN (continued) 

NSTN 

LNFN 

OMTN LEX 

- 

DNA 

LNPL 

LNLN 

LNFN (continued) 

TL TITLE1 TITLE2 TLD 

TITLE1D TITLE2D 

DES 

4 7 

NICK 

PLA 

PLA (continued) 

LTXNUM 

LTXTY 

LPHRASE LTEXT 




ACA ADI LAPR 

LANO 

LASF 

LASD 

LASN 

LATH 

LASS 

LALO 

LALOC 

LAST LAZC 








ATN 


- - 

AN 

V5 

8/00 

Caption/SLU Indent Section 

LVL PLS PLINFO 


PLTN SO FAINFO 


FATN 

LVL PLS 

PLINFO 




FATN 

LVL PLS 

PLINFO 




FATN 

LVL PLS 

PLINFO 




FATN 

LVL PLS 

PLINFO 




FATN 








ATN 


- - 

AN 

V5 

8/00 

Delivery Address/Information Section - use if delivery address different than listed or service address 

DELNUM DACT DATY NAME DDAPR DDANO 

DDASF 

DDASD 

DDASN 

DDATH 

DDASS 


AAI 

CITY 

STATE ZIP 

DIRQTY 

DIRTYP DIRQTYA DIRQTYNC DIRID DIRNAME 



Advertising Section 

EA 

YPHV 

ADVCONT 

ADVCONT TN 

- - 

- 

SIC 

YPH 



REMARKS 





15.0 LOCAL RESPONSE (LR) 

15.1 Local Response Form 

The Local Response (LR) is prepared by Windstream and is forwarded to the NSP. This form 

provides the NSP with information regarding critical dates, circuit identification, disconnect 

telephone number(s), order numbers and tie down information associated with the NSP’s 

request for service. The LR Form also provides the NSP with the information necessary for 

control and tracking of the applicable request(s) for the provisioning of local service. 

When a LR is issued in response to a Firm Order LSR, its issuance signifies Windstream's 

good faith effort to provide the local service as ordered by the NSP on the matching version of 

the referenced LSR Form. 

When a LR is issued in response to a Directory Service Request (DSR), its issuance signifies 

Windstream's good faith effort to provide the service as ordered by the NSP on the matching 

version of the referenced DSR Form. The Directory Section of the LR Form provides the 

NSP with the information necessary for control and tracking of the applicable requests for 

directory services. 

The following describes the use of some of the critical entries provided on the LR Form. 

PON - The purchase order number used by the NSP to identify the original local 


LSR NO - Control number used by Windstream's mechanized order processor. 

RT - Identifies the type of Local Response being returned to the customer. 

ECCKT - The circuit identification assigned to the local service. This is the ECCKT, 

which will be used on the Design Layout Report, the customer's bill, for 

acceptance testing and for trouble reporting purposes. 

Dates - Identifies the critical dates for the NSP's order process, which are provided 

to the customer for planning and scheduling. 

REP - Identifies Windstream's representative to whom the NSP may direct 

questions concerning this particular request. 

In conjunction with the LR Form, the REQTYP field on the LSR Form will reflect the 

provider's mechanized order processing indication that a Service Inquiry or Firm Order 

Confirmation has been processed: 

2nd character of REQTYP is: 

A 

B 

Type of Confirmation is: 

Service Inquiry Confirmation 

Firm Order Confirmation 

NOTE 1: 

NOTE 2: 

For stand alone directory service requests the value will always be "B". 

Currently, only Firm Orders can be submitted using Windstream's 

mechanized order processor making 'B' the only valid entry. 

Again, this form is prepared by Windstream and is submitted to the NSP for the Firm Order 

Confirmation. 


411


15.2 LR Form Fields 





NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 







CCNA is not necessarily the customer to be billed for the specific service. 

The billed party should be specified in the ACNA field. 


• IAC Code 

NOTE 1: 

USAGE: 

NOTE 1: 


751-100-112. 


Required when the CCNA on the LSR is populated, otherwise optional. 







NOTE 1: 

USAGE: 

This PON field entry must be identical to the PON field entry on the LSR 

Form. 




EXAMPLE: 

8 2 4 Z 9 


412



Identifies the customer's version number. 

NOTE 1: 

This VER field entry must be identical to the VER field entry on the LSR 

Form and/or DSR Form. 


00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 


Required when the SUP field on the LSR Form or the DSUP field on the 

DSR Form is populated, otherwise optional. 



EXAMPLE: A A 



NOTE 1: 

NOTE 2: 





USAGE: 

NOTE 1: 


Required when the AN field on the LSR Form is populated, otherwise 

prohibited. 



EXAMPLE: A B 3 2 2 1 4 7 


413


5. SPAN – Simple Port Account Number 

Identifies the end user’s account number assigned by the Old Local Service Provider 

associated with a simple port request. 



USAGE: 

NOTE 1: 


Required when the SPAN on the SPSR is populated, otherwise prohibited. 



EXAMPLE: A B C D 1 2 3 





NOTE 1: 

USAGE: 

NOTE 1: 




Required when the ATN field on the LSR Form is populated, otherwise 

optional. 



EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 

7. LSR NO - Local Service Request Number 


to the customer by the provider, or manually assigned by the provider to identify a 


USAGE: 




EXAMPLE: 

3 1 2 3 4 5 6 7 8 9 0 1 


414



Identifies the provider’s order number for the service requested. 

NOTE 1: 

USAGE: 

NOTE 1: 

This number may be pre-assigned to the customer by the provider. 


Required when the RT field is “B”, “C”, “D”, “F”, “G”, “H”, or “L”, 




EXAMPLE: 

C 2 3 4 5 6 

9. CNO - Case Number 

Identifies the case number assigned by the provider in response to a Diversity Inquiry 

Request. 

USAGE: 




EXAMPLE: B S 0 6 1 1 9 6 - 0 0 2 

10. INIT - Initiator Identification 

Identifies the initiator as specified on the LSR Form by the customer. 

USAGE: 

NOTE 1: 


Required when the INIT field on the LSR Form is populated, otherwise 

prohibited. 



EXAMPLE: 

J O H N S M I T H 


415




USAGE: 






Identifies the date and time that the Local Response is sent by the provider. 


U.S. Standard 

Metric Format 







AM or PM 

AM or PM 

NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 

0 5 - 2 2 - 1 9 9 6 - 1 1 1 5 A M 

13. REP - Provider Contact Representative 

Identifies the provider's representative handling this service request. 

USAGE: 




EXAMPLE: 

M E L V I N S I M C O E 


416


14. ST - Switch Type 

Indicates the type of local serving office (LSO) switch that is used to provide the BRI. This 

information may be needed to correctly configure the end user's customer premises equipment 

(CPE). 


1 = 5ESS 

2 = DMS100 

3 = EWSD 

4 = Other (See Remarks) 

USAGE: 

NOTE 1: 


Required when the second position of the TOS field on the LSR Form is 

"H", otherwise prohibited. 



EXAMPLE: 1 

15. IBT - ISDN BRI Type 

Indicates the type of national ISDN BRI. 


1 = NI-1 

2 = NI-2 

3 = NI-3 

USAGE: 




EXAMPLE: 1 


Identifies the telephone number of the provider's representative handling this request. 

USAGE: 



hyphens) 

EXAMPLE: 2 0 1 - 9 8 1 - 3 5 8 2 


417


17. RT - Response Type 

Identifies the type of Local Response being returned to the customer. 


B = Firm Order with Facility Information 

C = Firm Order Confirmation 

D = Confirmation and DLR (Private Line) 

E = Errors Only (Directory) 


G = Confirmation and DSR Errors (Directory) 

H = Combined (Service and Directory Listing) Confirmation and DSR errors 

J = Jeopardy Notice 

L = Directory Only Completion 

USAGE: 




EXAMPLE: 

C 

18. PIA - Provider Initiated Activity 

Indicates a provider initiated response that is not the result of a customer Local Service 

Request or supplement, prior to order completion. 

NOTE 1: 

This may signal to the customer that additional investigation is needed to 

determine internal process impacts. 


1 = Provider Initiated ECCKT(s) Change 

2 = Provider Initiated Due Date Change 

3 = ECCKT and Due Date Change 

4 = Other (Clarify in Remarks) 

USAGE: 

NOTE 1: 


Required when the provider initiates a response that is not the result of a 

customer Local Service Request or supplement prior to order completion, 




EXAMPLE: 3 


418


19. CHC - Coordinated Hot Cut 

Indicates the provider acknowledges the coordinated hot cut. 

NOTE 1: 

NOTE 2: 



This field indicates the provider's intent to meet the coordinated hot cut due 

date (DD) and frame due time (FDT) when the RT is "B" or "F". 


Y = Yes 

NOTE 1: 

USAGE: 

An entry in this field requires a single time entry in the FDT field. 




EXAMPLE: 

Y 

20. FDT - Frame Due Time 

Identifies frame cutover time. 


Two Digit Hour (01-12)/Two Digit Minute (00-59)/AM or PM 

Two Digit Hour (01-12)/A or P/Two Digit Hour (01- 12)/A or P 

AM or PM 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

Indicates the window for cutover time when the CHC field is not populated. 

When the CHC field is populated, indicates the desired specific cutover 

time. 



Required when the DFDT field on the LSR Form is populated, otherwise 

optional. 



EXAMPLES: 1 0 1 5 P M 

1 2 P 0 2 P 

0 8 A 1 0 A 

A 

M 


419


21. DD - Due Date 

Identifies the date the service order requested is due to be completed. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 

NOTE 2: 



Prohibited when the SPDD/T field is populated. 

Required when the RT field is “B”, “C”, “D”, “F”, “G”, “H”, or “L”, 



hyphens) 

EXAMPLE: 0 3 - 2 2 - 1 9 9 6 


420


22. SPDD/T – Simple Port Due Date and Time 

Identifies the due date and time the simple port service request is due to be completed. 


U.S. Standard 

Metric Format 





Two Digit Hour (01-12 or 00-24) Two Digit Hour (01-12 or 00-24) 


AM or PM 

AM or PM 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

NOTE 2: 

NOTE 3: 

Windstream does not provide a time associated with a due date for simple 

ports. 



Required when the SPDDD/T field on the SPSR is populated and the RT 

field is “B”, “C”, “D”, “F”, “G”, “H”, or “L”. 

Optional when the SPDDD/T field on the SPSR is populated and the RT 

field is “J”. 




EXAMPLE: 0 5 - 2 2 - 1 9 9 6 



desired due date. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 0 4 - 0 2 - 1 9 9 7 


421








L = Loop 




P = Port 

R = Resale 

U = Usage 





USAGE: 

NOTE 1: 


Required when the BAN1 and BAN2 fields on the LSR Form are “N” or 

“E”, otherwise optional. 



EXAMPLE: 

L 




NOTE 1: 





NOTE 1: 

USAGE: 

NOTE 1: 

If the BAN1 sent is not correct, the provider will return the correct BAN1. 


Required when the BAN1 field on the LSR Form is “N”, otherwise 

optional. 



EXAMPLES: 2 0 1 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 


422








L = Loop 




P = Port 

R = Resale 

U = Usage 





USAGE: 

NOTE 1: 


Required when the BAN1 and BAN2 fields on the LSR Form are “N” or 

“E”, otherwise optional. 



EXAMPLE: 

L 




NOTE 1: 





NOTE 1: 

USAGE: 

NOTE 1: 

If the BAN2 sent is not correct, the provider will return the correct BAN2. 


Required when the BAN2 field on the LSR Form is “N”, otherwise 

optional. 



EXAMPLES: 2 0 1 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 


423


28. EC VER - Exchange Carrier Version 

Identifies the provider’s version and whether the response is a correction, resend or a 

reason/jeopardy. 


First two characters: 

AA-ZZ or blank 

Third character: 

C = Correction copy 

R = Resend copy 

J = Jeopardy/reason code 

NOTE 1: 

NOTE 2: 

USAGE: 

NOTE 1: 

For the initial issuance, this field may be populated. Any reissuance uses 

this entry to uniquely identify the form from any other version. 

The code set is comprised of three characters. The first two for are for 

version identification and the third character is for identification of a 

correction or resend, or jeopardy/reason. 


Required for subsequent issuance of response notice, otherwise optional. 



EXAMPLES: A B R 

A 

A 


424


29. RCODE - Reason Code 

Identifies the reason the order may not meet the requested Due Date at confirmation and/or 

Post Confirmation. 


1A = Inter Office Facility Shortage 

1B = Scheduling/Work Load 

1C = Customer (LSP) not ready 

1D = No loop available 

1E = End User Not Ready 

1F = NSP missed Appointment 

1G = No Access to End User Prem 

1H = Central Office Freeze 

1J = Special Construction 

1K = Natural Disaster (Flood, etc.) 

1L = Frame Due Time can not be met 

1M = Requested DD is less than published interval 

1N = DD and Frame Due Time can not be met 

1P = Other 

1Q = Assignment problem 

1R = Customer Could Not be reached at the reach number 

1S = Building Not Ready, Customer will advise 

1T = Invalid/Missing Passcode 

1W = Entrance Facilities Required 

1X = Invalid/Missing/Inactive Account Number 

1Y = No Central Office Equipment Available 

1Z = Loop Requires Installation of Additional Equipment 

2A = LSR Error, Incorrect or Missing Information 

2B = Facility Work Order Pending, No Bona Fide Request (BFR) Required 

USAGE: 

NOTE 1: 


Required when the RT field is populated with “J”, otherwise optional. 



EXAMPLE: 1 B 

30. RDET - Reason Jeopardy Code Detail 

Identifies further detail for the service when the reason/ jeopardy code for the order is not 

defined. 

USAGE: 




EXAMPLE: 

U n a b l e t o a s s i g n t o e x i s t 

i n g c a b l e 


425


31. ESDD - Estimated Due Date 

Identifies the date the provider expects to have service available. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 0 3 - 2 2 - 1 9 9 6 

32. AFVR - Additional Field Visit Required 

Identifies if a field visit is required at the customer/end user location, which requires 

arrangements to be established. 


Y = Yes 

USAGE: 




EXAMPLE: 

Y 

33. DSGCON - Design/Engineering Contact 

Identifies the representative of the customer or agent that should be contacted on 

design/engineering matters. 

USAGE: 






426


34. NSP DSGCON - Network Service Provider (NSP) Design/Engineering Contact 

Identifies the representative of the provider that should be contacted on design/engineering 

matters. 

USAGE: 




EXAMPLE: J U D Y J O N E S 


Identifies the telephone number of the provider's design/engineering contact. 

USAGE: 

NOTE 1: 


Required when the NSP DSGCON field is populated, otherwise optional. 



EXAMPLE: 2 0 1 - 9 8 1 - 3 5 0 0 

36. ONSP - Old Network Service Provider Identification 

Identifies the NPAC SPID of the current Network Service Provider. 

NOTE 1: 









• COMPANY Code - A four alphanumeric character code, which identifies 

providers in the United States and certain U.S. territories, maintained by NECA. 


100-112. 

NOTE 2: 

USAGE: 







427


37. TDTR - Ten Digit Trigger Response 

Indicates the activation of a ten-digit trigger for local routing number portability. 


N = No 

USAGE: 

NOTE 1: 


Required when the TDT field on the NP or LSNP Form is populated and a 

Ten Digit Trigger is not provided, otherwise optional. 



EXAMPLE: 

N 

37a. TYPE1 – Type 1 Indicator 

Indicates if a number port request is a Wireless Number Port. 


Y = Yes (Number is a Type 1 number porting to a Wireless Carrier) 

N = No (Number is a typical Wireline number porting to a Wireless Carrier) 

USAGE: 

NOTE 1: 


Optional when RT field is “C”, otherwise prohibited. 



EXAMPLE: 

Y 


428


15.2.2 Hunt Group Section 



NOTE 1: 

USAGE: 







9 9 9 

39. HNUM - Hunt Line Number 

Identifies the Hunt Line number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

The HNUM is customer assigned and is returned on the Local Response to 


Once HNUM is generated, it cannot be changed and is retained through 





This field is required when the HNUM field on the LSR Form is populated, 




EXAMPLE: 0 0 0 0 1 


429


40. HID - Hunt Group Identifier 

Identifies the hunt group. 

USAGE: 

NOTE 1: 


Required when the HTQTY field on the LSR Form is populated, otherwise 

optional. 




3 0 4 - 2 2 6 - 4 1 8 3 

41. TLI - Telephone Line Identifier 

Identifies the pilot number of a multi-line hunt group. 

USAGE: 

NOTE 1: 


Required when the TLP field on the LSR Form is populated, otherwise 

optional. 



EXAMPLE: 9 0 8 - 2 3 3 - 6 1 2 3 

42. HTSEQ - Hunt Sequence 

Identifies the desired hunting sequence. 

USAGE: 

NOTE 1: 


Required when the HID field on the LSR Form is populated, otherwise 

optional. 



EXAMPLE: 1 


430


15.2.3 DID Section 

43. DIDNUM - DID Reference Number 

Identifies each DID group as a unique number and each additional DID group as a unique 

number. 

USAGE: 

NOTE 1: 


Required when the DIDNUM field is populated on the DID Resale form, 





44. DSTN - Disassociated Telephone Number 

Identifies the telephone number disassociated from the DID Telephone Number Range. 

USAGE: 



hyphens) 

EXAMPLE: 2 0 3 - 5 2 2 - 1 2 3 5 

45. DTLI - DID Telephone Line Identifier 

Identifies the lead telephone line assigned to the DID Trunk Group. 

USAGE: 




EXAMPLE: 2 0 1 - 5 5 5 - 5 3 8 0 

46. DTK - DID Trunk Quantity 

Identifies the quantity of trunks being requested. 

USAGE: 




EXAMPLE: 1 0 


431


47. DTGN - DID Trunk Group Number 

Identifies the DID Trunk Group Number which has been assigned by the provider. 

NOTE 1: 

USAGE: 







4 5 6 

48. DRTI - DID Route Index Number 

Identifies the Route Index Number assigned to the DID Trunk Group Number. 

NOTE 1: 

USAGE: 







2 4 6 

49. DTKID - DID Trunk ID 

Identifies the trunk ID of the existing DID service. 

USAGE: 




EXAMPLES: D 1 - 1 0 

D 1 0 1 - 1 1 0 

D 5 0 0 0 - 5 9 9 9 


432


50. DGOUT - DID Digits Out 

Indicates the number of digits outpulsed from the Central Office to the customer’s equipment. 

USAGE: 

NOTE 1: 





EXAMPLE: 4 

51. DTNR - DID Telephone Number Range 

Identifies the range of DID telephone numbers 

USAGE: 



hyphens) 

EXAMPLE: 

2 0 3 - 5 2 2 - 1 2 0 0 - 1 2 5 9 


433


15.2.4 Circuit Detail Section 


Identifies the line or trunk as a unique number and each additional occurrence of either as a 

unique number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 



Once LNUM is generated it can not be changed and is retained through 







EXAMPLE: 0 0 0 0 1 

53. LNEX - Line Number Extension Number 



NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 


the customer. 

Once LNEX is generated, it can not be changed and is retained through 





Required when the LNEX field is populated on the service specific form, 




EXAMPLE: 0 0 0 1 0 


434




NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

NOTE 5: 



periods. 


standards. 



spaces. 







EXAMPLES: 

A2/SBFS/201/981/3500 

//800/123/4567 



applicable) 


EXAMPLE: 

A2/LBFS/032719/001/NY 




EXAMPLE: 

USAGE: 






435


55. DSN - Dialable Station Number 

Identifies the dialable 1-7 digit Station Digit Dialing number. 

USAGE: 

NOTE 1: 


Required when the LNA field is “N”, otherwise optional. 




56. LTC - Line Treatment Code 

Identifies the unique treatment profile code required for this line, when the CENTREX 

Common Block contains more than 

one treatment code. 

NOTE 1: 

USAGE: 

NOTE 1: 

Code is for associating profiles with lines. 


Required when the CENTREX Common Block has more than one 

treatment code and the LNA field is populated, otherwise optional. 



EXAMPLES: 1 

1 2 


Identifies the type of telephone number entered in the TNS or OTN fields. 




B = ISDN BRI Telephone Number 

USAGE: 

NOTE 1: 


Required when the TNS or OTN field is populated, otherwise prohibited. 



EXAMPLE: 

T 


436


58. TNS - Telephone Numbers 

Identifies the telephone number or consecutive range of telephone numbers for this request. 



Maintenance Number 

ISDN BRI Telephone Number 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

NOTE 2: 

When the LNA field is “X”, the entry in this field indicates the new 

telephone number or request for a new telephone number. The out 

telephone number is shown in the OTN field. 

There may be one or more ISDN telephone numbers assigned per ISDN 

BRI line. 


number components and ranges. 


Prohibited if the SPP TN field is populated. 

Required if the TNS field on the service specific form is “N”, otherwise 

optional. 


hyphens) 

EXAMPLES: 

2 0 1 - 5 5 5 - 1 1 1 1 

9 0 8 - 5 5 5 - 1 0 0 0 - 1 9 9 9 


437


59. TERS - Terminal Numbers 

Identifies the number for a non-lead line in a multi-line hunt group or consecutive range of 

terminal numbers associated with the TNS field for this request. 


Terminal number(s) 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

A pilot (lead) telephone number in the TNS field must accompany this 

field. 

When this field is populated, the TNS field must not be ranged. 

The first position is reserved for a terminal number indicator. 




EXAMPLES: T 0 0 0 1 

S 0 0 0 1 

T 0 0 4 

S 0 0 0 1 - 0 0 2 0 

60. MATN - Main/Alternate Telephone Number 

Indicates the dialable telephone number(s) assigned to the ISDN BRI line. If the same 

number cannot be used for both B-channels, then the main number will be assigned to B- 

channel 1, and the alternate number will be assigned to B-channel 2. 


M = Main Telephone Number 

A = Alternate Telephone Number(s) 

NOTE 1: 

USAGE: 

There can only be one main telephone number but multiple alternate 

telephone numbers may exist. 




EXAMPLE: 

M 


438




USAGE: 




EXAMPLES: 

L 0 0 0 2 

2 9 3 3 2 1 8 1 

62. ISPID - ISDN Service Profile Identification 

Provides a code that must be programmed into the ISDN BRI customer premises equipment 

(CPE). This code is transmitted from the CPE over the ISDN BRI D-channel to the LSO 

switch. It must be present in order for the BRI to become active. 

USAGE: 

NOTE 1: 


Required when the second position of the TOS field on the LSR Form is 

"H", otherwise prohibited. 



EXAMPLE: 7 0 3 5 0 6 6 3 5 5 0 1 0 1 


439




NOTE 1: 





1. Facility Designation - A code that, for a specific type of facility, uniquely 



2. Facility Type - A code that describes a type of facility when it is other than a 

single baseband channel on cable. Valid entries are outlined in Telcordia 


characters). 

3. Channel/Pair/Time Slot - A code that identifies a specific assignable portion 

of a facility (variable length, 1-5 alphanumeric characters). 

4. Location A - A standardized code that uniquely identifies the location of 




5. Location Z - A standardized code that uniquely identifies the location of 




NOTE 2: 

NOTE 3: 

NOTE 4: 

USAGE: 

NOTE 1: 






SCFA field. 


Required when utilizing Hi-Cap facilities and the customer has assignment 

control, otherwise optional. 




440



EXAMPLES: 


M A M T K 3 1 

1 0 1 / T 1 / 1 - 2 4 / B S T N M A G T C G 0 / B 



M A M T K 3 1 

NOTE 1: 


assignments. 

64. LORD - Loop Order Number 

Identifies the provider's order number for the loop. 

USAGE: 

NOTE 1: 



"A" or "B", otherwise prohibited. 



EXAMPLE: 

C 2 3 4 5 6 

65. NPORD - Number Portability Order Number 

Identifies the provider's order number for number portability. 

USAGE: 




EXAMPLE: 

C 2 3 4 5 6 


441


66. PORTED NBR - Ported Telephone Number 

Identifies the telephone number (TN) and/or consecutive range of TN’s residing in the same 

switch that are to be ported. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

NOTE 4: 

USAGE: 

NOTE 1: 

A single number of the first number of the range may also be used to 





numbers within the range are remote call forwarded to the same TN. 


iterations. 



“B” or “C”, otherwise prohibited. 


hyphens) 

EXAMPLES: 

9 0 8 - 6 9 9 - 7 0 0 0 

9 0 8 - 6 9 9 - 7 0 0 0 - 7 0 2 0 

67. SPP TN – Simple Port Ported Telephone Number 

Identifies the telephone number to be ported on a simple port service request. 

USAGE: 

NOTE 1: 

This field is conditional 

Required when the SPREQTYP field on the SPSR is populated, otherwise 

prohibited. 


hyphens) 

EXAMPLE: 2 0 1 - 9 8 1 - 3 5 0 0 


442





USAGE: 

NOTE 1: 


Optional when the NPT field on the NP Form is "A" or "C", otherwise 

prohibited. 






USAGE: 

NOTE 1: 


Required when the DISC NBR field on the EU or LS Form is populated, 




EXAMPLE: 2 0 1 - 6 9 9 - 1 2 3 4 

70. DISC ORD - Disconnect Order Number 

Identifies the provider's order number for the disconnect of end user service associated with 

this request. 

USAGE: 




EXAMPLE: 

D 2 3 4 5 6 


443


15.2.4.1 Tie Down 



USAGE: 

NOTE 1: 


Required when the provider has assignment control in a collocation 




EXAMPLE: A A 


Identifies the provider’s central office cable to be connected to the customer’s collocated 

equipment. 

USAGE: 

NOTE 1: 









USAGE: 

NOTE 1: 






EXAMPLE: 2 0 


444




USAGE: 

NOTE 1: 






EXAMPLE: 0 7 

75. RELAY RACK - Relay Rack 

A code that identifies the bay/cabinet in a central office and may include the floor and aisle 

where the specific piece of equipment is located. 

USAGE: 

NOTE 1: 






EXAMPLE: 1 0 0 0 5 2 . 0 3 0 



USAGE: 

NOTE 1: 






EXAMPLE: 2 4 

77. UNIT - Unit 

Identifies the number assigned to a panel, shelf or case within the bay/cabinet indicated in the 

relay rack field. 

USAGE: 




EXAMPLE: 2 4 


445


15.2.4.2 Facility Transmission 

78. PGI - Pair Gain Indicator 

Indicates whether pair gain will be used for this service. 


Y = Yes 

USAGE: 

NOTE 1: 


Optional when the RT field is "B" or "F", otherwise prohibited. 



EXAMPLE: 

Y 

79. DEMARC - Demarc Designation 

Identifies the point where the provider terminates service at the end user premises. 

USAGE: 

NOTE 1: 





EXAMPLE: R J 2 1 N O 7 P I N 1 5 

80. OOR - Out of Range Indicator 

Identifies the loop as out of range and additional engineering and/or an extended range card 

may be required. 


Y = Yes 

USAGE: 

NOTE 1: 





EXAMPLE: 

Y 


446


81. NID - Network Interface Device 

Indicates if the existing network interface device (NID) will be reused. 


Y = Yes 

USAGE: 

NOTE 1: 


Optional when the RT field is “B” or “F”, otherwise prohibited. 



EXAMPLE: 

Y 


447


15.2.5 SECLOC Section 



number. 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 










EXAMPLE: 0 0 0 0 1 

83. LNEX- Line Number Extension Number 



NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 


the customer. 

Once LNEX is generated, it cannot be changed and is retained through 





Required when the LNEX field is populated on the service specific form, 




EXAMPLE: 0 0 0 1 0 


448


84. DLCI - Data Link Connection Identifier 

Identifies the logical connection address between the provider's switch and the ECCKT. 

USAGE: 

NOTE 1: 



"L" and the NVC field on the RFR Form is populated, otherwise prohibited. 




85. RECCKT - Related Exchange Company Circuit Identification 

Identifies the provider's related physical circuit ID against which the VC activity is requested. 

USAGE: 

NOTE 1: 


Required when the RECCKT field on the RFR Form is not populated, 




EXAMPLE: 

1 1 H W D K 0 1 2 3 4 5 


449


86. LST - Local Service Termination 

Identifies the CLLI code of the end office switch from which service is being provided. 

NOTE 1: 






within a state, province, territory, country, or distinct region of the world (e.g., 

municipality). Valid entries are outlined in Telcordia Technologies practice 

BR 795-100-050 (4 alphanumeric characters). 



federal government, or a unique designation Valid entries are outlined in 





equipment entities, facility terminations, nodal locations, or administrative 

operations. Valid entries are outlined in Telcordia Technologies’ repository (2 

alpha or 2 numeric characters). 

4. Network Site Entity Code - A functional category of equipment or work 

center contained within a structure. Equipment categories are associated 

network site for purposes of maintaining equipment inventories and for 

identifying facility and circuit terminations and nodal locations. Valid entries 

are outlined in Telcordia Technologies practice BR 795-100-100 (3 


USAGE: 

NOTE 1: 



“L”, otherwise optional. 



EXAMPLE: S N F C C A M C W 0 1 


450


87. RDLCI - Related Data Link Connection Identifier 

Identifies the logical connection address between the provider's switch and the RECCKT. 

USAGE: 

NOTE 1: 



"L" and the NVC field on the RFR Form is populated, otherwise prohibited. 





451


15.2.6 Directory Section 


Identifies the main telephone number used to associate the main listing with any additional 

listings. 

USAGE: 




EXAMPLE: 2 0 1 - 9 8 1 - 3 5 0 0 


Identifies the type of Local Response being returned to the customer. 


B = Firm Order with Facility Information 

C = Firm Order Confirmation 

D = Confirmation and DLR (Private Line) 

E = Errors Only (Directory) 


G = Confirmation and DSR Errors (Directory) 

H = Combined (Service and Directory Listing) Confirmation and DSR Errors 

J = Jeopardy Notice 

L = Directory Only Completion 

USAGE: 




EXAMPLE: 

C 


452



Identifies the Exchange Carrier requesting service. 

NOTE 1: 












100-112. 

NOTE 2: 

USAGE: 

NOTE 1: 



Required when the CCNA field is “CUS”, otherwise optional. 




91. DOR - Date of Receipt 

Identifies the date this directory service request was received. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 0 4 - 0 2 - 1 9 9 6 


453


92. DLORD - Directory Listing Order Number 

Identifies the order number assigned by the provider. 

USAGE: 




EXAMPLE: 

N 0 6 2 2 0 0 1 1 

93. DAORD - Directory Assistance Order Number 

Identifies the order number assigned by the provider for directory assistance. 

NOTE 1: 

USAGE: 

May be used when a different order number is used for directory listings. 




EXAMPLE: 

N 0 6 2 2 0 1 1 

94. DSRNO - Directory Service Request Number 




USAGE: 

NOTE 1: 


The value in this field is system generated. 



EXAMPLE: 

3 1 2 3 4 5 6 7 8 9 0 1 


454


95. DDA - Date of Availability in DA 

Identifies the date this listing will appear in or be deleted from Directory Assistance (DA). 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 0 3 - 2 2 - 1 9 9 6 

96. DINIT - Directory Request Initiator 

Identifies the name of the customer's representative or group initiating this directory request. 

USAGE: 




EXAMPLE: J A N E D O E 

97. DCHC - Directory Assistance Coordinated Hot Cut 

Indicates that the customer has requested near seamless cutover activity. 


Y = Yes 

NOTE 1: 

USAGE: 

An entry in this field requires a single time entry in the DADT field. 




EXAMPLE: 

Y 


455


98. DADT - Directory Assistance Due Time 

Identifies directory assistance due time. 


Two Digit Hour (01-12)/Two Digit Minute (00-59)/AM or PM 

Two Digit Hour (01-12)/A or P/Two Digit Hour/(01-12)/A or P - AM or PM 

NOTE 1: 

NOTE 2: 

NOTE 3: 

USAGE: 

NOTE 1: 

Indicates the window for cutover time when the DCHC field is not 

populated. 

When the DCHC field is populated, indicates the desired specific cutover 

time. 



Prohibited when the first position of the REQTYP field on the DSR Form is 

"H", otherwise optional. 



EXAMPLES: 1 0 1 5 P M 

1 2 P 0 2 P 

0 8 A 1 0 A 

A 

M 


456








L = Loop 



P = Port 

R = Resale 

U = Usage 





NOTE 1: 

USAGE: 

NOTE 1: 



Required when the DBAN1 and DBAN2 fields on the DSR Form are “N” 

or “E”, otherwise optional. 



EXAMPLE: 

C 


457





NOTE 1: 





NOTE 1: 

USAGE: 

NOTE 1: 

If the DBAN1 sent is not correct, the provider will return the correct 

DBAN1. 


Required when the DBAN1 field on the DSR Form is “N”, otherwise 

optional. 



EXAMPLES: 2 0 1 - 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 







L = Loop 



P = Port 

R = Resale 

U = Usage 





NOTE 1: 

USAGE: 



NOTE 1: Required when the DBAN1 and DBAN2 fields on the DSR Form are “N” 

or “E”, otherwise optional. 

DATA CHARACTERISTICS: 1 alpha character 

EXAMPLE: 

C 


458





NOTE 1: 





NOTE 1: 

USAGE: 

NOTE 1: 

If the DBAN2 sent is not correct, the provider will return the correct 

DBAN2. 


Required when the DBAN2 field on the DSR Form is “N”, otherwise 

optional. 



EXAMPLES: 2 0 1 - 9 8 1 - 3 5 8 7 

2 A 1 B A C 5 G 1 9 C C 5 

103. DLCONT INIT - Name of Contact at Providing Company 

Identifies the provider's representative that should be contacted on directory/listing matters. 

USAGE: 





104. DLCONT TN - Directory Contact Telephone Number 

Identifies the telephone number of the provider's directory/listing contact. 

USAGE: 

NOTE 1: 


Required when the DLCONT INIT field is populated, otherwise optional. 



EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 0 0 - 2 2 6 2 


459


105. DACONT INIT - Name of Contact at Providing Company 

Identifies the provider's representative that should be contacted on directory assistance listing 

matters, if different from the DLCONT INIT. 

USAGE: 





106. DACONT TN - Directory Contact Telephone Number 

Identifies the telephone number of the provider's directory/listing contact. 

USAGE: 

NOTE 1: 


Required when the DACONT INIT field is populated, otherwise optional. 



EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 0 0 - 2 2 6 2 

107. DLQTYR - Number of Listings Received 

Identifies the number of listing detail sections (control, instructions and indicator) received for 

this request. 

USAGE: 




EXAMPLE: 1 2 

108. SQTYR - Service Address Quantity Received 

Indicates the quantity of service address segments received for this request. 

USAGE: 




EXAMPLE: 1 


460


109. DDQTYR - Number of Delivery Segments Received 

Identifies the number of delivery address/information segments received for this request. 

USAGE: 




EXAMPLE: 2 



form. 

USAGE: 




EXAMPLE: 

T H I S I S A P A R T I A L N U M B E R 

P O R T 


461


15.3 LR Alphanumeric Glossary 

The following table is an alpha numeric cross-reference glossary of the Local Response Form. 

LR FORM 


AFVR 32 Additional Field Visit Required 













CHC 19 Coordinated Hot Cut 


CNO 9 Case Number 


DACONT INIT 105 Name of Contact at Providing Company 

DACONT TN 106 Directory Contact Telephone Number 

DADT 98 Directory Assistance Due Time 

DAORD 93 Directory Assistance Order Number 





DCHC 97 Directory Assistance Coordinated Hot Cut 

DD 21 Due Date 

DDA 95 Date of Availability in DA 

DDQTYR 109 Number of Delivery Segments Received 

DEMARC 79 Demarc Designation 

DGOUT 50 DID Digits Out 

DIDNUM 43 DID Reference Number 

DINIT 96 Directory Request Initiator 


DISC ORD 70 Disconnect Order Number 

DLCI 84 Data Link Connection Identifier 

DLCONT INIT 103 Name of Contact at Providing Company 

DLCONT TN 104 Directory Contact Telephone Number 

DLORD 92 Directory Listing Order Number 

DLQTYR 107 Number of Listings Received 

DOR 91 Date of Receipt 

DRTI 48 DID Route Index Number 


462


15.3 LR Alphanumeric Glossary (continued) 

LR FORM 


DSGCON 33 Design/Engineering Contact 

DSN 55 Dialable Station Number 

DSRNO 94 Directory Service Request Number 

DSTN 44 Disassociated Telephone Number 

DTGN 47 DID Trunk Group Number 

DTK 46 DID Trunk Quantity 

DTKID 49 DID Trunk ID 

DTLI 45 DID Telephone Line Identifier 

DTNR 51 DID Telephone Number Range 


EC VER 28 Exchange Carrier Version 


ESDD 31 Estimated Due Date 

FDT 20 Frame Due Time 

HID 40 Hunt Group Identifier 

HNUM 39 Hunt Line Number 

HTSEQ 42 Hunt Sequence 

IBT 15 ISDN BRI Type 

INIT 10 Initiator Identification 

ISPID 62 ISDN Service Profile Identification 






LORD 64 Loop Order Number 

LSR NO 7 Local Service Request Number 

LST 86 Local Service Termination 

LTC 56 Line Treatment Code 

MATN 60 Main/Alternate Telephone Number 

NID 81 Network Interface Device 


NPORD 65 Number Portability Order Number 

NSP DSGCON 34 Network Service Provider (NSP) 

Design/Engineering Contact 

ONSP 36 Old Network Service Provider Identification 

OOR 80 Out of Range Indicator 



PGI 78 Pair Gain Indicator 

PIA 18 Provider Initiated Activity 




463


15.3 LR Alphanumeric Glossary (continued) 

LR FORM 


RCODE 29 Reason Code 

RDET 30 Reason Jeopardy Code Detail 

RDLCI 87 Related Data Link Connection Identifier 

RECCKT 85 Related Exchange Company Circuit Identification 



REP 13 Provider Contact Representative 

RT 17 Response Type 




SLOT 74 Slot 

SPAN 5 Simple Port Account Number 

SPDD/T 22 Simple Port Due Date and Time 

SPP TN 67 Simple Port Ported Telephone Number 

SQTYR 108 Service Address Quantity Received 

ST 14 Switch Type 


TDTR 37 Ten Digit Trigger Response 

TEL NO 16 Telephone Number 


TERS 59 Terminal Numbers 

TLI 41 Telephone Line Identifier 

TNS 58 Telephone Numbers 

TYPE1 37a Type 1 Indicator 

UNIT 77 Unit 



464


Local Response 

V5 

8/00 


CCNA 

1 

PON 

2 

VER AN 

4 

ATN 

3 5 

- - 

LSR NO 

6 

ORD 

7 

CNO 

8 

INIT 

PG _of_ 

9 1 0 

D/TSENT 

1 1 

REP 

1 2 

ST 

13 

IBT 

14 

TEL NO 

1 5 

- - 

RT 

16 

PIA 

17 

CHC 

18 

FDT 

1 9 

DD 

2 0 

EBD 

2 1 

BI1 

22 

BAN1 

2 3 

BI2 

24 

BAN2 

2 5 

EC VER 

2 6 

RCODE 

2 7 

RDET 

2 8 

ESDD 

2 9 

AFVR 

30 

DSGCON 

3 1 

NSP DSGCON 

TEL NO 

3 2 3 3 

- - 

ONSP 

3 4 

TDTR 

35 

Hunt Group Section 

LOCNUM 

3 6 

HNUM 

3 7 

HID 

3 8 

TLI 

HTSEQ 

3 9 4 0 

DID Section 

LOCNUM 

3 6 

DIDNUM 

4 1 

DSTN 

4 2 

- - 

DTLI 

4 3 

DTK 

4 4 

DTGN 

4 5 

DRTI 

4 6 

DTKID 

4 7 

DGOUT 

4 8 

DTNR 

4 

9 - - - 

Circuit Detail Section 

LOCNUM 

3 6 

LNUM 

5 0 

LNEX 

5 1 

ECCKT 

5 2 

DSN 

5 3 

LTC 

5 4 

NOTYP 

55 

TNS 

5 6 

- - 

TERS 

5 7 

MATN 

58 

CKR 

5 9 

ISPID 

6 0 

CFA 

6 1 

LORD 

6 2 

NPORD 

PORTED NBR 

6 3 6 4 

- - 

RTI 

DISC NBR 

6 5 6 6 

- - 

DISC ORD 

6 7 

Tie Down 

SYSTEM ID 

6 8 

CABLE ID 

6 9 

SHELF 

7 0 

SLOT 

7 1 

RELAY RACK 

7 2 

CHAN/PAIR 

7 3 

UNIT 

7 4 

Facility Transmission 

PGI 

75 

DEMARC 

7 6 

OOR 

77 

NID 

78 




(Insert Your Company Logo) Local Response (continued) 


PG _of_ 

1 0 

CCNA 

1 

PON 

2 

VER 

AN 

ATN 

3 4 

5 

- - 

V5 

8/00 

SECLOC Section 

LST 

8 3 

LOCNUM LNUM LNEX DLCI 

3 6 7 9 

8 0 

8 1 

RDLCI 

8 4 

RECCKT 

8 2 


LOCNUM 

3 6 

LNUM 

5 0 

LNEX 

5 1 

ECCKT 

5 2 

DSN 

5 3 

LTC 

5 4 

NOTYP 

55 

TNS 

5 6 

- - 

TERS 

5 7 

MATN 

58 

CKR 

5 9 

ISPID 

6 0 

CFA 

6 1 

LORD 

6 2 

NPORD 

PORTED NBR 

6 3 6 4 

- - 

RTI 

DISC NBR 

6 5 6 6 

- - 

DISC ORD 

6 7 

Tie Down 

SYSTEM ID 

6 8 

CABLE ID 

6 9 

SHELF 

7 0 

SLOT 

7 1 

RELAY RACK 

7 2 

CHAN/PAIR 

7 3 

UNIT 

7 4 


PGI 

75 

DEMARC 

7 6 

OOR 

77 

NID 

78 


LOCNUM 

3 6 

LNUM 

5 0 

LNEX 

5 1 

ECCKT 

5 2 

DSN 

5 3 

LTC 

5 4 

NOTYP 

55 

TNS 

5 6 

- - 

TERS 

5 7 

MATN 

58 

CKR 

5 9 

ISPID 

6 0 

CFA 

6 1 

LORD 

6 2 

NPORD 

PORTED NBR 

6 3 6 4 

- - 

RTI 

DISC NBR 

6 5 6 6 

- - 

DISC ORD 

6 7 

Tie Down 

SYSTEM ID 

6 8 

CABLE ID 

6 9 

SHELF 

7 0 

SLOT 

7 1 

RELAY RACK 

7 2 

CHAN/PAIR 

7 3 

UNIT 

7 4 


PGI 

75 

DEMARC 

7 6 

OOR 

77 

NID 

78 

ATN 

Directory Section 8 5 

- - 

DAORD 

9 0 

DBAN1 

9 7 

DACONT TN 

1 0 3 

- - 

- 

DBI2 

98 

DBAN2 

9 9 

DLQTYR 

1 0 4 

DSR NO 

9 1 

RT 

86 

SQTYR 

105 

CC 

8 7 

DDQTYR 

1 0 6 

DOR 

8 8 

DDA 

9 2 

DLORD 

8 9 

DINIT 

9 3 

DLCONT INIT 

DLCONT TN 

0 10 1 

10 - - 

- 

DCHC 

94 

DACONT INIT 

10 2 

DADT 

9 5 

DBI1 

96 






PG _of_ 

1 0 

CCNA 

1 

PON 

2 

VER 

AN 

ATN 

3 4 

5 

- - 

V5 

8/00 


LOCNUM 

3 6 

LNUM 

5 0 

LNEX 

5 1 

ECCKT 

5 2 

DSN 

5 3 

LTC 

5 4 

NOTYP 

55 

TNS 

5 6 

- - 

TERS 

5 7 

MATN 

58 

CKR 

5 9 

ISPID 

6 0 

CFA 

6 1 

LORD 

6 2 

NPORD 

PORTED NBR 

6 3 6 4 

- - 

RTI 

DISC NBR 

6 5 6 6 

- - 

DISC ORD 

6 7 

Tie Down 

SYSTEM ID 

6 8 

CABLE ID 

6 9 

SHELF 

7 0 

SLOT 

7 1 

RELAY RACK 

7 2 

CHAN/PAIR 

7 3 

UNIT 

7 4 


PGI 

75 

DEMARC 

7 6 

OOR 

77 

NID 

78 


LOCNUM 

3 6 

LNUM 

5 0 

LNEX 

5 1 

ECCKT 

5 2 

DSN 

5 3 

LTC 

5 4 

NOTYP 

55 

TNS 

5 6 

- - 

TERS 

5 7 

MATN 

58 

CKR 

5 9 

ISPID 

6 0 

CFA 

6 1 

LORD 

6 2 

NPORD 

PORTED NBR 

6 3 6 4 

- - 

RTI 

DISC NBR 

6 5 6 6 

- - 

DISC ORD 

6 7 

Tie Down 

SYSTEM ID 

6 8 

CABLE ID 

6 9 

SHELF 

7 0 

SLOT 

7 1 

RELAY RACK 

7 2 

CHAN/PAIR 

7 3 

UNIT 

7 4 


PGI 

75 

DEMARC 

7 6 

OOR 

77 

NID 

78 

REMARKS 

1 0 7 





Local Response 

V5 

8/00 


CCNA PON 

VER AN 

LSR NO ORD CNO INIT 

ATN 

- - 

PG _of_ 

D/TSENT REP ST IBT 

TEL NO RT PIA CHC FDT 

- - 

EBD BI1 BAN1 BI2 BAN2 EC VER RCODE 

DD 

RDET 

ESDD 

AFVR 

DSGCON 

NSP DSGCON 

TEL NO 

- - 

ONSP 

TDTR 

Hunt Group Section 

LOCNUM 

HNUM HID TLI HTSEQ 

DID Section 

LOCNUM 

DIDNUM 

DSTN DTLI DTK DTGN DRTI DTKID 

- - 

DGOUT 

DTNR 

- 

- - 


LOCNUM 

LNUM 

LNEX 

ECCKT 

DSN 

LTC 

NOTYP 

TNS 

- - 

TERS 

MATN 

CKR 

ISPID 

CFA 

LORD 

NPORD 

Tie Down 

PORTED NBR 

- - 

SYSTEM ID CABLE ID SHELF SLOT RELAY RACK CHAN/PAIR UNIT 

RTI 

DISC NBR 

- - 

DISC ORD 


PGI 

DEMARC OOR NID 






PG _of_ 

CCNA PON 

VER AN 

ATN 

- - 

V5 

8/00 

SECLOC Section 

LOCNUM 

LNUM 

LNEX 

DLCI 

RECCKT 

LST 

RDLCI 


LOCNUM 

LNUM 

LNEX 

ECCKT 

DSN 

LTC 

NOTYP 

TNS 

- - 

TERS 

MATN 

CKR 

ISPID 

CFA 

LORD 

NPORD 

Tie Down 

PORTED NBR 

- - 


RTI 

DISC NBR 

- - 

DISC ORD 


PGI 



LOCNUM 

LNUM 

LNEX 

ECCKT 

DSN 

LTC 

NOTYP 

TNS 

- - 

TERS 

MATN 

CKR 

ISPID 

CFA 

LORD 

NPORD 

Tie Down 

PORTED NBR 

- - 


RTI 

DISC NBR 

- - 

DISC ORD 


PGI 


ATN RT CC DOR DLORD 

Directory Section - - 

DAORD 

DSR NO DDA DINIT DCHC DADT DBI1 

DBAN1 

DACONT TN 

- - 

- 

DBI2 DBAN2 DLCONT INIT 

DLQTYR 

SQTYR DDQTYR 

DLCONT TN 

- - 

- 

DACONT INIT 






PG _of_ 

CCNA PON 

VER AN 

ATN 

- - 

V5 

8/00 


LOCNUM 

LNUM 

LNEX 

ECCKT 

DSN 

LTC 

NOTYP 

TNS 

- - 

TERS 

MATN 

CKR 

ISPID 

CFA 

LORD 

NPORD 

Tie Down 

PORTED NBR 

- - 


RTI 

DISC NBR 

- - 

DISC ORD 


PGI 



LOCNUM 

LNUM 

LNEX 

ECCKT 

DSN 

LTC 

NOTYP 

TNS 

- - 

TERS 

MATN 

CKR 

ISPID 

CFA 

LORD 

NPORD 

Tie Down 

PORTED NBR 

- - 


RTI 

DISC NBR 

- - 

DISC ORD 


REMARKS 

PGI 






16.0 LOCAL SERVICE RESPONSE COMPLETION (LSRCM) 

16.1 Local Service Response Completion Form 

This section describes the Local Service Response/Completion (LSRCM) Form that is 

prepared by Windstream and is forwarded to the NSP. This form provides the NSP with 

information regarding critical dates, time and material costs incurred, and Purchase Order 

Number (PON) associated with the customer’s request for service. 

When the LSRCM Form is issued in response to a firm order LSR, its issuance signifies 

Windstream’s local service has been completed with the matching version of the referenced 

LSR Form. 


471


16.2 LSRCM Form Fields 




receiving the completion. 

NOTE 1: 

NOTE 2: 




This CCNA field entry must be identical to the CCNA field entry on the 

LSR Form. 


• IAC Code 

NOTE 1: 

USAGE: 

NOTE 1: 


751-100-112. 


Required when the CCNA on the LSR Form is populated, otherwise 

optional. 





Identifies the customer’s unique purchase order or requisition number that authorizes the 


NOTE 1: 

USAGE: 

This purchase order number field must be identical to the PON field entry 

on the LSR Form. 




EXAMPLE: 

8 2 4 Z 9 


472




NOTE 1: 

This VER field entry must be identical to the VER field entry on the LSR 

Form and/or DSR Form. 


00 - 99 

AA - ZZ 

Blank 

USAGE: 

NOTE 1: 


Required when the SUP field on the LSR Form or DSUP on the DSR Form 

is populated, otherwise optional. 



EXAMPLES: 0 1 

A 

A 



NOTE 1: 

NOTE 2: 

USAGE: 






EXAMPLE: 

A B 3 2 2 1 4 7 



NOTE 1: 

USAGE: 






EXAMPLE: 2 0 1 - 5 5 5 - 1 2 1 2 


473



Identifies the date and time that the response is sent by the provider. 

NOTE 1: 

This date may be different than the completion date. 


U.S. Standard 

Metric Format 







AM or PM 

AM or PM 

NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 

0 5 - 2 2 - 1 9 9 6 - 1 1 1 5 A M 



NOTE 1: 

USAGE: 






EXAMPLE: 

2 0 1 - M 8 1 - 3 5 8 2 


474



Identifies the end user’s existing account telephone number assigned by the current NSP. 

NOTE 1: 

USAGE: 






EXAMPLE: 

2 0 1 - 5 5 5 - 1 2 1 2 

9. CD - Completion Date 

Identifies the date the service order was completed and turned up to the customer. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 




hyphens) 

EXAMPLE: 0 5 - 2 2 - 1 9 9 6 


Identifies the type of response being returned to the customer. 


Z = Completion 

USAGE: 




EXAMPLE: 

Z 


475




due date. 


U.S. Standard 

Metric Format 





NOTE 1: 

USAGE: 

NOTE 1: 



Required when the RT field is “Z” and the CD field and the billing date are 

different, otherwise optional. 


hyphens) 

EXAMPLE: 0 3 - 2 2 - 1 9 9 6 

12. TIND - Time Indicator 

Indicates the type of chargeable labor rate incurred to install the service. 


1 st Character (Time Type) 

A = Normal Regulated 

B = Premium Regulated 

C = Holiday Regulated 

D = Overtime Regulated 

E = Normal Unregulated 

F = Premium Unregulated 

G = Holiday Unregulated 

H = Overtime Unregulated 

2 nd Character (Type of Labor) 

A = Engineering 

B = Plant 

C = Other 

USAGE: 




EXAMPLE: B A 


476


13. TIME - Amount of Time on Job 

Identifies the amount of time on the job to the nearest quarter hour. 


Increments of 15 minutes reflected as quarter hour entries. 

USAGE: 

NOTE 1: 


Required if TIND field is populated, otherwise prohibited. 


6 numeric characters (with 1 decimal) 

EXAMPLES: . 2 5 

1 0 . 2 5 

14. MTL - Installation Material 

Identifies the material required to complete the inside wire service requested. 


C = Cable 

J = Jacks 

B = Both 

USAGE: 




EXAMPLE: 

C 

15. MCOST - Material Cost 

Identifies the cost of the inside wire material used at the end user premises. 

USAGE: 

NOTE 1: 


Optional when the MTL field is populated, otherwise prohibited. 


9 numeric characters (with 1 decimal) 

EXAMPLE: 1 1 4 . 0 0 


477


16. REP - Provider Contact Representative 

Identifies the provider's representative handling this response. 

USAGE: 




EXAMPLE: 

M E L V I N S I M C O E 


Identifies the telephone number of the provider's representative handling this response. 

USAGE: 




EXAMPLE: 

2 0 1 - 9 8 1 - 3 5 8 2 


478




form. 

USAGE: 




EXAMPLE: 

R E Q U E S T C O M P L E T E D A S O R I G 

A N A L L Y 

S C H E D U L E D 


479


16.3 LSRCM Alphanumeric Glossary 

The following table is an alphanumeric cross-reference glossary of the Local Service 

Response/Completion Form fields. 

LSRCM FORM 





CD 9 Completion Date 





MCOST 15 Material Cost 

MTL 14 Installation Material 



REP 16 Provider Contact Representative 



TIME 13 Amount of Time on Job 

TIND 12 Time Indicator 



480


Local Service Completion Form 

V5 

8/00 

Administrative 

Section 

CCNA 

1 

PON 

2 

VER 

3 

AN 

ATN 

4 5 

- - 

RD/TSENT 

6 

EAN 

7 

EATN 

8 - - 

CD 

9 

RT 

10 

EBD 

1 1 

TIND 

1 2 

TIME 

1 3 . 

MTL 

14 

MCOST 

1 5 

. 

REP 

1 6 

TEL NO 

1 7 - - 

REMARKS 

1 8 





Administrative 

Section 

Local Service Completion Form 

CCNA PON 

VER AN ATN 

V5 

8/00 

- - 

EATN CD 

- - 

TEL NO 

- - 

RD/TSENT EAN 

RT EBD 

TIND TIME 

. 

MTL MCOST 

. 

REP 

REMARKS

Local Service Ordering Practices - Windstream Business Wholesale

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?