BellSouth E911 Скачать руководство пользователя страница 4

Страница: 4 / 107

Wireless E911 Guide

CG-EWCG-001

Table of Contents

Issue 3, January 6, 2004

3.5

Interface Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSAG Maintenance and ESN Assignment . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2

ESN Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3

MSAG Maintenance and Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TN Database Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2

TN Database Daily Updates: Wireless Carrier Responsibilities . . . . . . . . . . . . . . . .

5.3

E911 Customer Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4

Instructions for NXX Table Update Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5

NXX Table Update Form

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.6

MSAG Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.6.1

Correct Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.6.2

Incorrect Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.7

Standard Street Suffix (Thoroughfare) Designations / Directionals . . . . . . . . . . . . . .

5.7.1

BellSouth Street Suffix (Thoroughfare) Abbreviations (Table) . . . . . . . . . . . . . . .

5.8

Standard Location Designations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.9

Updating the TN Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.10

Service Order Interface File Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.11

SOIR File Data Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.11.1

Table: SOIR File Data Record - BellSouth 512 Character Format for Data Exchange

5.12

SOIR File Header Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.12.1

Table: SOIR File Header Record - BellSouth 512 Character Format for Data
Exchange

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.13

SOIR File Trailer Record Layout

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.13.1

SOIR File Trailer Record - BellSouth 512 Character Format for Data Exchange . . .

5.14

Mechanized File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.15

Mechanized File Confirmations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TN Errors and Corrective Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2

Electronic Error Delivery

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.1

The Confirmation Report

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.2

The Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.3

Distribution of Daily Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.4

TN Error Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3

Error Codes and Error Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4

Error Code and Corrective Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5

Compiled Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PSAP Inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2

PSAP Inquiry Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3

PSAP Inquiry Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.1

Instructions for Completing PSAP Inquiry Log . . . . . . . . . . . . . . . . . . . . . . . .

7.4

Inquiry Flow

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.5

Investigation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page iv

Содержание E911

Страница 1: ...Customer Guide CG EWCG 001 Issue 3 January 6 2004 Wireless E911 Guide...

Страница 2: ...Wireless E911 Guide CG EWCG 001 Copyright Issue 3 January 6 2004 Copyright April 2002 January 6 2004 BellSouth Page ii...

Страница 3: ...Interconnection 9 2 1 Overview 9 2 2 Coordination Process Wireless Carrier 9 2 3 Coordination Process BST Wireless Account Team 10 2 4 Coordination Process BST Wireless E911 Implementation Manager 10...

Страница 4: ...11 SOIR File Data Record Layout 34 5 11 1 Table SOIR File Data Record BellSouth 512 Character Format for Data Exchange 34 5 12 SOIR File Header Record Layout 40 5 12 1 Table SOIR File Header Record Be...

Страница 5: ...Interconnection Guide 75 A 1 BellSouth Wireless E 9 1 1 SS7 Interconnection Guide 75 A 2 Executive Summary 75 A 2 1 Identified Options 76 A 2 1 1 Call Scenario 1 ESRK Delivery 76 A 2 1 2 Call Scenari...

Страница 6: ...S 90 A 9 Cross Reference Tables to NENA TID 05 501 SS7 Guidelines for MSC to Selective Router Connectivity 91 A 9 1 Call Scenario 1 ESRK Delivery 92 A 9 2 8 2 Call Scenario 2 CBN and ESRD Delivery 92...

Страница 7: ...nuary 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...

Страница 8: ...arfield Overview of E911 Coordination of Wireless Interconnection Network Specifications and Ordering N A April 3 2003 2a Overview of E911 Added GMLC Term Changed contact for Level One Escalation Intr...

Страница 9: ...e By All N A July 15 2002 1b Revisions to sections entitled Overview of E911 Coordination of Wireless Interconnection and Network Specifications and Ordering Rosemary Parker Mike Harfield Various N A...

Страница 10: ...Wireless E911 Guide CG EWCG 001 Introduction Revision History Issue 3 January 6 2004 Page 10...

Страница 11: ...fic PSAP rather than an antenna face An ESN is assigned to the pseudo ANI telephone numbers during database record processing and is assigned from the Master Street Address Guide MSAG based on the add...

Страница 12: ...1 area where the cell site is located 1 1 4 Premises Based ALI Systems Premises based ALI systems may have a separate database software and hardware located on the E911 Customer premises Wireless Carr...

