€¦ · Web view15.0 pa and delaware ... conditional posting 50. 20.0 county codes for new york 51. 21.0 tar code listings for ... thrwy concourse conc lower lwr tower twr convent

VERIZONREGIONAL E 9-1-1 Electronic

Interface GuideIssue Date January, 2014

IMPORTANT: Please contact the Verizon E911 System Administration group at =>>[email protected] for further guidance and direction due to the migration to a new ALI system that is underway.

mailto:[email protected]

Welcome to VERIZON’S E 9-1-1 Electronic Interface USER GUIDE!

Competitive Local Exchange Carriers (CLECs), Independent Telephone Companies, and Wireless Carriers (jointly described as ”Carriers use the Verizon E 9-1-1 Electronic Interface to access the Verizon E 9-1-1 database depending on the geographic area in which the Carrier is doing business with Verizon.

The 9-1-1 Information Manager Web portal is being migrated to a new web portal called Intrado Unified Portal. It has similar functionality with new security access method. States are being migrated on a staggered basis and the project should complete by end of year 2015. As of January 2014, the states of California and Florida have already migrated to this new platform.

As used within this document, the term “Verizon East” refers to the following states:

Delaware, District of Columbia, Maryland, Massachusetts, New Jersey, New York, Pennsylvania, and Virginia;

and “Verizon West” refers to the following states:

California, Florida, and Texas

Please contact Verizon E 9-1-1 System Administration below with any questions regarding the appropriate Verizon Electronic Interface at either the telephone numbers shown below or via email at [email protected].

Contact Name Telephone Number Business CellDonna Beecher 914-801-3717 914-417-5874Joyce Juliano-Pais 732-221-7863Linda Kerkam 914-801-3740Julie Leahy 617-535-5551 617-835-3270Betty Scala 617-535-5495National 911 Support 800-872-3356

:

V2.12


TABLE OF CONTENTS

1.0 INTRODUCTION.........................................................................................................................5

1.1 E9-1-1 ELECTRONIC INTERFACE.....................................................................5

2.0 GETTING STARTED...................................................................................................................5

3.0 USER ID/ACCESS REQUEST FORM .......................................................................................6

4.0 ACCESSING VERIZON’S 9-1-1 INFORMATION MANAGER.....................................................74.1 LOGGING IN TO VERIZON’S 9-1-1 INFORMATION MANAGER...................................84.2 FILE NAMES...................................................................................................................8

5.0 MODIFIED NENA 2.1 FORMAT FOR DATA EXCHANGE..........................................................95.1 DISABILITY INFORMATION – NEW ENGLAND DATABASE.......................................10

6.0 NENA 2.1 DATA RECORD SPECIFICATIONS.........................................................................11

7.0 PS/ALI DATABASE MANAGEMENT SOFTWARE - DISCONTINUED ....................................16

8.0 VERIZON E9-1-1 CONTACT TELEPHONE NUMBERS...........................................................17

9.0 SERVICE ORDER PROCESSING ERROR CODE MESSAGES.............................................19

10.0 AUTOMATIC ERROR CORRECTION FEATURE...................................................................25

11.0 LNP.........................................................................................................................................26

11.1 OVERVIEW.................................................................................................................2611.2 AUTOMATIC ERROR CORRECTION FEATURE FOR LOCAL NUMBER PORTABIILTY.....................................................................................................................2711.3 AUTOMATIC ERROR CORRECTION SAMPLE FILES..............................................2811.4 CHANGES TO SERVICE ORDER PROCESSING IN AN LNP ENVIRONMENT........2911.5 763 AUTO-REPROCESS FUNCTIONALITY...............................................................3011.6 LNP UNLOCK REPORT..............................................................................................31

12.0 VERIZON’S ELECTRONIC INTERFACE SAMPLE FILES.....................................................32

12.1 ATTACHMENT 1.........................................................................................................3312.2 VERIFYING THAT FILE PROCESSED SUCCESSFULLY..........................................3412.3 ATTACHMENT 2.........................................................................................................3512.4 ATTACHMENT 3A & 3B..............................................................................................3612.5 ATTACHMENT 4.........................................................................................................3812.6 ATTACHMENT 5A &5B...............................................................................................3912.7 ATTACHMENT 6.........................................................................................................4112.8 ATTACHMENT 7.........................................................................................................4212.9 ATTACHMENT 8.........................................................................................................43

V2.13

TABLE OF CONTENTS

13.0 NEW YORK STREET THOROUGHFARES – VALID ABBREVIATIONS................................44

14.0 NEW ENGLAND STREET THOROUGHFARES – VALID ABBREVIATIONS.........................45

15.0 PA AND DELAWARE STREET SUFFIX THOROUGHFARES – VALID ABBREVIATIONS........................................................................................................................................................ 46

16.0 NEW ENGLAND STREET ADDRESS GUIDELINES..............................................................47

17.0 NEW YORK STREET ADDRESS GUIDELINES.....................................................................48

18.0 PENNSYLVANIA AND DELAWARE ADDRESS GUIDELINES..............................................49

19.0 PENNSYLVANIA AND DELAWARE – CONDITIONAL POSTING..........................................50

20.0 COUNTY CODES FOR NEW YORK.......................................................................................51

21.0 TAR CODE LISTINGS FOR PENNSYLVANIA AND DELAWARE..........................................53

22.0 WASHINGTON DC TAR CODE LISTING...............................................................................54

23.0 VIRGINIA TAR CODE LISTING..............................................................................................55

24.0 MARYLAND TAR CODE LISTING..........................................................................................64

25.0 NEW JERSEY E9-1-1 REQUIREMENTS...............................................................................65

26.1 NEW JERSEY MSAG QUARTERLY EXTRACTS.....................................................10626.2 OUTPUT FILE FORMAT FOR NEW JERSEY MSAGS.............................................10726.3 NEW JERSEY COUNTY ABBREVIATION CODES..................................................110

26.0 GLOSSARY OF ACRONYMS ..............................................................................................111

V2.14

1.0 Introduction

1.1 E 9-1-1 Electronic Interface:

Within the Verizon footprint, there are two unique Electronic Interfaces that are utilized depending on the geographic area in which the Carrier operates. The guide contains general information for both Verizon East and Verizon West and for the State of New Jersey. Descriptions on how to access each of the individual interfaces are described in the following User Guides:

Verizon East and West: 911 IM USER GUIDENew Jersey: SYSTEM-9 ONLINE INTERFACE

2.0 Getting Started

Before contacting E 9-1-1 System Administration, contact must be made with a Verizon Account Representative in order to establish a business relationship with Verizon.

Read through this entire Guide before contacting System Administration. Each local service provider must register with the National Emergency Number

Association (NENA) to establish a company identifier. The telephone number to call to obtain a (NENA) company ID is 1-800-332-3911 or 202-466-4911.

You can register on-line at http://www.nena.org/?page=CID2014 Obtain Internet Explorer and an internet connection as this is how you will access the

Verizon E9-1-1 Systems. Obtain a copy of the appropriate User Guide from E9-1-1 System Administration. The E 9-1-1 records that a carrier transmits to Verizon need to be entered in a

database by using software such as Microsoft Access. Microsoft EXCEL is not acceptable because the data that is transmitted is not formatted properly.

Verizon uses modified NENA 2 data requirements for file transfer. There are mandatory field requirements as shown in the NENA 2 Section of this Guide.

In order to obtain access to the Verizon E911 Electronic Interface to transmit, update and maintain your customer records in the Verizon E911 Database, please have your Verizon Account Manager contact the Verizon E911 System Administration Group by completing the form below and forwarding as indicated. An electronic version of the login form is available by contacting [email protected] In Verizon East (states MA, NY, NJ, PA, DE, MD, DC, VA, the account

manager will forward the customer’s completed 9-1-1 Information Manager Login Request form (see below) to: [email protected].

In Verizon West (states CA, FL,TX) the account manager will forward the customer’s completed 9-1-1 Information Manager Login Request form (see below) to (via internal Notes): dbmc-ca-fl-request.Once the Verizon Account Manager has contacted the Verizon E911 System Administration Group, a member of that group will contact the customer to work with you on this matter.

Notify Verizon E 9-1-1 System Administration (Verizon West – Database Management Center) when NENA/Company ID is obtained.

V2.15


http://www.nena.org/?page=CID2014

3.0 USER ID/Access Request Form

Verizon 9-1-1 Information ManagerLogin Request Form

Note: An electronic version of this form will be provided when you are ready to convert.

V2.16

4.0 Accessing Verizon’s 9-1-1 Information Manager

SYSTEM REQUIREMENTS

The following list identifies general requirements for 9-1-1 Information Manager: Users access the server over a secured network. The software is designed for use with Internet Explorer version 6.0 or higher.

Compatibility with other browsers is not guaranteed. The software is designed for use with Windows® 2000 Professional and Windows

XP and Windows 7. Compatibility with other operating systems is not guaranteed.

SECURITY

Overall Security Requirements All users must have a digital certificate as well as a login and password to access

the system. The Verizon E9-1-1 System Administration group will submit the request for the digital certificate on behalf of the user to the Verizon Wholesale Access Gateway (WAG) group. It will take at least 24 hours for the digital certificate request to be processed.

All user instructions regarding digital certificates can be obtained by contacting the Verizon E911 System Administration Group via email at [email protected].

These instructions are also available on the Verizon Wholesale E911 Website: http://www22.verizon.com/wholesale/local/E911/enhanced-9-1-1.html

Users must change their passwords the first time they log in, and can then change it at any time thereafter.

System functionality and information retrieval is determined by the user’s profile.

.

V2.17

1.4.1 Accessing Verizon’s 9-1-1 Information Manager

When a carrier is ready to access the system for the first time, it should contact the E 9-1-1 System Administration Team. Verizon will provide detailed instructions required to access the system. Verizon will also provide the appropriate URL and an initial user name and password. All 9-1-1 Information Manager functionality is detailed in the 9-1-1 Information Manager User Guide

4.2 File Names

Update files must be sent using the naming convention below:

Filename= xxxxyyyz.dat

Verizon E 9-1-1 System Administration provides the first four digits of your filename ‘xxxx’ to the Carrier. It is unique for your company alone.

The ‘yyy’ of the filename is the three digit Julian calendar day that indicates the

Actual calendar day that the file was actually transmitted. The ‘z’ of the filename is a sequence number. The sequence number can be a digit 0 to 9 as the Carrier may send up to 10

files to Verizon on a daily basis. The “.dat” extension signifies that a data file is being transmitted to Verizon.

This transmission is required or else the file will not process. The “.dat” extension is required, otherwise the file will not process.

V2.18

5.0 Modified NENA 2.1 Format for Data Exchange

This Section displays the unique differences that exist in several of the East states within Verizon that must be recognized when inputting data into the E 9-1-1 database. NENA Version 2.1 Format for Data Exchange is displayed in Section 6 of this document.

FIELD NAME POS BYTES IMPORTANT INFO TO REVIEW

HOUSE NUMBER SUFFIX

22-25 4 NOTE: IN THE MID-ATLANTIC STATES (PA, DE, VA, DC, MD) THE 1ST CHARACTER OF THIS FIELD MUST CONTAIN A HYPHEN (FOR EX: -1/2 OR –A

* STREET NAME 28-87 60 Verizon READS 48 BYTES FOR STREET NAME.

STREET SUFFIX 88-91 4 NEED TO DISCUSSNEED TO COMPLY WITH STATE REQUIREMENTS

FIELD NAME POS BYTES IMPORTANT NOTES TO DISCUSSLOCATION 128-187 60 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

NOTE 1: THE LOCATION FIELD IN THE NEW ENGLAND & NEW YORK DATABASE IS LISTED AS THE TELCO FIELD. IT IS 30 BYTES IN LENGTH AND IS FOUND IN POSITIONS 128-157. THIS IS WHERE LOCATION INFORMATION SUCH AS APARTMENT, FLOOR AND BUILDING SHOULD BE ENTERED.NOTE 2: THE LOCATION FIELD IN THE PENNSYLVANIA AND DELAWARE DATABASES IS LISTED AS THE ADDRESS EXTENSION FIELD.

NOTE 3: THE LOCATION FIELD IN THE GATEWAY DATABASE (VIRGINIA, MARYLAND AND DC) IS LISTED AS LOCATION/DRIVING INSTRUCTIONS.

* See Sections 13- 18 for Valid Street Thoroughfares for NY, NE, PA and DE, all others use valid Postal abbreviations.

TAR 350-355 6 Populate this field with the applicable TAR Code inNew York, Virginia, Maryland, Pennsylvania, Delaware, Maryland and Washington DC. All other states should space fill

V2.19

5.1Disability Information New England Database

In New England disability information is populated in the ‘location’ field using the following specific ‘disability indicators’.

DISABILITY INDICATORS USED FOR:LSS LIFE SUPPORT SYSTEMMI MOBILITY IMPAIREDB BLIND

DHH DEAF & HARD OF HEARINGTTY TELETYPWRITERSI SPEECH IMPAIREDDD DEVELOPMENTALLY DISABLED

NOTE: In New York, there are no specific procedures or indicators used to reference disability information in the database. Handicapped information may be entered within the “location” field as a ‘free floating’ remark and is entered at the discretion of the telephone company provider.

V2.110

NENA 2.1 Data Record Specifications

The following section contains the Data Record, Header Record, and Trailer Record specifications based on the National Emergency Number Association (NENA) recommended format for data exchange - Version 2. This version can also be found on the Internet at http://www.nena.org/9-1-1TechStandards/nena_recommended_standards.htm.

Field Name Positions Bytes

Type Req’d Description

Function Code

1 1 A R The type of activity the record is being submitted for. Valid entries are: C = Change, D= Delete, I = InsertU= Unlock, M=Migrate

NPA 2 - 4 3 N R The three-digit area code of the Calling/Working Number.

Calling Number

5 - 11 7 N R The seven-digit telephone number of the Calling/Working Number.

House Number

12 - 21 10 AN R/SF The house number. This field should be spaced filled if no house number is available.

House Suffix Number

22 - 25 4 AN R/SF ***NEED TO DISCUSS WITH VERIZON***The house number extension. (e.g. 1/2) This field should be space filled if no suffix applies.

Prefix Directional

26 - 27 2 A R/SF The leading street direction prefix. Valid entries are: N, S, E, W, NE, NW, SE, and SW. This field should be space filled if no prefix applies.

Street Name 28 - 87 60 AN R ***NEED TO DISCUSS WITH VERIZON***The service address of the Calling Number.

Street Suffix 88 - 91 4 A R/SF ***NEED TO DISCUSS***The street abbreviation, as defined by the U. S. Postal Service Publication 28. (e.g. AVE) This field should be space filled if no suffix applies.

Post Directional

92 - 93 2 A R/SF The trailing street direction suffix. Valid entries are: N, S, E, W, NE, NW, SE, and SW. This field should be space filled if no suffix applies.

Community Name

94 - 125 32 A R The service community name of the street / house number as assigned by

V2.111

http://www.nena9-1-1.org/



the Municipal Street Address Guide.

State 126 - 127 2 A R The alphabetic state abbreviation as defined by the U. S. Postal Service. (e.g. PA)

Location 128 - 187 60 AN R/SF The additional address information describing the exact location of the Calling Number. (e.g. SUITE 2002, APT 706A) This field should be space filled if no location applies. See Notes for additional information on the use this field.

Customer Name

188 - 219 32 AN R The subscriber name associated with the Calling Number.

Class of Service

220 1 AN R Valid entries are:

1 = Residence2 = Business3 = Residence Private Branch Exchange (PBX)4 = Business PBX5 = CENTREX6 = Coin 1 way out7 = Coin 2 way8 = Mobile9 = Residence Off Premise Extension (OPX)0 = Business OPXA= Customer Owned Coin TelephoneG= Wireless Phase 1H= Wireless Phase 2V= VOIP

Type of Service

221 1 N R Valid entries are:

0 = Not Foreign Exchange (FX) or Non Published (Non Pub)1 = FX in 9-1-1 serving area2 = FX outside 9-1-1 serving area3 = Non Pub4 = Non Pub FX in 9-1-1 serving area5 = Non Pub FX outside 9-1-1 serving area

Note: The only valid entries for FX service is1 and 4.

V2.112



Exchange 222 - 225 4 AN R/SF Field not used, space fill.

ESN 226 - 230 5 AN N/SF Field not used, space fill.

Main NPA 231 - 233 3 N R +/or SF

The three-digit area code of the Main Number associated with the Calling Number.***NEED TO DISCUSS WITH VERIZON***

Main Number 234 - 240 7 N R +/orSF

The seven digit telephone number of the Main Number associated with the Calling Number***NEED TO DISCUSS***

Order Number 241 - 250 10 AN R/SF The service order number for the activity establishing this record.

Extract Date 251 - 256 6 N R +/orSF

The date on which the record was created in month, day, year, format (e.g. MMDDYY).

County ID 257 - 260 4 AN N/SF Field not used, space fill.

Company ID 261 - 265 5 AN N/SF The Telephone Company Identification code. This field is to be populated using the NENA Company Code.

Source ID 266 1 AN R +/orSF

A code that indicates whether the data is part of an initial data load or re-load or part of a daily update process. Valid values are:Space = Daily Update, C = Load

Zip Code 267 - 271 5 AN N/SF The five digit Postal Zip Code.

Zip + 4 272 - 275 4 AN N/SF Field not used, space fill.

General Use 276 - 286 11 AN N/SF Field not used, space fill.

Customer Code

287 - 289 3 AN N/SF Field not used, space fill.Need to discuss in the West

Comments 290 319 30 AN N/SF Field not used, space fill.

X Coordinate 320 - 328 9 N N/SF Field not used, space fill.

Y Coordinate 329 - 337 9 N N/SF Field not used, space fill.

Z Coordinate 338 - 342 5 N N/SF Field not used, space fill.

V2.113



Cell ID 343 - 348 6 AN N/SF Field not used, space fill.

Sector ID 349 1 AN N/SF Field not used, space fill.

TAR code 350 - 355 6 AN R ***NEED TO DISCUSS***Taxing Area Rate code. See Notes for additional information on the use this field.

Reserved 356-376 21 AN N/SF This field is reserved for the Database Management Systems provider’s use.

Alternate Number

377-386 10 N R/SF Customer Number being remote call forwarded in Interim Number Portability service.

Expanded Extract Date

387-394 8 N R/SF Date on which the record was created in the format YYYYMMDD

NENA reserved

395-480 86 AN N This field is reserved for NENA Data Technical Committee Assignment.

Reserved 481-511 31 AN N/SF This field is reserved for the Data Base Management Systems Provider’s use.

End of Record

512 1 AN R End of record indicator. Always contains an asterisk (*).

Notes:

1. Req’d (required) column R = Required field. Must be populated for every subscriber’s record spaces not permitted. R/SF = Required field. Must be populated if present in subscriber’s record otherwise space fill. N/SF = Not required field. Space fill.

2. All fields are left justified with trailing spaces.

3. The actual lengths of some fields on the 9-1-1 systems (e.g. Street, Community, Location, et al) are shorter than the NENA-2 defined length and vary by system, which may result in truncation of rightmost data. The most significant information should always be left justified in these and all fields.

4. All alphanumeric (AN) fields may contain upper case letters, numbers and punctuation characters. Lower case and control characters are not permitted.ASCII characters used in alpha only and alpha/numeric fields should be limited to A thru Z, a thru z, 0 thru 9, comma ‘, ’,forward slash ‘ / ’, semi colon ‘; ‘, ampersand ‘&’, and apostrophe ‘ ’ ’. Spaces are allowed with one exception----the first character of a field may not be a space.

V2.114

Other characters may impact the accurate processing of data.Do NOT use the accent mark (for ex. Café) as it will fail data file processing.

NENA 2.1 Data Record Specifications (continued)

NENA Header and Trailer format for data exchange

NENA Recommended Header Format for Data ExchangeField Name Position Bytes TypeHeader Indicator 1-5 5 UHLExtract Date 6-11 6 MMDDYY

for ex 030300Company Name 12-61 50 CWTCycle Counter 62-67 6 Numeric fieldCounty Id 68-71 4 Alpha Numeric fieldState 72-73 2 NYGeneral Use 74-93 20 Alpha Numeric fieldRelease Number 94-96 3 Numeric fieldFormat Version 97 1 Numeric fieldExpanded Extract Date 98-105 8 Numeric fieldReserved 106-511 406 Alpha Numeric fieldEnd of Record 512 1 *

Note: All fields are Left-justified with trailing spaces, EXCEPT for the Cycle Counter;This is Right-justified with leading spaces.

NENA Recommended Trailer Format for Data Exchange

Field Name Position Bytes TypeTrailer Indicator 1-5 5 UTLExtract Date 6-11 6 MMDDYY

for ex 030300Company Name 12-61 50 CWTRecord Count 62-70 9 Numeric FieldExpanded Extract Date 71-78 8 Numeric FieldReserved 79-511 433 Alpha Numeric fieldEnd of Record 512 1 *

Note: All fields are Left-justified with trailing spaces, EXCEPT for the Record count; This is Right-justified with leading spaces.

V2.115

7.0 PS ALI Database Management Software – Discontinued

This Verizon proprietary product, PS-ALI 95 has been discontinued. Support for this product will be withdrawn after 12/31/2008.

V2.116

8.0 Verizon E 9-1-1 Contact Telephone Numbers

Title Telephone Number

E 9-1-1 System Administrators

Julie Leahy 617-535-5551 Joyce Juliano-Pais 732-221-7863 Linda Kerkam 914-801-3740 Donna Beecher 914-801-3717 Betty Scala 617-535-5495NEW ENGLAND DBMC Fall River Help Desk 508-675-6800

Data Management (NE)

Supervisors: Marie Keeler 508-673-3911

NEW YORK DBMCData Management (NY)

Associate Director: Joseph Gondek 914-422-8370 Supervisors: Tanya Whitfield 914-422-8306 Erika Hart 914-422-8368 NEW JERSEY DBMCUser Help Desk 732-922-9911

Supervisors: Sherri Evans 732-922-0618 Henry Hanson 973-509-9902

V2.117

Title Telephone Number

MARYLAND/VIRGINIA/ WESTVIRGINIA/WASHINGTON DCPENNSYLVANIA/DELAWARE DMCSupervisors:Mike Hafer (Acting Supervisor) Clec 610-853-5552

Amy McKinnon (DE) 302-761-5322

Jacqueline Turner (MD & DC)

410-393-9017

Victoria Vereb (PA) 724-830-2654

Manager – Database ManagementCenter (PA,DE,MD,DC,VA)Cathy Snowden 973-509-9901

Staff Support:Meladee Noble-Carbajal 562-335-3968

V2.118

2. Service Order Processing Error Code Messages

The following lists contains a description of the Service order processing error messages and suggested corrective action required to correct these errors:

E9-1-1 Error Code Descriptions - Carrier Corrective ActionError Code

Description Suggested Corrective Action [West only]

002 Non-numeric character in the telephone number. This includes any spaces or alpha characters in the NPA, NNX, or TN fields of the telephone number. This is considered a data error.

Correct the TN and resend the record.

003 Non-numeric character in the main telephone number. This includes any space or alpha characters in the NPX, NNX, or TN fields of the main number. This is considered a data error.

Same as 002 above.

009 Illegal class of service. The class of service must be a digit from 0 to 9.

Correct the Class of Service and resend the record.

010 Illegal type of service. The type of service must be a single digit from 0 to 5.

Correct the Type of Service and resend the record.

011 Attempted an illegal main number default. An attempt was made to default part of a main number that already had a distinct component. Blank fields in the main telephone number will be populated with the same value as the telephone number. But a field can not be defaulted if some earlier part of the main number has already been specified. (Example: leaving the main NNX field blank after specifying an NPA.) This is considered a data error.

Enter a complete TN in the ‘Main Number’ field, or make sure that the field is completely blank.

012 Non-numeric character in the end-user code. The end-user code must be all numeric. Leading spaces are allowed. This is considered a data error.

Correct the ‘Customer Code’ entry and resend the record.

700 Illegal function of change. The valid functions of change for telephone number records are (I)nsert, (C)hange, (D)elete, (M)igrate, and (U)nlock. This is considered a data error.

Correct the ‘Function of Change’ and resend the record.

701 No MSAG record found. No MSAG record was found for this address. This includes cases where the street name does not exist in the MSAG and where the street exists, but the ranges do not cover the current address.

Verify all fields of the address (including directionals, suffixes, and community name) are entered completely; and that the address matches an existing MSAG range. Correct the address and resend the record. If the address appears correct, contact the E9-1-1 jurisdiction for their MSAG action.

702 Record already exists. An attempt was made to insert a telephone number that already exists.

If authorized by the CARRIER, Verizon will automatically convert the FOC from ‘I’ to ‘C’, and process the record. If not authorized, the CARRIER should change the FOC to ‘C’ and resend the record. Reference Exhibit A.

V2.119

703 Main record not found. An attempt was made to insert or change a subsidiary whose main telephone number does not exist in the database.

Verify that an ALI record for the Main TN has been sent, and that the Main TN entered on the record in error is entered correctly. Correct and resend the record. Ensure that the Main TN record did not fail validation.

704 Telephone number record doesn't exist on a delete. An attempt was made to delete a telephone number record that does not exist in the database.

This record does not currently exist in the database. DO NOT RESEND THE RECORD. If authorized, Verizon will automatically delete these error records upon receipt. Reference Exhibit A.

705 Record does not exist on a pilot delete. An attempt was made to perform a delete on a main telephone number that does not exist in the database.

Contact "the appropriate E9-1-1 DBMC if you receive this error.

706 Service order error field is populated. The service order error field is populated with some non-space character(s). The meaning of this error field is implementation specific.

Verify that this field is space filled only and resend the record.

707 Subsidiary end-user code mismatch. An attempt was made to insert a subsidiary with a different end-user code than its main telephone number record.

Correct the ‘Customer Code’ and resend the record.

709 For internal use only. If received, contact "the appropriate E9-1-1 DBMC.

710 Customer codes do not match on a change. The end-user code on a change to a telephone number record does not match the end-user code of the existing record.

Correct ‘Customer Code’ entry and resend the record. If the TN in error was a Verizon CA TN, the entry should be the NXX of the TN.

711 Customer codes do not match on a delete. The end-user code on a delete or pilot delete operation does not match the end-user code of the record to be deleted.

Same as 710 above.

712 Record does not exist for a change. An attempt was made to change a telephone number record that does not exist in the database.

If authorized by the CARRIER, Verizon will automatically convert the FOC from ‘C’ to ‘I’, and process the record. If not, the CARRIER should change the FOC to ‘I’ and resend the record. Reference Exhibit A.

720 NPA to NPD translation not found. The NPD translation for the current NPA does not exist in the NPA to NPD translation table.

Check that the NPA of the TN record is correct and resend. If the NPA appears correct, contact your Verizon E9-1-1 Database Management Center representative.

721 Type of service is a foreign exchange. The number belongs to a foreign exchange, i.e. the type of service is a 2 or 5.

Ensure that the proper entry was made in the 'Type of Service' field and resend.

723 NPANNX to ESSID translation not found. The translation for the given NPANNX was not found in the NPANNX to ESSID translation table. Verizon corrects this error.

N/A Contact your Verizon Area Specialist in the appropriate E9-1-1 DBMC if you receive this error code.

725 For internal use only. If received, contact "the appropriate E9-1-1 DBMC as noted in Section 3.1".

V2.120

732 Multiple MSAG record exchange matches found. An attempt to insert or change a record with no community name was made. While trying to query the MSAG to match based on the address and exchange, multiple records were found.

Correct the ‘Community Name’ field and resend the record.

737 Exchange matching failed to find a unique MSAG record. The MSAG was queried using the address and community name with the exchange-matching feature turned on. Multiple address and community name matches were found, and the exchange was used to try and find a unique MSAG record. There were no MSAG records found with the same address, community, and exchange.

Ensure that the correct value is entered in the ‘Exchange’ field of the record and resend it.

738 Attempted to change a main number to a subsidiary line. The record in error is currently a main number with subsidiaries in the database. The attempted change would make this number into a subsidiary of another line. This would leave the original subsidiaries without a valid main number.

Verify and correct the ‘Main Number’ field and resend the record.

739 Street names do not match on a delete. The street name in the delete record does not match the street name in the database. If a delete record has a street name present, it must match the street name of the record in the database. The street name is not a required field on a delete.

Verify the address, correct, and resend the record or resend the delete without a street name.

740 Delete attempted on a number with subsidiaries. A function of change "D" was attempted on a phone number that has subsidiaries.

Correct the FOC and resend the record or send updates to remove or change the pilot relationship.

741 Main number is already a subsidiary line. An attempt was made to insert a subsidiary whose main number is already a subsidiary to another line. This would leave this number without a valid main number.

Verify the ‘Main Number’ field, correct, and resend the record.






747 Record already exists in another database. This telephone record already exists on the system, but in another database.

Contact "the appropriate E9-1-1 DBMC as noted in Section 3.1".




V2.121

759 Exact exchange match not found. Exchange matching is turned on and this TN record has matched against a single MSAG record, but the exchange value in the TN record does not match the exchange value in the MSAG.

Verify and correct the ‘Exchange’ field and resend the record. Contact your Verizon E9-1-1 Area Specialist in the appropriate E9-1-1 DBMC.

760 For internal use only. If received, contact "the appropriate E 9-1-1 DBMC.

761 Unlock attempted on an unlocked TN (same Company ID). The same Company ID as is in the new service order record has already unlocked this TN. In effect, this is a duplicate unlock request.

The TN has already been unlocked. DO NOT RESEND THE RECORD.

762 Unlock attempted on an unlocked TN (different Company ID). This means that two different Companies have tried to unlock the same TN record. One of these Companies is in error. Further investigation as to which Company actually owns this record should be pursued.

Another company has unlocked the TN. Verify the FOC for the update record. Contact the migrating company to investigate. If the record should belong to your company, contact "the appropriate E9-1-1 DBMC for the identity of the current record owner.

763 Migrate attempted on a locked TN. In order for an "M" or migrate function of change service order to process correctly, a "U" or unlock service order must have been previously processed successfully.

Contact the Service Bureau for the ‘donor’ company to determine the status of the ‘U’ (unlock) record. DO NOT RESEND THE RECORD. For Verizon. Once you have been notified the donor company has unlocked the record, resend your record.

764 Insert attempted on a TN that is unlocked. Once a TN record has been successfully unlocked, the only valid function of change is "M" or migrate.

Verify and correct the FOC and resend the record.

765 Change attempted on a TN that is unlocked. Once a TN record has been successfully unlocked, the only valid function of change is "M" or migrate.

Same as 764 above.

766 Delete attempted on a TN that is unlocked. One a TN record has been successfully unlocked, the only valid function of change is "M" or migrate.

Same as 764 above.

767 Company IDs do not match on a change. The TN record that you are trying to change is assigned to a different Company ID. This record needs to be unlocked by the original Company and a migrate order processed by the new Company. Only after the migrate order has been successfully processed can change orders be applied.

Verify that the TN has been entered correctly on the record. If the record appears correct, contact the service bureau of the donor company. For Verizon.

768 Company IDs do not match on a delete. The TN record that you are trying to delete is assigned to a different Company ID. This record needs to be unlocked by the original Company and a migrate order processed by the new Company. Only after the migrate order has been successfully processed can delete orders be applied.

Same as 767 above.

V2.122

769 Clerical and ERROR record Company IDs do not match. The Company ID(s) associated with the clerical user does not match the Company ID of the ERROR record. Either an additional Company ID needs to be assigned to the clerical user, or a different clerical user with the appropriate Company ID should process this record.

N/A If this error is received, contact "the appropriate E9-1-1 DBMC.

770 Clerical and TN record Company IDs do not match. The Company ID(s) associated with the clerical user does not match the Company ID of the TN record. Either an additional Company ID needs to be assigned to the clerical user, or a different clerical user with the appropriate Company ID should process this record.

Same as 769 above.

771 Unlock attempted on a nonexistent TN. The TN record that you are attempting to unlock does not exist.

The TN does not exist in the database and cannot be unlocked. DO NOT RESEND THE RECORD.

772 Company IDs do not match on an unlock. Only the Company ID associated with the TN record can unlock that TN record.

Verify the TN on the record. If it appears correct, contact the Verizon DBMC for current owner information. If the TN is incorrect, correct and resend the record.

773 Migrate attempted on a nonexistent TN. The TN record that you are trying to migrate does not exist.

If authorized by the CARRIER, Verizon will automatically convert the FOC from ‘M’ to ‘I’, and process the record. If not, the CARRIER should change the FOC to ‘I’ and resend the record.

774-780 No Action Required No Action Required

775 A County default MSAG record does not exist for this county.

Verify that the TAR Code (Pos 350-355) is populated on the record.

781 Insert attempted on an existing TN with a different Company ID.

Verify FOC and ownership of the TN and resend the correcting record. If the TN on the record looks correct, contact the appropriate E9-1-1 DBMC for the current owner’s identity.


792 Migrate attempted on a Telephone Number that has an existing queued Migrate waiting to be reprocessed. Only one queued Migrate can exist for a given Telephone Number at any time.


800 For internal use only. If received, contact "the appropriate E9-1-1 DBMC as noted in Section 3.1".

819 Subsidiary line unchanged. A change was made to this subsidiary line's main number. This is an informational error. If the change should not be applied to the subsidiary line, this error record should be deleted.

N/A Information only. No action required.

V2.123

825 Location comment flag set on a change. An attempt was made to change a record that has the location comment flag set. This is an informational error, therefore the record was processed but the location and telco comment fields remained unchanged.


826 Location comment flag set on a Migrate to an external company. An attempt was made to migrate a record that has the location comment flag set. This is an informational error, therefore the record was processed but the location and telco comment fields remained unchanged.



833 Location comment flag set on a delete. The Location comment flag was set on a deleted record. This is an informational error, therefore the record was deleted despite this error occurring. This may result from a delete or pilot delete. In the case of a deleted subsidiary during a pilot delete, the subsidiary's record will appear in the error table.


863 Migrate attempted on a TN that has not been unlocked. This is an informational error indicating that the donor company has not unlocked the TN record you are trying to migrate yet. This record will be reprocessed automatically and will become a 763 error if the unlock record has not been received by then.


875 – 899 No Action Required No Action Required

V2.124

10.0 Automatic Error Correction Feature

The automatic error correction feature is an option to the service program that will cause the following actions to occur:

702 Error (Record already exists on Insert)With the auto-correct feature enabled for 702 errors, the FOC “I” will be changed to FOC “C” and the record will be reprocessed immediately.

A log entry will be made to the “autofoc” file that shows the TN record that existed before the error was corrected, and the new TN record that replaced it.

704 Error (Record does not exist on Delete)With the auto-correct feature enabled for 704 errors, the error record will be inserted directly into the boneyard table and will not be presented to the clerk or posted to the “.err” file for a PS/ALI user.

The service order input record will be logged to the “autofoc” file after it has been processed.

712 Error (Record does not exist for Change)With the auto-correct feature enabled for 712 errors, the FOC “C” will be changed to FOC “I” and the record will be reprocessed immediately.

The service order input record will be logged to the “autofoc” file after it has been processed.

Sample “autofoc” file that will be placed in your directory:*******************************************************************************************

702 ERROR->INCOMING RECORD:617-111-9999 617-111-9999 1 3 TESTING 702 ERROR 7960 TEST AVTEST COMMUNITY TEST MA 2 1234567

2000-10-14 03:00:29EXISTING RECORD:617-111-9999 - - 1 3 TESTING ERROR

7960 TEST AV

***********************************************************************************************

704 ERROR>617-111-8888 313 617-111-8888

NE 17 1234567

2000-09-15 07:25:15 572

712 ERROR, FOC CHANGED FROM 'C' TO 'I':617-111-7777 000 617-111-7777 2 0 TESTING 712 ERROR 2316 ROUTE 80 NE 17 1234567 APT 24392000-09-15 07:26:09

V2.125

11.0 LNP

11.1 OVERVIEW

With LNP, end-users can switch carriers and retain their telephone number. Because ranges of telephone numbers can be used to segregate Carrier data in the E 9-1-1 database, another method must be used to identify telephone numbers and corresponding carriers. A NENA study group has developed a set of standards called the “NENA Recommended Standards for Service Provider Local Number Portability”. These standards provide a framework to allow carriers to exchange data for end-users that port from one carrier to another carrier.

The NENA standards include:

1) Every Service Order record must carry a Company ID. These ID’s are assigned by NENA and consist of 3 to 5 alpha characters.

2) Two FUNCTION OF CHANGE “FOC”codes are used for service order input records:

FOC U / (“UNLOCK”) is used by the donor company (company losing the end user); and makes the Telephone Number (“TN”) available to the “recipient company” for issuance of their MIGRATE (M) request

- FOC M / (“MIGRATE”) is used by the recipient to migrate the TN from the donor Company ID to Recipient Company ID and to replace the end-user account details if necessary (for instance, if the end user has changed addresses at the same time that they have changed carriers)

When the donor company issues a ‘U’ FOC (to UNLOCK the TN), the existing E 9-1-1 record and associated selective routing record is not changed. The ‘U’ FOC symbolizes that the donor company acknowledges that this end-user has decided to change carriers, and that an ‘M’ service order record can be expected. Until the ‘M’ order is received, the existing data is to remain unchanged. Any service order activity against this telephone number by the donor company, or any other company other than the recipient company, must be rejected. The only exception is that the donor company is allowed to issue an ‘M’ order to reclaim the number.

Other rules exist that define what can happen to a record that has been unlocked. Rules also exist that protect telephone numbers owned by one Local Service Provider from being changed or deleted by the service order records (or clerical activity) of another Local Service Provider.

V2.126

11.2 Automatic Error Correction Feature for Local Number Portability

The automatic error correction feature for end-users using feature “LNP” is an option that is now available and must be turned on for the LNP service order enhancements to be active.

761 Error (Unlock attempted on an Unlocked TN by the same company)When an unlock service order is received for a TN which is already unlocked, if the company requesting the unlock matches the company which unlocked the TN, the unlock service order will be logged to the AUTOFOC file before being discarded. 761 error count will not be incremented and not reported as errors.

771 Error (Unlock attempted on a Nonexistent Telephone Number)When an unlock service order is received for a TN which does not exist in the database, the unlock service order will be logged to the AUTOFOC file before being discarded. 771 error count will not be incremented and not reported as errors.

773 Error (Migrate attempted on a Nonexistent Telephone Number) When a migrate service order is received for a TN which does not exist in the database, the migrate service order will be logged to the AUTOFOC file and reprocessed as an insert ('I') order. 773 error count will not be incremented and not reported as errors.

763 Error (Migrate attempted on a Locked Telephone Number)When a migrate service order is received for a TN which has not been unlocked and the company requesting the migrate matches the company which owns the TN, the migrate service order will be logged to the AUTOFOC file and reprocessed as a change ('C') order. 763 error count will not be incremented and not reported as errors.

See sample files on the next page!

V2.127

11.3 Automatic Error Correction Sample Files

Below is an example of an “autofoc” file, which will be placed in your home directory. Filenames will begin with ‘af’ and they will list the records that were processed through the service program.

761 ERROR, 'U' RECORD DISCARDED:410-555-0110 410-555-0110 1 0 TEST COMPANY 6 TEST AVTEST BOLA MD 47 NICK 2002-02-23 10:59:25771 ERROR, 'U' RECORD DISCARDED:610-555-2113 610-555-2113 1 0 TEST COMPANY 4 TEST AVTEST DELA PA 5 2002-02-23 11:41:13773 ERROR, FOC CHANGED FROM 'M' TO 'I':610-555-1000 610-555-1000 1 0 TEST COMPANY 2 TEST AVTEST DELA PA 5 2002-02-23 11:41:13763 ERROR, FOC CHANGED FROM 'M' TO 'C':610-555-0015 610-555-0015 1 0 TEST COMPANY 6 TEST LNREADING BERK PA 5 2002-02-23 12:07:29

V2.128

11.4 Changes to Service Order Processing in an LNP Environment

IMPORTANT:

Please contact the appropriate National Marketing Center (NMC) if you have questions on whether your telephone number record has been unlocked. For Verizon West inquiries please email [email protected].

Verizon processes all Migrate orders when received. If a corresponding Unlock order has not yet been received, the Carrier will receive an 863 informational error only. This allows a 72-hour aging process so that each day the records can be reprocessed against incoming unlocks. If after 72 hours the unlock record is still not received, the informational 863 error becomes a 763 ‘hard” error and is returned to the carrier for reprocessing. At this point, the Carrier must contact the “DONOR:” company and notify them that they must process an Unlock record so that a migrate record can be processed.

If during the 72 hour reprocessing, the unlock is received and additional errors are identified with the record, typically 701 Errors [Invalid MSAG information], the error is written to the MERR file. The carrier must then correct the error reported on the MERR file and also reprocess the Migrate request

V2.129

11.5 763 Auto-Reprocess Functionality

763 Error (Migrate attempted on a Locked Telephone Number)

763 auto-reprocess functionality. When an unlock service order is successfully processed, the LNP_m_errors table will be searched for any 763 errors matching the newly unlocked TN. If any exist, the errors will be reprocessed.

If the 763 errors are successfully reprocessed, they will be logged to a status file and placed in the home directory (where all of the files are also logged). This file, the auto-reprocess status file, will contain telephone number records that were successfully migrated via auto-reprocess. The file extension containing these records will appear in the same format as the other files with the extension of ‘ASTA’. This file will be created on an ‘as-needed’ basis, and will only be created when 763 errors are successfully auto-reprocessed. Since reprocessing of 763 errors will occur any time during the day, this file will be written to throughout the current day.

Below is an example of the ‘ASTA’ (auto-reprocess status file).

Filename= 02280580.ASTA

TNs MIGRATED TO TEST COMPANY:

TN DATE/TIME OF MIGRATE------------ --------------------610-555-4000 2002-02-27 08:00:42610-555-4001 2002-02-27 08:00:48

Any errors generated by reprocessed 763 errors will be written to the auto-reprocess error file. This file will be the same format as the Carrier MERR file. The file extension containing these records will appear in the same format as the other files with the extension of ‘AERR’. This file will be created on an ‘as-needed’ basis, and will only be created when reprocessed 763 errors result in new (non-763) errors. Since reprocessing of 763 errors will occur any time during the day, this file will be written to throughout the current day.

Below is an example of the ‘AERR’ (auto-reprocess error file).

Filename= 02280580.AERR

701 M (610) 555-4002 259 S BOLAND BLVD TEST DELA PA TEST COMPANY 1 0

(610) 555-4002 VERIFY CALLER'S LOCATION 2002-02-27 08:00:03 Y N

V2.130

11.6 LNP UNLOCK REPORT

The Unlock Report is available and lists the Carrier Telephone numbers that remain in the Unlocked for an extended period of time. Each company having unlocked telephone numbers meeting the age criteria will have a report placed in their home directory early Monday morning. The report is listed with the first 4 digits of the filename followed by a three digit Julian date, ending with an “.rpt” extension. Below is an example of the ‘Unlock Exception Report’.

Filename= 0123354.RPT

UNLOCK EXCEPTION REPORT Dec 20, 1999 02:00:00

COMPANY ID: BELAT

-----TN----- ---DATE UNLOCKED--- DAYS UNLOCKED 212-9-1-1-2943 1999-12-09 17:12:29 10 212-9-1-1-6905 1999-12-09 17:12:29 10 718-9-1-1-9233 1999-12-10 15:37:10 9 516-9-1-1-9996 1999-12-10 15:37:21 9 516-9-1-1-9997 1999-12-10 15:37:21 9 516-9-1-1-9998 1999-12-10 15:37:21 9 516-9-1-1-9999 1999-12-10 15:37:21 9 718-9-1-1-3542 1999-12-10 15:37:21 9 718-9-1-1-5579 1999-12-10 15:37:25 9

V2.131

12.0 Verizon’s Electronic Interface Sample Files

These attachments are to help carriers better understand the files Verizon’s Electronic Interface users will have available to them when they log into E 9-1-1 after their downloaded TN files have processed.

ATTACHMENT 1 is a sample of the file “dat” (input data file) that changes to a ‘done’ file when the file that has been downloaded to E 9-1-1 has completed processing.

ATTACHMENT 2 is a sample of the “sta” file (statistics) that is produced when the input file has completed processing. This “statistics” file provides a summary of the number of telephone number records that processed including a breakdown of inserts, changes and deletes. It also shows the number of errors that were generated along with the error code messages.

ATTACHMENT 3A is a sample of the “err” file (error) that is produced if any of the records in the input file failed to successfully process. This file displays the Error code number and the input data that was included upon transmission, such as telephone number, address, end-user name etc. The error code numbers are displayed in this guide with a description of the error message.

ATTACHMENT 3B is a sample of the “proc” file (processed) that contains a list of the successfully records processed by data file that is transmitted. When a record in the .dat file is successfully processed, then the NPA-NNX-TN will be written to this .proc file

ATTACHMENT 4 is a sample of the “MERR” file (Migrate errors) that is produced following the reprocessing of the initial Migrate errors via clec Ali mode 2 processing program. At this point, these are ‘hard’ errors that must be reviewed by the Carrier.

ATTACHMENT 5 is a sample of the “MSTA” file (Migrate statistics) that is produced following the reprocessing of the initial MIGRATE requests via ‘clec_ali mode processing program.

ATTACHMENT 6 is a sample of the “af” (Automatic Function) of change file. The error correction is an optional feature that is part of the service program. This program will cause the following actions to occur:If Error code 712 (record does not exist for change) is generated, the Service program will cause the Change ‘C’ to become an Insert ‘I’ and the record will reprocess immediately. The records that were processed through this program will appear in this report.

ATTACHMENT 7 is a sample of the ‘AERR’ file.(to be updated at a later date)

ATTACHMENT 8 is a sample of the ‘ASTA’ file. (to be updated at a later date)

V2.132

12.1 Attachment 1

Example of a ‘dat’ (input file) that changes to a ‘done’ file upon successful completion.

Filename= 01230410.done

C2121112001001 110 AVENUE C COMMUNITY NYCUSTOMER NAME 20 A

C2121112002001 999 AVENUE A COMMUNITY NYCUSTOMERNAME 20 A

I2121112003001 815 E 95 COMMUNITY NYCUSTOMERNAME 20 A D2121112004001 100 5 AV COMMUNITY NYCUSTOMERNAME 20 A C2121112005001 123 AVENUE C COMMUNITY NYCUSTOMER 20 A C2121112006001 111 E 14 COMMUNITY NYCUSTOMERNAME 20 A I2121112007001 19 STUYVESANT OVAL COMMUNITY NYCUSTOMERNAME 20

V2.133

12.2 Verifying That File Processed Successfully

IMPORTANT: The Carrier should go back into its home directory every time a file is transmitted to Verizon’s Electronic Interface to verify that the file processed successfully. Even if the user does not plan on working on the errors until the next business day, it is imperative that the user verifies that the file successfully completed.

To check for processing completion

Retrieve the “sta” (statistics file) after the input “dat” file has completed processing.The statistics file provides a summary of the number of telephone records that processed with a breakdown of Inserts, Changes and Deletes. It also shows the number of errors that were generated along with the error code number.

If the statistics file shows “No records committed” or an “abstract error message” appears, this may be an indication that the file did not process successfully and aborted midstream. If this situation is encountered, then notify E 9-1-1 System Administration immediately.

Reasons why files abort can vary

Occasionally, large amounts of traffic on the E 9-1-1 Database will cause this to happen. In this situation, waiting and re-transmitting usually is the fix. Other times, because a file has exceeded its maximum allowable data errors (20), the file will stop processing. In this case, though, re-transmitting will not work. Notify E 9-1-1 System Administration if a problem is encountered.

_____________________________________________________________________

V2.134

12.3 Attachment 2

Example of a Statistics file ‘sta’ that is generated after a file has processed. It is so important that this statistics file is retrieved every time a file is transmitted. This file tells the carrier how many records processed and how many errors were generated. CLEC PROCESSING RESULTS: COMPANY ID: VERIZ Finish Time: Thu Feb 11 14:23:17 1999 41 Total Records Processed: 100 Total Errors: 7 Data Errors: 0 Informative Errors: 0 702 Match Records: 0 SR Updates Generated: 1 SD Possibles Generated: 0 Subsidiaries Examined: 0 Inserts: 80 Changes: 5 Deletes: 8 Pilot Deletes: 0 Transfers: 0 Unlocks: 0Migrates: 0 Finals: 0 Auto FOC status filename Auto FOC records reprocessed: 0 Auto FOC 702 records: 0 Auto FOC 704 records: 0 Auto FOC 712 records: 0 Auto FOC 702 successfuls: 0 Auto FOC 712 successfuls: 0 ERROR SUMMARY: -------------------------------------------------------------------0 002 errors 0 738 errors 0 771 errors 0 003 errors 0 739 errors 0 772 errors 0 009 errors 0 740 errors 0 773 errors 0 010 errors 0 741 errors 0 774 errors 0 011 errors 0 742 errors 0 775 errors 0 012 errors 0 743 errors 0 776 errors 0 700 errors 0 744 errors 0 777 errors 7 701 errors 0 745 errors 0 778 errors 0 702 errors 0 746 errors 0 779 errors 0 703 errors 0 748 errors 0 780 errors0 704 errors 0 749 errors 0 781 errors 0 705 errors 0 750 errors 0 782 errors 0 706 errors 0 760 errors 0 783 errors 0 707 errors 0 761 errors 0 784 errors 0 709 errors 0 762 errors 0 785 errors 0 710 errors 0 763 errors 0 800 errors 0 711 errors 0 764 errors 0 819 errors 0 712 errors 0 765 errors 0 825 errors 0 720 errors 0 766 errors 0 826 errors 0 721 errors 0 767 errors 0 827 errors 0 723 errors 0 768 errors 0 828 errors 0 725 errors 0 769 errors 0 833 errors 0 732 errors 0 770 errors 0 863 errors 0 737 errors

V2.135

100 Records processed 7 Total errors

V2.136

12.4 Attachment 3A

Example of an Error file ‘err’ that is generated if the file that was transmitted has errors. This file displays the error code number and all telephone number record data.

In this 1st entry below, the layout of the error is as follows:

(a) 710= Error code number (Customer codes do not match on a change) See page 16 for more detailed description(b) I (Insert) Function of change(c) 315-555-0106 NPA/NXX/TN(d) 000 = Customer Code (e) S= Directional(f) 201= House number(g) STATE= Street name(h) NY= STATE(i) TEST PS= Customer name(j) 1= Class of service (1= residence)(k) 0=Type of service (0=Not foreign exchange or NOT non-pub)(l) 501B = Exchange code or TAR code(m) 315-555-1061 = Telephone Number

710 I (315) 555-0106 000 201 S STATEa b c d f e g NY TEST PS

1 0 501B (315) 555- 1061 h i j k l m1995-06-21 08:43:08 N N

==============================================================712 C (315) 555-0102 1002 201 S STATE

NY TEST PS 1 0 501B (315) 555- 1022

==============================================================704 D (315) 555-0103 1002 S STATE

NY TEST PS 1 0 501B (315) 555- 1033

1995-06-21 08:43:08 N N=======================================================712 I (315) 555-0104 1002 201 S STATE

NY TEST PS 1 0 501B (315) 555- 1044

1995-06-21 08:43:08 N N

V2.137

12.4 Attachment 3B

Example of a Proc file ‘proc’ that contains a list of the successfully records processed by data file that is transmitted. When a record in the .dat file is successfully processed, then the NPA-NNX-TN will be written to this .proc file.

Example of .proc file:

610-555-0011610-555-2112610-555-2113610-555-0014610-555-2020610-555-2103

V2.138

12.5 Attachment 4

Example of a ‘MERR’ (migrate error) file that is produced following the reprocessing of the initial migrate errors. These are LNP error codes that are found on pages 51 and 52.

.MERR

763 M (978) 222-0006 6 NPA SPLIT LN a b c d e ANYTOWN USA MA Test Name f g h 1 0 (978) 222-0006 i j k N001137 1997-10-31 12:02:13 N N l

a. 763= Error Code Number (Migrate attempted on a locked TN) See Section 11.2 for more detailed description.

b. M (Migrate) Function of Changec. 978-222-0006 (NPA NNX TN)d. 6=House numbere. NPA SPLIT LN = Street namef. ANYTOWN =Communityg. MA= Stateh. Test Name= Customer namei. 1= Class of service (1= Residence)j. 0 =Type of servicek. 978-222-0006= Telephone Numberl. N001137 = Order Number

V2.139

12.6 Attachment 5A

Example of a ‘MSTA’ (Migrate statistics) that is produced from the reprocessing of MIGRATE requests. This file contains processing statistics.

MSTA file: CLEC PROCESSING RESULTS:Finish Time: Mon Nov 3 16:46:02 1997 306Total Records Processed: 1Total Errors: 1Data Errors: 1Informative Errors: 0702 Match Records: 0SR Updates Generated: 0SD Possibles Generated: 0Inserts: 0Changes: 0Deletes: 0Pilot Deletes: 0Transfers: 0Unlocks: 0Migrates: 0Finals: 0Auto FOC records reprocessed: 0Auto FOC 702 records: 0Auto FOC 704 records: 0Auto FOC 712 records: 0Auto FOC 702 successfuls: 0Auto FOC 712 successfuls: 0 ERROR SUMMARY:0 002 errors 0 721 errors 0 762 errors0 003 errors 0 723 errors 1 763 errors0 009 errors 0 725 errors 0 764 errors0 701 errors 0 740 errors 0 769 errors0 702 errors 0 741 errors 0 770 errors0 703 errors 0 742 errors 0 771 errors0 704 errors 0 743 errors 0 772 errors0 705 errors 0 744 errors 0 773 errors0 706 errors 0 745 errors 0 800 errors0 707 errors 0 746 errors 0 819 errors0 709 errors 0 748 errors 0 825 errors0 710 errors 0 749 errors 0 826 errors0 711 errors 0 750 errors 0 833 errors0 712 errors 0 760 errors 0 863 errors1 Records processed 1 Total errors

V2.140

12.6 Attachment 5B

Example of an ‘MPROC’ file that contains a list of the successfully records processed by data file that is transmitted. When a Migrate record is successfully re-processed, then the NPA-NNX-TN will be written to this .MPROC file.

Example of .MPROC file:

610-555-0011610-555-2112610-555-2113610-555-0014610-555-2020610-555-2103

V2.141

12.7 Attachment 6

Example of an automatic function of change (AF) file that is produced from the reprocessing of 712 and 702 errors. Error code 712 states that the telephone number record does not exist for a change record.

This file contains the records that were processed through the service program. It lists the telephone number record that was changed from a ‘C’ to an ‘I’.

bhdbms: more af01_0523100_123440 ********************************************************************712 ERROR, FOC CHANGED FROM 'C' TO 'I': 631-111-0090 000 631-111-9090 2 0 I CAN INC 1 HUNTINGTON QUADRANGLE MELVILLE NY 51 1747 0000000 2000-05-23 12:34:40 ****************************************************************************************************************************************712 ERROR, FOC CHANGED FROM 'C' TO 'I': 631-111-0013 000 631-111-0013 2 0 I CAN INC 1 HUNTINGTON QUADRANGLE MELVILLE NY 51 1747 0000000 2000-05-23 12:34:40 ****************************************************************************************************************************************712 ERROR, FOC CHANGED FROM 'C' TO 'I': 631-111-0064 000 631-111-0064 2 0 I CAN INC 1 HUNTINGTON QUADRANGLE MELVILLE NY 51 1747 00000002000-05-23 12:34:40

V2.142

12.8 Attachment 7

02280580.AERR

701 M (610) 555-4001 259 S BOSTON BLVD TEST DELA PA TEST COMPANY 1 0 032236 C (610) 555-4001 VERIFY CALLER'S LOCATION 2002-02-27 08:00:03 Y N

V2.143

12.9 Attachment 8

02280480.ASTA

TNs MIGRATED TO TEST COMPANY: TN DATE/TIME OF MIGRATE------------ --------------------610-555-1000 2002-02-17 13:50:11610-555-1001 2002-02-17 13:51:07

V2.144

13.0 NEW YORK Street Thoroughfares -Valid Abbreviations

Thoroughfare Name Abbreviation



AIRPORT AIRPT FIELD FLD RAILROAD RRANNEX ANX FREEWAY FRWY RIDGE RDGAPARTMENT APT GARDEN GRDN RIVER RIVARCADE ARC HEAD HD ROAD RDAVENUE AV HEIGHTS HGTS ROADWAY RDWYBEACH BCH HIGHWAY HWY ROUTE RTBLOCK BLK HOSPITAL HOSP SOUTH SBOARDWALK BDWK HOUSE HSE SOUTHEAST SEBRANCH BR INSTITUTE INST SOUTHWEST SWBUILDING BLDG ISLAND ISL SQUARE SQCAUSEWAY CSWY JUNCTION JCTN STATION STACEMETERY CEMTRY LANDING LDG STREET STCENTER CTR LANE LN TERMINAL TERMNLCENTRE CTR LODGE LODG TERRACE TERRCIRCLE CIR LOOP LP THRUWAY THRWYCONCOURSE CONC LOWER LWR TOWER TWRCONVENT CNVNT MANOR MNR TRAIL TRCORNER COR MARKET MKT TRAILER TRLRCOURT CT MEADOW MDW TURNPIKE TRNPKCOURTHOUSE CTHSE MEADOWS MDWS UPPER UPRCRESCENT CRSNT MOUNT MT VALLEY VLYCROSS CR NECK NK VILLAGE VLGCROSSING CRSG NORTH N WALK WKCROSSROAD CRSRD NORTHEAST NE WAREHOUSE WHSECROSSWAY CRSWY NORTHWEST NW WEST WCOTTAGES COTGS PARK PK WHARF WHFDEPOT DEP PARKWAY PKWY WOOD WDDISTRICT DIST PIER PR WAY WAYDRIVE DR PIKE PKE YARD YDEAST E PLACE PLESPLANADE ESPLND PLAZA PLZESTATE EST POINT PTESTATES ESTS POND PDEXPRESSWAY EXPWY PROMENADE PROMEXTENSION EXT PATH PTH

**NO SPACE ON “MC” (EX. MCDONALD); SPACE, NO APOSTROPHE ON “O” (EX.OLEARY)*SECOND WORD IS SPELLED IN FULL WHEN THIRD WORD FOLLOWS (EX. BASIN STREET RD)*IF THIRD WORD IS A DIRECTIONAL, DO NOT SPELL OUT SECOND WORK (EX. BASIN AVE E)

V2.145

14. NEW ENGLAND Street Thoroughfares-Valid Abbreviations

Thoroughfare \Name Abbreviation


ALLEY ALY ISLAND ISLANNEX ANX JUNCTION JCTNAPARTMENT APT LAKE LKARCADE ARC LANDING LNDGAVENUE AV LANE LNBASE BS LOOP LPBEACH BCH MARKET MKTBEND BND NECK NKBLOCK BLK PARK PKBOARDWALK BDWK PARKWAY PKWYBOULEVARD BLVD PASS PSBRANCH BR PATH PABUILDING BLDG PIER PRCAUSEWAY CSWY PIKE PKECENTER CTR PLACE PLCIRCLE CIR PLAZA PLZCIRCUIT CIRCT POINT PTCLOSE CLS POND PDCONCOURSE CONC PROMENADE PROMCORNER COR RIDGE RDGCOURSE CORS ROAD RDCOURT CT ROADWAY RDWYCOURTHOUSE CTHSE ROUTE RTCRESCENT CRES SHOREWAY SHWYCROSSING CRSG SQUARE SQDEPOT DEP STATION STADISTRICT DIST *STREET STDRIVE DR TERMINAL TERMESPLANADE ESPLND TERRACE TERRESTATE EST THRUWAY THRWYESPRESSWAY EXPWY TRAIL TRLEXTENSION EXT TUNNEL TUNFREEWAY FRWY TURNPIKE TRNPKGARDEN GRDN WALK WKGREEN GREEN WAY WYHEIGHTS HTS WHARF WHFHIGHWAY HWY YARD YD* NOTE PLEASE SEE SECTION 6 FOR FURTHER INFORMATION.

V2.146

15.0 Pennsylvania and Delaware Street Suffix Thoroughfares- Valid Abbreviations




ALLEY ALY GARDEN GDN RANCH RANCHANNEX ANNEX GARDENS GDNS RANCHES RNCHSAPARTMENT APT GATEWAY GTWY RAPID RAPIDARCADE ARC GLEN GLEN RAPIDS RPDSAVENUE AV GREEN GRN RIDGE RIDGEBLOCK BLOCK GROVE GRV ROAD RDBOARDWALK BLK HALL HALL ROUTE ROUTEBOULEVARD BLVD HARBOR HBR ROW ROWBUILDING BLDG HEIGHTS HTS RUN RNBYPASS BY HIGHWAY HWY SHOAL SHOALCAUSEWAY CSWY HILL HL SHOALS SHLSCENTER CE HILLS HLS SOUTH SCHURCH CHRCH HOLLOW HOLO SOUTHEAST SECIRCLE CIR HORSESHOE HRSHE SOUTHWEST SWCIRCUIT CIRCT HOUSE HSE SPRING SPGCLOSE CLOSE INLET INLET SPRINGS SPGSCONCOURSE CONC INTERSTATE INT SQUARE SQCORNER(S) COR(S) ISLAND ISL STATION STATCOURSE CRSE JUNCTION JCTN STRAND STRNDCOURT CT KEEP KEEP STREAM STRMCOURTHOUSE CTHSE LAKE LAKE STREET STCOURTS CTS LANDING LNDG TERMINAL TERMCOVE COVE LANE LN TERRACE TERCREEK CK MANOR MNR THRUWAY THRWYCRESCENT CRES MARKET MKT TOWER TOWERCROSS CROSS MEADOW MDW TOWERS TWRSCROSSING CRSG MEADOWS MDWS TRAIL TRCROSSROAD CR MEWS MEWS TRAILER TRLRCUTOFF CUTOF MOUNT MOUNT TURN TURNDEPOT DEPOT NORTH N TURNPIKE TRNPKDISTRICT DIST NORTHEAST NE VALE VALEDRIVE DR OFF OFF VIEW VIEWDRIVEWAY DRWAY OUTLET OUTLT VILLAGE VLGEAST E PARK PRK WALK WALKENTRY EZ PARKWAY PRKWY WALKWAY WKWAYESTATE(S) EST(S) PASS PASS WAREHOUSE WHSEEXPRESSWAY EXPWY PATH PATH WATERWAY WTRWYEXTENDED EXT PIER PIER WAY WAYEXTENSION EXT PIKE PKE WEST WFIELD FIELD PLACE PL WHARF WHARFFIELDS FLDS PLAZA PLZ YARD YARDFLAT FLAT POINT POINTFLATS FLATS POND PONDFOREST FRST PRAIRIE PRAIR

V2.147

FREEWAY FRWY PROMENADE PROM16.0 NEW ENGLAND Street Address Guidelines

*ST for STREET appears as a suffix only in the following instances:

1. Street name is a letter or a numeral ---- M ST---- 2ND ST

---- THIRTEENTH ST

2. Street name is a direction ---- SOUTH ST

3. Street name is the same as the community ---- ARLINGTON ST/ARL

4. Street name ends in a direction or suffix ---- MAIN ST SOUTH

---- MAIN ST EXT

DIRECTION abbreviations are:

NORTH, EAST, WEST OR SOUTH ----- First letter of Direction N, E, W, or S

NORTHEAST, NORTHWEST ---- NE NW SOUTHEAST, SOUTHWEST ---- SE SW

_____________________________________________________________________

Note A direction may not be abbreviated when:

1) It is the Street Name (Example: SOUTH ST)

