Intrado Direct Services Telecommunications Service Provider Users Guide Version: 2012.03.21

Intrado Direct Services Telecommunications Service Provider Users Guide Version: 2012.03.21

Notice Intrado Direct Services Program and Documentation 2008-2012 by Intrado Inc. All Rights Reserved Printed in U.S.A. This software product is copyrighted and all rights reserved by Intrado Inc. The product is licensed to the original Licensee only for use according to the terms and conditions set forth in the System Agreement or applicable document containing the licensing provisions. Copying, selling, or using the product contrary to those licensing terms and conditions is a violation of the law. All parts of the Intrado Direct Services documentation are copyrighted and all rights reserved. This documentation may not be copied, photocopied, or reproduced in whole or in part without Intrado s prior written consent except as otherwise provided in writing. Any authorized copying or reproduction in whole or in part, must contain the following statement: Intrado Direct Services Program and Documentation 2008-2012 by Intrado Inc. All Rights Reserved Printed in U.S.A. If you have any questions regarding the appropriate use of this software product and documentation, please direct your comments to: Intrado Inc. 1601 Dry Creek Drive Longmont, CO 80503 720.494.5800 Trademark Information Intrado, triangle beacon design, and the logo forms of the foregoing, are trademarks and/or service marks of Intrado Inc. in the United States, other countries, or both and may be registered therein. Trademark Ownership All trademarks used herein are the property of their respective owners. Product Updates It is the policy of Intrado to improve products as new technology, software, hardware, and firmware become available. Intrado, therefore, reserves the right to change specifications without prior notice. All features, functions, and operations described herein may not be available worldwide.

Table of Contents Table of Contents List of Tables... 1 Support Plan Introduction... 2 Hours of Operation... 2 Support Plan Activities... 2 TSP Support Contact Lists... 2 Data Processing Overview... 4 Data Provisioning Activities... 4 SOI Processing... 5 Error Correction Overview... 6 Function Codes... 6 MSAG Related TN Errors... 7 MSAG Error Codes (Managed by Intrado Analyst)... 7 TN Errors... 7 Error Codes Written to and Retained in Error Database... 7 Local Number Portability Errors... 8 Error Code Descriptions... 9 Data Provisioning Input and Output File Descriptions...13 Service Order Interface Record File SOI (Input)...14 Error File (Output)...19 Statistics File (Output)...20 MSAG Management... 21 Overview...21 MSAG Distribution Medium...21 Delta MSAG...21 Delta MSAG File Format...21 Appendix A Glossary of Terms and Definitions... 24 Appendix B Version History... 26 (V2012.03.21) i

List of Tables Intrado Direct Services Telecommunications Service Provider Users Guide List of Tables Table 1: Version 2.1 Header Format for Data Exchange 14 Table 2: Version 2.1 Trailer Format for Data Exchange 15 Table 3: Version 2.1 Format for Data Exchange 15 Table 4: Error File Record Format 19 Table 5: Delta MSAG Data Exchange Header Record, NENA Version 2 21 Table 6: Delta MSAG Data Exchange Trailer Record, NENA Version 2 22 Table 7: MSAG Inserts, Deletes, and Changes, NENA Version 2 22 1 (V2012.03.21)

Support Plan Introduction Support Plan Introduction This support plan represents Intrado s commitment to the ongoing support by the Direct Data Integrity Unit (DIU) services being provided to Telecommunication Service Providers (TSPs). The following pages provide useful information for effective and efficient data management services support. This support plan includes: Hours of Operation Support Plan Activities TSP Support Contact List Hours of Operation Intrado Direct DIU analysts provide data management services on a 9-hour (8:00 a.m. to 5:00 p.m. MT) by 5-day (Monday through Friday) basis. For emergency situations occurring outside of the 9x5 work hours, Intrado provides 24-hour, 7 days per week support services. The Computer Operations support staff is available at the Longmont Emergency Call Relay Center (ECRC) facility around the clock for emergency services. ECRC management teams are also available via a nationwide radio pager network and supplemental staff is available in the event specialized services are required to respond to specific situations. Support Plan Activities When 9-1-1 data problems occur, Intrado provides prompt resolution assistance. For day-to-day data management and processing matters, the TSP will contact the Intrado DIU analyst who manages the specific ALI database region for problem resolution, communication, and operational matters. For all other issues, including new TSP setup, 9-1-1Net access, connectivity issues, file processing questions, or critical problems, contact a Telecommunications Service Provider Project Specialist. TSP Support Contact Lists Point of Contact During Business Hours (8:00 a.m. to 5:00 p.m. MT), contact the Direct DIU Analyst After Hours, Holidays, and Weekends, contact the Emergency Call Relay Center (ECRC) Telephone Number 877-655-2638 Fax number: 720.494.6600 877.856.7504 2 (V2012.03.21)