Страница 13: ...pseudo ANI telephone numbers are processed from the wireless carriers the address information on the data record is validated against the MSAG Address information on the data records must exactly matc...

Страница 14: ...abase prior to testing or activating service If data records are not posted to the TN database the PSAP will receive a NO RECORD FOUND display when subscribers dial 911 which may delay getting them th...

Страница 15: ...less carrier to the cell face or PSAP Also known as Pseudo ANI and Emergency Service Routing Digits ESRD Note The pseudo ANI number MUST be assigned from the wireless carrier number pool and be geogra...

Страница 16: ...ver SS7 signaling Intrado A vendor designated by BST to handle E911 data maintenance formerly SCC LOC Location Master Street Address Guide MSAG All street data including street names address ranges an...

Страница 17: ...7 SS7 Common Channel Signaling 7 CCS7 An out of band signaling system used to provide basic routing information call set up and other call termination functions Signaling is removed from the voice ch...

Страница 18: ...ns MANAGER Mike Wallace extension 6270 1 888 584 3810 1 8 4 Level Three Escalation Bellsouth BellSouth Wireless E911 Implementation Manager 205 321 4785 If the problem has not been resolved by Intrado...

Страница 19: ...er two 2 digital data circuits with secondary channel to the BST Automatic Location Identification ALI computers These circuits are necessary to provide Phase 1 real time updates to the ALI database f...

Страница 20: ...and interfaces to the ALI computers Carriers must post valid records in the E911 database prior to testing or turning up service Additional information related to database requirements is found in thi...

Страница 21: ...w data circuits to the ALI computers if applicable The BST Wireless E911 Implementation Manager will issue a Teleprocessing Request form to Intrado and the BST IT Transport Group if new data circuits...

Страница 22: ...r will be required This notification may be sent via US Mail electronic mail or faxed to the address noted above 2 5 4 Information Required for Phase 2 MPC GMLC Circuits to the ALI Hosts The following...

Страница 23: ...uary 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 Mi...

Страница 24: ...Wireless E911 Guide CG EWCG 001 Issue 3 January 6 2004 Page 14 Blank...

Страница 25: ...SS7 connectivity will be used refer to Appendix A of this guide Note These trunks must use J STD 034 7 POI T8 MF Interface Signaling which can be designed with or without the optional pause for ackno...

Страница 26: ...er of the solution chosen by the Wireless Carrier Wireless Carriers must work with Intrado to ensure the chosen solution is compatible with the supported interfaces to the ALI Host computers Wireless...

Страница 27: ...e www interconnection bellsouth com guides html tech_ref html and may be amended from time to time TR 73610 BELLSOUTH E911 REAL TIME DATA INTERFACES FOR WIRELESS AND COMMERCIAL MOBILE RADIO SERVICE CM...

Страница 28: ...back number and the longitude latitude of the caller The delivery or lack of delivery of additional data elements which may be provided by the Wireless Carrier will not be the responsibility of BellSo...

Страница 29: ...1 serving area based on the ESN numbers available in the E911 tandem central office switch The ESN for wireless 911 calls are used to route the call to the proper PSAP Due to the geographical variatio...

Страница 30: ...the agreed upon PSAP For some solutions each antenna face should be assigned unique pseudo ANI pANI numbers by the Wireless Carrier to identify the specific cell site sector location In other solutio...

Страница 31: ...cessing 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 proce...

Страница 32: ...Wireless E911 Guide CG EWCG 001 Issue 3 January 6 2004 Page 22 Blank...

Страница 33: ...I or pANI numbers Some technological solutions require pANI numbers to be assigned to each antenna face while other solutions require pANI numbers to be assigned to each PSAP In either case the databa...

Страница 34: ...uld begin submitting TN database records also known as Service Order Interface Records SOIRs after the MSAG has been updated with cell site addresses and the NXXs have been added to the table The proc...

Страница 35: ...ocation or PSAP records must be updated into the TN database Each record affected must be sent individually with the appropriate changes For example if the address changes for a cell site which has 3...

Страница 36: ...I systems 15 Provide dynamic update interface to populate call back number and latitude longitude in ALI database 5 3 E911 Customer Responsibilities The on going maintenance responsibilities for the E...

Страница 37: ...ESS Enter the address to be used for correspondence on data issues CONTACT NAME Enter the name of the person responsible for data issues CONTACT PHONE NUMBER Enter the full telephone number of the per...