2) It precedes a lettered Street Name (Example: NORTH D ST)____________________________________________________________________________

The following five thoroughfares will always be abbreviated when they appear within the actual Street Name field:

AV AvenuePK ParkPL PlaceST StreetTERR Terrace

************************************************************************

NOTE: Street names that include ‘ROUTE’ must be fully spelled (for example) Route 1

V2.148

17.0 NEW YORK Street Address Guidelines

*ST for STREET appears as a suffix only in the following instances:

1. Street name is a letter or a numeral ---- M ST---- 4 ST

2. Street name is a direction ---- SOUTH ST ---- NORTH WEST ST

3. Street name is the same as the community ---- ARLINGTON ST/ARL

4. Street name ends in a direction or suffix ---- MAIN ST SOUTH

---- MAIN ST EXT

EXCEPTION: When the thoroughfare or suffix is part of the street name, it is spelled in full. For example : Avenue of the Americas

Park Av

V2.149

18.0 Pennsylvania and Delaware Address Guidelines

Address records in the state of Pennsylvania and Delaware are built and maintained by State County officials.In order to request MSAG extracts, CLECS, Independents and PBX end-users must obtain authorization from the respective counties in order to obtain MSAG extracts.

Under normal processing rules, only street-level MSAG records exist. Street-level MSAG entries require the following address information:

Street NameCommunityCountyStateOdd/Even IdentifierLow House NumberHigh House NumberESN

Omission of any of the above data on a TN update would result in an error. Conditional Posting introduces two additional MSAG record types.

The first is a county default MSAG record, which contains only county, state and ESN information.

The second is a community default record, which contains only community, county, state and ESN information. These default records are inserted and maintained by Verizon personnel.

County personnel maintain street level MSAG records responsible for each specific county.

Error Code 701 (NO MSAG record found)

Because of conditional posting in PA/DE, 701 errors will be handled differently. Since all records post to the 9-1-1 DBMS, all corrections for 701 errors will have to be submitted with a function of change “C”.

V2.150

19.0 Pennsylvania and Delaware – Conditional Posting

Description

Conditional Posting is a process that allows Telephone Company records to update the ALIs when an MSAG does not exist for a jurisdiction or when a matching street-level MSAG is not found.

Records that pass through Conditional Posting are assigned an ESN based on a default MSAG record and passed to the ALI retrieval system with “unsubscribed” data. This ESN is also used for selective routing if applicable. The actual subscriber information appears on the ALI record (i.e., RR 1, RD 1, Main St, Box 2, etc. . .), with a ‘VERIFY CALLER’S LOCATION” message appended to the screen. The emergency providers displayed are based on the default record.