Support Plan Introduction During Business Hours, contact the appropriate TSP Project Specialist for the following issues: New TSP 911Net Access Connectivity Issues File Processing Questions Critical Problems To escalate any unresolved issue(s), contact the Direct Data Operations Manager For Texas, Vermont and Virginia Beach, contact: Donna Kaniowski at 720.494.6257 or Donna.Kaniowski@Intrado.com For all other Direct A9-1-1 areas, contact Brian Scattergood at 720.494.5259 or Brian.Scattergood@Intrado.com Terri Bhatt 720.494.6266 303.619.3162 (mobile) tbhatt@intrado.com 3 (V2012.03.21)

Data Processing Overview Data Processing Overview Processing E9-1-1 data requires a sequence of events that the TSP and Intrado perform in a collaborative effort to ensure data quality. 1. The TSP sends data to Intrado through an electronic transfer process to allow record processing. 2. Intrado processes the SOI files submitted by the TSP 24x7x365, with the exception of scheduled maintenance times. Data fallout that the Intrado DIU is responsible for is addressed by the next business day, excluding company holidays. Data Provisioning Activities In order for the TSP s data to be processed in the E9-1-1 database, the TSP sends their service order interface (SOI) records to Intrado via electronic data transfer. Electronic data transfer can be one of the following file transfer methods: Dial up connectivity HTTP Connectivity to Connect:Enterprise via HTTP requires an Internet connection and a standard Web browser. Intrado provides (and retains ownership of) a Key Code Token. In addition to the Key Code Token s six-character alphanumeric code, a valid username and password must be provided to log on to Connect:Enterprise. If using HTTP to access Connect:Enterprise, the TSP will be given a copy of the Connect:Enterprise via HTTP Reference Guide, which provides detailed instructions for logging on to send and access files. Secure FTP Connectivity to Connect:Enterprise via sftp is accomplished through the Internet using a sftp client. Setup involves collaboration between the TSP and Intrado and includes establishing site names and ports and generation of private and public keys. Once setup has been completed, data exchange over the Internet to Intrado s Connect:Enterprise server is a matter of simply opening a sftp session. NDM Network Data Manager allows for data transmissions to be established using dedicated circuit for host-to-host connectivity. Data communication through this method requires compatible communications equipment. Intrado provides the associated data communications hardware at Intrado s Longmont, Colorado headquarters. The TSP provides similar equipment, support personnel, and all network components to achieve connectivity from the TSP s system. When a TSP chooses NDM, the TSP deposits a SOI file onto Intrado s system daily. This produces outputs such as Error and Statistics files. These files and Delta MSAGs are automatically sent back to the TSP. 4 (V2012.03.21)

Data Processing Overview SOI Processing The following outline provides the general process flow and timeline of SOI records: 1. Error-free records are sent through Intrado's TSS and updated in ALI within 24 hours. 2. All service order updates that err are returned in an Error file to the TSP s Connect:Enterprise inbox or NDM folder. The Error files returned by Intrado contain the NENA Version 2 formatted record that includes fields for up to three (3) error codes. Note: The error file is only generated when a SOI file has passed the pre-processing validations. Files that fail pre-processing validations will not receive an Error file. 3. Intrado attempts to correct MSAG errors. If Intrado needs additional information to resolve a MSAG-related SOI error, the Intrado DIU analyst refers the error to the appropriate party for additional assistance in correcting the error condition. 4. Intrado creates a Statistics file that confirms the total number of records received in the SOI file, how many records processed without error, and how many records were in error, by error code. Note: The Statistics file is only generated when a SOI file has passed the pre-processing validations. Files that fail pre-processing validations will not receive a Statistics file. 5. Intrado creates Delta MSAG records that contain daily MSAG changes for the regions in which the TSP operates. Any expansion into new regions requires notification to Intrado to update the Delta MSAG report. 5 (V2012.03.21)

Error Correction Overview Error Correction Overview Intrado receives daily service order interface (SOI) records throughout the day from multiple TSPs. SOI files are loaded into Intrado s Transaction Services System (TSS) for processing. The SOI records validate against the different databases and tables of TSS. If a SOI record passes all of the validations, the TN record posts to the ALI database. If the SOI record does not successfully pass all required validations, the TN posts to the Error database and does not post to the ALI database until the error is resolved. Function Codes When the TSPs extract program creates SOI records from service orders, it assigns a function code to the SOI. Function codes indicate the action to be taken on the TN on the service order. It is important to compare the order type and function code to determine intended action of the service order. The function codes accepted by TSS are: C E I D P U M Change. Remove error from Error database. Insert line. Delete line. Only affects the subline on the SOI record. Pilot delete. Deletes pilot line and all sublines. LNP: Unlock. Sent by the donor company to unlock a TN record for Local Number Portability. LNP: Migrate. Migrates the TN record to recipient company ownership. The update SOI process may convert a SOI function code to a TSS action code. The action codes processed within TSS are as follows: C E I L P U M Z Change line detail. Only affects the subline on the SOI record. Change pilot detail. All sublines associated with the pilot receive the changes. Insert line. Delete line. Deletes the subline. Pilot delete. Deletes pilot line and all sublines. LNP: Unlock. Sent by the donor company to unlock a TN record for Local Number Portability. LNP: Migrate. Migrates the TN record to recipient company ownership. Remove TN error from Error database. 6 (V2012.03.21)

