Instruction manual

Page 2044 of 3156 Meridian 911
553-3001-306 Standard 10.00 January 2002
Once the call is abandoned, the trunk is released for other 911 calls.
Information on abandoned calls can be included in Call Detail Recording
(CDR) records if New Format CDR (FCDR) package 234 is equipped.
Operating parameters
Meridian 911
Meridian 911 routes are restricted to incoming traffic only.
Incoming M911 trunks use MF signaling only. Dial Pulse (DP) and Dual-tone
Multifrequency (DTMF) are not supported for M911 routes.
911 Calls on Integrated Services Digital Network (ISDN) trunks are not
supported.
A call is considered a 911 call by X11 software if it arrived on a trunk
belonging to an M911 route. Calls dialing 911 internally can, through
configuration of the Electronic Switched Network (ESN) digit manipulation
tables, be terminated locally (for example, to a Controlled DN), but these calls
are internal calls to the software, not 911 calls.
ANI is expected for every call. Meridian 911 does not support 911 calls from
an E911 Tandem which does not support sending ANI.
The priority of incoming trunk calls internally transferred to an Automatic
Call Distribution (ACD) DN queue (a secondary answering center) may be
preserved via blind transfer only. All other types of call modification (for
example, consultation transfer, or conference) are treated as internal calls and
the calls are linked to the low priority queue of the ACD DN.
The No Hold Conference feature, the recommended feature for transferring
calls between answering positions, is not available on analog (500/2500 type)
telephones.
The Call Prioritization (911 calls presented with higher priority) and Call
Waiting Notification features are applicable to ACD answering centers only.
These cannot be supported on Multiple Appearance Directory Number
(MADN) answering centers.
The first answering center must be an ACD DN.