V2.151

20.0 COUNTY CODES FOR NEW YORK

NOTE: THE COUNTY CODE IS A 4 CHARACTER FIELD.IF THE LAST DIGIT OF THE COUNTY CODE IS 1, THENIT IS A Verizon COUNTY CODE.

COUNTY COUNTY CODE

ALBANY ALBALLEGHANY ALGBROOME BROBRONX BNXBROOKLYN BKNCATTARAUGUS CATCAYUGA CAYCHAUTAUGA CHACHEMUNG CHMCHENANGO CHNCLINTON CLICOLUMBIA COLCORTLAND CORDELAWARE DELDUTCHESS DUTERIE ERIESSEX ESSFRANKLIN FRAFULTON FULGENESSE GENGREENE GRNHAMILTON HAMHERKIMER HERJEFFERSON JEFLEWIS LEWLIVINGSTON LIVMADISON MADMANHATTAN MANMONROE MOEMONTGOMERY MOGNASSAU NAS

V2.152

COUNTY CODES FOR NEW YORK

COUNTY NAME COUNTY CODE

NIAGARA NIAONEIDA ONEONONDAGA ONOONTARIO ONTORANGE ORAORLEANS ORLOSWEGO OSWOTSEGO OTSPUTNAM PUTQUEENS QUERENSSELAER RENROCKLAND ROCST. LAWRENCE STLSARATOGA SARSCHENECTADY SCNSCHOHARIE SCHSCHUYLER SHYSENECA SENSTATEN ISLAND STISTEUBEN STBSUFFOLK SUFSULLIVAN SULTIOGA TIOTOMPKINS TOMULSTER ULSWARREN WARWASHINGTON WASWAYNE WAYWESTCHESTER WESWYOMING WYOYATES YAT

V2.153

21.0 TAR code listings for Pennsylvania and Delaware

PENNSYLVANIA TAR CODES

ENTITY TAR CODE ENTITY TAR CODE ENTITY TAR CODE

Adams ADAM Dubois DUBO Montour MNTRAllegheny ALLE Elk ELK Northampton NHAMAllentown ALTN Erie ERIE Northumberland NORTArmstrong ARMS Fayette FAYE Perry PERRBeaver BEAV Forest FORE Philadelphia PHILBedford BEDF Franklin FRAN Pike PIKEBerks BERK Fulton FULT Pittsburgh PITTBethlehem BETH Greene GREE Potter POTT

Blair BLAI Huntington HUNT Schuylkill SCHUBradford BRAD Indiana INDI Snyder SNYDBucks BUCK Jefferson JEFF Somerset SOMEButler BUTL Juniata JUNI Sullivan SULLCambria CAMB Lackawanna LACK Susquehanna SUSQCameron CAME Lancaster LANC Tioga TIOGCarbon CARB Lawrence LAWR Union UNIOCenter CENT Lebanon LEBA Venango VENAChester CHES Lehigh LEHI Warren WARRClarion CLAR Luzerne LUZE Washington WASHClearfield CLEA Lycoming LYCO Wayne WAYNClinton CLIN McKean MCKE Westmoreland WESTColumbia COLU Mercer MERC Wyoming WYOMCrawford CRAW Mifflin MIFF York YORKCumberland CUMB Monroe MONRDauphin DAUP Montgomery MONTDelaware DELA

DELAWARE TAR CODES

Kent KENTNew Castle NEWCSussex SUSS

V2.154

22.0 Washington DC TAR Code Listing

STATE TAR CODE ENTITYDC WASH ANACOSTIADC WASH ANANCOSTIADC WASH BENNINGDC WASH BEORGETOWNDC WASH BROOKLANDDC WASH CELLULAR ONEDC WASH CONGRESSDC WASH CONGRESS HEIGHDC WASH CONGRESS HEIGHTSDC WASH DOWNTOWNDC WASH DROT DUPONTDC WASH FOGGY BOTTOMDC WASH FOGGY BOTTONDC WASH FORT DUPONTDC WASH FORT SUPONTDC WASH GEORGETOWNDC WASH GEORGIADC WASH GEORIGADC WASH LENFANTDC WASH LINCOLNDC WASH MERIDIANDC WASH METRODC WASH NERIDIANDC WASH ROCKVILLE-DOJDC WASH TENELYDC WASH TENLEYDC WASH WASHDC WASH WASHINGTONDC WASH WASHINGTON-DOJDC WASH WDCDC WASH WOODLEY

V2.155

23.0 VIRGINIA TAR CODE LISTING

STATE TAR CODE ENTITYVA ACOM ACCOMACK COUNTY/ATLANTICVA ACOM ACCOMACK COUNTY/ACCOMACK TOWNVA ACOM ACCOMACK COUNTY/BELLE HAVENVA ACOM ACCOMACK COUNTY/BLOXOMVA ACOM ACCOMACK COUNTY/CHINCOTEAGUEVA ACOM ACCOMACK COUNTY/HALLWOODVA ACOM ACCOMACK COUNTY/ISLANDVA ACOM ACCOMACK COUNTY/KELLERVA ACOM ACCOMACK COUNTY/LEEVA ACOM ACCOMACK COUNTY/MELFA (LEE)VA ACOM ACCOMACK COUNTY/MELFA (PUNGOTEAGUE)VA ACOM ACCOMACK COUNTY/METOMPKIN VA ACOM ACCOMACK COUNTY/ONANCOCKVA ACOM ACCOMACK COUNTY/ONLEYVA ACOM ACCOMACK COUNTY/PAINTERVA ACOM ACCOMACK COUNTY/PARKSLEYVA ACOM ACCOMACK COUNTY/PUNGOTEAGUEVA ACOM ACCOMACK COUNTY/SAXISVA ACOM ACCOMACK COUNTY/TANGIERVA ACOM ACCOMACK COUNTY/WACHAPREAGUEVA ACOM ACCOMACK COUNTY/ACCOMACK COUNTYVA ALBE ALBERMARLEVA ALEX ALEXANDRIA (CITY OF)VA ALLE ALLEGHANY COUNTYVA ALLE ALLEGHANY COUNTY/IRON GATE TOWNVA AMEL AMELIA COUNTYVA AMHT AMHERST COUNTYVA AMHT AMHERST COUNTY/AMHERST (TOWN OF)VA WISE APPALACHIA/WISE COUNTYVA APOM APPOMATTOX (COUNTY OF)VA ARLG ARLINGTON COUNTYVA ARLG ARLINGTON COUNTY/THE PENTAGONVA HANO ASHLAND/HANOVER COUNTYVA ACOM ATLANTIC/ACCOMACK COUNTYVA AGST AUGUSTA COUNTYVA AGST AUGUSTA COUNTYVA AGST AUGUSTA COUNTYVA BATH BATH COUNTY/CEDAR CREEK DISTRICTVA BATH BATH COUNTY/MILLBORO DISTRICTVA BATH BATH COUNTY/VALLEY SPRINGS DISTRICT

V2.156

VIRGINIA TAR CODE LISTING

STATE TAR CODE ENTITYVA BATH BATH COUNTY/WARM SPRINGS DISTRICTVA BDFD BEDFORD COUNTYVA BDFD BEDFORD COUNTY/BEDFORD TOWNVA ACOM BELLE HAVEN/ACCOMACK COUNTYVA YORK BETHEL/YORK COUNTYVA WISE BIG STONE GAP/WISE COUNTYVA BKBG BLACKSBURG (TOWN OF) MONTGOMERY

COUNTYVA ACOM BLOXOM/ACCOMACK COUNTYVA BOTE BOTETOURT COUNTYVA BOTE BOTETOURT COUNTY/BUCHANAN TOWNVA BRNW BRUNSWICK COUNTYVA BRNW BRUNSWICK COUNTY/ALBERTAVA BRNW BRUNSWICK COUNTY/LAWRENCEVILLEVA YORK BRUTON/YORK COUNTYVA BUCH BUCHANAN COUNTYVA BUCH BUCHANAN COUNTY/GRUBDY TOWNVA BOTE BUCHANAN TOWN/BOTETOURTVA CHEP BUTTS ROAD/CHESAPEAKE CITYVA CAMP CAMPBELL COUNTYVA NRTH CAPE CHARLES/NORTHAMPTON COUNTYVA CARO CAROLINE COUNTYVA CRLL CARROLL COUNTYVA RUSS CASTLEWOOD/RUSSELL COUNTYVA BATH CEDAR CREEK DISTRICT/BATH COUNTYVA CHRL CHARLES CITY COUNTYVA CHAC CHARLOTTE COUNTYVA CHAC CHARLOTTE COUNTY/DRAKES BRANCHVA CHAC CHARLOTTE COUNTY/CHARLOTTE

COURTHOUSEVA CHAC CHARLOTTE COUNTY/PHENIX TOWNVA CHAC CHARLOTTE COUNTY/KEYSVILLEVA NRTH CHERITON/NORTHAMPTON COUNTYVA CHEP CHESAPEAKE CITY/BUTTS ROADVA CHEP CHESAPEAKE CITY/DEEP CREEKVA CHEP CHESAPEAKE CITY/PLEASANT GROVEVA CHEP CHESAPEAKE CITY/SOUTH NORFOLKVA CHEP CHESAPEAKE CITY/WASHINGTONVA CHEP CHESAPEAKE CITY/WESTERN BRANCHVA CHEP CHESAPEAKE CITY/WESTERN BRANCHVA CHES CHESTERFIELD COUNTY

V2.157


STATE TAR CODE ENTITYVA CHIN CHINCOTEAGUEVA CHBG CHRISTIANSBURG TOWN/MONTGOMERY

COUNTYVA CLAR CLARKE COUNTYVA RUSS CLEVELAND (TOWN OF)VA FAIR CLIFTON/FAIRFAX COUNTYVA DICK CLINCHO/DICKENSONVA SCOT COUNT CLINCHPORT TOWN/SCOTT COUNTYVA DICK CLINTWOOD TOWN/DICKENSONVA HALF CLOVER/HALIFAX COUNTYVA WISE COEBURN/WISE COUNTYVA COHT COLONIAL HEIGHTS CITYVA FLUV COLUMBIA TOWN/FLUVANNA COUNTYVA CRAG CRAIG COUNTYVA AGST CRAIGSVILLE CTOWN/AUGUSTA COUNTYVA CULP CULPEPER COUNTYVA CUMB CUMBERLAND COUNTYVA NASM CYPRESS/SUFFOLK CITYVA DANV DANVILLE (CITY OF)VA CHEP DEEP CREEK/CHESAPEAKE CITYVA DICK DICKENSON COUNTYVA DICK DICKENSON COUNTY/CLINCHOVA DICK DICKENSON COUNTY/CLINTWOOD TOWNVA DICK DICKENSON COUNTY/HAYSI TOWNVA DINW DINWIDDIE COUNTYVA DINW DINWIDDIE COUNTY/MCKENNYVA SCOT DUNGANNON TOWN/SCOTT COUNTYVA NRTH EASTVILLE TOWN/NORTHAMPTON COUNTYVA NRTH EASTVILLE DISTRICT/NORTHAMPTON COUNTYVA GRAY ELK CREEK DISRICT/GRAYSON COUNTYVA ESSX ESSEX COUNTYVA NRTH EXMORE/NORTHAMPTON COUNTYVA FAIR FAIRFAX COUNTYVA FAIR FAIRFAX COUNTY/ANNEX TO VIENNAVA FAIR FAIRFAX COUNTY/CLIFTONVA FAIR FAIRFAX COUNTY/HERNDONVA FAIR FAIRFAX COUNTY/VIENNAVA FAIR FAIRFAX COUNTY/ANNEX TO VIENNAVA PRED FARMVILLE/PRINCE EDWARD COUNTYVA FAUQ FAUQUIER COUNTYVA FAUQ FAUQUIER COUNTY/THE PLAINS