Страница 38: ...n 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 yo...

Страница 39: ...CG EWCG 001 Wireless E911 Guide Issue 3 January 6 2004 TN Database Updates 5 5 NXX Table Update Form Figure 1 NXX Table Update Form Page 29...

Страница 40: ...e Prefix Directional Street Name Street Suffix Thoroughfare Post Directional Community 100 399 N MAIN ST SW CHARLOTTE The address for the TN record being submitted via file transfer would need to be f...

Страница 41: ...iption T F Abbrev Description ALY ALLEY LN LANE ANX ANNEX LOOP LOOP ARC ARCADE MKT MKT AV AVENUE MNR MANOR BDWK BOARDWALK MT MOUNT BEND BEND MTN MOUNTAIN BLK BLOCK NK NECK BLVD BOULEVARD PASS PASS BR...

Страница 42: ...shown below When the name of a street is an alphabetic character the word Street is spelled in full Refer to the examples shown below Directional words North N South S East E West W North East NE Nor...

Страница 43: ...a records for the E911 database as described in this tab Data records are validated for proper format and to ensure the address information is defined in the MSAG database The TN data record includes...

Страница 44: ...1 All files contain a single file header record followed by one or more data records followed by a single file trailer record All records are 512 characters in length Layouts are described in this tab...

Страница 45: ...Calling Number Yes Yes CALLING NUMBER TN 5 11 7 N Seven 7 digit telephone number of the Calling Number For Wireless pseudo ANI of PSAPor antenna face receiving wireless call Yes Only eight 8 characte...

Страница 46: ...on and post directional Street Suffixes must conform to BellSouth MSAG standards valid Post Directional entries are N S E W NE NW SE SW EX MAIN ST NW Yes Only 18 characters sent to PSAP Yes Some solut...

Страница 47: ...Yes TYPE OF SERVICE 221 1 N Value of 0 Not Non Pub 3 Non Pub No Yes EXCHANGE 222 225 4 AN Phone company exchange identifier for the serving telephone office of the customer ALEC and Wireless may be bl...

Страница 48: ...COMPANY ID 261 265 5 AN Telephone Company Identification code as assigned through NENA registration process No Yes source identifier 266 1 AN Code which indicates whether data is part of the initial...

Страница 49: ...ation No No cell identifier 343 348 6 AN Reserved for future use Identification number indicating a geographic region of cellular coverage No No sector identifier 349 1 AN Reserved for future use Subs...

Страница 50: ...st file cycle is incremented by 1 until reaching 999999 county identifier 68 71 4 AN state 72 73 2 A general use 74 93 20 AN release number 94 96 3 N format version 97 1 N reserved 98 511 414 AN END O...

Страница 51: ...ST Wireless E911 Implementation Manager INTRADO Once established support for Connect MailboxTM will be handled by INTRADO Connect Mailbox Client for Windows requires the following minimum system requi...

Страница 52: ...4 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 Trai...

Страница 53: ...er is expected to resolve the errors by Issuing Address Verification Requests AVR to the E911 Coordinator for MSAG changes Issuing corrective SOIRs within 24 hours of receipt 6 2 Electronic Error Deli...

Страница 54: ...use Number The field should be spaced filled if no house number is available HOUSE NUMBER SUFFIX House number extension e g 2 The field should be spaced filled if no suffix applies PREFIX DIRECTIONAL...

Страница 55: ...2 Not used 3 Non pub not FX 4 Non pub FX 5 Not Used EXCHANGE Local Exchange Carrier exchange identifier for the serving telephone office of the customer MAIN NPA Three 3 digit area code of the Main Nu...

Страница 56: ...r coverage SECTOR ID Sub set section of a cell TAR CODE Taxing Area Rate Code RESERVED Positions 356 511 are reserved Positions 378 380 are used by Intrado to populate the three 3 digit error code e g...

Страница 57: ...on 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 i...

Страница 58: ...SOIR with an FOC E When the FOC E on the subsequent SOIR the error file will be searched for a match on TN and if found the error will be deleted from the error file SOIRs sent with a FOC of E are use...

Страница 59: ...found in MSAG 710 customer code doesn t match on change 711 Customer code or street name does not match on delete 712 Record does not exist for change 713 TN and Main Account mismatch 729 Change fail...