Error Correction Overview MSAG Related TN Errors The street names and address ranges in the MSAG should mirror the street names and address ranges within the TSP address validation database. Since the address on a service order must be valid within the TSP s SAG or MSAG, investigation of MSAG errors often involves comparing the MSAG ranges to the TSP s SAG ranges, and the TSP submitting a SOI correction when necessary. When a MSAG related error posts to the database, the Intrado analyst will perform error correction, if possible. If the analyst is unable to correct and validate the error, it will automatically be referred to the appropriate party for either a MSAG update or error correction. The resolution of MSAG errors often requires changes to the MSAG. The MSAG Coordinator must approve all MSAG changes by submitting a MSAG Change Request via 9-1-1Net to the Intrado DIU analyst. MSAG Error Codes (Managed by Intrado Analyst) 701 HOUSE NUMBER DOES NOT FIT MSAG RANGE 709 STREET NOT IN MSAG FILE 738 MSAG UPDATE CAUSED A TN ERROR TN Errors TSP personnel resolve TN errors by researching the account information in the TSP source systems. Because these errors are mainly subscriber data related errors, investigation often requires a thorough analysis of all completed service order activity to determine the correct data for the E9-1-1 database. Error Codes Written to and Retained in Error Database 101 PREFIX IS NOT IN THE PREFIX TABLE 701 HOUSE NUMBER DOES NOT FIT MSAG RANGE 703 PILOT RECORD NOT FOUND 709 STREET NOT IN MSAG FILE 738 MSAG UPDATE CAUSED A TN ERROR 755 UNABLE TO MIGRATE A LOCKED RECORD 760 LOCK EXCEEDED NUMBER OF RETRIES 7 (V2012.03.21)

Error Correction Overview Local Number Portability Errors Depending on the Direct ALI customer, Intrado may provide automatic LNP verification and validation; however, LNP error correction may be the responsibility of the Telecommunication Services Provider (TSP). Depending on the Direct ALI customer, Intrado will use information from Neustar to determine the correct ownership of a telephone number and, if an LNP error occurs, it may automatically be corrected by Intrado. 8 (V2012.03.21)

Error Code Descriptions Error Code Descriptions ERROR CODE 100 Customer code not numeric 101 Prefix not in prefix table 103 Pilot number is not numeric 105 Name missing 107 House number contains invalid characters 110 Street directional is invalid 112 Street name is invalid 114 Community name is missing or invalid 115 Class of service is invalid 116 House suffix is invalid 120 TN incorrectly formatted DESCRIPTION The customer code on the incoming SOI record is not numeric and the Run Time Parameter is set to edit for this condition. Contact DIU analyst. The prefix (NPA-NXX) on the SOI record does not match a record in the Intrado prefix table. Contact DIU analyst. The incoming SOI record contains a pilot TN that is non numeric. The incoming SOI record does not contain the customer name and the Run Time Parameter is set to edit for this condition. Contact DIU analyst. The incoming SOI record contains invalid characters in the house number field. The incoming SOI record contains invalid characters in the street directional field. The incoming SOI record contains invalid or unknown characters in the street name field or the street name field is blank. The incoming SOI record contains invalid or unknown characters in the community name field or the community name field is blank. The incoming SOI record has a class of service that is not defined as valid for the Company ID associated with that record within the SOI file. The incoming SOI record has invalid or unknown characters in the house suffix field. The TN on the incoming SOI record is not numeric or it is not properly formatted. 9 (V2012.03.21)

Error Code Descriptions ERROR CODE 126 Invalid type of service 701 House number does not fit MSAG range 702 Insert not allowed, record already exists in database 703 Pilot record not found 704 Record does not exist for delete 705 Pilot not found for delete 709 Street not in MSAG file 710 Customer code does not match on change 711 Customer code does not match on delete 712 Record does not exist for change DESCRIPTION The service type on an incoming SOI contains a type of service that has not been defined in the Run Time Parameter. Contact DIU analyst. The street name and community on the SOI record match a street name and community on the MSAG, but the house number is not within the MSAG house number range. The TN on an insert function SOI record already exists in the TN database. Correction of this error can be automated by changing the Run Time Parameter flag to Y. Contact DIU analyst. Either the pilot TN on a subline order is not found in the database, or the pilot TN on a subline order is found in the TN database but it is not a pilot TN (that is, the TN is a subline associated with another pilot). The subline TN on a delete SOI record does not exist in the TN database. Correction of this error can be automated by changing the Run Time Parameter flag to Y. Contact DIU analyst. The pilot TN on a delete SOI record does not exist in the TN database. Correction of this error can be automated by changing the Run Time Parameter flag to Y. Contact DIU analyst. The street name and community on a SOI record does not match a street name and community in the MSAG. The customer code on a change order does not match the customer code on an established TN record. This error only occurs if the Run Time Parameter flag has been set to validate customer code on this activity. Contact DIU analyst if this edit should be removed. The customer code on a delete order does not match the customer code on an established TN record. This error only occurs if the Run Time Parameter flag has been set to validate customer code on this activity. Contact DIU analyst if this edit should be removed. The TN on a change order is not found in the TN database. Correction of this error can be automated by setting the Change to Insert flag on the Run Time Parameter. Contact DIU analyst. 10 (V2012.03.21)