V2.158


STATE TAR CODE ENTITYVA FLUV FLUVANNA COUNTYVA FLUV FLUVANNA COUNTY/COLUMBIA TOWNVA NRTH FRANKTOWN/NORTHAMPTONVA FRED FREDERICK COUNTYVA FRBG FREDERICKSBURG (CITY OF)VA WARN FRONT ROYAL/WARREN COUNTYVA PGEO FT LEE/PRINCE GEORGE COUNTYVA GILL GILES COUNTYVA GILL GILES COUNTY/GLEN LYN TOWNVA GILL GILES COUNTY/NARROWS TOWNVA GILL GILES COUNTY/PEARISBURG TOWNVA GILL GILES COUNTY/PEMBROKE TOWNVA GILL GILES COUNTY/RICH CREEK TOWNVA WISE GLADEVILLE/WISE COUNTYVA GILL GLEN LYN TOWN/GILES COUNTYVA GOCH GOOCHLAND COUNTYVA ROCK GOSHEN/ROCKBRIDGE COUNTYVA YORK GRAFTON/YORK COUNTYVA GRAY GRAYSON COUNTY/ELK CREEK DISTRICTVA GRAY GRAYSON COUNTY/OLD TOWN DISTRICTVA GRAY GRAYSON COUNTY/PROVIDENCE DISTRICTVA GRAY GRAYSON COUNTY/TROUTDALE TOWNVA GRAY GRAYSON COUNTY/WILSON DISTRICTVA GREN GREENE COUNTYVA GRNV GREENSVILLE COUNTYVA AGST GROTTOES/AUGUSTA COUNTYVA HALF HALIFAX COUNTYVA HALF HALIFAX COUNTY/CLOVERVA HALF HALIFAX COUNTY/SCOTTSBURGVA ACOM HALLWOOD/ACCOMAC COUNTYVA LOUD HAMILTON/LOUDOUN COUNTYVA HAMP HAMPTON (CITY OF)VA HANO HANOVER COUNTYVA HANO HANOVER COUNTY/ASHLANDVA DICK HAYSI TOWN/DICKENSONVA HENR HENRICO COUNTYVA HENY HENRY COUNTYVA FAIR HERNDON/FAIRFAX COUNTYVA HIGH HIGHLAND COUNTYVA LOUD HILLSBORO/LOUDON COUNTYVA NASM HOLY NECK/SUFFOLK COUNTY

V2.159


STATE TAR CODE ENTITYVA RUSS HONAKER (TOWN OF)VA HOPE HOPEWELL (TOWN OF)VA ALLE IRON GATE TOWN/ALLEGHANY COUNTYVA ACOM ISLAND/ACCOMACKC COUNTYVA IOWT ISLE OF WIGHT COUNTYVA JAMC JAMES CITY COUNTYVA SUSX JARRATT/SUSSEX COUNTYVA ACOM KELLER/ACCOMACK COUNTYVA LANC LANCASTER COUNTYVA LANC LANCASTER COUNTY/WHITE STONE TOWNVA BRNW LAWRENCEVILLE/BRUNSWICK COUNTYVA RUSS LEBANON (TOWN OF)/RUSSELL COUNTYVA ACOM LEE (MELFA) ACCOMACK COUNTYVA LOUD LEESBURG TOWN/LOUDOUN VA LOUD LEESBURG (TOWN OF)VA ACOM LEE/ACCOMACK COUNTYVA WISE LIPPS/WISE COUNTYVA LOUD LOUDOUNVA LOUD LOUDOUN COUNTY/HAMILTONVA LOUD LOUDOUN COUNTY/HILLSBOROVA LOUD LOUDOUN COUNTY/LEESBURG TOWNVA LOUD LOUDOUN COUNTY/LOVETTSVILLE TOWNVA LOUD LOUDOUN COUNTY/MIDDLEBURG TOWNVA LOUD LOUDOUN COUNTY/PURCELLVILLE TOWNVA LOUD LOUDOUN COUNTY/ROUND HILLVA LOUS LOUISA COUNTYVA LOUS LOUISA COUNTY/LOUISA TOWNVA LOUS LOUISA COUNTY/MINERAL (TOWN OF)VA LOUS LOUISA TOWN/LOUISA COUNTYVA LOUD LOVETTSVILLE TOWN/LOUDOUN COUNTYVA LUNE LUNENBURG COUNTYVA LYBG LYNCHBURG (CITY OF)VA MADN MADISON COUNTYVA MADN MADISON COUNTY/MADISON TOWNVA MADN MADISON TOWN/MADISON COUNTYVA DINW MCKENNEY/DINWIDDIE COUNTYVA BLND MECHANICSBURG DISTRICT/BLAND COUNTYVA MECK MECKLENBURG COUNTYVA MECK MECKLENBURG COUNTY/BRADNAX TOWNVA MECK MECKLENBURG COUNTY/CHASE CITY TOWNVA ACOM MELFA (LEE) ACCOMACK COUNTY

V2.160


STATE TAR CODE ENTITYVA ACOM MELFA (PUNGOTEAGUE) ACCOMACK COUNTYVA ACOM METOMPKIN/ACCOMACK COUNTYVA LOUD MIDDLEBURG TOWN/LOUDOUN COUNTYVA MIDD MIDDLESEX COUNTYVA MIDD MIDDLESEX COUNTY/URBANNA TOWNVA BATH MILLBORO DISTRICT/BATH COUNTYVA LOUS MINERAL (TOWN OF)/LOUISA COUNTYVA MONT MONTGOMERY COUNTYVA BKBG MONTGOMERY COUNTY/BLACKSBURGVA CHBG MONTGOMERY COUNTY/CHRISTIANSBURG

TOWNVA MONT MONTGOMERY COUNTYVA MONT MONTGOMERY COUNTYVA MONT MONTGOMERY COUNTYVA MONT MONTGOMERY COUNTYVA GILL NARROWS TOWN/GILESVA NRTH NASSAWADOX/NORTHAMPTON COUNTYVA NELS NELSON COUNTYVA YORK NELSON/YORK COUNTYVA NWKT NEW KENT COUNTYVA NNEW NEWPORT NEWS (CITY OF)VA SCOT NICKELSVILLE TOWN/SCOTT COUNTYVA NORF NORFOLK NOB (NAVY OPERATIONS BASE)VA NORF NORFOLK (CITY OF)VA NRTH NORTHAMPTON COUNTY/CAPE CHARLESVA NRTH NORTHAMPTON COUNTY/CAPEVILLEVA NRTH NORTHAMPTON COUNTY/CHERITONVA NRTH NORTHAMPTON COUNTY/EASTVILLE TOWNVA NRTH NORTHAMPTON COUNTY/EASTVILLE DISTRICTVA NRTH NORTHAMPTON COUNTY/EXMOREVA NRTH NORTHAMPTON COUNTY/FRANKTOWNVA NRTH NORTHAMPTON COUNTY/NASSAWADOXVA NTLD NORTHUMBERALNDVA NORT NORTONVA NOTW NOTTOWAY COUNTYVA NOTW NOTTOWAY COUNTY/BLACKSTONE TOWNVA GRAY OLD TOWN DISTRICT/GRAYSON COUNTYVA ACOM ONANCOCK/ACCOMACK COUNTYVA ACOM ONLEY/ACCOMACK COUNTYVA ORNG ORANGE COUNTY

V2.161


STATE TAR CODE ENTITYVA PAGE PAGE COUNTYVA ACOM PAINTER/ACCOMACK COUNTYVA ACOM PARKSLEY/ACCOMACK COUNTYVA PATK PATRICK COUNTYVA GILL PEARISBURG TOWN/GILES COUNTYVA ARLG PENTAGON/ARLINGTON COUNTYVA PTBG PETERSBURG (CITY OF)VA CHAR PHENIXTOWN/CHARLOTTE COUNTYVA PITT PITTSYLVANIA COUNTYVA FAUQ PLAINS (THE) FAUQUIER COUNTYVA CHEP PLEASANT GROVE/CHESAPEAKEVA POQN POQUOSON (CITY OF)VA PORT PORTSMOUTH (CITY OF )VA WISE POUND/WISE COUNTYVA POWH POWHATAN COUNTYVA PRED PRINCE EDWARD COUNTYVA PRED PRINCE EDWARD COUNTY/FARMVILLEVA PGEO PRINCE GEORGE COUNTYVA PGEO PRINCE GEORGE COUNTY/FT LEEVA GRAY PROVIDENCE DISTRICT/GRAYSON COUNTYVA PULA PULASKI COUNTYVA ACOM PUNGOTEAGUE (MELFA) ACCOMACK COUNTYVA ACOM PURCELLVILLE TOWN/LOUDOUN COUNTYVA PRWN QUANTICO TOWN/PRINCE WILLIAM COUNTYVA RDFD RADFORD (CITY OF)VA RAPP RAPPAHANNOCK COUNTYVA RAPP RAPPAHANNOCK COUNTY/WASHINGTONVA GILL RICH CREEK TOWN/GILES COUNTYVA RICH RICHMOND (CITY OF)VA RCMD RICHMOND COUNTY/WARSAW TOWNVA RNKE ROANOKE COUNTYVA VINT ROANOKE COUNTY/VINTON TOWNVA ROAN ROANOKE (CITY OF)VA WISE ROBERSON/WISE COUNTYVA ROCK ROCKBRIDGE COUNTYVA ROCK ROCKBRIDGE COUNTY/GOSHENVA LOUD ROUND HILL/LOUDOUN COUNTYVA RUSS RUSSELL COUNTYVA SALM SALEM (CITY OF)VA ACOM SAXIS/ACCOMACKCK COUNTYVA SCOT SCOTT COUNTY

V2.162


STATE TAR CODE ENTITYVA SCOT SCOTT COUNTY/CLINCHPORT TOWNVA SCOT SCOTT COUNTY/DUNGANNON TOWNVA SCOT SCOTT COUNTY/NICKELSVILLE TOWNVA HALF SCOTTSBURG/HALIFAX COUNTYVA BLND SEDDON DISTRICT/BLAND COUNTYVA BLND SHARON DISTRICT/BLAND COUNTYVA NASM SLEEPY HOLE/SUFFOLK CITYVA CHEP SOUTH NORFOLK/CHESAPEAKE CITYVA SPOT SPOTSYLVANIA COUNTYVA STAF STAFFORD COUNTYVA STNT STAUNTONVA NASM SUFFOLK/SUFFOLK CITYVA NASM SUFFOLK CITY/CYPRESSVA NASM SUFFOLK CITY/HOLY NECKVA NASM SUFFOLK CITY/SLEEPY HOLEVA NASM SUFOLK CITY/SUFFOLK TOWNVA NASM SUFFOLK CITY/WHALEYVILLEVA NASM SUFFOLK CITY/SUFFOLK CITYVA SUSX SUSSEX COUNTYVA SUSX SUSSEX COUNTY/WAVERLYVA ACOM TANGIER/ACCOMACKCK COUNTYVA GRAY TROUTDALE TOWN/GRAYSON COUNTYVA MIDD URBANNA TOWN/MIDDLESEX COUNTYVA BATH VALLEY SPRINGS DISTRICT/BATH COUNTYVA FAIR VIENNA (TOWN OF) FAIRFAX COUNTYVA FAIR VIENNA/ANNEXED TO FAIRFAX COUNTYVA FAIR VIENNA/ANNEXED FR FAIRFAX COUNTYVA VINT VINTON TOWN/ROANOKE COUNTYVA VABH VIRGINIA BEACH (CITY OF)VA ACOM WACHAPREAGUE/ACCOMACK COUNTYVA BATH WARM SPRINGS DISTRICT/BATH COUNTYVA WARN WARREN COUNTYVA WARN WARREN COUNTY/FRONT ROYALVA CHEP WASHINGTON/CHESAPEAKE CITYVA RAPP WASHINGTON TOWN/RAPPAHANNOCK

COUNTYVA SUSX WAVERLY/SUSSEX COUNTYVA WSPT WEST POINT (TOWN OF)VA CHEP CHESAPEAKE CITYVA NASM WHALEYVILLE/SUFFOLK CITY

V2.163


STATE TAR CODE ENTITYVA LANC WHITE STONE TOWN/LANCASTER COUNTYVA WMBG WILLIAMSBURGVA GRAY WILSON DISTRICT/GRAYSON COUNTYVA WNCH WINCHESTER (CITY OF)VA WISE WISE COUNTY/APPALACHIAVA WISE WISE COUNTY/BIG COUNTY GAPVA WISE WISE COUNTY/COEBURNVA WISE WISE COUNTY/GLADEVILLEVA WISE WISE COUNTY/LIPPSVA WISE WISE COUNTY/POUNDVA WISE WISE COUNTY/RICHMOND TOWNVA WISE WISE COUNTY/ROBERSONVA WISE WISE COUNTY/WISE TOWNVA WISE WISE TOWN/WISE COUNTYVA WYTH WYTHE COUNTYVA YORK YORK COUNTYVA YORK YORK COUNTY/BETHELVA YORK YORK COUNTY/BRUTONVA YORK YORK COUNTY/GRAFTONVA YORK YORK COUNTY/NELSON

V2.164

24.0 MARYLAND TAR CODES

25.0 MARYLAND TAR CODES

STATE TAR CODE ENTITYMD ALLE ALLEGHANYMD ANNE ANNE ARUNDELMD BCIT BALTIMORE CITYMD BCOU BALTIMORE COUNTYMD CALV CALVERTMD CRLN CAROLINEMD CARR CARROLLMD CECL CECILMD CHAS CHARLESMD DORC DORCHESTERMD FRED FREDERICKMD GARR GARRETTMD HARF HARFORDMD HOWD HOWARDMD KENT KENTMD MONT MONTGOMERYMD PRGE PRINCE GEORGESMD QANN QUEEN ANNEMD STMY SAINT MARYSMD SOMR SOMERSETMD TALB TALBOTMD WSCO WASHINGTONMD WICO WICOMICOMD WORC WORCESTER

V2.165

26.0 New Jersey E 9-1-1 Requirements

System-9 ONLINE is the Web-based Interface to the New Jersey E-9-1-1 database.

System-9 ONLINE is the method used for entering E 9-1-1 information into the Verizon E 9-1-1 Database Management System by Facility Based Certified Local Exchange Carriers, Independent Telephone Companies and Wireless Carriers, defined as (“Carriers”) in this document. This web-based application is a secured access system, which requires a digital certificate and secure login.

Verizon E 9-1-1 System Administration may be contacted via email [email protected] or may be reached at the numbers shown below if you have any questions concerning the information contained in this document.

Contact Name Telephone NumberJoyce Juliano-Pais 732-221-7863 Julie Leahy 617-535-5551Linda Kerkam 914-801-3740Donna Beecher 914-801-3717Betty Scala 617-535-5495

V2.166


Getting Started

READ THE SYSTEM-9 ONLINE INTERFACE GUIDE!! It explains how the System 9 ONLINE application works in the State of New Jersey. A copy can be obtained by contacting E9-1-1 System Administration at the email address below:

[email protected]

Obtain NENA company identifier by calling 1-800-332-3911 or by registering on-line at www.nena.org/companyid/cid.asp

For proper display and functioning of the SYSTEM-9 ONLINE application, the Carrier must use Microsoft Internet Explorer, version 5.5 or higher (recommended).

Obtain WinZip software program which is required if multiple file retrieval is selected.

Notify Verizon E 9-1-1 System Administration when you have your NENA ID via email at [email protected].

Contact Verizon E 9-1-1 System Administration for instructions on how to obtain a digital certificate. Verizon E 9-1-1 System Administration will provide documentation and the login and pass phrase needed to obtain the digital certificate.

Schedule Conference call with Verizon E 9-1-1 System Administration to review NENA 2 format for data exchange requirements.

Verizon E 9-1-1 System Administration will notify the Carrier with their E 9-1-1 login and initial password.

V2.167

Accessing E 9-1-1 Database via System 9 ONLINE

DISPLAY SPECIFICATIONS

For best results when running the SYSTEM-9 ONLINE application, Verizon recommends that the carrier set its desktop display properties as follows:

Choose a resolution of 1024 by 768 pixels or more. Set this resolution in the Display Properties window (Control panel>>Display>>Settings) tab.

Choose at least 256 colors (preferably more). Set the colors on the Display Properties window (Control Panel>> Display>> Settings) tab.

Choose a conservative color scheme such as Windows standard. Set this color scheme in the Scheme field on the Display Properties window (Control Panel>>Display>>Appearance) tab.

V2.168


The E 9-1-1 database is available 24 hours a day, seven days a week. Carriers can download up to 10 separate files each day into the E 9-1-1 database. A maximum of 10,000 NENA-2 data records may be included in each file. Please contact Verizon System Administrator to make special arrangements for larger daily update files or larger load files if necessary. When the TN files have been submitted to the E 9-1-1 database and have completed processing, output files will be generated and placed in user’s home directory. Verizon E 9-1-1 System Administration assigns each user their own home directory. The home directory serves as the holding place for all of the users input files. The home directory also includes all associated files such as Error Files, Statistics files, Acknowledgement files, LNP files etc.

FILE MANAGEMENT

The following section explains how the carrier manages its files within SYSTEM-9 ONLINE. The Carrier can complete the following tasks using the Web Application:

Deposit Files Retrieve Files View TN & MSAG Data Print TN & MSAG Data

Access SYSTEM-9 ONLINE:

https://wholesalegwfe911.verzion.com/system9

When depositing or sending files, the carrier can only deposit or send one file at a time. The file that is sent must adhere to NENA 2 data specifications. See Nena 2 format specifications in Section 7 for more details.

All Filenames must follow the following convention, and the filename’s Julian day must be the day that the file was transmitted.

The naming convention for the file is LECIDyyyyjjjnn

LECID= The first 5 characters of the carrier’s Nena Company ID (e.g. VERIZ) If your LECID is less than 5 character's fill the blank character spaces with an _

(underscore) yyyy= the four digit year in which the file is created jjj= the three digit Julian day of the year in which the file is created nn= the two digit file sequence number . It must begin with 00 through 09.

V2.169


New Jersey File Specifications – General

The following section contains the specifications for providing the three types of NENA-2 records: Data Record Specifications, Header Record Specifications, Trailer Record specifications.

Data Record Requirements

Each file must contain both Header and Trailer records.

NENA-2 Data Record Specifications

1. Req’d (required) columnR = Required field. Must be populated for every subscriber’s record spaces not

permitted. R/SF = Required field. Must be populated if present in subscriber’s record otherwise

space fill.N/SF = Not required field. Space fill.

2. All fields are left-justified with trailing spaces.