Страница 60: ...is sent in the customer code field of the incoming record Issue corrective SOIR for errored TN showing 999 in the customer code field 101 NPA NXX not valid The incoming record contains a NPA NXX combi...

Страница 61: ...ored TN 112 Street name has invalid characters The street name for the street on the incoming SOIR contains invalid characters Determine the correct MSAG valid street name and submit corrective SOIR f...

Страница 62: ...with the error determine if the existing database TN is incorrect or if the SOIR error is incorrect If the existing database TN is incorrect resubmit the SOIR with a FOC of C to overlay the existing d...

Страница 63: ...rect customer code and resubmit corrective SOIR with customer code of 999 or blanks 711 Customer code or street name does not match on delete The customer code directional prefix street name and suffi...

Страница 64: ...lict with disconnect file The incoming insert SOIR is for a TN that has been disconnected and the date on the insert SOIR is the same or prior to the date of the disconnected TN Determine if the inser...

Страница 65: ...for resolution 739 Invalid house number format The incoming SOIR contain special or invalid characters for an alpha or alphanumeric house number Determine correct house number for TN and resubmit corr...

Страница 66: ...ord will process once the unlock SOIR is received If the error record TN is invalid resubmit a E FOC SOIR to delete the error record 756 Company code mismatch on change The NENA ID on the incoming C F...

Страница 67: ...ification of action taken for the TN on the weekly NPAC Validation report 762 NENA ID required for U or M FOC SOIR The incoming U or M SOIR does not have a valid three 3 to five 5 digit NENA ID Submit...

Страница 68: ...lling number TN as the main account 792 I FOC record exists with a different Company ID The TN shown on the I FOC SOIR has a different NENA Company ID than the existing TN in the database Verify the T...

Страница 69: ...ceive E911 Inquiry Forms from the E911 Customer county or INTRADO Inquiry forms should be logged by the Carrier A PSAP Inquiry Log form and instructions are provided in this tab Once the inquiry has b...

Страница 70: ...Wireless E911 Guide CG EWCG 001 PSAP Inquiries Issue 3 January 6 2004 7 2 PSAP Inquiry Form Figure 3 PSAP Inquiry Form Page 60...

Страница 71: ...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 Nu...

Страница 72: ...check to see if the TN is a valid pseudo ANI number If valid a SOIR should be sent to insert the pseudo ANI TN record If it is determined that the TN record is in the error file a corrective SOIR shou...

Страница 73: ...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 Custome...

Страница 74: ...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...

Страница 75: ...ducting 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 INT...

Страница 76: ...nd time of NRF report creation State Two 2 character state identifier TN Pseudo ANI number including NPA which resulted in NRF Bid Date Date time and day of week of PSAP query bid that resulted in NRF...

Страница 77: ...E911 database is updated The Analyst will assign REF LEC when the investigation cannot be completed in the time frame which the Analyst began their work This status would be typical when additional i...

Страница 78: ...Wireless E911 Guide CG EWCG 001 Issue 3 January 6 2004 Page 68 Blank...

Страница 79: ...1 1 service will allow the PSAP to identify the Wireless Carrier serving the caller and to determine the 24 x 7 number of that Carrier for emergency contact needs In the Company ID database descripti...

Страница 80: ...is usually possible The Company s choice for an Identifier is likely to be accepted by NENA provided that it is not already registered by another Company 9 4 Instructions The chosen Company ID code s...

Страница 81: ...CG EWCG 001 Wireless E911 Guide Issue 3 January 6 2004 NENA Company Registration Process Figure 6 Input Form Page 71...

Страница 82: ...Wireless E911 Guide CG EWCG 001 Issue 3 January 6 2004 Page 72 Blank...

Страница 83: ...iation 10 2 Notification and Scheduling Complete the 9 1 1 Database Reconciliation Extract Request form that was attached to the annual letter and return it to the INTRADO Continuous Improvement Analy...

Страница 84: ...Wireless E911 Guide CG EWCG 001 Issue 3 January 6 2004 Page 74 Blank...

Страница 85: ...TR 73554 is a supplement to GR 905 TR 73554 is available through the appropriate BellSouth Interconnection Services Account Representative Before any new device is connected to the BellSouth Common Ch...

Страница 86: ...eir BellSouth Account Representative to begin a test and installation plan or to discuss technical information This document identifies only SS7 signaling options supported for E9 1 1 trunk interconne...