Error Code Descriptions ERROR CODE 713 Pilot does not match on change 733 Number change cannot be completed, new number already exists 735 Delete not allowed, record in the TN database with same completion date 738 MSAG update caused a TN error 742 Class of service does not match pilot 743 Type of service does not match pilot 744 Customer name does not match pilot 745 Multiple community/exchange matches found 746 Community and Exch are blank DESCRIPTION The pilot TN on a change function SOI record does not match the pilot TN on an existing record. The TN on a pilot change SOI record already exists in the database. The incoming delete SOI record has a completion date that is later or the same as the existing TN. This error occurs if an analyst shortens or deletes a MSAG range that has associated TN records. The TNs that are affected remain in the TN and ALI database but post to the error database as well. These errors are worked daily by the Direct DIU analysts. The class of service on a subline SOI record does not match the pilot record class of service. This error only occurs if the Run Time Parameter flag is set to edit for this condition. Contact DIU analyst. The type of service on a subline SOI record does not match the pilot record type of service. This error only occurs if the Run Time Parameter flag is set to edit for this condition. Contact DIU analyst. The customer name on a subline SOI record does not match the pilot record customer name. This error only occurs if the Run Time Parameter flag is set to edit for this condition. Contact DIU analyst. The house number, street name, and exchange on the SOI record match more than one MSAG range. This error only occurs if the Run Time Parameter flag is set to edit for this condition. When this edit is activated, the SOI validation process attempts to validate a SOI record without a community name against the MSAG by populating the community field with each community within the exchange. Contact DIU analyst. The incoming SOI record s community and exchange fields are blank. 11 (V2012.03.21)

Error Code Descriptions ERROR CODE 748 LOC does not match pilot 749 Customer code does not match pilot 751 Invalid function code 752 Invalid company ID 753 No record exists on unlock 754 No record exists on lock 755 Unable to migrate a locked record 756 Company code mismatch on change 757 Company code mismatch on delete 758 Company ID mismatch on unlock 759 Company ID mismatch on lock DESCRIPTION The LOC on a subline SOI record does not match the pilot record LOC. This error only occurs if the Run Time Parameter flag is set to edit for this condition. Contact DIU analyst. The customer code on a subline SOI record does not match the pilot customer code. This error only occurs if the Run Time Parameter flag is set to edit for this condition. Contact DIU analyst. A SOI record contains an invalid function code. Valid function codes are (C)hange, (D)elete, (I)nsert, (E)rror delete, (P)urge all, (U)nlock and (M)igrate. The incoming SOI record contains an invalid/unrecognized company ID. No record exists in the TN database to unlock. The TN on a migrate function SOI record does not exist in the TN database. Correction of this error can be automated by changing the Run Time Parameter to Change M to I. Contact DIU analyst. The TN on a migrate function SOI record is in the TN database with a Locked status because the donor company s corresponding Unlock order has not been received or successfully processed. The company code on a change function SOI record does not match the company code on the existing TN record. The company code on a delete function SOI record does not match the company code on an existing TN record. The company code on an unlock function SOI does not match the company code on the existing TN record. The Company ID on an unlock function SOI does not match the Company ID on the existing TN record. 12 (V2012.03.21)

Error Code Descriptions ERROR CODE 760 Lock exceeded number of retries 761 Subline company code does not match pilot 762 Required NENA ID missing from U or M function 763 Delete failed, pilot has sublines 781 Error does not exist for delete 782 Company ID mismatch on error delete 782 Unlock failed; pilot has subline(s) 792 Record exists for another company. 798 Company Code Mismatch on SOIP DESCRIPTION Occurs after 755 error has reprocessed for a set number of days. After the number of days has been exceeded, the TN will no longer be reprocessed. The company code on a subline SOI record does not match the pilot company code. The incoming SOI record indicates a U or M function and the company ID is missing. A delete function SOI record for a pilot TN with sublines is processed, but there are sublines associated with the pilot. The pilot TN posts to the Error database with a 763 error. Both the pilot and subline records remain in the TN database. The incoming SOI record contains a Delete Error (E) function code but no error record exists for deletion. The Company ID on an incoming SOI record does not match the Company ID on the record in the error database. The incoming SOI record contains an Unlock (U) function code for a pilot TN that has existing sublines attached. The company ID on the current record does not match the company ID on the incoming error. The company ID on the current record does not match the valid company IDs associated with the incoming SOI file ID. Data Provisioning Input and Output File Descriptions This section describes the following input and output files used in the data exchange between Intrado and the TSP customer: 13 (V2012.03.21)

