Avaya BCM 4.0 Networking Konfigurationsanleitung PDF herunterladen (Seite 293)

100

101

Chapter 25 Dialing plan: Routing configurations 293

BCM 4.0 Networking Configuration Guide

5 Set Absorbed Length to 1.

The digit 9 is only used internally and should be dropped. The 1 is needed to direct the call to

the public carrier network.

Using the MCDN access codes to tandem calls

Three special access codes exist specifically for programming calls over PRI and VoIP trunks that

are using the MCDN protocol, and which connect to a call servers that use specific call codes for

special call types, such as the Meridian 1 (M1). The purpose of the codes is to allow easier

programming of the call servers when calls are tandemed through a BCM system to the local

PSTN. Refer to “Private Network Settings” on page 324 for a description of these fields in context

with the private dialing plan.

This is how the codes relate:

Calls tandeming to the public network through the private network need to retain their dialing

protocol throughout network. This means that a call from an M1 node tagged as a local call gets

received by the local node and is recognized as a call intended for the public network, but also as a

call that needs to maintain the local tag until it gets to the local node that is directly connected to

the PSTN. This is accomplished by ensuring that the destination code, which starts with this access

code, passes the call on using the route designated with the correct DN type. Refer to “Setting up a

route through a dedicated trunk” on page 286.

Calls coming in from the public network need to be translated to their private network destination

before routing/tandeming through the private network. In this case, the route used is defined with

the DN type of Private.

Figure 96 charts the process for a call tandeming through a BCM to the local public network.

Tips: The destination codes 9 and 91 used in the examples cannot be

used together. If you need the destination code 91 to direct long distance

calls, you must create a separate set of codes that use local calling routes.

These codes would be, for example, 90, 92, 93, 94, 95, 96, 97, 98 and 99.

Refer to “Grouping destination codes using a wild card” on page 287 for

information on programming destination codes.

Meridian 1 access codes BCM access codes Sample code

Network/long distance code Private access code 6

National access code 61

Local code Local access code 9

Special access code 9

1 2 ... 288 289 290 291 292 293 294 295 296 297 298 ... 757 758

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya BCM 4.0 Networking Konfigurationsanleitung Seite 293

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Vernetzung Avaya BCM 4.0 Networking