Skip to content
ATIS Best Practices

Search

1098 matching practices

NumberBest Practice
13-9-0568Network Operators, Service Providers, and Public Safety should establish a routing plan so that in the case of lost connectivity or disaster impact affecting a Public Safety Answering Point (PSAP), 9-1-1 calls are routed to an alternate PSAP answering point.
13-9-0569Network Operators, Service Providers, and Public Safety should consider using the Public Switch Telephone Network (PSTN) as a backup to dedicated trunks for the 9-1-1 network during periods of network failure. In cases where the ability to deliver 9-1-1 calls to the Public Safety Answering Point (PSAP) through normal routing is interrupted by a failure (not all trunks busy conditions) consider forwarding the call over the PSTN to a telephone number specified and answered by Public Safety authorities. It is desirable for that specified telephone number to be a type that can provide the original Caller ID/Automatic Number Identification (ANI).
13-9-0570Network Operators, Service Providers, and Public Safety should implement procedures that allow for 9-1-1 traffic to be rerouted to an alternate 9-1-1 answering location such as a fixed, mobile, or temporary PSAP (automatically, based on policy rules or with minimal manual intervention). For example situations where a network condition causes 9-1-1 call delivery to be disrupted or PSAP personnel must be evacuated for safety reasons.
13-9-0571Network Operators and Public Safety should consider deploying dual active 9-1-1 selective routing architectures to enable circuits from the serving end office to be split between two selective routers or Emergency Service Routing Proxies (ESRP) in order to eliminate single points of failure (SPOF) taking diversity between Selective Routers (SR) or ESRP and PSAP into consideration.
13-9-0574Network Operators, Service Providers, and Public Safety should actively monitor and manage the 9-1-1 network components using network management controls, where available, to quickly restore 9-1-1 service and provide priority repair during network failure events. When multiple interconnecting providers and vendors are involved, they will need to cooperate to provide end-to-end analysis of complex call-handling problems.
13-9-0575Network Operators, Service Providers, and Public Safety should deploy location identification systems used by Public Safety in a redundant, geographically diverse manner (i.e., two identical ALI/Mobile Positioning Center (MPC) Gateway Mobile Location Center (GMLC)/VPC/LIS database systems with mirrored data located in geographically diverse locations).
13-9-0576Network Operators and Service Providers should minimize impact from pre-planned high volume call events by invoking network management and congestion controls for affected end offices to maximize 9-1-1 call throughput.
13-9-0577Network Operators, Service Providers and Public Safety should jointly and periodically test and verify that critical components (e.g., automatic re-routes, PSAP Make Busy keys) included in contingency plans work as designed if they are responsible for Public Safety Answering Point (PSAP) operations.
13-9-0578Network Operators, Service Providers, and Public Safety should actively engage in public education efforts aimed at informing the public of the capabilities and proper use of 9-1-1.
13-9-0579Network Operators, Service Providers, and Public Safety should routinely team to develop, implement, test, evaluate and update, as needed, plans for managing 9-1-1 disruptions (e.g., share information about network and system security and reliability where appropriate).
13-9-0580Network Operators and Public Safety should apply redundancy and diversity where feasible, to all network links considered vital to a community's ability to respond to emergencies.
13-9-0581Network Operators and Service Providers should include Automatic Location Identification (ALI) data for both traditional and alternate providers (e.g., Private Switch, Competitive Local Exchange Carrier (CLEC), Voice over Internet Protocol (VoIP)) in the ALI systems, where required.
13-9-0599Network Operators, Service Providers, and Public Safety should conduct exercises periodically to test a network's operational readiness for various types of events (e.g., hurricane, flood, nuclear, biological, and chemical), through planned, simulated exercises being as authentic as practical including scripts prepared in advance with team members playing their roles as realistically as possible.
13-9-0603Network Operators, Service Providers, and Public Safety should establish policies and procedures that outline how critical network element databases will be backed up onto a storage medium (e.g., tapes, optical diskettes) on a scheduled basis.
13-9-0619Network Operators, Service Providers, Property Managers, and Public Safety should coordinate with fire agencies in emergency response preplanning efforts for communications equipment locations.
13-9-0622Network Operators, Service Providers, Property Managers, and Public Safety should use approved industry standards for Telecommunications Environmental Protection, DC Power Systems for key equipment locations (e.g., routers, central office switches, and other critical network elements) to reduce fires associated with DC power equipment.
13-9-0635Network Operators, Service Providers, Property Managers, and Public Safety should ensure that AC surge protection is provided at the power service entrance to minimize the effects caused by lightning or extremely high voltages.
13-9-0644Network Operators, Service Providers, Property Managers, and Public Safety should use over-current protection devices and fusing.
13-9-0655Network Operators, Service Providers, Property Managers, and Public Safety should coordinate hurricane and other disaster restoration work with electrical and other utilities as appropriate.
13-9-0657Network Operators, Service Providers, Property Managers, and Public Safety should design standby generator systems for fully automatic operation and for ease of manual operation, when required.

Download matching Best Practices

Next results