3. The actual lengths of some fields on the 9-1-1 systems (e.g. Street, Community, Location, et al) are shorter than the NENA-2 defined length and vary by system, which may result in truncation of rightmost data. The most significant information should always be left-justified in these and all fields.

4. All AN (Alphanumeric) fields may contain Upper case letters, Numbers and punctuation characters. Lower case and control characters are not permitted.

5. All required fields must be populated on Insert, Change and Delete type records. In order for a Data Record to be deleted, all of the data fields in the NENA-2 Data Record must exactly match with the data in the Data Record on the Verizon’s E 9-1-1 system.

6. All records must only reflect completed activity for the Calling NPA and Calling Number Data Record as of the Extract Date.

7. The Location field must include additional information describing the exact location of the Calling Number, if provided. This field is processed differently by the NJ system; refer to the additional information on next page.

V2.170

NENA-2 Data Record Specifications (continued)

The NJ system is keyword driven and is based on state requirements to have location data uniformly displayed at all PSAPs. Please note: Data will only be extracted from the NENA-2 Location field if one or more keywords, associated data, and delimiters are present in the exact prescribed format. If none of the keywords are present, any data in the location field will be ignored.

The NJ system location has four separate and distinct location type fields which can be simultaneously displayed at the PSAP; they are: Unit Type, Floor Number, Building Description, and Coin Location Description. The following editing and formatting rules apply to the location type fields:

Unit TypeIf one of the eleven unit type keywords listed below [followed by a blank space] is detected, the system sets an indicator to denote the unit type detected and will then extract the data following it up to the first space, comma, semicolon, open parenthesis, close parenthesis or a total length of 5 characters. Note: The first unit type and its associated data will be selected if more than one unit type is included in the NENA-2 Location field.

Format: [Unit Type Keyword] [blank space] [Unit Type Information] [delimiter]

Unit Type keywords: APT, BOX, LOT, PIER, RM, ROOM, RU, SUIT, SUITE, UNIT, WINGUnit Type Information maximum length: 5 characters

Example of data in the NENA-2 Location field: SUITE 2400 Unit Type keyword: SUITEblank space: blank spaceUnit Type Information: 2400delimiter: blank space

Floor NumberIf the floor number keyword, FLR [followed by a blank space] is detected the system will then extract the data following it up to the first space, comma, semicolon, open parenthesis, close parenthesis or a total length of 5 characters.

Format: [Floor Number Keyword] [blank space] [Floor Number Information] [delimiter]

Floor Number keyword: FLRFloor Number Information maximum length: 5 characters

Example of data in the NENA-2 Location field: FLR 7TH Floor Number keyword: FLRblank space: blank spaceFloor Number Information: 7THdelimiter: blank space

V2.171

Building DescriptionIf the building description keyword BLDG [followed by a blank space] is detected, the system will extract the data following the keyword up to the first comma, semicolon, open parenthesis, close parenthesis for a total length of 20 characters.

Format: [Building Description Keyword] [blank space] [Building Description Information] [delimiter]

Building Description keyword: BLDGBuilding Description Information maximum length: 20 characters

Example of data in the NENA-2 Location field: BLDG GATEWAY TOWERS II HIGH RISE Building Description keyword: BLDGblank space: blank spaceBuilding Description Information: GATEWAY TOWERS II HI (note: maximum of 20 characters extracted) delimiter: blank space

Coin Location DescriptionIf the NENA-2 Class of Service is COIN (6, 7) and the coin location description keyword DES[followed by a blank space] is detected, the system will extract the data following the keyword for a total length of 20 characters. The DES keyword, if present, must be the last, if any of the other keywords are present in the NENA-2 Location field.

Format: [Coin Location Desc. Keyword] [blank space] [Coin Location Desc. Information] [delimiter]Coin Location Desc. keyword: DESCoin Location Desc. Information maximum length: 20 characters

Example of data in the NENA-2 Location field: DES NEXT TO SECURITY POST Coin Location Desc. keyword: DESblank space: blank spaceCoin Location Desc. Information: NEXT TO SECURITY POS (note: maximum of 20 characters extracted) delimiter: blank space

8. The Class of Service field should also be used to indicate Duplicate Service and should be coded as shown below: 9 = Residence Duplicate Service Address - coded the same as Residence Off Premise Extension (OPX).0 = Business Duplicate Service Address - coded the same as Business OPX

9. The Taxing Area Rate (TAR) code must be populated with the appropriate value for all records.

NOTE: Refer to the New Jersey County Code Listing For New Jersey NPANXX numbers: If the STATE field is equal to NJ (New Jersey) the TAR code must be populated with the NJ county abbreviation corresponding to its address in the MSAG file, otherwise the TAR code must be populated with FXbbbb (where bbbb denotes four spaces).

V2.172

NENA-02-010APPROVED January 2002

EXHIBIT 6VERSION 2.1 FORMAT FOR DATA EXCHANGE

FIELD NAME POSITION

BYTES

REQ’D

TYPE

DESCRIPTION

Function Code 1 1 R A Type of activity the record is being submitted for. Valid entries: C Change D Delete I Insert U Unlock M Migrate

NPA 2-4 3 R N Three-digit area code of the Calling Number.

Calling Number 5-11 7 R N Seven-digit telephone number of the Calling Number.

House Number 12-21 10 R/SF AN House number. The field should be space filled is no house number is available.

NOTE: Although the House Number field is ten characters, it is understood that telephone companies may only support up to 8 characters.

House NumberSuffix

22-25 4 R/SF AN House number extension (e.g. /2). The field should be space filled if no suffix applies.

Prefix Directional

26-27 2 R/SF A Leading street direction prefix. The field should be space filled if no prefix applies. Valid entries: N S E W NE NW SE SW

Street Name 28-87 60 R AN Valid service address of the Calling Number.

Street Suffix 88-91 4 R A Valid street abbreviation, as defined by the U. S. Postal Service Publication 28. (e.g. AVE)

Post Directional

92-93 2 R/SF A Trailing street direction suffix. The field should be space filled if no suffix applies. Valid entries: N S E W NE NW SE SW

Community Name

94-125 32 R A Valid service community of the street name/house number as designated by the MSAG.

State 126-127 2 R A Alpha state abbreviation (e.g. TX)

V2.173

V2.174


EXHIBIT 6VERSION 2.1 FORMAT FOR DATA EXCHANGE

FIELD NAME POSITION BYTES REQ’D

TYPE DESCRIPTION

Location 128-187 60 R/SF AN Additional address information (free formatted) describing the exact location of the Calling Number (e.g. Apt 718).

Customer Name

188-219 32 R AN Subscriber name associated with the Calling Number.

Class of Service

220 1 R AN Value of:1=Residence 7=Coin 2 Way2=Business 8=Wireless3=Residence PBX 9=Residence OPX4=Business PBX 0=Business OPX5=Centrex A=Customer Owned Coin6=Coin 1Way out Telephone (COCT)(* ) FOR FUTURE USE

Type of Service

221 1 R N Value of:0=Not FX nor Non-Published1=FX in 911 serving area2=FX outside 911 serving area3=Non-Published4=Non-Published FX in 911 serving are5=Non-Published outside 911 serving area6=Local Ported Number (LNP)7=Interim Ported Number

Exchange 222-225 4 N/SF AN Local Exchange Carrier exchange identifier for the serving telephone office of the customer.

ESN 226-230 5 N/SF AN Emergency Service Number associated with the House number and Street Name.

Main NPA 231-233 3 R N Three-digit area code of the Main Number associated with the Calling Number.

Main Number 234-240 7 R N Seven Digit telephone number of the Main Number associated with the Calling Number.

Order Number

241-250 10 R AN Service order number for the activity establishing this record.

Extract Date 251-256 6 R N Date on which the record was created in the format MMDDYY

V2.175

FIELD NAME POSITION BYTES REQ’D

TYPE DESCRIPTION

County ID 257-260 4 N/SF AN County Identification Code (usually the FIPS code)NOTE: County Identification field is used to identify the county of call origination. The Subcommittee recommends use of the FIPS codeassigned to each county by the U S Census Bureau.

Company ID 261-265 5 R AN NENA registered Company Identification code

Source ID 266 1 R AN Code which indicates whether data is part of the initial database creation process or part of the daily update process.Daily = Space, Initial Load = C

Zip Code 267-271 5 N/SF AN Postal Zip CodeZip + 4 272-275 4 N/SF AN Postal Zip Code ExtensionGeneral Use 276-286 11 N/SF AN Field not used, space fill.Customer Code

287-289 3 N/SF AN Field not used, space fill.

Comments 290-319 30 N/SF AN Field not used, space fill.X Coordinate 320-328 9 N/SF AN Field not used, space fill.Y Coordinate 329-337 9 N/SF AN Field not used, space fill.Z Coordinate 338-342 5 N/SF AN Field not used, space fill.Cell ID 343-348 6 N/SF AN Field not used, space fill.Sector ID 349 1 N/SF AN Field not used, space fill.TAR Code 350-355 6 R AN Taxing Area Rate Code

See NJ County Code Listing Reserved 356-376 21 N/SF AN Field not used, space fillALT # 377-386 10 R/SF N Customer Number being remote call

forwarded in Interim Number Portability service.


387-394 8 R N Date on which the record was created in the format YYYYMMDDThis date should be the date that the record is submitted to Verizon for processing.

NENA Reserved

395-437438-439 *440-480

86 N/SF AN Field not used, space fill.Need to discussPositions 438 and 439 are reserved for future use!

Reserved 481-511 31 N/SF AN Field not used, space fill.End of Record

512 1 R AN Always an asterisk (*).

V2.176

NENA-02-010EXHIBIT 6

VERSION 2.1 FORMAT FOR DATA EXCHANGEFIELD NAME POSITION BYTES REQ’

DTYPE DESCRIPTION

Sector ID 349 1 N/SF AN Field not used, space fill.TAR Code 350-355 6 R AN Taxing Area Rate Code

See NJ County Code Listing Reserved 356-376 21 N/SF AN Field not used, space fillALT # 377-386 10 R/SF N Customer Number being remote call

forwarded in Interim Number Portability service.


387-394 8 R N Date on which the record was created in the format YYYYMMDDThis date should be the date that the record is submitted to Verizon for processing.

NENA Reserved

395-437438-439 *440-480

86 N/SF AN Field not used, space fill.Need to discussPositions 438 and 439 are reserved for future use!

Reserved 481-511 31 N/SF AN Field not used, space fill.End of Record

512 1 R AN Always an asterisk (*).

NOTE: All fields are left-justified, with trailing spaces.

V2.177


The Header Record allows Verizon to identify and to verify the sending company’s file to ensure accurate processing, since the data required facilitates identification of missing and/or duplicate file transmissions.

Header Requirements

1. Each file will contain one (1) NENA-2 Header Record.2. The Header Record will be the first record of the file.3. The Header Record will be formatted as described in the NENA-2 Header Record

Specification.

EXHIBIT 8VERSION 2.1 HEADER FORMAT FOR DATA EXCHANGE

NAME POSITION

BYTES TYPE REQ’D VALUE

Header Indicator

1-5 5 AN R “UHL”

Extract Date 6-11 6 N R MMDDYYCompany

Name12-61 50 AN R NENA

COMPANY IDCycle Counter 62-67 6 N R N

County ID 68-71 4 AN N/SF ANState 72-73 2 AN N/SF A

General Use 74-93 20 AN N/SF ANRelease Number

94-96 3 N R N

Format Version

97 1 N R N


98-105 8 N R N

Reserved 106-511 406 AN N/SF ANEnd of Record 512 1 AN R Always “*”

NOTE: All fields are left-justified, with trailing spaces, except the Cycle Counter, this field will be right- justified with leading spaces.

Header records will employ cycle counting to ensure a cycle of updates is not missed. If cycle # is incorrect, then the file will be rejected.

Company Name: The Company Name field should include the literal company name, it should include a contact name, and contact telephone number. This will facilitate communication between the two companies should it be necessary to resolve transmission, data or other problems.

V2.178

V2.179


Trailer Record

The Trailer Record allows Verizon to verify the sending company’s file to ensure accurate processing, since the record count ensures all records were processed.

Trailer Requirements1. Each file will contain one (1) NENA-2 Trailer Record.2. The Trailer Record will be the last record of the file.3. The Trailer Record will be formatted as described in the NENA-2 Trailer Record Specification.

EXHIBIT 9VERSION 2.1 TRAILER FORMAT FOR DATA EXCHANGE

NAME POSITION BYTES TYPE REQ’D VALUETrailer Indicator 1-5 5 AN R “UTL”

Extract Date 6-11 6 N R MMDDYYCompany Name 12-61 50 AN R NENA

COMPANY ID

Record Count 62-70 9 N R NExpanded Extract

Date71-78 8 N R N

Reserved 79-511 433 AN N/SF ANEnd of Record 512 1 AN R Always “*”

NOTE: All fields are left-justified, with trailing spaces, except for the Record Count, this field will be right justified with leading spaces.

Trailer records will employ record counting to ensure a record within an update file is not missed. If count is incorrect, then the file will be rejected.

V2.180

Error/Warning Messages - NJ

This document describes the user and error messages for SYSTEM-9. For eachmessage, it provides the message number, the message text, an explanation ofthe message, and the action necessary to correct the error or problem.

The messages fall into the following general categories:

Error Code Type100-109 Nena Standard Error Code 200- 202 Nena Standard Error Code 301 Nena Standard Error Code0001-0100 Load errors in SOP Input1000-1999 Load errors in SOP Queue3000-3999 ESI process errors

NENA STANDARD ERROR CODES:

100 Phone Class Not ValidExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 0014, 0046.

101 Phone Type Not ValidExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 0015, 0047.

102 Invalid Value for Trans TypeExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 0030.

103 Not MSAG ValidExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 0026, 0101, 0102, 0103, 0104, 0105, 0106, 0108, 0109, 0110, 0111, 1040, 1041, 2006, and 2007.

104 Street Number Not ValidExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 0028, 0029

105 Street Name Not ValidExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 0027 and 1010.

107 Community Name Not ValidExplanation This is a NENA standard error code.Action Refer to HBF error message 1000.

V2.181

NENA STANDARD ERROR CODES

109 Illegal NENA IDExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 0008, 0009, 0045, and 1064.

200 Record Already Exists, Insert Not AllowedExplanation This is a NENA standard error code.Action Refer to HBF error message 1061.

201 Record Does Not Exist for a ChangeExplanation This is a NENA standard error code.Action Refer to one or more of the following HBF error messages: 1062 and 1073.

202 Record Does Not Exist for a DeleteExplanation This is a NENA standard error code.Action Refer to HBF error message 1063.

301 Migrate Attempted on a Locked TNExplanation This is a NENA standard error code.Action Refer to HBF error message 1059.

HBF ERROR MESSAGES:0001 Alt Line must be numeric

Explanation The line number portion of the alternate telephone number on an incoming subscriber record contains non-numeric data.

Action Either correct the line number (i.e., the last four positions) of the alternatetelephone number to contain digits, or leave the entire Alt TN blank.

0002 Invalid values for Alt NPA are 200-999, excluding 911

Explanation The area code portion of the alternate telephone number on an incoming subscriber record contains an invalid value.

Action Either correct the area code portion of the alternate telephone number to containdigits between 200 and 999 (excluding 911), or leave the entire Alt TN blank.

0003 Alt NXX must be three digits

Explanation The exchange portion of the alternate telephone on an incoming subscriber record contains non-numeric data or contains less than three digits.

Action Either correct the exchange portion (i.e., the fourth, fifth, and sixth positions) of the alternate telephone number to contain three digits, or leave the entire Alt TNblank.

0005 Customer is required

Explanation The Customer field on the incoming subscriber record is blank; this is a requiredfield.

Action Enter the customer name in the Customer field.


V2.182

0006 Elevation must be numeric

Explanation The incoming subscriber record contains invalid data in the Elevation field.

Action Enter a numeric value in the Elevation field, or leave the field blank. Seefor a description of this field.

0007 Latitude must be numeric

Explanation The incoming subscriber record contains invalid data in the Latitude field.

Action Enter a valid numeric value in the Latitude field, or leave the field blank.

0008 LEC ID is required

Explanation The LEC ID field on the incoming subscriber record is blank; this is a requiredfield.

Action Enter a valid value in the LEC ID field.

0009 The LEC does not exist

Explanation The LEC ID on the incoming subscriber record does not exist in the LEC table.

Action If this is a new LEC, notify the Administrator to add an entry to the LEC table. This automatically clears all SOP Input records that have this LEC ID.If this is an incorrect LEC ID, enter a valid one in the LEC ID field.

0010 The valid values for Line are 0000-9999

Explanation The line number portion of the telephone number - incoming subscriber record contains an invalid value.

Action Enter a number between 0000 and 9999 for the line number portion (i.e., the lastfour digits) of the telephone number.

0011 Longitude must be numeric

Explanation The incoming subscriber record contains invalid data in the Longitude field.

Action Enter a valid numeric value in the Longitude field, or leave the field blank

0012 The valid values for NPA are 200-999, excluding 911

Explanation The area code portion of the telephone number on anincoming subscriber record contains an invalid value.

Action Correct the area code portion of the telephone number to contain digits between200 and 999 (excluding 911).


V2.183

0013 NXX must be three digits

Explanation The exchange portion of the telephone number - incoming subscriber record contains non-numeric data or contains less than three digits.

Action Correct the exchange portion (i.e., the fourth, fifth, and sixth positions) of thetelephone number to contain three digits.

0014 Invalid value for Phone Class

Explanation The Phone Class on an incoming subscriber record contains an invalid value.

Action Select the appropriate valid value from the Phone Class drop-down list.

0015 Invalid value for Phone Type

Explanation The Phone Type on an incoming subscriber record contains an invalid value.

Action Select the appropriate valid value from the Phone Type drop-down list.

0016 The valid values for Pilot Line are 0000-9999

Explanation The line number portion of the pilot telephone number on an incoming subscriber record contains an invalid value.

Action Enter a number between 0000 and 9999 for the line number portion (i.e., the lastfour digits) of the pilot telephone number.

0017 The valid values for Pilot NPA are 200-999, excluding 911

Explanation The area code portion of the pilot telephone number on an incoming subscriber record contains an invalid value.

Action Correct the area code portion of the pilot telephone number to contain digitsbetween 200 and 999 (excluding 911).

0018 Pilot NXX must be three digits

Explanation The exchange portion of the pilot telephone number on an incoming subscriber record contains non-numeric data orcontains less than three digits.

Action Correct the exchange portion (i.e., the fourth, fifth, and sixth positions) of the pilottelephone number to contain three digits.

0019 SO Completed contains data that cannot be converted to a date

Explanation The incoming subscriber record contains invalid data for the service ordercompletion date.

Action Correct the data for the service order completion date. The date value must benumeric, and must be in YYYYMMDD format.


V2.184

0020 SO Due contains data that cannot be converted to a date

Explanation The incoming subscriber record contains invalid data for the service order duedate.

Action Correct the data for the service order due date. The date value must be numeric,and must be in YYYYMMDD format.

0021 SO Due is required

Explanation There is no service order due date in the SO Due field on the incoming subscriber record; this is a required field.

Action Enter a service order due date in the SO Due field. The date value must benumeric, and must be in YYYYMMDD format.

0022 SO Num is required

Explanation There is no service order number in the SO Num field on the incoming subscriber record; this is a required field.

Action Enter the identifier of the last service order affecting 9-1-1 service for thistelephone number.

