Wireless Router Owner Guide

ManualsBrandsBellSouth ManualsNetwork RouterE911

Customer Guide

CG-EWCG-001

Issue 3, January 6, 2004

Wireless E911 Guide

Summary of content (107 pages)

PAGE 1
Customer Guide CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide
PAGE 3
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide Table of Contents Contents Subject Introduction / Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Overview of E911 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
Wireless E911 Guide Table of Contents CG-EWCG-001 Issue 3, January 6, 2004 3.5 Interface Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. MSAG Maintenance and ESN Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 ESN Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.
PAGE 5
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide Table of Contents 7.5.1 ALI Record Not Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.2 Wrong ALI Display Of: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.3 Address — Community — Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.4 ESN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.
PAGE 6
Wireless E911 Guide Table of Contents A.7.3 A.7.4 A.7.5 A.7.6 A.8 A.8.1 A.8.2 A.8.3 A.8.4 A.9 A.9.1 A.9.2 A.10 A.10.1 A.10.2 A.11 A.11.1 A.11.2 A.11.3 A.11.4 A.11.5 A.11.6 A.12 Page vi CG-EWCG-001 Issue 3, January 6, 2004 Generic Digits Parameter & GDP Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Charge Number Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calling Party Category Parameter (CPC, aka: CPCat) . . . . . . . . . . . . . . . . . . . .
PAGE 7
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide Introduction / Revision History Introduction / Revision History Purpose This document addresses Wireless E911. Version Information Added SS7/ISUP signaling option for trunking between the MSC and E911 tandems. Added Appendix A.
PAGE 8
Action Request # N/A N/A N/A N/A N/A Chapter All Page 8 MSAG Maintenance and ESN Assignment Overview of E911; Coordination of Wireless Interconnection; Network Specifications and Ordering TN Database Updates TN Database Updates and PSAP Inquiries Added SS7/ISUP signaling option for trunking between the MSC and E911 tandems. Added Appendix A. Description Corrected FAX numbers. Overview of E911: Added "GMLC" Term, Changed contact for "Level One Escalation: Intrado".
PAGE 9
Action Request # N/A N/A N/A Chapter All Various All April 4, 2002 / 1 Initial Issue June 20, 2001 / 1a General revisions to section entitled "TN Errors and Corrective Action" July 15, 2002 / 1b Revisions to sections entitled, "Overview of E911", "Coordination of Wireless Interconnection", and "Network Specifications and Ordering".
PAGE 10
Wireless E911 Guide Introduction / Revision History Page 10 CG-EWCG-001 Issue 3, January 6, 2004
PAGE 11
CG-EWCG-001 Issue 3, January 6, 2004 1. Overview of E911 1.1 Definition of E911 Wireless E911 Guide Overview of E911 "911" has been designated in the United States as the number to be used by the public to summon emergency aid or to report a crime, fire or accident. Its main purpose is to make it easier for people in time of emotional stress to contact the proper emergency agency. An important advantage of 911 emergency service is improved (reduced) response time.
PAGE 12
Wireless E911 Guide Overview of E911 CG-EWCG-001 Issue 3, January 6, 2004 wireless carrier providing a real-time update to the ALI databases during 9-1-1 call processing. Phase 2 requires both of the data elements provided in Phase 1 plus the longitude and latitude of the caller’s location when they dialed 9-1-1. BellSouth supports E2 connectivity between MPCs and the ALI database hosts as defined in BellSouth Technical Reference TR73610, Issue 2.
PAGE 13
CG-EWCG-001 Issue 3, January 6, 2004 1.3 Wireless E911 Guide Overview of E911 Databases Required to Support E911 Three (3) data files (or databases) are required to provide the data for display at the PSAP: • • • 1.4 Master Street Address Guide (MSAG) Telephone Number (TN) Database E911 Tandem/Network Information (TN/ESN) Master Street Address Guide (MSAG) The MSAG contains all street information in the full featured E911 service area.
PAGE 14
Wireless E911 Guide Overview of E911 CG-EWCG-001 Issue 3, January 6, 2004 telephone number which has been assigned by the carrier, the carrier name, and the MSAG valid address of the cell site sector location. A full description of the data fields in the TN database may be found inTN Database Updates. The TN database is updated by the wireless carrier on an ongoing basis as new pseudo-ANI numbers are assigned or when existing information changes.
PAGE 15
CG-EWCG-001 Issue 3, January 6, 2004 1.7 Wireless E911 Guide Overview of E911 Glossary of Terms Table B Glossary of Terms Term Definition ACAC Access Carrier Advocacy Center Address Verification Request (AVR) A form issued by each telco to refer and resolve address discrepancies with the E911 Customer. ALEC Alternative Local Exchange Carrier Alternate Routing A standard feature provided to allow E911 calls to be routed to a designated alternate location if : 1.
PAGE 16
Wireless E911 Guide Overview of E911 CG-EWCG-001 Issue 3, January 6, 2004 Table B Glossary of Terms (continued) Term Definition E911 Tandem Central Office Switch The central office designated for a geographical area to receive end office E911 calls and route to the appropriate PSAP. Emergency Service Number (ESN) A number associated with the geographical area served by the same fire, police and ambulance districts.
PAGE 17
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide Overview of E911 Table B Glossary of Terms (continued) Term Definition Pseudo-ANI (pANI) The telephone number assigned by the wireless carrier to designate a specific cell antenna face or PSAP. Also see Automatic Number Identification (ANI). Public Safety Answering Point (PSAP) The answering location for 911 calls.
PAGE 18
Wireless E911 Guide Overview of E911 1.8 CG-EWCG-001 Issue 3, January 6, 2004 Database Escalation Procedures The following procedures have been established for Wireless Carrier escalation of database related issues to BellSouth / Intrado: (Examples of these issues are, but not limited to: MSAG problems, NPA / NXX updates, etc.) The initial trouble / problem referral made by the Wireless Carrier should go to the Intrado NDSC Data Analyst.
PAGE 19
CG-EWCG-001 Issue 3, January 6, 2004 2. 2.1 Wireless E911 Guide Coordination of Wireless Interconnection Coordination of Wireless Interconnection Overview This section provides the Wireless Carrier with the steps necessary to interconnect with the BellSouth (BST) E911 network. The FCC Wireless Phase 1 Order requires the Wireless Carrier to provide both the cell site sector location information and the wireless subscribers call - back number for wireless 911 calls.
PAGE 20
Wireless E911 Guide Coordination of Wireless Interconnection CG-EWCG-001 Issue 3, January 6, 2004 of the appropriate E911 tandem, 911 call routing, default routing for ANI failures, and assignment of geographically valid pANI numbers from the wireless carrier’s number range. The E911 customers must agree on which PSAP will accept 911 calls from the various cell sites including when ANI failures occur.
PAGE 21
CG-EWCG-001 Issue 3, January 6, 2004 • • • • Wireless E911 Guide Coordination of Wireless Interconnection If the Wireless Carrier is connecting to a DMS100 E911 tandem utilizing an existing Nortel wireless connection to the ALI computers, no additional data circuits will be required for Phase 1. If the Wireless Carrier provides their own wireless solution hardware in their network, the Wireless Carrier must provide the data circuits.
PAGE 22
Wireless E911 Guide Coordination of Wireless Interconnection 2.5.2 CG-EWCG-001 Issue 3, January 6, 2004 Initial Establishment of Mobile Position Center Provider The first step for the Wireless Carrier in establishing their MPC provider is to contact the BST Wireless E911 Implementation Manager. At that time a discussion will take place to determine the method of connectivity.
PAGE 23
CG-EWCG-001 Issue 3, January 6, 2004 2.5.
PAGE 24
Wireless E911 Guide Page 14 - Blank CG-EWCG-001 Issue 3, January 6, 2004
PAGE 25
CG-EWCG-001 Issue 3, January 6, 2004 3. 3.1 Wireless E911 Guide Network Specifications and Ordering Network Specifications and Ordering Overview This section provides the Wireless Carrier with the Network Specifications and Ordering Procedures to be followed when ordering facilities to interconnect to the BST E911 network.
PAGE 26
Wireless E911 Guide Network Specifications and Ordering 3.2.2 CG-EWCG-001 Issue 3, January 6, 2004 Specification & Ordering Process: Option 2: Third Party Vendor Solution The Wireless Carrier will be required to order a minimum of two (2), Type 2C, CAMA or SS7/ISUP signaling trunks, connecting to the appropriate BellSouth E911 Tandem switch. If SS7 connectivity will be used, refer to Appendix A of this guide.
PAGE 27
CG-EWCG-001 Issue 3, January 6, 2004 3.3.2 Only Wireless E911 Guide Network Specifications and Ordering Data Connections Required For Wireless Carrier Owned Hardware - Phase 1 In addition to the Type 2C CAMA or SS7 trunks, the Wireless Carrier will be required to purchase two(2)data link connections from their protocol conversion hardware directly to the BellSouth ALI Host computers.
PAGE 28
Wireless E911 Guide Network Specifications and Ordering CG-EWCG-001 Issue 3, January 6, 2004 II testing and implementation. BellSouth requires that Wireless Carriers provide notification in writing upon the selection or change in MPC providers. BellSouth is not responsible for the location determination technology, the accuracy of the location determination technology, or the investigation or maintenance of said technologies.
PAGE 29
CG-EWCG-001 Issue 3, January 6, 2004 4. 4.1 Wireless E911 Guide MSAG Maintenance and ESN Assignment MSAG Maintenance and ESN Assignment Overview This section provides general information on ESN assignments and guidelines for working with BST, BST’s data vendor, Intrado, and with the E911 Customer on MSAG maintenance.
PAGE 30
Wireless E911 Guide MSAG Maintenance and ESN Assignment CG-EWCG-001 Issue 3, January 6, 2004 For areas with existing E911 service, existing ESN numbers should be assigned for wireless call routing. Any of the currently assigned ESN numbers for a specific PSAP can be selected and placed in the corresponding MSAG entries for the cell site addresses as described in the next section. The PSAP should identify which ESNs should be used. 4.
PAGE 31
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide MSAG Maintenance and ESN Assignment Some solutions will dynamically provide the cell site location, subscriber call back number, and lat/long during 911 call processing. Wireless carriers are still required to provide "static" pseudo-ANI data records to the E911 host with MSAG valid addresses. These "static" records will be dynamically updated during 911 call processing.
PAGE 32
Wireless E911 Guide Page 22 - Blank CG-EWCG-001 Issue 3, January 6, 2004
PAGE 33
CG-EWCG-001 Issue 3, January 6, 2004 5. 5.1 Wireless E911 Guide TN Database Updates TN Database Updates Overview The E911 Telephone Number (TN) database contains data records provided by the different wireline and wireless carriers offering service within the E911 service area. For wireline service, the TN records contain the subscriber’s telephone number, name, service address, and other information about the fixed wireline subscriber location that may be helpful in providing emergency response.
PAGE 34
Wireless E911 Guide TN Database Updates CG-EWCG-001 Issue 3, January 6, 2004 basis as changes occur. Wireless Carriers will send daily updates to the E911 database via a mechanized file transfer. Specifications for mechanized file transfer are described later in the tab. The file must include pseudo-ANI TN records for the cell site locations or PSAPs in each E911 serving area.
PAGE 35
CG-EWCG-001 Issue 3, January 6, 2004 STEP Wireless E911 Guide TN Database Updates ACTION 5 Coordinate MSAG updates for the cell sites (or PSAPs) submitted on Maintenance Ledgers by the E911 Customer (including naming/numbering street data) 6 Update address on pseudo-ANI (TN) records as address data or cell site coverage area is modified. 7 Any new service and all subsequent activity affecting the cell site location or PSAP records must be updated into the TN database.
PAGE 36
Wireless E911 Guide TN Database Updates STEP 5.3 CG-EWCG-001 Issue 3, January 6, 2004 ACTION 11 Three(3) weeks prior to testing or implementing a new NXX, the Wireless Carrier must furnish the NXX Table update form to the BST Wireless E911 Implementation Manager. The form and instructions for its completion are contained in this tab. 12 Work with E911 Customer to resolve address or ESN discrepancies.
PAGE 37
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Database Updates Pseudo-ANI records that are not geographically correct for the E911 selective routing tandem may result in "NO RECORD FOUND" or a wrong ALI display due to improper NPA translation. 5.
PAGE 38
Wireless E911 Guide TN Database Updates CG-EWCG-001 Issue 3, January 6, 2004 Table C Instructions for NXX Table Update Form (continued) Instructions for NXX Table Update Form NPA / NXX(s): List all NPA/NXXs for pANI records in this service area. E911 TANDEM CLLI: Enter the CLLI code for the E911 tandem for which 911 calls using a pANI with This NXX will be routed to. (The BST Wireless E911 Implementation Manager can assist you in determining this value).
PAGE 39
CG-EWCG-001 Issue 3, January 6, 2004 5.
PAGE 40
Wireless E911 Guide TN Database Updates 5.6 CG-EWCG-001 Issue 3, January 6, 2004 MSAG Formatting There are basic guidelines for the format of the address on the incoming TN records in order for the TN record to find an exact match to an existing entry in the MSAG database. TN records which do not match the MSAG exactly will error back to the Wireless Carrier for resolution and re-transmission of the TN data.
PAGE 41
CG-EWCG-001 Issue 3, January 6, 2004 5.7 Wireless E911 Guide TN Database Updates Standard Street Suffix (Thoroughfare) Designations / Directionals The following table outlines the BellSouth street suffix (thoroughfare) abbreviations. 5.7.
PAGE 42
Wireless E911 Guide TN Database Updates CG-EWCG-001 Issue 3, January 6, 2004 Table D BellSouth Street Suffix (Thoroughfare) Abbreviations (Table) (continued) T / F Abbrev Description T / F Abbrev Description FRK FORK RUN RUN FRWY FREEWAY SQ SQUARE GRDN GARDEN ST STREET HBR HARBOR STA STATION HL HILL TER TERRACE HLS HILLS THRWY THRUWAY HOLW HOLLOW TR TRAIL HT HEIGHT TRC TRACE HTS HEIGHTS TRNPK TURNPIKE HWY HIGHWAY VLG VILLAGE ISL ISLAND WAY WAY JCTN JUNCTION
PAGE 43
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Database Updates data records, the location data field may be used to define the cell site sector geographical service area. Wireless Carriers should work with the E911 Customer and agree on the TN data record formats including use of the LOCATION (LOC) data field. There are four(4) levels of identifiers used for different types of information.
PAGE 44
Wireless E911 Guide TN Database Updates 5.10 CG-EWCG-001 Issue 3, January 6, 2004 Service Order Interface File Specifications This section describes BellSouth Service Order Interface file specifications and Service Order Interface Record (SOIR) layouts. BellSouth SOIR layouts resemble the 512 character NENA Version 2 layouts for Data Exchange with some BellSouth specific differences. Files for updating the BellSouth E911 database must adhere to the following file specifications: 1.
PAGE 45
CALLING NUMBER (TN) HOUSE NUMBER house number suffix Yes Yes Yes Yes Yes Yes - Only eight(8) characters sent to PSAP. Yes Yes Yes Yes prefix directional NPA FUNCTION CODE No No Field Name Stored in Database Sent to PSAP 26 - 27 22 - 25 12 - 21 5 - 11 2-4 1 2 4 10 7 3 1 Bytes A AN AN N N A Type Leading street direction prefix.The field should be space filled if no prefix applies. Valid entries: N, S, E, W, NE, NW, SE, SW. House number extension (e.g., 1/2).
PAGE 46
Page 36 Yes - Only twenty(20) characters stored and sent to PSAP. Yes - Value of G = Wireless P1 (Sent to PSAP as WRLS). Value of H = Wireless P2 (Sent to PSAP as WPH2) location Alpha postal state abbreviation (e.g., AL, FL, GA, KY, LA, MS, NC, SC, and TN). Additional address information (free formatted) describing the exact location of the Calling Number (e.g., APT 718). AN Valid service community of the street name / house number as designated by the MSAG.
PAGE 47
Yes No MAIN NPA No Yes No Yes Bytes 1 1 Type N N AN AN N AN AN - continued - 234 - 240 7 231 - 233 3 226 - 230 5 222 - 225 4 221 220 188 - 219 32 Position Main telephone number associated with the Calling Number. For wireless use same value as Calling Number field. Area code of the Main Number associated with the Calling Number. For wireless, use same value as NPA field.
PAGE 48
Stored in Database Yes Yes Yes Yes Yes Yes Yes No Yes Yes Sent to PSAP No Page 38 No No Yes No No No No No No Bytes 1 Type AN AN AN AN AN AN AN AN N AN - continued - 290 - 319 30 287 - 289 3 276 - 286 11 272 - 275 4 267 - 271 5 266 261 - 265 5 257 - 260 4 251 - 256 6 241 - 250 10 Position Optional notes Code used to uniquely identify a customer. For ICO, ALEC, and Wireless companies this code can be blank on input or filled with 999.
PAGE 49
Yes y coordinate Dynamically updated in DB. No No No Yes Yes No No Yes Dynamically updated in DB. No No No No Yes No No END OF RECORD Bytes 1 512 1 366 - 511 146 356 - 365 10 350 - 355 6 349 343 - 348 6 338 - 342 5 329 - 337 9 320 - 328 9 Position AN AN N AN AN AN AN AN AN Type Always an asterisk (*) This field is reserved for the processing company’s use.
PAGE 50
Wireless E911 Guide TN Database Updates 5.12 CG-EWCG-001 Issue 3, January 6, 2004 SOIR File Header Record Layout 5.12.
PAGE 51
CG-EWCG-001 Issue 3, January 6, 2004 5.14 Wireless E911 Guide TN Database Updates Mechanized File Transfer The Service Order Interface Record (SOIR) is the TN database information that is mechanically transmitted to INTRADO for inclusion in the E911 database. If the Wireless Carrier data file passes all validity checks, it will be processed to the E911 database. PLEASE NOTE: THE PREFERRED METHOD OF DATA TRANSMISSION IS CONNECT:MAILBOXTM, A PRODUCT OFFERED THROUGH INTRADO.
PAGE 52
Wireless E911 Guide TN Database Updates CG-EWCG-001 Issue 3, January 6, 2004 If an error is detected, an error confirmation notice will be sent via mechanized fax.
PAGE 53
CG-EWCG-001 Issue 3, January 6, 2004 6. 6.1 Wireless E911 Guide TN Errors and Corrective Action TN Errors and Corrective Action Overview This section provides procedures for correcting errors that are generated when updates to the E911 database do not pass database edits. Records that fail the edits will be sent daily in an error report to the Wireless Carrier. Errors are sorted in TN order and an error code is provided on each error to aid the Carrier in identifying the erroneous information.
PAGE 54
Wireless E911 Guide TN Errors and Corrective Action Table F FIELD CG-EWCG-001 Issue 3, January 6, 2004 Confirmation Report Fields and Descriptions DESCRIPTION FUNCTION CODE Valid codes are: • : I=Insert • C=Change • P=Main account delete • E=Error delete • U=Unlock • M=Migrate NPA Three(3) digit number of Calling Number CALLING NUMBER Seven(7) digit number of Calling Number HOUSE NUMBER House Number. The field should be spaced filled if no house number is available.
PAGE 55
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Errors and Corrective Action Table F Confirmation Report Fields and Descriptions (continued) COMMUNITY NAME Valid service community of the street name/house number as designated by the MSAG. STATE Alpha state abbreviation LOCATION Additional address information (free formatted) describing the exact location of the Calling Number (e.g. APT 718). CUSTOMER NAME Subscriber name associated with the Calling Number.
PAGE 56
Wireless E911 Guide TN Errors and Corrective Action CG-EWCG-001 Issue 3, January 6, 2004 Table F Confirmation Report Fields and Descriptions (continued) 6.2.2 GENERAL USE Mutually used by data exchange partners to pass information not defined in previous fields. CUSTOMER CODE Code used to uniquely identify customer.
PAGE 57
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Errors and Corrective Action Figure 2 The Statistics Report 6.2.3 Distribution of Daily Reports Intrado forwards daily reports electronically each business day. The Saturday and Sunday Confirmation and Statistical reports are included in Monday’s cycle.
PAGE 58
Wireless E911 Guide TN Errors and Corrective Action CG-EWCG-001 Issue 3, January 6, 2004 to Intrado Connect, (2) click on the transfer key, and (3) click on the download key and automatically retrieve your reports. 6.2.4 TN Error Deletion When a SOIR is processed, a check is made to determine if an error record exists in the error file with the same TN on the SOIR.
PAGE 59
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Errors and Corrective Action Table G Error Codes and Error Descriptions (continued) ERROR DESCRIPTION 112 Street name has invalid characters 113 Community Name is too long 114 Community Name has invalid characters 115 Service class invalid 116 House Number Suffix is too long 120 TN is incorrectly formatted 126 Invalid type of service 701 House number is not in MSAG range 702 Record already exists, insert not allowed 704 Rec
PAGE 60
Wireless E911 Guide TN Errors and Corrective Action Table G CG-EWCG-001 Issue 3, January 6, 2004 Error Codes and Error Descriptions (continued) ERROR 6.
PAGE 61
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Errors and Corrective Action Table H Error Code Error Message Error Codes and Corrective Action (continued) Occurs when. . . Corrective Action for . . . 107 House number contains invalid characters The house number on the incoming SOIR contains characters other than alpha or numeric.
PAGE 62
Wireless E911 Guide TN Errors and Corrective Action Table H Error Code Error Message CG-EWCG-001 Issue 3, January 6, 2004 Error Codes and Corrective Action (continued) Occurs when. . . Corrective Action for . . .
PAGE 63
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Errors and Corrective Action Table H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . .
PAGE 64
Wireless E911 Guide TN Errors and Corrective Action Table H Error Code Error Message CG-EWCG-001 Issue 3, January 6, 2004 Error Codes and Corrective Action (continued) Occurs when. . . Corrective Action for . . . 713 TN and main account mismatch The main account shown on the incoming Submit D FOC on existing database SOIR doesn’t match the main account record to delete TN with different main shown on the database record.
PAGE 65
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Errors and Corrective Action Table H Error Code Error Message Error Codes and Corrective Action (continued) Occurs when. . . Corrective Action for . . .
PAGE 66
Wireless E911 Guide TN Errors and Corrective Action Table H CG-EWCG-001 Issue 3, January 6, 2004 Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 754 No record exists on lock The TN on the incoming Migrate SOIR does not exist in the database. Determine if the error record TN is valid: • If error record TN is valid, no action is necessary. Processing in the TN database will change the M FOC to an I FOC and insert the record.
PAGE 67
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide TN Errors and Corrective Action Table H Error Code 758 Error Message Error Codes and Corrective Action (continued) Occurs when. . . Company code The NENA ID on the incoming U FOC mismatch on unlock SOIR does not match the NENA ID of the TN record in the database Corrective Action for . . .
PAGE 68
Wireless E911 Guide TN Errors and Corrective Action Table H Error Code CG-EWCG-001 Issue 3, January 6, 2004 Error Codes and Corrective Action (continued) Error Message Occurs when. . . Corrective Action for . . . 783 Unlock failed; main The incoming U FOC TN is in the There are two possible corrective actions: account has sublines database as a main account with other 1.
PAGE 69
CG-EWCG-001 Issue 3, January 6, 2004 7. 7.1 Wireless E911 Guide PSAP Inquiries PSAP Inquiries Overview E911 is a critical emergency service. Therefore, any address condition that interferes with a caller reaching the appropriate PSAP, and having an accurate display, must be corrected as quickly as possible. For this reason, the E911 Inquiry Form has been developed as a tool for the PSAP attendants to use in reporting address problems encountered with the E911 system.
PAGE 70
Wireless E911 Guide PSAP Inquiries 7.
PAGE 71
CG-EWCG-001 Issue 3, January 6, 2004 7.3 Wireless E911 Guide PSAP Inquiries PSAP Inquiry Log The following is an example of a PSAP Inquiry Log and instructions for completion: Figure 4 PSAP Inquiry Log 7.3.1 Instructions for Completing PSAP Inquiry Log 1. Serial Number Enter the serial number assigned by the E911 Customer 2. Date Received Enter the date the Inquiry was received 3. NPA / Telephone Number Enter the NPA and telephone number being referred on the Inquiry 4.
PAGE 72
Wireless E911 Guide PSAP Inquiries CG-EWCG-001 Issue 3, January 6, 2004 - continued - 7.4 6. Date Returned Enter the date the Inquiry was returned to the originator 7. Response Code Enter the appropriate response code as follows: • Trouble Cleared, Enter date • No trouble found • Referred to repair Inquiry Flow Inquiry Forms that involve the "Database Reason For Inquiry" will be forwarded to the Carrier for investigation and resolution.
PAGE 73
CG-EWCG-001 Issue 3, January 6, 2004 7.5.4 Wireless E911 Guide PSAP Inquiries ESN Investigate as necessary with the E911 Customer to determine the correct address. Update the address information for the pseudo-ANI TN record by submitting a corrected SOIR with the valid information. Once resolved, check action: "Trouble cleared as of (enter the date)" and return the inquiry to the originator.
PAGE 74
Wireless E911 Guide PSAP Inquiries 7.6.
PAGE 75
CG-EWCG-001 Issue 3, January 6, 2004 8. 8.1 Wireless E911 Guide No Record Found (NRF) Processing No Record Found (NRF) Processing Overview A No Record Found (NRF) condition occurs when a subscriber calls 911 and no database information exists for the cell site pseudo-ANI telephone number.
PAGE 76
Wireless E911 Guide No Record Found (NRF) Processing CG-EWCG-001 Issue 3, January 6, 2004 - continued - 8.4 Tuesday’s NRFs NRF report distributed on Wednesday Wednesday’s NRFs NRF report distributed on Thursday Thursday’s NRFs NRF report distributed on Friday No Record Found (NRF) Report Layout The NRF report is separated by Wireless Carrier and by state and sorted by telephone number. A summary is provided for numbers of NRFs.
PAGE 77
CG-EWCG-001 Issue 3, January 6, 2004 • • • Wireless E911 Guide No Record Found (NRF) Processing If the TN should be in the database, a SOIR should be submitted to insert the TN record or to resolve an outstanding error in the error file. Research why the record was not in the database and take action to prevent further NRF occurrences.
PAGE 78
Wireless E911 Guide Page 68 - Blank CG-EWCG-001 Issue 3, January 6, 2004
PAGE 79
CG-EWCG-001 Issue 3, January 6, 2004 9. 9.1 Wireless E911 Guide NENA Company Registration Process NENA Company Registration Process NENA Cmpany ID Registration Service Wireless Service Providers and the FCC mandate placed upon them for delivery of location information and the wireless subscribers callback number generates a need in 9–1–1 service for identification of the relationship between the telecommunication company and telephone number.
PAGE 80
Wireless E911 Guide NENA Company Registration Process 9.3 CG-EWCG-001 Issue 3, January 6, 2004 Use of the Service For your convenience, NENA has created an online Company Identifier Data Base Input Form that you can either print out and fill in or you can complete it online, hit the submit button, and you will be invoiced for the fee. The NENA Web page address is http://www.nena9–1–1.org/companyid.
PAGE 81
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide NENA Company Registration Process Figure 6 Input Form Page 71
PAGE 82
Wireless E911 Guide Page 72 - Blank CG-EWCG-001 Issue 3, January 6, 2004
PAGE 83
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide Reconciliation 10. Reconciliation 10.1 Overview Wireless Carriers or their agents are granted an extract of their E9-1-1 data annually for database reconciliation. The BellSouth Implementation Manager offering a yearly reconciliation of data sends a letter and extract request form to each company in the first quarter of the year. This document outlines the procedures used to request a data extract for the purpose of reconciliation. 10.
PAGE 84
Wireless E911 Guide Page 74 - Blank CG-EWCG-001 Issue 3, January 6, 2004
PAGE 85
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide A. BellSouth Wireless E9–1–1/SS7 Interconnection Guide A.1 BellSouth Wireless E-9–1–1/SS7 Interconnection Guide This document is intended to provide an explanation of how SS7/ISUP trunks can be used for delivery of Wireless E9-1-1 calls in the BellSouth E9-1-1 serving area. NOTE: The need to provide and maintain the reliability and integrity of E9-1-1 service is a top priority.
PAGE 86
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide CG-EWCG-001 Issue 3, January 6, 2004 NENA (National Emergency Number Association) has published a Technical Information Document: "NENA 05-501 Technical Information Document on SS7 Guidelines for MSC to Selective Router Connectivity." (available at: http://www.nena9-1-1.org/9-1-1TechStandards/tech_info_docs.htm ).
PAGE 87
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide A1, A2, A3, B1, B2, and B3 are supported using the E911_STD trunk options on the BellSouth Nortel DMS E9-1-1 Tandem (Referred to as NDET throughout this document.). For all practical purposes these calls appear to be like wireline calls at the NDET. A.2.1.
PAGE 88
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide A.2.2 CG-EWCG-001 Issue 3, January 6, 2004 Database Steering Options The NENA 05-501 document also defines data base steering options that are used to interconnect the wireless carrier’s network with the BellSouth Enhanced 9-1-1 ALI Database systems.
PAGE 89
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide view, this general location number is simply used to determine which PSAP should receive the call. This document will use the term pANI generically, except where it is more appropriate to use ESRD or ESRK. Other industry documents specify which precise term is applicable for different situations, but that distinction is beyond the scope or intention of this document.
PAGE 90
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide • • CG-EWCG-001 Issue 3, January 6, 2004 TR 73554 Issue D, December 2002 (or later), BST GUIDELINES TO TECHNICAL PUBLICATION GR-905-CORE (Telcordia document GR-905-CORE specifies the interfaces required to interconnect out-of-band Common Channel Signaling (CCS) networks that utilize the Signaling System Number 7 (SS7) protocol provided by a different CCS Network.
PAGE 91
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide The WSP (or their agent) must have the ALI database pre-populated with records matching the pANIs (ESRD/ESRK) they will use, or the call will default route, and the PSAP will receive a "no record found" rather than the expected location information. A.6 A.6.
PAGE 92
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide CG-EWCG-001 Issue 3, January 6, 2004 regard to how they are used in this document. There may be significant impact to Wireless E9-1-1 service if the Wireless Engineer fails to understand these differences during establishment of initial interconnection using SS7/ISUP for wireless E9-1-1. Generally speaking, the term CAS (Callpath Associated Signaling) means the same thing in Wireless Phase 1 and Phase 2.
PAGE 93
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide Wireless E9-1-1 Solution (WLS911), a Hybrid architecture functional in both Phase 1 and Phase 2 environments. WSPs should see their BellSouth account team for details on how the WLS911 Solution may be of value in their overall architecture plans. A.7 Interface Protocol for Wireless Call Setup when using SS7/ISUP signaling.
PAGE 94
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide A.7.2 CG-EWCG-001 Issue 3, January 6, 2004 Calling Party Number Parameter Calling Party Number is a required parameter in the IAM. The Called Party Number parameter value is variable depending upon which trunk group signaling option is being used. In any case it shall either contain the digits "911" or a pANI.
PAGE 95
CG-EWCG-001 Issue 3, January 6, 2004 A.7.4 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide Charge Number Parameter If present, the Charge Number parameter shall contain the caller’s CBN or the non-dialable callback number, or in Wireline Compatibility Mode it shall contain the pANI. Charge Number is an optional parameter in the IAM. Charge Number is an optional parameter in the IAM.
PAGE 96
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide A.8 CG-EWCG-001 Issue 3, January 6, 2004 Cross Reference Tables to J-STD-036-A The intention of this section is to provide a method for a WSP to assess which type of BellSouth supported SS7/ISUP signaling option can best fit their needs. Each decision MUST take into account the capability of the WSPs MSC and the capability of the PSAP CPE, and may be impacted by the type of ALI steering options involved.
PAGE 97
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide 1. For an ESC, the ISUP Called Party Number parameter shall only be populated with the digit value "911". 2. The Calling Party Number MUST be included in the IAM message. The Charge Number may also be included in the IAM, but if so it MUST be the SAME as the Calling Party Number. 3. The Generic digits parameter SHALL NOT be included in the IAM. A.8.
PAGE 98
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide CG-EWCG-001 Issue 3, January 6, 2004 their BellSouth account team for details on how the WLS911 Solution may be of value in their overall architecture plans.
PAGE 99
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide WARNING If an MSC switch can support a GDP, and if Wireline Compatibility Mode is NOT desired, then the GDP is the recommended place to put the pANI. If the WSP will be using a Non Callpath Associated Signaling (NCAS) Solution (as described in J-STD-036-A, Annex-D, Section D.1.
PAGE 100
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide CG-EWCG-001 Issue 3, January 6, 2004 - continued Orreq Parameters Digits(Dialed) ISUP Parameters Called party number (see Note 1 below) Value pANI (see Note 1 below) MDN (aka: CBN) Calling party number (see Note 3 below) CBN or the non-dialable number used in lieu of a real callback DMH_BillingDigits Charge Number (see Note 3 below) CBN or the non-dialable number used in lieu of a real callback (see Note 3 below) GenericDigits
PAGE 101
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide In this mode the initial position of the mobile is also sent in the IAM.
PAGE 102
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide A.9.1 CG-EWCG-001 Issue 3, January 6, 2004 Call Scenario 1: ESRK Delivery Call Scenario 1 describes the mode where an MSC uses ISDN User Part (ISUP) protocol to send an ESRK to an E911 selective router. Call Scenario 1 supports the Wireline Compatibility Mode1described in J-STD-036-A, Annex D, Section D.1.1. Wireless carriers can use Call Scenario 1 to support Phase I and/or Phase II wireless E911 calls.
PAGE 103
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide BellSouth’s equivalent of NENA 05-501 Table 4-2 (CBN & ESRD Delivery): ISUP Parameter Option OLI Wireless A1 Yes Yes A2 Yes A3 CpCAT CdPN Emergency CPN CHGN GDP NDET signaling option Note(s) 911 CBN CBN ESRD WRLS_STD 1 Yes 911 CBN Blank ESRD WRLS_STD 1 Yes Yes 911 Blank CBN ESRD E911_STD 1 B1 Yes No 911 CBN CBN ESRD WRLS_STD 3 B2 Yes No 911 CBN Blank
PAGE 104
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide CG-EWCG-001 Issue 3, January 6, 2004 - continued ISUP Parameter Option OLI Wireless CpCAT CdPN Emergency CPN CHGN GDP NDET signaling option Note(s) K2 No Yes ESRD CBN Blank ESRD WRLS_STD 3 L1 No No ESRD CBN CBN ESRD WRLS_STD 3 L2 No No ESRD CBN Blank ESRD WRLS_STD 3 NOTES: 1. This ISUP parameter option is widely supported in the U.S.
PAGE 105
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide not modify it, it simply passes whatever value it receives. Once again, the NDET sets this value, but as of NA013 does not use it to identify wireless calls. In NA016, the NDET began checking the OLI parameter on wireless E9-1-1 calls ONLY when using AIN Selective routing.
PAGE 106
Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide CG-EWCG-001 Issue 3, January 6, 2004 A.11.5 What if I don’t have SS7 signaling "A" link connectivity to support trunking to the appropriate NDET? You can order it through your normal BellSouth circuit ordering procedures.
PAGE 107
CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide KEYWORDS Wireless Carrier BST Wireless E911 Page 97