BellSouth E911 Bedienungsanleitung

Customer Guide CG-EWCG-001 Issue 3, J anuary 6, 2004 Wireless E911 Guide[...]

Wir eless E911 Guide CG-EWCG-001 Copyright Issue 3, January 6, 2004 Copyright April, 2002 - January 6, 2004 © BellSouth Page ii[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 T able of Contents Contents Subject Page Introduction / Revision History . . . . . . . . .... ...... ....... ....... ..... v i i Purpose ...................................................... vii V ersion Information .............................................. vii 1. Overview of E911 . . [...]

Wir eless E911 Guide CG-EWCG-001 T able of Contents Issue 3, J anuary 6, 2004 3.5 Interface T esting ........ ...................................... 18 4. MSA G Maintenance and ESN Assignment . . . . . . . ....... ....... ..... 1 9 4.1 Overvie w ................................................... 19 4.2 ESN Assignments .............................[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 T able of Contents 7.5.1 ALI Record Not Found . . ...................................... 62 7.5.2 Wrong ALI Display Of: . ...................................... 62 7.5.3 Address — Community — Location ............................... 62 7.5.4 ESN ..........................................[...]

Wir eless E911 Guide CG-EWCG-001 T able of Contents Issue 3, J anuary 6, 2004 A.7.3 Generic Digits Parameter & GDP T ype ............................. 84 A.7.4 Charge Number Parameter ..................................... 85 A.7.5 Calling Party Category Parameter (CPC, aka: CPCat) .................... 85 A.7.6 Originating Line Information Param[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Introduction / Revision History Introduction / Revision History Purpose This document addresses W ireless E911. V er sion Information Added SS7/ISUP signaling option for trunking between the MSC and E911 tandems. Added Appendix A. Page vii[...]

Wir eless E911 Guide CG-EWCG-001 Introduction / Re vision History Issue 3, J anuary 6, 2004 T able A Revision History Chapter Action Request # Date / Issue Description Change Requested By / Made By All N/ A January 6, 2004 / 3 Added SS7/ISUP signaling option for trunking between the MSC and E911 tandems. Added Appendix A. T om Breen / Bill Marczak [...]

CG-EWCG-001 Wir eless E911 Guide Issue 3, J anuary 6, 2004 Introduction / Revision History T able A Revision History (continued) Chapter Action Request # Date / Issue Description Change Requested By / Made By All N/ A July 15, 2002 / 1b Revisions to sections entitled, "Overvie w of E911", "Coordination of W ireless Interconnection&qu[...]

Wir eless E911 Guide CG-EWCG-001 Introduction / Re vision History Issue 3, J anuary 6, 2004 Page 10[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Overview of E911 1. Overview of E911 1.1 Definition of E911 "911" has been designated in the United States as the number to be used by the public to summon emergenc y aid or to report a crime, f ire or accident. Its main purpose is to make it easier for people in time of emotional [...]

Wir eless E911 Guide CG-EWCG-001 Overview of E911 Issue 3, January 6, 2004 wireless carrier pro viding 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 connectiv[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Overview of E911 1.3 Databases Required to Suppor t E911 Three (3) data f iles (or databases) are required to pro vide the data for display at the PSAP: • Master Street Address Guide (MSA G) • T elephone Number (TN) Database • E911 T andem/Network Information (TN/ESN) 1.4 Master Street[...]

Wir eless E911 Guide CG-EWCG-001 Overview of E911 Issue 3, January 6, 2004 telephone number which has been assigned by the carrier , the carrier name, and the MSA G 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 c[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Overview of E911 1.7 Glossary of T erms T able B Glossary of T erms T erm Definition AC AC Access Carrier Advocac y Center Address V erification Request (A VR) A form issued by each telco to refer and resolve address discrepancies with the E911 Customer . ALEC Alternativ e Local Exchange Car[...]

Wir eless E911 Guide CG-EWCG-001 Overview of E911 Issue 3, January 6, 2004 T able B Glossary of T erms (continued) T erm Definition E911 T andem Central Off ice Switch The central off ice designated for a geographical area to receiv e end off ice E911 calls and route to the appropriate PSAP . Emergenc y Service Number (ESN) A number associated with[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Overview of E911 T able B Glossary of T erms (continued) T erm 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 answe[...]

Wir eless E911 Guide CG-EWCG-001 Overview of E911 Issue 3, January 6, 2004 1.8 Database Escalation Procedures The following procedures ha ve been established for W ireless Carrier escalation of database related issues to BellSouth / Intrado: (Examples of these issues are, b ut not limited to: MSA G problems, NP A / NXX updates, etc.) The initial tr[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Coordination of W ireless Inter connection 2. Coordination of Wireless Interconnection 2.1 Overview This section provides the W ireless Carrier with the steps necessary to interconnect with the BellSouth (BST) E911 network. The FCC W ireless Phase 1 Order requires the W ireless Carrier to pr[...]

Wir eless E911 Guide CG-EWCG-001 Coordination of W ireless Inter connection 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 fro[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Coordination of W ireless Inter connection • If the W ireless 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 W ireless Carrier provides their o wn wire[...]

Wir eless E911 Guide CG-EWCG-001 Coordination of W ireless Inter connection Issue 3, January 6, 2004 2.5.2 Initial Establishment of Mobile P osition Center Pro vider The f irst step for the W ireless Carrier in establishing their MPC provider is to contact the BST W ireless E911 Implementation Manager . At that time a discussion will take place to [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Coordination of W ireless Inter connection 2.5.5 Forms B irmingham D A T A Center: (serving L A, MS, AL, T N, KY) N ashville D A T A Center: (servin g L A, MS, AL, TN, KY) C harlotte D A T A Ce nt er: (serving FL, GA, N C, SC) M iami D A T A Center: (serving F L , GA, NC, SC ) Page 13[...]

Wir eless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 14 - Blank[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Network Specifications and Ordering 3. Network Specifications and Ordering 3.1 Overview This section pro vides the W ireless Carrier with the Network Specifications and Ordering Procedures to be followed when ordering facilities to interconnect to the BST E911 network. Due to the complex nat[...]

Wir eless E911 Guide CG-EWCG-001 Network Specifications and Ordering Issue 3, J anuary 6, 2004 3.2.2 Specification & Ordering Pr ocess: Option 2: Thir d Party V endor Solution The W ireless Carrier will be required to order a minimum of two (2) , T ype 2C, CAMA or SS7/ISUP signaling trunks, connecting to the appropriate BellSouth E911 T andem s[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Network Specifications and Ordering 3.3.2 Data Connections Required For Wireless Carrier Owned Har dware - Phase 1 Only In addition to the T ype 2C CAMA or SS7 trunks, the W ireless Carrier will be required to purchase two(2) data link connections from their protocol con version hardware dir[...]

Wir eless E911 Guide CG-EWCG-001 Network Specifications and Ordering Issue 3, J anuary 6, 2004 II testing and implementation. BellSouth requires that W ireless 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 [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 MSA G Maintenance and ESN Assignment 4. MSA G Maintenance and ESN Assignment 4.1 Overview This section provides general information on ESN assignments and guidelines for working with BST , BST’s data v endor , Intrado, and with the E911 Customer on MSA G maintenance. The W ireless Carrier [...]

Wir eless E911 Guide CG-EWCG-001 MSA G Maintenance and ESN Assignment Issue 3, January 6, 2004 For areas with e xisting E911 service, existing ESN numbers should be assigned for wireless call routing. Any of the currently assigned ESN numbers for a specif ic PSAP can be selected and placed in the corresponding MSA G entries for the cell site addres[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 MSA G Maintenance and ESN Assignment Some solutions will dynamically pro vide the cell site location, subscriber call back number , and lat/long during 911 call processing. W ireless carriers are still required to provide "static" pseudo-ANI data records to the E911 host with MSA G[...]

Wir eless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 22 - Blank[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates 5. TN Database Updates 5.1 Overview The E911 T elephone Number (TN) database contains data records provided by the dif ferent wireline and wireless carriers offering service within the E911 service area. For wireline service, the TN records contain the subscriber’s tele[...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 basis as changes occur . W ireless Carriers will send daily updates to the E911 database via a mechanized file transfer . Specifications for mechanized f ile transfer are described later in the tab . The file must include pseudo-ANI TN records for the cell site locations[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates STEP A CTION 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 cov erage area is modified. 7 Any n[...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 STEP A CTION 11 Three(3) weeks prior to testing or implementing a new NXX, the Wireless Carrier must furnish the NXX T able update form to the BST Wireless E911 Implementation Manager . The form and instructions for its completion are contained in this tab. 12 W ork with[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates Pseudo-ANI records that are not geographically correct for the E911 selectiv e routing tandem may result in "NO RECORD FOUND" or a wrong ALI display due to improper NP A translation. 5.4 Instructions for NXX T able Update Form T able C Instructions for NXX T abl[...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 T able C Instructions for NXX T able Update Form (continued) Instructions for NXX T able Update Form NP A / NXX(s): List all NP A/NXXs for pANI records in this service area. E911 T ANDEM CLLI: Enter the CLLI code for the E911 tandem for which 911 calls using a pANI with [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates 5.5 NXX T able Update Form Figure 1 NXX T able Update Form Page 29[...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 5.6 MSA G Formatting There are basic guidelines for the format of the address on the incoming TN records in order for the TN record to f ind an exact match to an e xisting entry in the MSA G database. TN records which do not match the MSA G e xactly will error back to th[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates 5.7 Standard Street Suffix (Thoroughfare) Designations / Directionals The following table outlines the BellSouth street suf fix (thoroughfare) abbreviations. 5.7.1 BellSouth Street Suffix (Thoroughfare) Abbreviations (T able) T able D BellSouth Street Suffix (Thoroughfare[...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 T able D BellSouth Street Suffix (Thoroughfare) Abbre viations (T able) (continued) T / F Abbre v Description T / F Abbr ev Description FRK FORK RUN RU N FR WY FREEW A Y SQ SQU ARE GRDN GARDEN ST STREET HBR HARBOR ST A ST A TION HL HILL TER TERRA CE HLS HILLS THR WY THR [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates data records, the location data field may be used to define the cell site sector geographical service area. W ireless Carriers should work with the E911 Customer and agree on the TN data record formats including use of the LOCA TION (LOC) data field. There are four(4) le [...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 5.10 Service Order Interface File Specifications This section describes BellSouth Service Order Interface f ile specifications and Service Order Interface Record (SOIR) layouts. BellSouth SOIR layouts resemble the 512 character NEN A V ersion 2 layouts for Data Exchange [...]

CG-EWCG-001 Wir eless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates T able E SOIR File Data Record - BellSouth 512 Character Format for Data Exchange Sent to PSAP Stored in Database Field Name Position Bytes T ype BellSouth Description No No FUNCTION CODE 1 1 A T ype of activity the record is being submitted for . V alid entries: • C -[...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 T able E SOIR File Data Record - BellSouth 512 Character Format for Data Exchange (continued) Sent to PSAP Stored in Database Field Name Position Bytes T ype BellSouth Description Y es - Only 48 characters sent to PSAP .EX: Main St NW Y es - Some solutions may change thi[...]

CG-EWCG-001 Wir eless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates T able E SOIR File Data Record - BellSouth 512 Character Format for Data Exchange (continued) Sent to PSAP Stored in Database Field Name Position Bytes T ype BellSouth Description Ye s Ye s CUSTOMER N AME 188 - 219 32 AN Carrier name associated with the Calling Number . [...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 T able E SOIR File Data Record - BellSouth 512 Character Format for Data Exchange (continued) Sent to PSAP Stored in Database Field Name Position Bytes T ype BellSouth Description No Ye s order number 241 - 250 10 AN Service order number for the acti vity establishing th[...]

CG-EWCG-001 Wir eless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates T able E SOIR File Data Record - BellSouth 512 Character Format for Data Exchange (continued) Sent to PSAP Stored in Database Field Name Position Bytes T ype BellSouth Description Ye s - Dynamically updated in DB. Ye s - Dynamically updated in DB. x coordinate 320 - 328 [...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 5.12 SOIR File Header Recor d Lay out 5.12.1 T able: SOIR File Header Recor d - BellSouth 512 Character Format for Data Exchange Field Name Position Bytes T ype BellSouth Description HEADER INDICA TOR 1-5 5 A Always "UHL " EXTRA CT D A TE 6-11 6 N Date formatte[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Database Updates 5.14 Mechanized File T ransfer 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 W ireless Carrier data f ile passes all validity checks, it will be processed to [...]

Wir eless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, J anuary 6, 2004 If an error is detected, an error conf irmation notice will be sent via mechanized fax. The following error conditions will be detected: • Record Count Mismatch • Cycle Mismatch • Header Record Not Found • T railer Record Not Found The error confirmation notice i[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action 6. TN Error s and Corrective Action 6.1 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 W[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 T able F Confirmation Report Fields and Descriptions FIELD DESCRIPTION FUNCTION CODE V alid codes are: • : I=Insert • C=Change • P=Main account delete • E=Error delete • U=Unlock • M=Migrate NP A Three(3) digit number of Calling Number CALLING NU[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action T able F Confirmation Repor t Fields and Descriptions (continued) COMMUNITY N AME V alid service community of the street name/house number as designated by the MSA G. ST A TE Alpha state abbreviation LOCA TION Additional address information (free formatted) d[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 T able F Confirmation Repor t Fields and Descriptions (continued) GENERAL USE Mutually used by data exchange partners to pass information not defined in pre vious fields. CUSTOMER CODE Code used to uniquely identify customer . COMMENTS Optional notes may be [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action Figure 2 The Statistics Repor t 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 c ycle. T o retriev e reports after s[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 to Intrado Connect, (2) click on the transfer key , and (3) click on the download ke y and automatically retriev e your reports. 6.2.4 TN Error Deletion When a SOIR is processed, a check is made to determine if an error record e xists in the error file with [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action T able G Err or Codes and Error Descriptions (continued) ERROR DESCRIPTION 112 Street name has in valid characters 113 Community Name is too long 114 Community Name has in valid characters 115 Service class in valid 116 House Number Suff ix is too long 120 TN[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 T able G Err or Codes and Error Descriptions (continued) ERROR DESCRIPTION 756 Company Code mismatch on Change 757 Company Code mismatch on Delete 758 Company ID mismatch on Unlock 760 Lock exceeded number of retries 762 U or M Function Required for LNP 781 [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action T able H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 107 House number contains in valid characters The house number on the incoming SOIR contains characters other than alpha or numeric. D[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 T able H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 701 House number is not in MSA G range The house number on the incoming SOIR is not found in the house number range for the street an[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action T able H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 709 Street not found in MSA G The directional prefix, street name, community or state on the incoming SOIR cannot be found in the MSAG[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 T able H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 713 TN and main account mismatch The main account shown on the incoming SOIR doesn’t match the main account shown on the database r[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action T able H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 735 Delete failed, record in TN database has same completion The incoming delete SOIR has a completion date that is the same completio[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 T able H 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 [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 TN Err ors and Corrective Action T able H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 758 Company code mismatch on unlock The NEN A ID on the incoming U FOC SOIR does not match the NEN A ID of the TN record in the databa[...]

Wir eless E911 Guide CG-EWCG-001 TN Err ors and Corrective Action Issue 3, J anuary 6, 2004 T able H Error Codes and Corrective Action (continued) Error Code Error Message Occurs when. . . Corrective Action for . . . 783 Unlock failed; main account has sublines The incoming U FOC TN is in the database as a main account with other TNs shown as subli[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 PSAP Inquiries 7. PSAP Inquiries 7.1 Overview E911 is a critical emergenc y 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 For[...]

Wir eless E911 Guide CG-EWCG-001 PSAP Inquiries Issue 3, January 6, 2004 7.2 PSAP Inquiry Form Figure 3 PSAP Inquiry Form Page 60[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 PSAP Inquiries 7.3 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 Receiv ed Enter t[...]

Wir eless E911 Guide CG-EWCG-001 PSAP Inquiries Issue 3, January 6, 2004 - continued - 6. Date Returned Enter the date the Inquiry was returned to the originator 7. Response Code Enter the appropriate response code as follows: • T rouble Cleared, Enter date • No trouble found • Referred to repair 7.4 Inquiry Flow Inquiry Forms that in volv e [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 PSAP Inquiries 7.5.4 ESN In vestigate 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 v alid information. Once resolv ed, check action: "Trouble cleared as of (enter[...]

Wir eless E911 Guide CG-EWCG-001 PSAP Inquiries Issue 3, January 6, 2004 7.6.1 PSAP Inquiry Log Figure 5 PSAP Inquiry Log Page 64[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 No Record F ound (NRF) Pr ocessing 8. No Record Found (NRF) Pr ocessing 8.1 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 . The purpose of an NRF in vestigation is to: • identif[...]

Wir eless E911 Guide CG-EWCG-001 No Record Found (NRF) Processing Issue 3, J anuary 6, 2004 - continued - T uesday’s NRFs NRF report distributed on W ednesday W ednesday’s NRFs NRF report distributed on Thursday Thursday’s NRFs NRF report distributed on Friday 8.4 No Record Found (NRF) Repor t Lay out The NRF report is separated by W ireless [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 No Record F ound (NRF) Pr ocessing • 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 prev ent further NRF occurrences. • Ad[...]

Wir eless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 68 - Blank[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 NENA Company Registration Process 9. NENA Company Registration Pr ocess 9.1 NENA Cmpany ID Registration Service W ireless Service Pro viders and the FCC mandate placed upon them for deliv ery of location information and the wireless subscribers callback number generates a need in 9–1–1 s[...]

Wir eless E911 Guide CG-EWCG-001 NENA Company Registration Process Issue 3, January 6, 2004 9.3 Use of the Service For your con venience, NEN A has created an online Company Identifier Data Base Input F orm that you can either print out and f ill in or you can complete it online, hit the submit button, and you will be in voiced for the fee. The NEN[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 NENA Company Registration Process Figure 6 Input Form Page 71[...]

Wir eless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 72 - Blank[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 Reconciliation 10. Reconciliation 10.1 Overview W ireless Carriers or their agents are granted an extract of their E9-1-1 data annually for database reconciliation. The BellSouth Implementation Manager of fering a yearly reconciliation of data sends a letter and extract request form to each [...]

Wir eless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 74 - Blank[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide A. BellSouth Wireless E9–1–1/SS7 Inter connection Guide A.1 BellSouth Wireless E-9–1–1/SS7 Interconnection Guide This document is intended to pro vide an e xplanation of ho w SS7/ISUP trunks can be used for deli very of W irele[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 NEN A (National Emergenc y Number Association) has published a T echnical Information Document: "NEN A 05-501 T echnical Information Document on SS7 Guidelines for MSC to Selecti ve Router Connectivity ." (available at: h ttp[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless 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 T andem (Referred to as NDET throughout this document.). For all practical purposes these calls appear to be like wireline cal[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 A.2.2 Database Steering Options The NEN A 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. BellSouth will sup[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide view , this general location number is simply used to determine which PSAP should receiv e the call. This document will use the term pANI generically , except where it is more appropriate to use ESRD or ESRK. Other industry documents s[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 • TR 73554 Issue D, December 2002 (or later), BST GUIDELINES TO TECHNICAL PUBLICA TION GR-905-CORE (T elcordia document GR-905-CORE specifies the interfaces required to interconnect out-of-band Common Channel Signaling (CCS) networks[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide The WSP (or their agent) must hav e the ALI database pre-populated with records matching the pANIs (ESRD/ESRK) the y will use, or the call will default route, and the PSAP will receiv e a "no record found" rather than the exp[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 regard to how they are used in this document. There may be significant impact to W ireless E9-1-1 service if the W ireless Engineer fails to understand these differences during establishment of initial interconnection using SS7/ISUP fo[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide W ireless E9-1-1 Solution (WLS911), a Hybrid architecture functional in both Phase 1 and Phase 2 en vironments. WSPs should see their BellSouth account team for details on how the WLS911 Solution may be of value in their ov erall archi[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 A.7.2 Calling Party Number Parameter Calling Party Number is a requir ed parameter in the IAM. The Called Party Number parameter value is variable depending upon which trunk group signaling option is being used. In an y case it shall e[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide A.7.4 Charge Number Parameter If present, the Charge Number parameter shall contain the caller’s CBN or the non-dialable callback number , or in W ireline Compatibility Mode it shall contain the pANI. Charge Number is an optional par[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 A.8 Cross Reference T ables 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 acco[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide 1. For an ESC, the ISUP Called P arty Number parameter shall only be populated with the digit value "911". 2. The Calling Party Number MUST be included in the IAM message. The Char ge Number may also be included in the IAM, b[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 their BellSouth account team for details on ho w the WLS911 Solution may be of value in their ov erall architecture plans. Orreq Parameters UP Parameters V alue Digits(Dialed) Called party number (see Note 1 below) 911 MDN (aka: CBN) C[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide W ARNING If an MSC switch can support a GDP , and if Wireline Compatibility Mode is NO T desir ed, 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 [...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 - continued - Orreq Parameters ISUP Parameters V alue Digits(Dialed) Called party number (see Note 1 below) 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[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide In this mode the initial position of the mobile is also sent in the IAM. Orreq Parameters ISUP Parameters V alue Digits(Dialed) Called party number (911) or PSAP DN (see Note 1 below) or ESRD MDN Calling party number CBN or the non-dia[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 A.9.1 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 selectiv e router . Call Scenario 1 supports the Wir eline Compatibility Mode 1 describ[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide BellSouth’s equiv alent of NEN A 05-501 T able 4-2 (CBN & ESRD Deliv ery): ISUP Parameter Option OLI Wir eless CpCA T Emergency CdPN CPN CHGN GDP NDET signaling option Note(s) A1 Ye s Ye s 911 CBN CBN ESRD WRLS_STD 1 A2 Ye s Ye s[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide Issue 3, January 6, 2004 - continued - ISUP Parameter Option OLI Wir eless CpCA T Emergency CdPN CPN CHGN GDP NDET signaling option Note(s) K2 No Ye s 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 [...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide not modify it, it simply passes whatev er value it recei ves. Once again, the NDET sets this value, but as of N A013 does not use it to identify wireless calls. In N A016, the NDET be gan checking the OLI parameter on wireless E9-1-1 c[...]

Wir eless E911 Guide CG-EWCG-001 BellSouth Wir eless E9–1–1/SS7 Interconnection Guide 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? Y ou can order it through your normal BellSouth circuit ordering procedures. See BellSouth TR 73554 Issue D, Decem[...]

CG-EWCG-001 Wireless E911 Guide Issue 3, J anuary 6, 2004 BellSouth W ireless E9–1–1/SS7 Interconnection Guide KEYWORDS Wireless Carrier BST Wireless E911 Page 97[...]