1. Manuals
  2. Brands
  3. BellSouth Manuals
  4. Wireless Router
  5. E911
  6. Owner's manual

BellSouth E911 Owner's Manual

Bellsouth wireless router owner guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Customer Guide
CG-EWCG-001
Issue 3, January 6, 2004
Wireless E911 Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the E911 and is the answer not in the manual?

Questions and answers

Summary of Contents for BellSouth E911

  • Page 1 Customer Guide CG-EWCG-001 Issue 3, January 6, 2004 Wireless E911 Guide...
  • Page 2 Wireless E911 Guide CG-EWCG-001 Copyright Issue 3, January 6, 2004 Copyright April, 2002 - January 6, 2004 © BellSouth Page ii...

  • Page 3: Table Of Contents

    PSAP Display ..........Databases Required to Support E911 ....... . .
  • Page 4 TN Database Daily Updates: Wireless Carrier Responsibilities ....E911 Customer Responsibilities ........
  • Page 5 BellSouth Wireless E9–1–1/SS7 Interconnection Guide ..BellSouth Wireless E-9–1–1/SS7 Interconnection Guide ....Executive Summary ..........
  • Page 6 Attachment "B" - Wireless Customer Questions & Answers: ....A.11.1 Why is BellSouth issuing this document? ......A.11.2 Do I have to change my existing trunks to SS7? .

  • Page 7: Introduction / Revision History

    Wireless E911 Guide Issue 3, January 6, 2004 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 vii...
  • Page 8 Wireless E911 Guide CG-EWCG-001 Introduction / Revision History Issue 3, January 6, 2004 Page 8...
  • Page 9 CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 Introduction / Revision History Page 9...
  • Page 10 Wireless E911 Guide CG-EWCG-001 Introduction / Revision History Issue 3, January 6, 2004 Page 10...

  • Page 11: Overview Of E911

    The attendant then determines the appropriate agency and dials the number to transfer the caller to that agency. Enhanced 911 service, or E911, is a full featured electronic system that provides three (3) major enhancements to Basic 911 service: 1.1.1...

  • Page 12: Premises Based Ali Systems

    9-1-1. BellSouth supports E2 connectivity between MPCs and the ALI database hosts as defined in BellSouth Technical Reference TR73610, Issue 2. BellSouth will deliver the lat / long data to the PSAP in the ALI response message as described in BellSouth Technical Reference TR73528, Issue 6.

  • Page 13: Databases Required To Support E911

    Master Street Address Guide (MSAG) The MSAG contains all street information in the full featured E911 service area. The Emergency Service Numbers (ESNs) are assigned to the streets for routing 911 calls to the proper PSAP. As data records for the pseudo-ANI telephone numbers are processed from the wireless carriers, the address information on the data record is validated against the MSAG.

  • Page 14: E911 Tandem / Network Information

    Determining the proper PSAP to route wireless 911 calls must be negotiated between the wireless carrier and the E911 Coordinators in the serving areas. This must also include the proper PSAP to receive the wireless 911 call in the event of an ANI (pANI) failure from the MSC. All 911 calls will default route to the negotiated PSAP when an ANI (pANI) failure occurs.

  • Page 15: Glossary Of Terms

    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. all E911 trunks to the primary PSAP are busy OR 2. the primary PSAP closes down for a period. (i.e. night service)
  • Page 16 A message protocol to support call set up and release for interoffice Digital Network User voice call connections over SS7 signaling. Part (ISUP) Intrado A vendor designated by BST to handle E911 data maintenance (formerly SCC) Location Master Street Address All street data, including street names, address ranges and ESNs...
  • Page 17 A vendor designated by BST to handle E911 data maintenance (now Intrado) Selective Routing (SR) A standard feature that routes an E911call from the E911 tandem to the designated PSAP based upon the address and assigned ESNof the pseudo-ANI telephone number record.

  • Page 18: Database Escalation Procedures

    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: Coordination Of Wireless Interconnection

    E911 tandem. Some solutions may require SS7 / ISUP trunking between the wireless MSC and the E911 tandem. If SS7 connectivity will be used, refer to Appendix A of this guide. In addition to these trunks, Wireless Carriers may be required to order two(2) digital data circuits with secondary channel to the BST Automatic Location Identification (ALI) computers.

  • Page 20: Coordination Process: Bst Wireless Account Team

    A Service Inquiry must be initiated by the Wireless Carrier through the BST Account team for the Type 2C trunk connections and/or SS7 /ISUP trunks to the E911 tandems. If SS7 connectivity will be used, refer to Appendix A of this guide. The BST Wireless E911 Implementation Manager will discuss with the Wireless Carrier the process of ordering / provisioning the digital data circuits to the ALI computers, if new circuits are required.

  • Page 21: Coordination Process: Mobile Position Center Provider

    CG-EWCG-001 Issue 3, January 6, 2004 • 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: Initial Establishment Of Mobile Position Center Provider

    If the Wireless Carrier will use their own equipment and provide their own E2 Interface to BST, the first step is to contact the BST ICS E911 Product Manager. The Wireless Carrier is required to sign the Wireless E911 Phase 2 MPC Operator Interface Agreement and to work with the BST Wireless E911 Implementation Manager to connect the E2 circuits to the ALI databases.

  • Page 23: Forms

    CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 Coordination of Wireless Interconnection 2.5.5 Forms Birmingham DATA Center: (serving LA, MS, AL, TN, KY) Nashville DATA Center: (serving LA, MS, AL, TN, KY) Charlotte DATA Center: (serving FL, GA, NC, SC)
  • Page 24 Wireless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 14 - Blank...

  • Page 25: Network Specifications And Ordering

    The Wireless Carrier will deliver a twenty(20) Digit FG-D signal consisting of the ten(10) digit call back number (CBN) and the ten(10) digit pseudo ANI (p-ANI), to the BellSouth E911 Tandem switch. This signal is in the following format: KP + II + 10 Digit CBN + ST + KP + 10 Digit p-ANI + ST Note that the "II"...

  • Page 26: Specification & Ordering Process: Option 2: Third Party Vendor Solution

    Appendix A of this guide. If using CAMA signaling, the Wireless Carrier must be able to deliver to the BellSouth E911 Tandem the two(2) stage CAMA MF signal required for interfacing directly with the appropriate BellSouth E911 Tandem switches.

  • Page 27: Data Connections Required For Wireless Carrier Owned Hardware - Phase 1 Only

    ALI database. Each MPC provider must execute a contract with BellSouth. This contract must be signed and in place prior to testing Phase II. Wireless Carriers should ensure they have contracted with an MPC provider prior to negotiating Phase...

  • Page 28: Wireless E911 Guide Cg-Ewcg

    Only the data required and specified by the FCC in its Report and Order 94-102 will be delivered by BellSouth to the PSAP when provided by the CMRS. This required data includes the cell site or sector location, the callback number, and the longitude/latitude of the caller.

  • Page 29: Msag Maintenance And Esn Assignment

    BST Wireless E911 Implementation Manager. ESN Assignments ESN mapping is necessary if calls are to be routed to more than one PSAP within an E911 service area. The E911 Customer is responsible for providing boundary information to BST during the conversion to E911 and, ongoing, as emergency districts change.

  • Page 30: Msag Maintenance And Validation

    It is the responsibility of all telcos (wireless and wireline) participating in an E911 service area to ensure that all data records sent to the E911 host database have an MSAG valid address. Each telco will work directly with the E911 Customer to resolve any address discrepancies.
  • Page 31 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. The cell site location information provided during the dynamic updates are not validated against the MSAG, but the original "static"...
  • Page 32 Wireless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 22 - Blank...

  • Page 33: Tn Database Updates

    The ten digit call back number of the wireless caller and the latitude/longitude coordinates are normally provided to the full featured E911 database by way of a real time update during 911 call processing. This interface to the E911 database will vary by the technological solution implemented, but normally involves updating the corresponding TN database pANI record to include the ten digit call back number of the caller, latitude/longitude, and in some solutions, the cell site sector location information.

  • Page 34: Tn Database Daily Updates: Wireless Carrier Responsibilities

    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. Only cell site or PSAP information should be supplied, individual wireless subscriber data should not be provided unless the service is provided to a fixed location.
  • Page 35 Issue 3, January 6, 2004 STEP Coordinate MSAG updates for the cell sites (or PSAPs) submitted on Maintenance Ledgers by the E911 Customer (including naming/numbering street data) Update address on pseudo-ANI (TN) records as address data or cell site coverage area is modified.

  • Page 36: E911 Customer Responsibilities

    911 call is made. The PSAP attendant will see "NO RECORD FOUND". Wireless Carriers must ensure all cell site sector locations are defined in the E911 database. Page 26...

  • Page 37: Instructions For Nxx Table Update Form

    CG-EWCG-001 Issue 3, January 6, 2004 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. Instructions for NXX Table Update Form...
  • Page 38 Wireless E911 Implementation Manager can assist you in determining this value). The NPA/NXXs for the pANI records must be valid in this E911selective routing tandem. Completed forms should be faxed to the BST Wireless E911 Implementation Manager, (205) 977-7692 (fax). Page 28...

  • Page 39: Nxx Table Update Form

    CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 TN Database Updates NXX Table Update Form Figure 1 NXX Table Update Form Page 29...

  • Page 40: Msag Formatting

    MSAG exactly will error back to the Wireless Carrier for resolution and re-transmission of the TN data. Wireless Carriers must work with the E911 Customer and agree on cell site address formats and to ensure corresponding entries are present in the MSAG database. Cell site sector location information provided by some solutions real time during 911 call processing is not validated against the MSAG, although the initial TN record added to the database must have an MSAG valid address.

  • Page 41: Standard Street Suffix (Thoroughfare) Designations / Directionals

    CG-EWCG-001 Issue 3, January 6, 2004 Standard Street Suffix (Thoroughfare) Designations / Directionals The following table outlines the BellSouth street suffix (thoroughfare) abbreviations. 5.7.1 BellSouth Street Suffix (Thoroughfare) Abbreviations (Table) Table D BellSouth Street Suffix (Thoroughfare) Abbreviations (Table) T / F Abbrev...

  • Page 42: Standard Location Designations

    Wireless E911 Guide TN Database Updates Table D BellSouth Street Suffix (Thoroughfare) Abbreviations (Table) (continued) T / F Abbrev FORK FRWY FREEWAY GRDN GARDEN HARBOR HILL HILLS HOLW HOLLOW HEIGHT HEIGHTS HIGHWAY ISLAND JCTN JUNCTION LANDING LAKE When "Avenue" precedes a street name that is a letter or number, it is not considered a street suffix designation and is, therefore, spelled in full.

  • Page 43: Updating The Tn Database

    Wireless Carriers should work with the E911 Customer and agree on the TN data record formats including use of the LOCATION (LOC) data field.

  • Page 44: 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 CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 TN Database Updates Page 35...
  • Page 46 Wireless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, January 6, 2004 Page 36...
  • Page 47 CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 TN Database Updates Page 37...
  • Page 48 Wireless E911 Guide CG-EWCG-001 TN Database Updates Issue 3, January 6, 2004 Page 38...
  • Page 49 CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 TN Database Updates Page 39...

  • Page 50: Soir File Header Record Layout

    Wireless E911 Guide TN Database Updates 5.12 SOIR File Header Record Layout 5.12.1 Table: SOIR File Header Record - BellSouth 512 Character Format for Data Exchange Field Name HEADER INDICATOR EXTRACT DATE COMPANY NAME CYCLE COUNTER county identifier state general use...

  • Page 51: 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.
  • Page 52 Wireless E911 Guide TN Database Updates If an error is detected, an error confirmation notice will be sent via mechanized fax. The following error conditions will be detected: • Record Count Mismatch • Cycle Mismatch • Header Record Not Found •...

  • Page 53: Tn Errors And Corrective Action

    Wireless Carrier error records will not be manually corrected or processed to the E911 database. A corrective SOIR must be issued to update the TN information in the E911 database and / or to delete the error record as appropriate. The records which error must be corrected as quickly as possible for the wireless data to be included in the E911 database.
  • Page 54 Wireless E911 Guide TN Errors and Corrective Action Table F Confirmation Report Fields and Descriptions FIELD FUNCTION CODE Valid codes are: • • • • • • Three(3) digit number of Calling Number CALLING Seven(7) digit number of Calling Number...
  • Page 55 H=Wireless Phase 2 (with X,Y) 0=Not Non-pub or FX 1=FX not Non-pub 2=Not used 3=Non-pub, not FX 4=Non-pub, FX 5=Not Used Daily = Space Initial Load = C - continued - Wireless E911 Guide TN Errors and Corrective Action Page 45...

  • Page 56: The Statistics Report

    The bottom portion of the report lists all the valid error codes for the BellSouth region and the number of errors with that error code. Example of the Statistics Report is shown below.

  • Page 57: Distribution Of Daily Reports

    CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 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. To retrieve reports after sending a file: (1) return...

  • Page 58: Tn Error Deletion

    TN on the SOIR. If an error record other than a U (Unlock) or M (Migrate) exists, the error record will be deleted and the TN will be processed to the E911 Database if the subsequent SOIR is successful. If...
  • Page 59 Update not allowed; flagged for PS / ALI Invalid Function Code Invalid Company ID No record exists on Unlock No record exists on Lock Unable to migrate a locked record TN Errors and Corrective Action DESCRIPTION - continued - Wireless E911 Guide Page 49...

  • Page 60: Error Code And Corrective Action

    A character other than 999 is sent in the customer code field of the incoming record The incoming record contains a NPA / NXX combination that is not valid E911 database tables The main telephone number shown on the SOIR is non-numeric...
  • Page 61 The type of service on an incoming SOIR contains a type of service value other than 0 or 3 - continued - Wireless E911 Guide TN Errors and Corrective Action Corrective Action for . . . Determine the correct MSAG valid...
  • Page 62 MSAG. • If the house number on the SOIR is correct but is not in the MSAG, issue an AVR to the E911 coordinator to update the MSAG house number range • If the house number on the SOIR...
  • Page 63 If the prefix, street, community and state shown on the error record is not found in the MSAG issue an AVR to the E911 Coordinator to have the MSAG updated (Note: Once the MSAG is updated the error record will process and load.) •...
  • Page 64 Wireless E911 Guide TN Errors and Corrective Action Table H Error Codes and Corrective Action (continued) Error Code Error Message TN and main account mismatch Change failed, completion date conflict with disconnect file Insert failed, completion date conflict with disconnect file...
  • Page 65 NENA ID The TN on the incoming unlock SOIR does not exist in the TN database - continued - Wireless E911 Guide TN Errors and Corrective Action Corrective Action for . . . Determine the correct sequence of order activity for the TN: •...
  • Page 66 Wireless E911 Guide TN Errors and Corrective Action Table H Error Codes and Corrective Action (continued) Error Code Error Message No record exists on lock Unable to migrate locked record Company code mismatch on change Company code mismatch on delete Page 56 Occurs when.
  • Page 67 NENA company ID that does not match the NENA ID shown on the TN in the error database - continued - Wireless E911 Guide TN Errors and Corrective Action Corrective Action for . . . Determine if the error record NENA ID is valid: •...

  • Page 68: Compiled Error Report

    This could result in E911 calls being directed to the wrong PSAP and having to be transferred to the appropriate PSAP.

  • Page 69: Psap Inquiries

    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: Psap Inquiry Form

    Wireless E911 Guide CG-EWCG-001 PSAP Inquiries Issue 3, January 6, 2004 PSAP Inquiry Form Figure 3 PSAP Inquiry Form Page 60...

  • Page 71: Psap Inquiry Log

    Number 911 Call Date Action taken Figure 4 PSAP Inquiry Log Enter the serial number assigned by the E911 Customer Enter the date the Inquiry was received Enter the NPA and telephone number being referred on the Inquiry Enter the date of the 911 call...

  • Page 72: Inquiry Flow

    7.5.3 Address — Community — Location Investigate as necessary with the E911 Customer to determine the correct address including a check for MSAG validity. Update the address information for the pseudo-ANI 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 73: Esn

    7.5.5 Misroutes A misroute indicates the E911 call routed to the wrong PSAP. Routing is determined by the ESN associated with the matching address record in the MSAG database. Investigate as necessary with the E911 Customer to determine the correct address. The E911 Customer should be able to assist with identifying the MSAG valid address and the associated ESN to route the calls to the desired PSAP.

  • Page 74: Psap Inquiry Log

    Wireless 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...

  • Page 75: No Record Found (Nrf) Processing

    It is imperative the Wireless Carriers ensure all appropriate pseudo-ANI records are successfully posted to the E911 database before conducting 911 call testing or turning up service. Wireless 911 calls processed without corresponding pseudo-ANI records in the database will result in NRFs at the PSAP and manual investigation by the INTRADO Data Integrity Unit.

  • Page 76: No Record Found (Nrf) Report Layout

    Total number of NRFs NRF Investigation The Wireless Carrier will only be required to investigate and correct NRFs that are not found in the E911 database or if the record was in the error file at the time of the 911 call.
  • Page 77 Telephone number is not in the TN database or the error file. If the record is found in the E911 database, the event will be “CLOSED” and the NRF will not be forwarded to the Carrier. If the TN is found in the error file, the status will be changed to “PENDERR” and will be included in the NRF report.
  • Page 78 Wireless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 68 - Blank...

  • Page 79: Nena Company Registration Process

    However, NECA codes are numeric and not as immediately interpretable as are alpha IDs. In addition, NECA codes do not apply to certain types of 9–1–1 call providing entities, such as resellers and PBX operators, that are needed in 9–1–1 applications. Wireless E911 Guide NENA Company Registration Process Page 69...

  • Page 80: Use Of The Service

    Wireless E911 Guide NENA Company Registration Process 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.
  • Page 81 CG-EWCG-001 Wireless E911 Guide Issue 3, January 6, 2004 NENA Company Registration Process Figure 6 Input Form Page 71...
  • Page 82 Wireless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 72 - Blank...

  • Page 83: 10. Reconciliation

    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.
  • Page 84 Wireless E911 Guide CG-EWCG-001 Issue 3, January 6, 2004 Page 74 - Blank...

  • Page 85: Appendix A. Bellsouth Wireless E9-1-1/Ss7 Interconnection Guide

    Level 3 protocol. These differences have typically been non-traffic affecting differences in timer settings. For these reasons BellSouth has taken the position that the continued investment in time and Level 3 protocol test equipment would be imprudent. However, any other type of devices (e.g., PBXs, VMS host machines, packet switching devices, etc.) that are not routinely connected to the network, will be asked to...

  • Page 86: Identified Options

    SS7/ISUP signaling.) As a high level statement, the intent of this BellSouth Wireless E9-1-1/SS7 Interconnection Guide is to list the call setup parameters shown in the NENA 05-501 TID that are supported by BellSouth, so wireless carriers can chose the one(s) that best meet their needs.

  • Page 87: Call Scenario 2, Cbn And Esrd Delivery - Without A Hybrid

    Call Scenario 3, CBN, ESRD and GLP Delivery: (GLP = Geodetic Location Parameter) BellSouth does not support this method at this time due to the inability of the selective router platform and the MSC platforms to use and/or route on the GLP, or to support ISDN PSAPs in an industry standard manner.

  • Page 88: Database Steering Options

    That general location is represented by a 10 digit number generally known as a psuedoANI (pANI), but also known as Emergency Services Routing Digits (ESRD) or Emergency Services Routing Key (ESRK) based on the type of wireless E9-1-1 solution in use. From the BellSouth E9-1-1 Tandem’s point of Page 78...

  • Page 89: Reason For Revision

    The "BellSouth Wireless E9-1-1 Solution" (aka: WLS911) currently supports Phase I service by allowing a wireless carrier to send the caller’s CBN and the pANI directly to a BellSouth Nortel DMS E9-1-1 Tandem switch (NDET) using dedicated FG-D Multi-Frequency signaling trunks. This Solution can also serve...
  • Page 90 This is the interface that BellSouth is using! Specific "Wireless E9-1-1" interconnection requirements for the CCS network interconnection architecture and the interface protocol for call setup are defined in this BellSouth Wireless E9-1-1/SS7 Interconnection Guide document. This document will define the interconnection requirements in the BellSouth E9-1-1 Network when using SS7/ISUP in concert with one of the various Wireless E9-1-1 options identified in J STD-036-A, and in the NENA 05-501 and 03-006 documents.

  • Page 91: Wireless Ccs Network Interconnection Architecture

    NENA web site at http://www.nena9-1-1.org as of March 25, 2003) If a WSP elects to provide direct MF trunks to be used as backup in the event of an SS7 failure, BellSouth can support such an arrangement. If MF backup is used, the quantity of MF trunks will be determined by Wireless Network Planning practices, but in no case will it be less than two trunk members per Trunk Group (TG).
  • Page 92 ONLY the pANI is sent directly from the WSPs MSC through the BellSouth E9-1-1 Tandem to the PSAP (with the callpath). The CBN is added to the existing pANI record in the BellSouth ALI-DB by the WSP or their agent during call setup, using an out-of-band signaling path (hence NCAS). The updated pANI ALI record including the CBN &...

  • Page 93: Interface Protocol For Wireless Call Setup When Using Ss7/Isup Signaling

    The wireless carrier shall specify the contents of the Calling Party Number (i.e., the CBN or a pANI) at the time the trunk group is ordered (via their BellSouth account team using form RF-1004-WS). Once a trunk group is provisioned, the wireless carrier shall adhere to their choice (i.e., a trunk cannot signal the CBN for one call and a pANI for another call).

  • Page 94: Calling Party Number Parameter

    The wireless carrier shall specify the contents of the Called Party Number (i.e., the digits "911" or a pANI) at the time the trunk group is ordered (via their BellSouth account team using form RF-1004-WS). Once a trunk group is provisioned, the wireless carrier shall adhere to their choice (i.e., a trunk cannot signal the digits "911"...

  • Page 95: Charge Number Parameter

    NOTE: WSPs seeking to waive this requirement should consult their BellSouth representative. See Attachment "A" for details. BellSouth NDETs running software NA016 or higher will require the OLI parameter IF AIN OFF-BOARD SELECTIVE ROUTING IS BEING USED. Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection...

  • Page 96: Cross Reference Tables To J-Std-036-A

    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: Isup Initial Address Message Parameter Contents For Ncas (Ndet Uses Signaling Option Wrls_Std, Because Msc Can Support Gdp)

    CBN (aka: MDN) are sent in the SS7/ISUP IAM directly from the WSPs MSC over dedicated trunks into the BellSouth NDET. The pANI is used by the NDET for selective routing, and then the CBN and the pANI are sent to the PSAP using Enhanced MF signaling (E-MF). This is of course dependant on the ability of the PSAP CPE to receive and utilize E-MF.

  • Page 98: Isup Initial Address Message Parameter Contents For Ncas (Ndet Uses Signaling Option Wrls_Cld Because Msc Cannot Support Gdp)

    Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide their BellSouth account team for details on how the WLS911 Solution may be of value in their overall architecture plans. Orreq Parameters Digits(Dialed) Called party number (see Note 1 below) MDN (aka: CBN) Calling party number (see Note 3...
  • Page 99 (aka: MDN) are sent in the SS7/ISUP IAM directly from the WSPs MSC over dedicated trunks into the BellSouth NDET. The pANI is used by the NDET for selective routing, and then the CBN and the pANI are sent to the PSAP using Enhanced MF signaling (E-MF). This is of course dependant on the ability of the PSAP CPE to receive and utilize E-MF.

  • Page 100: Isup Initial Address Message Parameter Contents For Cas

    GeographicPosition Calling geodetic location Originating Line Information (OLI) NOTES: 1. The pANI is used as the Called party number. In BellSouth the MSC MUST use dedicated trunks to the Emergency Services Network Entity (ESNE) to route the Emergency Services Call (ESC).

  • Page 101: Cross Reference Tables To Nena Tid 05-501 - Ss7 Guidelines For Msc To Selective Router Connectivity

    Cross Reference Tables to NENA TID 05-501 - SS7 Guidelines for MSC to Selective Router Connectivity. The intention of this section is to provide a way 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 102: Call Scenario 1: Esrk Delivery

    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. The table below shows the possible alternatives for populating the parameters in the Initial Address Message (IAM).
  • Page 103 CG-EWCG-001 Issue 3, January 6, 2004 BellSouth’s equivalent of NENA 05-501 Table 4-2 (CBN & ESRD Delivery): ISUP CpCAT Parameter Wireless Emergency Option BellSouth Wireless E9–1–1/SS7 Interconnection CdPN CHGN ESRD Blank ESRD Blank ESRD ESRD Blank ESRD Blank ESRD jCBN...

  • Page 104: A.10 Attachment "A" - Cpcat & Oli Notes

    Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide ISUP CpCAT Parameter Wireless Emergency Option NOTES: 1. This ISUP parameter option is widely supported in the U.S. It is estimated that 95% of the E9-1-1 selective routers deployed in the U.S. support this option when the selective router has been equipped with wireless E9-1-1 features.

  • Page 105: A.11 Attachment "B" - Wireless Customer Questions & Answers

    Selective Routing. Other than when using AIN Selective routing, the OLI parameter is not used for E9-1-1 purposes. If BellSouth NDET is running software NA016 or higher and IF AIN OFF-BOARD SELECTIVE ROUTING IS BEING USED by the NDET, BellSouth will require the WSP to provide the OLI parameter as defined in this document.

  • Page 106: What If I Don't Have Ss7 Signaling "A" Link Connectivity To Support Trunking To The Appropriate Ndet

    Does the MSC have SS7 signaling link connectivity to support trunking to the appropriate NDET? • Do we know what call scenario we plan to follow? (i.e. WCM or NCAS WITH the BellSouth hybrid functionality, etc.) • Do we know what trunk continuity test levels, and testing percentages that we plan to use? (BellSouth encourages that the percentage be 100%.) Remember, BellSouth has no provisions...
  • Page 107 CG-EWCG-001 Issue 3, January 6, 2004 KEYWORDS Wireless Carrier BST Wireless E911 Wireless E911 Guide BellSouth Wireless E9–1–1/SS7 Interconnection Guide Page 97...

Table of Contents