Avaya BCM50 Konfigurationsanleitung PDF herunterladen (Seite 43)

Chapter 2 System telephony networking overview 43

Networking Configuration Guide

• “Understanding Nortel Voice Networking (MCDN) network features” on page 46

• “Networking with ETSI QSIG” on page 50

• “Private networking with DPNSS” on page 60

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 of 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 lengths.

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 system 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.

VoIP note: You can also use VoIP trunks between some or all of the nodes. The setup is the same,

except that you need to create gateway records for each end of the trunk, and routing tables to

accommodate the gateway codes, or you can configure a gatekeeper. Refer to “VoIP

interoperability: Gatekeeper configuration” on page 389.

Note: A keycode is required to use the Nortel Voice Networking functionality

which is referred to as SL-1 in the BCM Element Manager.

1 2 ... 38 39 40 41 42 43 44 45 46 47 48 ... 567 568

Keine Kommentare

Avaya BCM50 Konfigurationsanleitung Seite 43