Error Code Descriptions Service Order Interface Record File SOI (Input) Error File (Output) Statistics File (Output) Service Order Interface Record File SOI (Input) The SOI file uses the NENA Version 2 data format shown in Tables 4 through 6 below. Files must adhere to the following file specifications: All files contain a file header. All files contain a file trailer. All data must be in ASCII format. All data must be upper case. All fields not in use should be space filled. The following tables describe the NENA Version 2 format. Table 1: Version 2.1 Header Format for Data Exchange Name Position Bytes Type Description Header Indicator 1-5 5 A Appears as UHL Extract Date 6-11 6 A MMDDYY Company Name 12-61 50 AN Cycle Counter 62-67 6 N County ID 68-71 4 AN State 72-73 2 A General Use 74-93 20 AN Release Number 94-96 3 N Format Version 97 1 N Expanded Extract Date 98-105 8 N Reserved 106-511 406 AN End of Record 512 1 Always is an asterisk (*) Note: All fields are left justified, with trailing spaces, except the Cycle Counter field. This field is right justified with leading spaces. Header records use cycle counting to ensure a cycle of updates is not is missed. 14 (V2012.03.21)

Error Code Descriptions Table 2: Version 2.1 Trailer Format for Data Exchange Name Position Bytes Type Description Trailer Indicator 1-5 5 A Appears as UTL Extract Date 6-11 6 N MMDDYY Company Name 12-61 50 AN Company Name Record Count 62-70 9 N Number of records within the file Expanded Extract Date 71-78 8 N YYYYMMDD Reserved 79-511 433 AN AN End of Record 512 1 Always is an asterisk (*) Note: All fields are left justified, with trailing spaces, except for the Record Count field. This field is right justified with leading spaces. Trailer records use record counting to ensure a record within an update file is not missed. Table 3: Version 2.1 Format for Data Exchange Field name Position Bytes Type Description Function Code 1 1 A Type of activity the record is being submitted for. Valid entries: C Change, D Delete, I Insert, U Unlock, M Migrate, E Error Delete NPA 2-4 3 N Three-digit area code of the Calling Number. Calling Number 5-11 7 N Seven-digit telephone number. House Number 12-21 10 AN House number. The field should be space filled if 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 eight characters. House Number Suffix 22-25 4 AN House number extension (e.g., 1/2). The field should be space filled if no suffix applies. Prefix Directional 26-27 2 A Leading street direction prefix. The field should be space filled if no prefix applies. Valid entries: N, S, E, W, NE, NW, SE, and SW 15 (V2012.03.21)