Страница 87: ...ding to J STD 036 A it is known as Non Callpath Associated Signaling NCAS A 2 1 3 Call Scenario 2 CBN and ESRD Delivery WITH a hybrid WITH a hybrid architecture at the Selective Router BellSouth suppo...

Страница 88: ...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 Failure to deploy SS7 ISUP...

Страница 89: ...hey chose to deploy their own architecture in a manner that accommodates delivery of longitude and latitude coordinates to a PSAP through the BellSouth ALI database once they are obtained over an E2 i...

Страница 90: ...ommunications Industry Association and the Alliance for Telecommunications Industry Solutions June 2002 This joint standard defines the messaging required to support information transfer to identify a...

Страница 91: ...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 Since CAMA MF only delivers a 7 digit...

Страница 92: ...However in Phase 2 NCAS as defined in J STD 036 A Annex D Section D 1 2 includes BOTH the CBN and the pANI being sent directly from the WSPs MSC through the BellSouth E9 1 1 Tandem to the PSAP In thi...

Страница 93: ...he NDET Generic Digits GDP Parameter IS NOT ALLOWED Depending on which signaling option is chosen the WSP will send an Initial Address Message IAM containing the following parameters when sending a wi...

Страница 94: ...004 WS Once a trunk group is provisioned the wireless carrier shall adhere to their choice i e a trunk cannot signal the digits 911 for one call and a pANI for another call Called Party Number is a re...

Страница 95: ...6 Originating Line Information Parameter For call scenarios 2 and 3 with or without a hybrid architecture at the Selective Router the Originating Line Information parameter shall be coded either as 00...

Страница 96: ...NI is sent into the BellSouth NDET directly from the WSPs MSC over dedicated trunks The pANI is used by the NDET for selective routing and then the pANI is sent to the PSAP the same way ANI would be o...

Страница 97: ...AM 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 sign...

Страница 98: ...indicate Location Identification Number 3 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 P...

Страница 99: ...n 4Q2003 or 1Q2004 When using this interconnection method the NCAS Solution provider might still create a record in the BellSouth the ALI database containing the pANI or the CBN among other data norma...

Страница 100: ...llSouth the MSC MUST use dedicated trunks to the Emergency Services Network Entity ESNE to route the Emergency Services Call ESC 2 The Generic Digits Parameter IS NOT ALLOWED TO BE SENT IN THE IAM WHE...

Страница 101: ...may be used on dedicated trunks that do not support the ISUP Generic Digits parameter 2 The Type of Digits field within the Generic Digits Parameter IF USED should be set to indicate Location Identif...

Страница 102: ...911_STD WCM 1 2 B3 No Yes 911 Blank ESRK Blank E911_STD WCM 1 2 NOTES 1 This ISUP parameter option is widely supported in the U S It is estimated that 95 of the E911 selective routers deployed in the...

Страница 103: ...D WRLS_STD 3 C3 No Yes 911 Blank CBN ESRD E911_STD 3 D1 No No 911 CBN CBN ESRD WRLS_STD 3 D2 No No 911 CBN Blank ESRD WRLS_STD 3 D3 No No 911 Blnk CBN ESRD E911_STD 3 E1 Yes Yes ESRD CBN CBN Blank WRL...

Страница 104: ...1 1 ISUP Enhancements implemented setting the CPC parameter in the outgoing IAM of ISUP E9 1 1 calls to Emergency Service Call which is a value of E0 This was to fulfill Telcordia standards Even thoug...

Страница 105: ...reless call NENA recognized this conflict and established a committee that included members from the wireless carriers service providers and public safety community They created the NENA 05 501 Techni...

Страница 106: ...ment C Wireless Customer Checklist Wireless Customer Checklist in no particular order Does the MSC have SS7 signaling link connectivity to support trunking to the appropriate NDET Do we know what call...

Страница 107: ...CG EWCG 001 Wireless E911 Guide Issue 3 January 6 2004 BellSouth Wireless E9 1 1 SS7 Interconnection Guide KEYWORDS Wireless Carrier BST Wireless E911 Page 97...

Результаты поиска

Содержание E911

Отзывы:

Похожие инструкции для E911

Бренды по названию

Популярные бренды

BellSouth E911, Руководство пользователя

Результаты поиска

Содержание E911

Отзывы:

Похожие инструкции для E911

Бренды по названию

Популярные бренды