Configuring Spn For Emergency Services; Mg 1000B Core Interoperability; Network Wide Redundancy Phase Ii And Network Music - Avaya 1000 Installation And Commissioning Manual

Branch office
Hide thumbs Also See for 1000:
Table of Contents

Advertisement

Configuring SPN for emergency services

Using an SPN for access to emergency services uses the digit manipulation capabilities configured
for the MG 1000B zone as follows:
• If the Branch User is in Normal Mode, the user dials the Access Code for the local PSTN and
the normal DN for emergency services.
If the main office and Branch Office use the same DN for accessing emergency services, a
conflict occurs in the NRS. The conflict is resolved by using the Zone Dialing Plan (ZDP)
configured in the Branch Office. The digits specified by the ZDP are prefixed to the dialed
digits, and the call is then sent to the NRS as an SPN. In the NRS, the SPNs have their own
separate numbering plan. The call is routed to the MG 1000B Call Server so that it can be sent
out to the MG 1000B PSTN.
• If the Branch User is in Local Mode (or an analog [500/2500-type] or digital telephone at the
MG 1000B), the user dials the Access Code for the local PSTN and the normal DN for
emergency services access. This selects the appropriate trunk for local PSTN access.

MG 1000B Core interoperability

MG 1000B Core to MG 1000B Core interoperability is fully supported between Communication
Server 1000 and Multimedia Communication Server 5100 (MCS 5100). A Network Connection
Server (NCS) is required for Branch Office, Virtual Office, and Geographic Redundancy features to
work.
Alternatively, Virtual Trunks can utilize the MCS 5100 H.323 Gatekeeper. In this case, at least one
dedicated Signaling Server is required to run as the primary Communication Server 1000 NCS,
where the H.323 endpoints are configured as non-RAS endpoints because Virtual Trunks will
establish a connection with MCS, not NCS. During endpoint configuration on that NCS, set the NCS
option to On; otherwise, all incoming requests from this endpoint are rejected. Set the Route cost to
1. Only those routes with the cost factor 1 are used for set redirections. However, the private
numbering plan must be configured on both the MCS 5100 H.323 Gatekeeper and the NCS
(Communication Server 1000 H.323 Gatekeeper). Without proper NCS server configuration,
redirection to the main office does not work. For further information on configuring the Branch Office
in the MCS database, refer to MCS documentation.

Network Wide Redundancy Phase II and Network Music

The Network Wide Redundancy Phase II feature interacts with the Branch Office feature. If you
configure a Branch Office as an endpoint in the NRS, and an IP set in a node in an IP Network has
June 2014
Branch Office Installation and Commissioning
Comments? infodev@avaya.com
MG 1000B Core interoperability
71

Advertisement

Table of Contents
loading

Table of Contents