Avaya BCM 4.0 Networking Guide de configuration télécharger pdf (Page 50)

100

101

50 Chapter 2 System telephony networking overview

N0060606N0060606

If the MCDN protocol is added to this type of private network, the network provides additional

network management features, as well as allowing centralized voice mail features to be available

to all nodes on the network.

The following sections describe the different aspects of SL-1 and MCDN private networking.

• “System dialing plans”

• “Creating tandem private networks”

• “Understanding MCDN network features” on page 53

• “Networking with ETSI QSIG” on page 56

• “Private networking with DPNSS” on page 65

The type of network you require depends on the equipment in the network, and how you want to

use the network.

• With MCDN, you can tie a set of BCM systems together with PRI SL-1(MCDN)/ETSI-QSIG,

DPNSS or VoIP trunks to create a tandem network. This type of network provides the

additional advantage of providing private line access to local PSTNs for all the nodes on the

network.

System dialing plans

Both these types of networks require similar setups for dialing plans and routing. Each node must

have a way to route external calls to the adjacent node or nodes. To do this, all nodes must have the

same Private DN length.

You use routing and a private dialing plan to control calls over the network. Each example in this

section describes the routing configurations that are required to support calls over the network.

Depending on the type of dialing plan you choose, each node must also have a unique location or

steering code so the calls can be correctly routed through the nodes of the network. MCDN

networks also require a Private Network ID, which is supplied by the Meridian network

administrator to define how the Meridian system identifies each node.

Creating tandem private networks

You can tie a number of BCM systems together with SL-1 lines. This tandem network provides

you with the benefits of end-to-end name display and toll-free calling over the SL-1 private link.

Each BCM becomes a node in the network. In this type of network, you must ensure that each

BCM system, known as a node of the network, is set up to route calls internally as well as to other

nodes on the system. This means each node must have a route to the immediately adjacent node,

and the correct codes to distribute the called numbers. Each node must have a unique identification

number, which is determined by the type of dialing plan chosen for the network.

As well, you can save costs by having a public network connection to only one or two nodes, and

routing external calls from other nodes out through the local PSTN, thus avoiding toll charges for

single calls.

Note: A keycode is required to use SL-1(MCDN).

1 2 ... 45 46 47 48 49 50 51 52 53 54 55 ... 757 758

Commentaires sur ces manuels

Pas de commentaire

Avaya BCM 4.0 Networking Guide de configuration Page 50

Commentaires sur ces manuels

Produits connexes et manuels pour Mise en réseau Avaya BCM 4.0 Networking