Clid Verification (Clidver); Networked M911 - Avaya 1000 Installation And Commissioning Manual

Access to Emergency Service using SPN should be configured in the following circumstances:
• When the Emergency Service number at the Branch Office is different from that at the main
office.
• When there is more than one number used for accessing Emergency Service; for example,
when there are different numbers for Police, Fire, and Ambulance services.
• In markets where the ESA feature is not available (outside of North America and CALA).
If MG 1000B PSTN access is correctly configured, Emergency Service from the Branch Office will
already be present.
Branch Office access to Emergency Service using SPN must be configured and tested on each call
processor (the main office Call Server and the MG 1000B Call Server) to differentiate between
emergency calls originating from IP Phones at each location and emergency calls originating on
trunks.

CLID verification (CLIDVER)

Use the CLIDVER prompt in LD 20 to verify that the ESA or non-ESA (SPN) emergency number is
properly composed and configured. Refer to

Networked M911

The Networked M911 feature provides a trunk subtype 911P exclusively for 911 calls redirected
over an MCDN Network. The prompt 911P is provided in the Route Data Block for TIE trunks only.
This prompt, if set to YES, signifies that the trunks associated with these routes are 911P trunks. All
incoming 911 calls to the tandem M1 are redirected to the target M1 over 911P trunks. At the target
node, these calls will be treated in respect the same as incoming calls on 911E/ 911T trunks.
A trunk subtype is provided in the Route Data Block exclusively for TIE trunks. All the prompts
specific to 911 are prompted in the RDB if the TKTP prompt value is TIE. In case of TIE trunks, the
M911_TRK_TYPE prompt does not appear and is replaced by the prompt 911P. The M911_ANI,
M911_NPID_FORM and NPID_TBL_NUM are not prompted in the RDB. If the 911P prompt is set to
YES, IFC prompt is set to SL1 by default since 911P trunks are supported only over MCDN.
June 2014
Verify CLID on page 201 for more information.
Branch Office Installation and Commissioning
Comments? infodev@avaya.com
CLID verification (CLIDVER)
191