0023 SO Sent contains data that cannot be converted to a date

Explanation The incoming subscriber record contains invalid data for the service order sentdate.

Action Correct the data for the service order sent date. The date value must be numeric,and must be in YYYYMMDD format.

0024 SO Sent is required

Explanation There is no service order sent date in the SO Sent field on the incomingsubscriber record; this is a required field.

Action Enter a service order sent date in the SO Sent field. The date value must benumeric, and must be in YYYYMMDD format.

0025 Invalid value for SO Type

Explanation The incoming subscriber record contains an invalid value for service order type

Action Select the appropriate valid value from the SO Type drop-down list.

0026 State is required

Explanation In SOP Input, this error means the address on an incoming subscriber recorddoes not contain any data in the State field; State is a required field.If you received this error after running MSAG Import

Action Enter data in the State field. Error/Warning Messages - NJ

0027 Street is required

V2.185

Explanation In SOP Input, this error means the address on an incoming subscriber recorddoes not contain any data in the Street field; Street is a required field.If you received this error after running MSAG Import

Action Enter the name of the street (not including the directional prefix, directional suffix,street suffix, etc.) in the Street field.

0028 Street Num is required

Explanation The address on an incoming subscriber record does not have a value in the Street Num field; this is a required field.

Action Enter data in the Street Num field

0029 Street Num must be numeric

Explanation The address on an incoming subscriber record contains a non-numeric streetnumber in the Street Num field.

Action Enter a numeric value in the Street Num field.

0030 Invalid value for Trans Type

Explanation The incoming subscriber record contains an invalid transaction type.

Action Select the appropriate valid value from the Trans Type drop-down list.

0031 Invalid value for Unit Type

Explanation The incoming subscriber record contains an invalid Unit Type.

Action Select the appropriate valid value from the Unit Type drop-down list.

0033 TransType 'From Dup' not valid with SO Type 'Undo'

Explanation The transaction type on the incoming subscriber record is From Dup (From Duplicate Service) and the service order. These conditions are mutuallyexclusive.

Action Change the Trans Type or delete the subscriber record.

0034 The NPA-NXX is not assigned to the current host

Explanation The NPA-NXX combination on the incoming subscriber record does not exist inthe Host TN table.

Action If this is a new NPA-NXX combo, notify the Administrator to add an entry to theHost TN table. This automatically clears all SOP Input records that have thisNPA-NXX.If this is an incorrect NPA-NXX, correct the values in the TN.


0036 OPX values for Phone Class require Ext 'False'

V2.186

Explanation The phone class on the incoming subscriber record is either ROPX (ResidentialOff-Premise Extension) or BOPX (Business Off-Premise Extension), indicatingthat an off-premise extension exists for this telephone number. The Ext flag is also checked, indicating that this record itself is an extension. These conditions are mutually exclusive.

Action Remove the checkmark from the Ext field or change the value of the Phone Class field.

0037 Since Trans Type is To Dup or From Dup, Ext must be False

