Orange County NC Website
Browse       Search
Orange County, NC <br /> <br />On-Premise OnCall Dispatch Implementation <br />Statement of Work 100 <br />Attachment H – Interface Descriptions <br />COTS Interfaces <br />ANI/ALI Interface <br />The ANI/ALI interface works with the Call-taker component of OnCall Dispatch Advantage to provide Next <br />Generation support for solicited multimedia data associated with a call. Call-Taker is designed to support <br />new modes of communication, such as SMS and MMS text (photos and video) and allows the addition of <br />new call types going forward. It provides global support for handling Next Generation data processed by <br />the PSAP. <br />OnCall Dispatch supports FCC Phase II requirements for cellular 911 calls and supports the creation of <br />events based on a geographic coordinate location. The ANI/ALI packets for Phase II Wireless 911 calls <br />include the coordinates (in lat/long or other standard coordinate system, as dictated by the NENA <br />standard or FCC requirements), and uses this information to show the caller's geographic coordinate <br />location on the map. The nearest civic address can also be estimated and displayed. The exact format of <br />this data in the ANI/ALI packet must be supplied by the Customer (in conjunction with their phone system <br />supplier). <br />Assumptions: <br /> Hexagon assumes that the Customer's ANI/ALI controller supports NENA Format Versions 1 and <br />2 (Fixed Length ASCII), NENA version 3 (Tagged Delimited), and NENA version 4 (XML). These <br />formats are documented in NENA documents NENA 02—010 v9 now “Legacy Data formats for <br />ALI, MSAG &GIS” and NENA 04-001 v2 now “E9-1-1 PSAP Equipment”. <br /> The ANI/ALI interface component of the OnCall Dispatch System will provide the interface to an <br />ANI/ALI controller, and will accept ANI/ALI packets containing ASCII, tagged delimited, or XML <br />data via an Ethernet Network (TCP/IP) or an RS-232 connection <br /> Hexagon assumes that the ANI/ALI protocol packet provides the number, address and answering <br />position of the call when answered. <br /> The FCC order released June 3, 2005 requires that all VoIP vendors, serving U.S. customers, <br />must offer service to route 911 VoIP calls through the current E-911 infrastructure. This means <br />that all VoIP 911 calls from registered subscribers will be received through the PSAP’s 911 trunks <br />and handled by their ANI/ALI Controller. The PSAP is responsible for ensuring that their ANI/ALI <br />Controller is capable of handling the ALI Database lookup for these calls. ANI/ALI packets for <br />VoIP calls will be received by the CAD system, over the same CAD link, from the ANI/ALI <br />Controller, as the landline and cellular calls. VoIP calls with a caller’s address will be handled like <br />landline calls and VoIP calls with a location specified by coordinates will be handled like Phase II <br />cellular calls. <br /> If the center requires an interface to a method of receiving ANI/ALI or other Data for VoIP calls <br />other than the traditional ANI/ALI Controller, this interface will have to be rescoped as a custom <br />interface. The Customer must provide complete specifications of the device or service providing <br />the data. <br /> Given the current uncertainty in the telephony provider market on how SMS/MMS information will <br />be transmitted, Hexagon assumes that the SMS/MMS information is being provided through the <br />external SMS provider. <br />Docusign Envelope ID: 463E937D-8F02-4D22-9EEA-B2B50627D9E0Docusign Envelope ID: DE681D27-7D55-4FB6-8C51-9394D26FBC9E