Error Code Descriptions Field name Position Bytes Type Description Street Name 28-87 60 AN Valid service address of the Calling Number. Street Suffix 88-91 4 A Street type information (e.g. AVE, DR, RD) (Valid street abbreviation, as defined by the U. S. Postal Service Publication 28 (e.g., AVE). Post Directional 92-93 2 A Trailing street direction suffix. The field should be space filled if no suffix applies. Valid entries: N, S, E, W,NE, NW, SE, and SW Community Name 94-125 32 A Valid service community of the street name/house number as designated by the MSAG. State 126-127 2 A Alpha state abbreviation (e.g., TX). Location 128-187 60 AN Additional address information (free formatted) describing the exact location of the Calling Number (e.g., Apt 718). Customer Name 188-219 32 AN Subscriber name associated with the Calling Number. Class of Service 220 1 AN Service class associated with the Calling Number. Value entries: 1 = Residence 2 = Business 3 = Residence PBX 4 = Business PBX 5 = Centrex; 6 = Coin 1W out Telephone (COCT) 7 = Coin 2 way 8 = Mobile 9 = Residence OPX 0 = Business OPX W = Wireless G = Wireless V = VOIP Type of Service 221 1 N Value of: 0=Not FX nor Non-Pub 1=FX in 911 serving area 2=FX outside 911 serving area 3=Non-Pub 4=Non-Pub FX in 911 serving area 5=Non-Pub outside 911 serving area Exchange 222-225 4 AN Local Exchange Carrier exchange identifier for the serving telephone office of the customer. 16 (V2012.03.21)

Error Code Descriptions Field name Position Bytes Type Description ESN 226-230 5 AN Emergency Service Number associated with the House number and Street Name. Note: ESN field may be space filled when the Database Management System Provider is validating the address. The Service Provider providing the E9-1-1 Selective Routing will provide a list of ESNs available for assignment. Main NPA 231-233 3 N Three-digit area code of the Main Number associated with the Calling Number. Main Number 234-240 7 N Seven-digit telephone number of the Main Number associated with the Calling Number. Order Number 241-250 10 AN Service order number for the activity establishing this record. Extract Date 251-256 6 N Date on which the record was created in the format MMDDYY. County ID 257-260 4 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 code assigned to each county by the U S Census Bureau. Company ID 261-265 5 AN NENA registered company identification code. Source ID 266 1 AN Code that 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 AN Postal zip code. Zip + 4 272-275 4 AN Postal zip code extension. General Use 276-286 11 AN This field will be used by data exchange partners to pass information not defined in previous fields. Customer Code 287-289 3 AN Code used to uniquely identify a customer. Comments 290-319 30 AN Optional notes, may be displayed at PSAP. X Coordinate 320-328 9 AN Longitude/ X coordinate. Y Coordinate 329-337 9 AN Latitude/ Y coordinate. Z Coordinate 338-342 5 AN Structure elevation. 17 (V2012.03.21)

Error Code Descriptions Field name Position Bytes Type Description Cell ID 343-348 6 AN Identification number indicating a geographic region of cellular coverage. Sector ID 349 1 AN Sub set/section of a cell. TAR Code 350-355 6 AN Taxing Area Rate code. Reserved 356-376 21 AN This field is reserved for the Database Management Systems Provider s use. ALT # 377-386 10 N Customer Name being remotely call forwarded in Interim Number Portability service. Expanded Extract Date 387-394 8 N Date on which the record was created in the format YYYYMMDD. NENA Reserved 395-480 86 AN This field is reserved for NENA Data Technical Committee Assignment. Reserved 481-511 31 AN This field is reserved for the Database Management Systems Provider s use. End of Record 512 1 AN Always is an asterisk (*). Note: All fields are left justified, with trailing spaces. The Service Provider providing E9-1-1 Selective Routing must provide the governmental entity with a list of ESNs available for assignment by MSAG development personnel. 18 (V2012.03.21)

Error Code Descriptions Error File (Output) The Error file consists of the returned NENA Version 2 SOI record with a confirmation code populating three (3) bytes of the Reserved field (bytes 378-380). Not all incoming information is used in processing service orders. The Confirmation file returns only the information that was used to process the service order. The following table details data fields used in Error records. Table 4: Error File Record Format Field Name Position Bytes Type Description 1-377 Refer to the NENA Version 2.1 data format shown above. Primary Error Code 378-380 3 N Indicates the primary error code. 381-382 2 N/A Empty spaces. Error Indicator 383 1 A E to indicate error record. 384-399 16 N/A Empty spaces. Additional Error Codes 400-406 6 N Indicates up to two additional error codes if required. Sample Error File 407-512 Refer to the NENA Version 2.1 data format shown above. The following is a sample Error file. In this sample, the error code is in bold and the error indicator is italicized. 6I98765402803601 WILSON BLVD S HOMETOWN FL OFFICE 21 9876540280 081201 ALEC 999 743 E 6I98765402813601 WILSON BLVD S HOMETOWN FLAPT 1 FRED SMITH 11 9876540281 081201 ALEC 999 702 E 6I98765402833601 WILSON BLVD S HOMETOWN FLAPT 3 JOHN SMITH 11 9876540283 081201 ALEC 999 709 E 6I98765402843601 WILSON BLVD S HOMETOWN FLAPT 4 JANE SMITH 11 9876540284 081201 ALEC 999 713 E Note: When editing an error file for resubmission, the error indicator and error code must be blanked out. Do not use the Tab key or delete the indicator or code; use the space bar to create blanks. Using the Tab or Delete keys will alter the size of the record and the record will not process properly. 19 (V2012.03.21)

Error Code Descriptions Statistics File (Output) The Statistics file provides information about the processed SOI records in an 80- column ASCII text file. The example below shows the information contained in a Statistics file. PAGE 1 E911 DATABASE UPDATE STATISTICS RUN DATE 08/26/01 RUN TIME 13:30:13 TOTAL NUMBER OF UPDATES RECEIVED: 15 NUMBER OF UPDATES IN ERROR: 1 NUMBER OF INSERTS APPLIED: 12 NUMBER OF CHANGES APPLIED: 0 NUMBER OF DELETES APPLIED: 2 NUMBER OF ERRORS BY TYPE 100 CUS CODE NOT NUMERIC 101 NPANXX RECORD NOT FOUND 105 NAME MISSING 106 LAD OR SAD IS IN BAD FORMAT 120 TN,CX OR PX INCORRECTLY FORMATED 126 INVALID TYPE OF SERVICE 701 RANGE NOT FOUND 702 RECORD EXISTS NO INSERT 703 PILOT RECORD NOT FOUND 704 NO RECORD EXISTS FOR DELETE 705 PILOT NOT FOUND FOR DELETE 1 709 STREET NOT FOUND 710 CUS CODE MISMATCH ON CHANGE 711 CUS CODE MISMATCH ON DELETE 712 RECORD DOES NOT EXIST FOR CHANGE 713 TN AND PILOT NUMBER MISMATCH 729 CD ERROR DATE CONFLICT 731 REC EXISTS LATER OR = CMPLT DATE 733 NEW NUMBER ALREADY EXISTS 735 NO DELETE SAME COMPLETION DATE 739 INVALID HOUSE FORMAT 742 SERVICE CLASS DOESNT MATCH PILOT 743 SERVICE TYPE DOESNT MATCH PILOT 744 CUS NAME DOES NOT MATCH PILOT 745 RANGE FITS IN MUTILPLE CITY EXCH 746 COMMUNITY AND EXCH ARE BLANK 748 LOCATION DOESNT MATCH PILOT 749 CUS CODE DOESNT MATCH PILOT 751 INVALID FUNCTION CODE 752 INVALID COMPANY CODE 753 NO RECORD EXISTS ON UNLOCK 754 NO RECORD EXISTS ON LOCK 755 UNABLE TO MIGRATE LOCKED REC 756 COMPANY CODE MISMATCH ON CHANGE 757 COMPANY CODE MISMATCH ON DELETE 758 COMPANY CODE MISMATCH ON UNLOCK 759 COMPANY CODE MISMATCH ON LOCK 760 LOCK EXCEED NUMBER OF RETRIES 761 PILOT COMPANY CODE MISMATCH 762 LNP REQUIRED ON U OR M FUNCTION 763 DELETE FAILED PILOT HAS SUBLINES 1 TOTAL ERROR(S) 20 (V2012.03.21)

MSAG Management MSAG Management Overview The Direct DIU analyst will support the 9-1-1 Agencies with MSAG management via the 9-1-1Net application. This process includes changes to the MSAG as well as the ability for the 9-1-1 Agency to view the MSAG. TSPs will also have the ability through their custom version of 9-1-1Net to view the MSAG. Intrado MSAG management processes also include Delta MSAG notifications, which provide TSPs with electronic daily MSAG changes. MSAG Distribution Medium Intrado can produce annual MSAG files for distribution via email, via Connect:Enterprise (C:E),or via Network Data Manager (NDM). For MSAG distribution files delivered via email, an Excel or a text file format can be provided. For MSAG distribution files delivered via Connect:Enterprise or Network Data Manager (NDM), only a text file format is available. TSPs can contact the Direct DIU project specialists via the Direct_Operations@Intrado.com inbox for further details or to request a MSAG distribution setup. Delta MSAG The 9-1-1 Agencies forward MSAG change requests to Intrado DIU analysts. Once the MSAG is updated, an audit record of the transaction is saved into a Delta MSAG file for TSPs to extract on a daily basis. The TSP has the choice of two (2) options for receiving the audit information: one (1) file for each county where the TSP subscribers are located or one (1) file with all updates combined. The Delta MSAG updates are received by the TSP either through the use of a Network Data Manager (NDM) or through the TSP Connect:Enterprise mailbox. Delta MSAG File Format The following tables detail NENA Version 2 formats for Delta MSAG Data Exchange Header and Trailer records. Table 5: Delta MSAG Data Exchange Header Record, NENA Version 2 Name Position Bytes Type Description Header Indicator 1-5 5 A Appears as UHL Extract Date 6-11 6 N MMDDYY Company Name 12-61 50 AN Blank 21 (V2012.03.21)

MSAG Management Cycle Counter 62-67 6 N County ID 68-71 4 AN Blank State 72-73 2 A Blank General Use 74-93 20 AN Release Number 94-96 3 N Reserved 97-199 102 AN End of Record 200 1 Always is an asterisk (*) Note: All fields are left justified with trailing spaces, except the Cycle Counter field. This field is right justified with leading spaces. Header records use cycle counting to ensure a cycle of updates is not missed. Table 6: Delta MSAG Data Exchange Trailer Record, NENA Version 2 Name Position Bytes Type Description Trailer Indicator 1-5 5 A Appears as UTL Extract Date 6-11 6 N MMDDYY Company Name 12-61 50 AN Blank Record Count 62-70 9 N N Reserved 71-199 129 AN End of Record 200 1 Always is an asterisk (*) Note: All fields are left justified with trailing spaces, except the Record Count field. This field is right justified with leading spaces. Trailer records use record counting to ensure a record within an update file is not missed. The following table details NENA Version 2 modified format for MSAG Inserts, Deletes, and Changes. (Refer to the bulleted information below the table for specifics on changes.) Table 7: MSAG Inserts, Deletes, and Changes, NENA Version 2 Name Position Bytes Type Description Prefix Directional 1-2 2 AN Street Name 3-62 60 AN Street Suffix 63-66 4 AN Post Directional 67-68 2 AN Low Range 69-78 10 AN High Range 79-88 10 AN Community Name 89-120 32 A State 121-122 2 A 22 (V2012.03.21)

MSAG Management Name Position Bytes Type Description Odd/Even 123 1 A O,E,B ESN 124-128 5 AN Extract Date 129-134 6 N MMDDYY PSAP ID 135-138 4 AN County ID 139-142 4 AN Exchange 143-146 4 AN General Use 147-166 20 AN TAR Code 167-172 6 AN Reserved 173-191 19 AN Expanded Extract Date 192-199 8 N YYYYMMDD End of Record 200 1 Always is an asterisk (*) General Use field should only contain the following values: From MSAG audit record, when identified as "B", populate "Before" in the General Use field. From MSAG audit record, when identified as "A", populate "After" in the General Use field. From MSAG audit record, when identified as "I", populate "Insert" in the General Use field. From MSAG audit record, when identified as "D", populate "Delete" in the General Use field. 23 (V2012.03.21)

Appendix A Glossary of Terms and Definitions Appendix A Glossary of Terms and Definitions Term Definition 9-1-1 9-1-1. The three-digit number reserved for use as an emergency telephone number throughout the United States. Traditionally seen with hyphens as in 9-1-1. ALI ANI C:E DIU ECRC ESN FTP GUI LEC LNP NDM MSAG Automatic Location Identification. The automatic display at the PSAP of the subscriber s TN and the address/location of the telephone. Automatic Number Identification. The automatic display at the PSAP of the subscriber s TN of the telephone or other device from which an Emergency Call is placed. Connect:Enterprise (C:E) is an Intrado application used for file transfers and report delivery. Service Providers submit their service order interface (SOI) files to Intrado via their C:E account and they receive return reports to their C:E inbox for each successfully processed SOI file. Data Integrity Unit Emergency Call Relay Center is the Longmont, Colorado computer operation center that provides 24x7 emergency services support. Emergency Service Number. The number assigned to each residence, business, and coin telephone, which is determined by a specific law enforcement, fire station, and emergency medical service zone. This number is used to deliver calls to the proper Public Safety Answering Point (PSAP). All telephone numbers served by a specific public agency are assigned the same ESN. Phone numbers assigned to the ESN are routed in the same manner to a given law enforcement agency, fire station, and medical agency. File Transfer Protocol. FTP is a communications protocol used to transfer files over a TCP/IP network (Internet, UNIX, etc.), which allows communications between a PC and a workstation for the rapid transfer of data to and from distant or local PCs. Graphical User Interface Local Exchange Carrier. A telecommunications carrier that provides local exchange telecommunications services. Also known as Incumbent Local Exchange Carrier (ILEC), Competitive Local Exchange Carrier (CLEC), Local Service Provider, or Local Dial Tone Provider. Local Number Portability. A circuit-switched network that allows an end user to change service provider, location, and/or service type without having to change their telephone number. Network Data Manager Master Street Address Guide. A listing of all streets in a 9-1-1 service area and the house number ranges for each ESN. The MSAG is typically controlled by the 9-1-1 coordinator. The primary functions of the MSAG database are to validate subscriber addresses and assign an ESN to each customer telephone number, which is then used to develop the selective routing feature. 24 (V2012.03.21)

Appendix A Glossary of Terms and Definitions NENA NENA ID NPA/NXX NRF PSAP RUNP SAG sftp SOI TN TSP TSS (Intrado s Provisioning System) National Emergency Number Association. NENA is a not-for-profit corporation established in 1982 to further the goal of One Nation-One Number. NENA is a networking source and promotes research, planning and training. NENA strives to educate, set standards and provide certification programs, legislative representation and technical assistance for implementing and managing 9-1-1 systems. NENA ID. A company identification number assigned by the National Emergency Number Association. Also known as Company ID. Number Plan Area/Prefix. The area code and the first three-digits of the local seven-digit phone number. This number identifies the central office from which the phone number originates. No Record Found. An incident in which a PSAP receives an E9-1-1 call and no ALI information displays on their equipment for the calling telephone number. Public Safety Answering Point. The answering location for 9-1-1 calls originating from a specified area and is a facility equipped and staffed to receive and dispatch 9-1-1 calls. The PSAP is designated as primary or secondary by software parameters. Run Time Parameter is a screen/table in TSS used to set custom SOI processing parameters for a specific telephone company. Street Address Guide Secure File Transfer Protocol Service Order Interface. Service order information is extracted from the telephone company's service orders and submitted in NENA-2, 512-byte format to Intrado. This data is used by Intrado to process CLEC customers' address records and ultimately to update E9-1-1 ALI databases. Telephone Number Telecommunications Service Provider Transaction Services System. A data management system developed by Intrado, which provides relational MSAG and TN databases that process and maintain data for ALI retrieval and selective routing of enhanced 9-1-1 systems. 25 (V2012.03.21)

Appendix B Version History Appendix B Version History Version Date 2008.06.11 Initial Release Summary of Changes 2008.07.07 Revised TSP Support Contact Support Lists section to reflect current contact information. 2012.03.21 Revised TSP Support Contact Support Lists section. Revised SOI Processing section to add two (2) qualifying Notes. Added new Error Codes Written to and Retained in Error Database table in the TN Errors section. Revised Local Number Portability Errors section. Updated Error Code Descriptions section to add new error codes. Revised SAG Distribution Medium section. Updated Appendix A. 26 (V2012.03.21)