Explanation The transaction type (on the incoming subscriber record is either To Dup(To Duplicate Service) or From Dup (From Duplicate Service), and the Ext flag is also checked.These conditions are mutually exclusive.

Action Correct the transaction type or remove the checkmark from the Ext field.

0038 AltNPA, AltNXX, and AltLine must all be NULL or all have values

Explanation The alternate telephone number on the incoming subscriber record is incomplete. It must contain NPA, NXX, and line number values, or these values must all be

blank.

Action Either enter a complete alternate telephone number (Alt NPA, Alt NXX, and AltLine), or leave all portions of the Alt TN field blank.

0042 SOType 'U' invalid with Ext 'T'

Explanation The service order type on the incoming subscriber record is Undo, and the Ext flag is also checked. These conditions are mutually exclusive.

Action Correct the SO Type or remove the checkmark from the Ext field.

0043 Undo SO Num Mismatch

Explanation The incoming subscriber record is attempting to cancel the Master Line record forthis telephone number (i.e., SO Type is Undo), but the SO Num on the incomingrecord does not match the SO Num on the Master Line record.

Action Correct the SO Num or delete the subscriber record.

0044 Missing Audit Record for Undo

Explanation The incoming subscriber record is attempting to cancel a SOP record (i.e., SOType is Undo), but a corresponding SOP record does not exist for this telephonenumber.

Action Correct the telephone number or delete the subscriber record.

V2.187


0045 The Dial Tone LEC does not exist

Explanation The Dial Tone LEC on the incoming subscriber record does not exist in the LEC table.

Action If this is a new LEC, notify the Administrator to add an entry to the LEC table. This automatically clears all SOP Input records that have this LEC ID or DT LEC.If this is an incorrect LEC ID, enter a valid one in the DT LEC field.

0046 Phone Class is required

Explanation The incoming subscriber record does not have a value in the Phone Class field;this is a required field.

Action Select the appropriate valid value from the Phone Class drop-down list.

0047 Phone Type is required

Explanation The incoming subscriber record does not have a value in the Phone Type field;this is a required field.

Action Select the appropriate valid value from the Phone Type drop-down list.

1000 Community does not have a master record

Explanation The address on the subscriber record contains a community name that does notexist in the Community Master and/or Community Link table.

Action Enter a valid Community Name if entry is correct contact Verizon NJ DatabaseManagement Team at 732-922-9911.

1010 Street does not have a master record

Explanation The address on the subscriber record contains a street name that does not existin the Street Master and/or Street Link table.

Action Enter a valid Street Name if entry is correct contact Verizon NJ DatabaseManagement Team at 732-922-9911.

1040 Street Num in Street Segment marked as a gap

Explanation The Street Segment containing the street number of the address on thesubscriber record is marked as a Gap; a valid address cannot be included in aGap segment.

Action Enter a valid Street Number, if entry is correct contact Verizon’s NJ DatabaseManagement Center at 732-922-9911.


V2.188

1041 Street Num does not have an ESN

Explanation The Street Segment containing the street number of the address on thesubscriber record does not have an assigned ESN, and the Community Masterdoes not have a default ESN.

Action Enter a valid Street Number, if entry is correct contact Verizon’s NJ DatabaseManagement Center at 732-922-9911.

1050 Locked due to related Queue record at another load level

Explanation This record is locked from final processing because there is a related subscriberrecord with the same telephone number, LEC ID, and a lower sequence numberthat has failed at another load level.

Action Please Verizon’s NJ Database Management Center at 732-922-9911.

1059 Waiting Unlock

Explanation At the Logic load level, the system checks whether there is an active SOP recordwith the same telephone number but a different LEC ID as the incomingsubscriber record. If there is an active SOP record (i.e., Trans Type = I, C, HL, U,M, HT, or HS), and if the SOP record’s Unlocked field is unchecked, the systemfails the incoming record at the Locked load level and assigns the message,“Waiting Unlock”. This is known as “LEC mismatch checking,” and prevents anactive SOP record from being overwritten accidentally.

Action This error remains until one of the following occurs:• the SOP record is unlocked by the donor LEC; once the SOP record isunlocked, the logic error is removed and the subscriber record resumesprocessing• the number of days specified in the Migration Days field (set up by HBFat installation) has passed since the SO Due date; if this occurs, theerror message is changed to “Queue record's LEC ID does not matchSOP record's LEC ID” ERROR CODE 1064.• the telephone number or LEC ID on the incoming subscriber record ischanged to resolve the conflict

1060 SO Num mismatch between Queue record and SOP record

Explanation The incoming subscriber record is attempting to modify the Master Line record for this telephone number (i.e., SO Type is Modification), but the SO Num on theincoming record does not match the SO Num on the Master Line record.

Action Correct the SO Num or delete the subscriber record.


V2.189

1061 SOP record already active

Explanation The incoming subscriber record is attempting to add a record that already exists in the SOP database. Specifically, the error occurs if:• the incoming record’s Trans Type is ‘Insert’ or ‘To’, and SO Type is‘Original’AND• the Master Line record for this telephone number is active and has notbeen unlocked

1062 SOP record disconnected

Explanation The incoming subscriber record is attempting to change a disconnected ornon-existent record. Specifically, the error occurs if the incoming record’s TransType is ‘Change’ and either:• the corresponding SOP record’s Trans Type is 'Delete' or 'From'OR• there is no SOP record for that telephone number in the SOP database

Action Correct or delete the subscriber record.

1063 Disconnect of inactive SOP record. Deleting Queue record

Explanation The incoming subscriber record is attempting to disconnect a telephone numberthat is already inactive. Specifically, it occurs if:• the incoming record’s Trans Type is ‘Delete’ or ‘From’, and SO Type is‘Original’ or ‘Modification’AND• the SOP record for this telephone number is inactive (Trans Type is'Delete' or 'From') or does not exist

Action The error message is written to the Failure table (Tables | Operation | Failure),and the subscriber record is automatically deleted from SOP Queue; no useraction is necessary.

1064 Queue record's LEC ID does not match SOP record's LEC ID

Explanation See Error Code 1059

Action See Error Code 1059

1065 Queue record for Extension has no active Master Line

Explanation The incoming subscriber record is for an Extension, but there is no Master Linerecord for that telephone number. An Extension record must always beassociated with a Master Line record. Specifically, the error occurs if:• the incoming record’s Ext flag is checked, and the Trans Type is 'Insert','Change', 'Load', 'Migrate', or 'To'AND• a Master Line record for this telephone number does not exist, or isinactive (Trans Type is 'Delete' or 'From')

Action Correct or delete the subscriber record

V2.190


1066 Queue record's SOSent/SOPSequence earlier than related SOP record's

Explanation The incoming subscriber record’s SOP Sequence number is lower than the SOPSequence number of the corresponding SOP record.

Action Delete the subscriber record and re-send the record, if necessary.

1067 Second service order too soon

Explanation This error occurs if all of the following conditions exist:• the incoming subscriber record’s Trans Type is not 'From Dup'• the incoming record’s Ign Too Soon flag is unchecked• a SOP record (with a Trans Type other than ‘X’) exists for the sametelephone number as the incoming subscriber record• the incoming record’s SO Num does not match the SO Num of thecorresponding SOP record• the incoming record’s LEC ID matches the LEC ID of the correspondingSOP record• the number of days specified in the SO Min Days field (set up by HBFat installation) is greater than zero• the number of days between the incoming record's SO Sent date andthe SO Sent date of the corresponding SOP record is less than thenumber of days specified in the SO Min Days fieldService Order Too Soon checking does not apply if the incoming record’sCustomer, Street Num, Street Num Suffix, Street Master, Community Master,Building, Floor, Unit Type, and Unit Num fields match those fields on thecorresponding SOP record.


1068 Effective Date out of sequence

Explanation This error occurs if all of the following conditions exist:• there are two incoming subscriber records for the same telephonenumber• the SO Num of the two incoming records does not match• the SO Type of both incoming records is 'Original'• the SO Due date of the record with the earliest SOP Sequence numberis later than the SO Due date of the record with the later SOP SequencenumberThe system fails both records at the Logic load level.

Action Correct or delete one of the subscriber records.

V2.191


1069 Address must match SOP record's Address on disconnect

Explanation The incoming subscriber record is attempting to disconnect a SOP record, but the address does not match the address on the corresponding SOP record.Specifically, the error occurs if:• the incoming record’s Trans Type is 'Delete', 'From', or 'Unlock'• the incoming record’s SO Type is 'Original' or 'Modification'• the incoming record’s Street Num, Num Suffix, or Street Master do notmatch the corresponding SOP record


1070 Cannot disconnect. Duplicate service connected

Explanation The incoming subscriber record’s Trans Type is 'Delete' or 'From', but thecorresponding SOP record has duplicate service connected.

Action Disconnect the duplicate service before disconnecting the SOP record. Use the‘From Dup’ transaction type to disconnect duplicate service.

1071 Invalid Load

Explanation This error occurs if all of the following conditions exist:• the incoming subscriber record’s Trans Type is 'Load' and SO Type is'Original'• a SOP record already exists for this telephone number• the SOP record’s Trans Type is NOT 'Non-existent' or 'Load'


1072 Undo Mismatch

Explanation The incoming subscriber record is attempting to cancel a SOP record (i.e., SOType is ‘Undo’), but the incoming record’s SO Num does not match the SO Numon the corresponding SOP record.


1073 Loading modification without original (MasterLine)

Explanation This error occurs if all of the following conditions exist:• the incoming record’s SO Type is 'Modification'• the incoming record’s Trans Type is 'Insert', 'Migrate', or 'To'• the incoming record’s Ext flag is unchecked• the Master Line record for this telephone number is inactive (TransType is 'Delete' or 'From') or does not exist• if there is a corresponding Master Line record, the incoming record’sSO Num does not match the SO Num of the Master Line record

Action The error message is written to the Failure table (Tables | Operation | Failure),and the incoming record is automatically loaded to the SOP database; no useraction is necessary.

V2.192


1074 Redundant 'From Dup'. Deleting Queue record

Explanation The incoming subscriber record is attempting to disconnect duplicate service thathas already been disconnected. Specifically, the error occurs if:• the incoming record’s Trans Type is 'From Dup', and SO Type is'Modification'AND• the SOP record for this telephone number does not have duplicateservice connected

Action The error message is written to the Failure table (Tables | Operation | Failure),and the incoming record is automatically deleted from SOP Queue; no user action is necessary.

1075 Cannot disconnect duplicate service. Duplicate service not connected

Explanation The incoming subscriber record is attempting to disconnect duplicate service, butthere is no duplicate service for this telephone number. Specifically, the erroroccurs if:• the incoming record’s Trans Type is 'From Dup', SO Type is 'Original'AND• the SOP record for this telephone number does not have duplicateservice connected


1076 Queue record with SOType 'M' must have same SONum as SOP record

Explanation The incoming subscriber record is attempting to modify an existing SOP record(i.e., SO Type is ‘Modification’), but the SO Num on the incoming record does notmatch the SO Num of the corresponding SOP record.


1077 OPX Address must be different than MasterLine's Address

Explanation The incoming subscriber record is for an OPX (Off Premise Extension), but theaddress is the same as the address on the corresponding Master Line record. AnOPX must have a different address than the Master Line with which it isassociated.


V2.193


1078 Loading modification without original (Extension)

Explanation The incoming subscriber record is attempting to modify an Extension record, butthe corresponding Extension record does not exist or has a different SO Num than the incoming record. Specifically, the error occurs if all of the following conditions exist:• the incoming record’s SO Type is 'Modification' and the Ext flag ischecked• the incoming record’s Trans Type is 'Insert', 'Change', 'Migrate', or 'To'• an Extension record with this telephone number does not exist, or theTrans Type of the corresponding Extension record is 'Load'• if there is a corresponding Extension record, the incoming record’s SONum does not match the SO Num of the Extension record

Action The error message is written to the Failure table (Tables | Operation | Failure),and the incoming record is automatically loaded to the SOP database; no useraction is necessary.

1079 Cannot connect duplicate service. MasterLine record is not active

Explanation The incoming subscriber record is attempting to connect duplicate service, butthere is no active Master Line record for the telephone number. Specifically, theerror occurs if:• the incoming record’s Trans Type is 'To Dup'AND• there is no Master Line record for that telephone number, or thecorresponding Master Line record is not active (i.e., Trans Type is‘Delete’ or ‘From’)

Action Delete the incoming subscriber record, activate the Master Line record (or createa Master Line record if one does not exist), and then connect the duplicateservice.

1080 Release of inactive SOP record. Deleting Queue record

Explanation The incoming subscriber record is attempting to unlock a Master Line record, butthere is no active Master Line record for the telephone number. Specifically, theerror occurs if:• the incoming record’s Trans Type is 'Unlock'AND• there is no Master Line record for that telephone number, or thecorresponding Master Line record is not active (i.e., Trans Type is‘Delete’ or ‘From’)

Action The error message is written to the Failure table (Tables | Operation | Failure),and the incoming record is automatically deleted from SOP Queue; no user action is necessary.

1081 Duplicate Service Address must be different than MasterLine’s Address

Explanation The incoming subscriber record is attempting to add duplicate service for thesame address as the Master Line record’s address; the addresses must bedifferent.


V2.194


1090 SO Due date in the future

Explanation The service order due date on the subscriber record is later than the current date.


3000 ESI process error

Explanation This is an error in the External Service Interface.

Action Contact System Administration [email protected].

3001 NENA AutoTN Import critical error

Explanation An internal program error has occurred.

Action Contact System Administration [email protected] immediately.

3002 NENA AutoTN Import major error

Explanation A program warning has occurred. Any of the messages which are in the NATIerror codes list with an alarm level of Major.

Action Contact System Administration [email protected].

3003 NENA Auto TN Import informational error

Explanation This is an informational logging message. Any of the messages which are in theNATI error codes list with an alarm level of Minor.

Action For informational purposes.

3004 NENA AutoTN Import error - Unexpected Cycle Number

Explanation The Cycle Counter indicated in the header does not match the expected InputCycle counter indicated in the AutoNENALec table.

Action Correct the Cycle Counter in the header to match the Input Cycle counterindicated in the AutoNENALec table.

3005 NENA Auto TN Import error - Record Count mismatch

Explanation The Record Count indicated in the trailer does not match the number of records in the Service Order file.

Action Correct the Record Count in the trailer to match the number of records in theService Order file. Or, if this is for LEC processing, unselect the "Check RecordCount" option.

V2.195


3006 NENA AutoTN Import major error - Abnormal termination

Explanation An internal program error has occurred.

Action Contact System Administration [email protected] immediately.

V2.196

Local Number Portability (LNP) Reporting

The reporting process for records submitted with FOC “M” (migrates) has changed significantly.

If there are any questions in regard to the content of this document, please send an e-mail to the Verizon E9-1-1 System Administration mailbox, [email protected].

The enhancements improve functionality, by enabling a 3-day reprocessing cycle for 301 Waiting Unlock errors and the associated output reports.

The LNP reporting process will now produce 2 output reports:

1. A daily report that lists soft errors 301 as well as a successfully migrated record and deleted errors. (Exhibit 1)

2. An error report that lists any hard errors 109. (Exhibit 2)

Overview

The LNP reports provide information to LECs concerning the following types ofrecords

• Records Waiting Unlock (error 301)

• Records with a LEC ID mismatch (error 109)

• Successful migrations since the last report was run

The information contained in the LNP reports allows LECs to follow up with TNowners as to why unlocks have not been issued.

The LNP Reporting process is daily.

The LNP reports generated are available for retrieval via the System 9 Online WebBrower.

V2.197

LNP Output Files Created

The sections below describe the two possible output files created by the LNPReporting process: the .LNP_sta file, the .LNP_err file.

LNP Statistic Report

The LNP statistic report lists TN records, that are Waiting for an Unlock from another LEC (error 301), a record that has successfully posted to the 9-1-1 database since the last run of the report (COMPLETED), or a record that has been DELETED after the 3 day migration period has elapsed(error 109).

The LNP statistic report includes the following columns:

• LEC ID

• Telephone Number

• Transaction status: DELETED, COMPLETED or PENDING; if PENDING, thereport also includes the number of days waiting

• Date transaction received (for PENDING transactions)

• Date transaction successfully posted (for COMPLETED transactions)

• Error code for PENDING transactions 301 (waiting unlock) or a 109 (LEC ID mismatch) for DELETED Transactions

• Trans Type

The following is a sample LNP statistic report: (Exhibit 1)

LecID TN Transaction Status Receive Date Post Date Code Trans Type

LNP 9065557650 PENDING 2 days 09/09/2004 15:42 301 - Waiting Unlock Migrate LNP 9065557651 PENDING 2 days 09/09/2004 15:42 301 - Waiting Unlock Migrate LNP 9065556500 COMPLETED 09/14/2004 15:48 Migrate LNP 9065556501 COMPLETED 09/14/2004 15:48 Migrate LNP 9065550000 Deleted 09/09/2004 09:42 109 - LECID Mismatch Migrate LNP 9065550001 Deleted 09/09/2004 09:42 109 - LECID Mismatch Migrate LNP 9065550002 Deleted 09/09/2004 09:42 109 - LECID Mismatch Migrate

**After the 3 day migration period the 301 becomes a 109 and is written to both the .LNP_sta and the .LNP_err

V2.198

Successful Migrations in the LNP Statistic Report

Each time the LNP statistic report runs, it includes a list of successful migrations that have processed through the system since the last run of the LNP reports. These items are marked “COMPLETE” in the LNP statistic report.

LecID TN Transaction Status Receive Date Post Date Code Trans Type

LNP 9065556500 COMPLETED 09/14/2004 15:48 Migrate LNP 9065556501 COMPLETED 09/14/2004 15:48 Migrate

SPECIAL NOTE:

If a successful “Migrate” record was the FIRST activity seen in the database for the TN, itis not included in the LNP statistic report. In other words, if a brand new TN entersthe 9-1-1 system for the first time, but for some reason it was submitted with a TransType of “M” instead of “I”, it is not considered a migration and is not included in thereport. Only migrations that come through as updates to existing TNs in the E9-1-1 system are included in the report.

Naming Convention for the LNP Statistic Report

The naming convention for the LNP statistic report is LECIDYYYYJJJ.LNP_sta,where:

• LECID = Your assigned Company ID.

If the LEC ID is five characters or longer, the application uses the firstfive characters of the ID. If the LEC ID is shorter than five characters, the system inserts underscores to create a five-character prefix.

• YYYY = The four-digit year in which the file is created

• JJJ = The Julian day of the year on which the file is created

• .LNP_sta = The file extension for all LNP statistic reports

The following is a sample filename for an LNP statistic report:

TEST_2004328.LNP_sta

Here the LECID = TEST - since TEST is less than 5 characters the system insets underscores to create a five character prefix.

V2.199

LNP Error File forDeleted ‘109’ Errors

Once the 3 day reprocessing cycle has elapsed the 301 (soft error) will become a109 (hard error).

The 109 errors are, written to a separate NENA-formatted output file, .LNP.err and listed in the .LNP.sta file. You may resubmit the resulting error file after investigation through System 9 Online. If you choose to resubmit the file you must change the filename accordingly before depositing.

Warning:

The Location field in the NENA2-formatted error file (positions128-187) is always set to spaces by the LNP Reporting program.If the error file is going to be corrected and resubmitted to ZOO,any Location information must be re-populated in the NENA2 fileby the LEC prior to re-submission; otherwise, this informationwill not be populated in the 9-1-1 database.

Naming Convention for the LNP Error File

The naming convention for the LNP error file is LECIDYYYYJJJ.LNP_err, where:• LECID = The LEC ID in ZOOIf the LEC ID is five characters or longer, the application uses the firstfive characters of the ID. If the LEC ID is shorter than five characters orcontains spaces, the application inserts underscores to create afive-character prefix.• YYYY = The four-digit year in which the file is created• JJJ = The Julian day of the year on which the file is created• .LNP_err = The file extension for all LNP error reports

The following is a sample LNP error report: (Exhibit 2)

("UHL"091504TST 2 2 120040915 *M90655576501 TEST ROAD BELLEVILLE TWP NJ TESTCO 30 5515558530MANUAL 090904 TST 08753 0.0 0.0 ESSX 20040909 FF O2004090920040909 *

M90655576511 TEST ROAD BELLEVILLE TWP NJ TESTCO 30 5515558530MANUAL 090904 TST 0.0 0.0 ESSX 20040909 FF O2004090920040909 *

M90655576551 TEST ROAD BELLEVILLE TWP NJ TESTCO 30 5515558530MANUAL 090904 TST 0.0 0.0 ESSX 20040909 FF O2004090920040909 *

V2.1100

File Types:

You can retrieve the following types of files:

Attachment 1DON files- After a file completes processing, the extension on the files changes from a “.dat” to a “.don”.

Attachment 2STA files- Statistics files provide a summary of the TN records that were processed.

Attachment 3ACK files- Acknowledgment files list the Telephone Number records that were successfully added to the E 9-1-1 database.

Attachment 4ERR files- Error Files list the Telephone Number records that failed and were not added to the E-9-1-1 database.

Attachment 5REJ files- Rejected files contain input files that were not processed due to file level errors such as InvalidNena header or trailer, unexpected cycle number, failed record count.

Attachment 6LNP files- Local Number Portability files provide the Migrate and Unlock Status of Telephone Number records.

Attachment 7MSAG files- The MSAG (master street address guide) file lists the TN records that have address information that needs to be verified.

V2.1101

TEST FILESEXAMPLE OF DONE (DON)

ATTACHMENT 1

"UHL"051503TEST 1224 0011 *D555555000138 COUNTY AVE SECAUCUS TOWN NJBLDG GRGE FEELGOOD CAFE 20 55555500011548871 051503 TEST HUDS *I5555550002341 PARAMUS PARK MALL PARAMUS BORO NJ AFTER HOURS 20 55555500021813344 051503 TEST BERG *I5555550003341 PARAMUS PARK MALL PARAMUS BORO NJ AFTER HOURS 20 55555500031813344 051503 TEST BERG *I55555500045255 STATE HWY NO 3 HWY SECAUCUS TOWN NJ PIP PRINTING 20 55555500041291640 051503 TEST HUDS *I5555550005255 STATE HWY NO 3 HWY SECAUCUS TOWN NJ PIP PRINTING 20 55555500051291640 051503 TEST HUDS *I5555550006255 STATE HWY NO 3 HWY SECAUCUS TOWN NJ PIP PRINTING 20 55555500061291640 051503 TEST HUDS *"UTL"051503TEST 6 *

V2.1102

TEST FILESEXAMPLE OF STATISTICS FILE (STA)

ATTACHMENT 2

COMPANY ID: TEST

Finish Time: Thu May 15 2003 19:39:39 135Total Records Processed 27Total Records Successfully Loaded 2Total Records With Errors 21Total Errors 21Data Errors 0Total Failures 4Inserts 3Changes 1Deletes 14Unlocks 9Migrates 0Unknown Transaction Type 0

ERROR/FAILURE SUMMARY:----------------------------------------------------------------------1 1010 errors3 1040 errors1 1050 errors8 1059 errors1 1062 errors4 1063 errors5 109 errors2 1069 errors

27 Records processed 21 Total errors

V2.1103

TEST FILESEXAMPLE OF ACKNOWLEDGEMENT FILE (ACK)

ATTACHMENT 3

"UHL"030515TEST TEST TELECOM INC 1221 NJ 2 120030515 *I5555550001341 PARAMUS PARK MALL PARAMUS BORO NJ AFTER HOURS 20 55555500011813344 051503BERGTEST BERG 20030515 FF O *I5555550002341 PARAMUS PARK MALL PARAMUS BORO NJ AFTER HOURS 20 55555500021813344 051503BERGTEST BERG 20030515 FF O *I5555550003282 1ST ST JERSEY CITY NJ RELIABLE FURNITURE 20 55555500031721337 051503HUDSTEST 1063 HUDS 20030515 FF O *I55555500046057 PALISADE AVE WEST NEW YORK TOWN NJ DRAPER GROCERY 20 55555500042117306 051503HUDSTEST 1063 HUDS 20030515 FF O *I555555000525 PROSPECT AVE HACKENSACK CITY NJ JOHN F POJEDONEC AVE 20 55555500051303104 051503BERGTEST 1063 BERG 20030515 FF O *I555555000691 U S HWY NO 46 HWY ELMWOOD PARK BORO NJ SARK GETTY CORP 20 55555500061548889 051503BERGTEST 1063 BERG 20030515 FF O *"UTL"030515TEST TEST TELECOM INC 620030515 *

V2.1104

TEST FILESEXAMPLE OF ERROR FILE (ERR)

ATTACHMENT 4

"UHL"030515TEST TEST TELECOM INC 1217 NJ 2 120030515 *D555555000138 COUNTY AVE SECAUCUS TOWN NJBLDG GRGE FEELGOOD CAFE 20 5555550001356701 051503HUDSTEST 1059 HUDS 20030515 FF O *U5555550002255 STATE HWY NO 3 HWY SECAUCUS TOWN NJ PIP PRINTING 20 55555500021291640 051503HUDSTEST 109 HUDS 20030515 FF O *U5555550003255 STATE HWY NO 3 HWY SECAUCUS TOWN NJ PIP PRINTING 20 55555500031291640 051503HUDSTEST 109 HUDS 20030515 FF O *U5555550004255 STATE HWY NO 3 HWY SECAUCUS TOWN NJ PIP PRINTING 20 55555500041291640 051503HUDSTEST 109 HUDS 20030515 FF O *D5555550005201 WEST SIDE AVE JERSEY CITY NJ MACS VIDEO CENTER INC 20 55555500051243676 051503HUDSTEST 1069 HUDS 20030515 FF O *I55555500061 THEIM AVE ROCHELLE PARK TWP NJBLDG MAIN TOWNSHIP OF ROCHELLE PARK 20 55555500062021903 051503BERGTEST 1010 BERG 20030515 FF O *"UTL"030515TEST TEST TELECOM INC 2120030515 *

V2.1105

TEST FILESEXAMPLE OF REJECT FILE (REJ)

ATTACHMENT 5

"UHL"042503TEST 1201 3004: Invalid Cycle 0011 *D555555000161 GRAND AVE PALISADES PARK BORO NJ MIMI TRADING CORPORATION 20 55555500012119558 042503 ALTI BERG *D555555000261 GRAND AVE PALISADES PARK BORO NJ MIMI TRADING CORPORATION 20 55555500022119558 042503 ALTI BERG *M5555550003135 FORT LEE ROAD LEONIA BORO NJFLR 1 VOIGHT LIGHTING INDUSTRIES 20 5555550003

V2.1106

TEST FILESEXAMPLE OF LNP FILE

ATTACHMENT 6

LECID TN PENDINGSTATUS RECEIVEDATE POSTDATE CODE

TEST 5555550001 PENDING 0.1 days 2003/05/15 19:24 3101 - Record unlocked - warning TEST 5555550002 PENDING 0.1 days 2003/05/15 19:24 3101 - Record unlocked - warning TEST 5555550003 PENDING 0.1 days 2003/05/15 19:24 3101 - Record unlocked - warning TEST 5555550004 PENDING 0.1 days 2003/05/15 19:24 3101 - Record unlocked - warning TEST 5555550005 PENDING 0.1 days 2003/05/15 15:10 3103 - Record locked - warning TEST 5555550006 PENDING 0.1 days 2003/05/15 15:10 3103 - Record locked - warning TEST 55555500007 PENDING 2.5 days 2003/05/13 15:29 3103 - Record locked - warning TEST 5555550008 PENDING 3 days 2003/05/03 01:44 3102 - Record unlocked - error TEST 5555550009 PENDING 3 days 2003/05/03 01:44 3102 - Record unlocked - error TEST 5555550010 PENDING 3 days 2003/05/03 01:44 3102 - Record unlocked - error TEST 5555550011 PENDING 3 days 2003/05/03 01:44 3102 - Record unlocked - error TEST 5555550012 PENDING 3 days 2003/05/09 14:24 3104 - Record locked - error TEST 5555550013 PENDING 3 days 2003/05/09 14:24 3104 - Record locked - error TEST 5555550014 PENDING 3 days 2003/05/09 14:24 3104 - Record locked - error TEST 5555550015 PENDING 3 days 2003/05/09 14:24 3104 - Record locked - error TEST 5555550016 COMPLETED 2003/05/15 15:10 TEST 5555550017 COMPLETED 2003/05/15 15:10 TEST 5555550018 COMPLETED 2003/05/15 15:10 TEST 5555550019 COMPLETED 2003/05/15 15:10 TEST 5555550020 COMPLETED 2003/05/15 15:10 TEST 5555550021 COMPLETED 2003/05/15 15:10 TEST 5555550022 COMPLETED 2003/05/15 15:10

V2.1107

TEST FILESEXAMPLE OF MSAG FILE

ATTACHMENT 7

"UHL"030515VERIZ TEST TELECOM INC 2 120030515 *I5555550001511 FRANK E RODGERS BLVD HARRISON TOWN NJ E. NARANJO 20NENA 5555550001577990 050301 TEST 00000 1040 20010503 F *I5555550002207 FRANK E RODGERS BLVD HARRISON TOWN NJ MYSTIC TRAVEL INC. 20NENA 5555550002483630 013001 TEST 00000 1040 20010130 F *I5555550003207 FRANK E RODGERS BLVD HARRISON TOWN NJ MYSTIC TRAVEL INC. 20NENA 5555550003483630 013001 TEST 00000 1040 20010130 F *I5555550004207 FRANK E RODGERS BLVD HARRISON TOWN NJ MYSTIC TRAVEL INC. 20NENA 5555550004483630 013001 TEST 00000 1040 20010130 F *I5555550005207 FRANK E RODGERS BLVD HARRISON TOWN NJ MYSTIC TRAVEL INC. 20NENA 5555550005483630 013001 TEST 00000 1040 20010130 F *I5555550006207 FRANK E RODGERS BLVD HARRISON TOWN NJ MYSTIC TRAVEL INC. 20NENA 5555550006483630 013001 TEST 00000 1040 20010130 F *"UTL"030515TEST TEST TELECOM INC 620030515 *

V2.1108

Verizon New Jersey Database Management Center Team Leader:

For all questions please contact:

Hope D’Amato - [email protected] 732-922-9902

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

MSAG (Master Street Address Guide) will be produced on a quarterly basisand will appear in the carrier’s list of files available for retrieval every quarter.

The naming conventions of the MSAG Extracts are as follows: QQ_XXXXtxt.zip

where QQ = the quarter – 1st, 2nd, 3rd , 4th

where XXXX equals the county id, i.e., 1st_ATLA.txt.zip

If the carrier requires an MSAG in an emergency situation, request an extract by sending an e-mail request form(below) to Verizon’s Group Mailbox at [email protected].

V2.1109



New Jersey MSAG – Master Street Address Guide

26.1 Output File Format

The output file format for the export file (in .TXT format) is NENA Version 2.1 as shown below.

Note - The MSAG records are not exported in any particular order. However, the resulting .TXT file can be sorted using any text editor containing a sort function (such as UltraEdit), and the resulting .XLS file can be sorted using Microsoft Excel.

Version 2.1 Header Format for Data Exchange

NAME POSITION BYTES TYPEHeader Indicator 1-5 5 “UHL”

Extract Date 6-11 6 MMDDYYCompany Name 12-61 50 ANCycle Counter 62-67 6 N

County ID 68-71 4 ANState 72-73 2 A

General Use 74-93 20 ANRelease Number 94-96 3 NFormat Version 97 1 N


98-105 8 N

Reserved 106-511 406 ANEnd of Record 512 1 Always “*”

Note - All fields except the Cycle Counter field are left-justified with trailing spaces; the Cycle Counter field is right-justified with leading spaces.

Header records employ cycle counting to ensure that a cycle of updates is not missed.

V2.1110

New Jersey MSAG – Master Street Address Guide (cont’d)

Version 2.1 Format for MSAG Data Exchange

NAME POSITION BYTES TYPEPrefix Directional 1-2 2 AN

Street Name 3-62 60 ANStreet Suffix 63-66 4 AN

Post Directional 67-68 2 ANLow Range 69-78 10 ANHigh Range 79-88 10 AN

Community Name 89-120 32 AState 121-122 2 A

Odd/Even 123 1 O, E, or BESN 124-128 5 AN

Extract Date 129-134 6 MMDDYYPSAP ID 135-138 4 AN (set to spaces)County ID 139-142 4 ANExchange 143-146 4 AN (set to spaces)

General Use 147-166 20 AN (set to spaces)TAR Code 167-172 6 AN (set to spaces)Reserved 173-191 19 AN (set to spaces)


192-199 8 YYYMMDD

End of Record 512 1 Always *

Note - All fields are left-justified with trailing spaces. A street is not exported if its only street segments are Gap segments.

V2.1111

New Jersey MSAG – Master Street Address Guide (cont’d)

Version 2.1 Trailer Format for Data Exchange

NAME POSITION BYTES TYPETrailer Indicator 1-5 5 “UTL” or UTL

Extract Date 6-11 6 MMDDYYCompany Name 12-61 50 ANRecord Count 62-70 9 N


71-78 8 N

Reserved 79-511 433 AN (set to spaces)End of Record 512 1 Always “*”

Note - All fields except the Record Count field are left-justified with trailing spaces; the Record Count field is right-justified with leading spaces.

Trailer records employ record counting to ensure that a record within an update file is not missed.

V2.1112

26.3 NEW JERSEY COUNTY ABBREVIATION CODES

COUNTY ABBR COUNTY ABBR COUNTY ABBR

ATLANTIC ATLA GLOUCESTER GLOU OCEAN OCEN

BERGEN BERG HUDSON HUDS PASSAIC PASS

BURLINGTON BURL HUNTERDON HUNT SALEM SALM

CAPE MAY CAPE MERCER MERC SOMERSET SMST

CAMDEN CAMD MIDDLESEX MDSX SUSSEX SUSX

CUMBERLAND CUMB MONMOUTH MONM UNION UNON

ESSEX ESSX MORRIS MORR WARREN WARR

V2.1113

27.0 Glossary of Acronyms

Key Term/Acronym DefinitionAERR Automatic ErrorALEC Alternative Local Exchange CarrierALI Automatic Location IdentificationAN Alpha NumericASTA Automatic StatusBOPX Business Off-Premise ExtensionCLEC Competitive Local Exchange CarrierDBMC Data Base Management CenterDBMS Data Base Management SystemDES DescriptionDMC Data Management CenterDT LEC Dial Tone Local Exchange CarrierESN Emergency Service NumberESS ID Electronic Switching System IdentifierFOC Function of ChangeFX Foreign ExchangeLEC ID Local Exchange Carrier IdentifierLNP Local Number PortabilityM Order Migrate OrderMERR Migrate ErrorMSAG Master Street Address GuideMSTA Migrate StatisticsNENA National Emergency Number AssociationNENA-2 National Emergency Number Association data specification 2

standard defining how subscriber data is to be formatted for entry into 9-1-1 database systems

NMC National Market Center NPA Numbering Plan Area (Area codes)NPD Number Planning DigitNXX N = Number between 2 & 9; X = number between 0 & 9OPX Off-Premise ExtensionPBX Private Branch ExchangePS/ALI Private Switch/Automatic Location IdentificationPSAP Public Safety Answering PointROPX Residential Off-Premise ExtensionSO Service OrderSOP Service Ordering and ProvisioningTAR code Taxing Area CodeTN Telephone Number UHL User Header LabelUSER ID User Identification – System identification used by individuals

logging on to a computer systemZOO System Zenith Opus One System

V2.1114

Documents

€¦ · Web view15.0 pa and delaware ... conditional posting 50. 20.0 county codes for new york 51. 21.0 tar code listings for ... thrwy concourse conc lower lwr tower twr convent