Avaya BCM 4.0 Networking Guia de Configuração descarregar pdf (Página 268)

100

101

268 Chapter 24 Dialing plans

N0060606N0060606

Tips about access codes

Use the following tips to assist you in planning the access codes for your system.

• External line access code: If the DN length is changed, and the changed DNs conflict with the

external line access code, the setting changes to None.

• Direct dial telephone: Another direct dial telephone, an extra dial telephone, can be assigned

for each schedule in Services programming.

If the DN length is changed, and the changed DNs conflict with the Direct dial digit, the

setting changes to None.

• Public/Private Auto DN: The length of the Auto DNs are the same as the Public or Private

Received Number Lengths specified under Configuration > Telephony > Dialing Plan. The

public/private Auto DN is cleared if the corresponding Received Number Length is changed.

• Public/Private DISA DN: The length of the DISA DNs are the same as the Public or Private

Received number length specified under Configuration > Telephony > Dialing Plan. The

public/private DISA DN is cleared if the corresponding Received number length is changed.

Using the MCDN access codes (tandem calls)

Three special codes exist specifically for programming over PRI and VoIP trunks that are using

the MCDN protocol, and which connect to a call server systems 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 server systems when calls are tandemed through a BCM to the local

PSTN.

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

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

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

also as a call that needs to maintain the local call tag until it gets to the BCM 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 call type.

Figure 86 charts this process.

Note: The following codes/digits must not conflict:

•park prefix

• external code

• direct dial digit

• private access code

• Public/Private Auto DN

• Public/Private DISA DN

• line pool code/destination code

• telephone DN

1 2 ... 263 264 265 266 267 268 269 270 271 272 273 ... 757 758

Comentários a estes Manuais

Sem comentários

Avaya BCM 4.0 Networking Guia de Configuração Página 268

Comentários a estes Manuais

Manuais e produtos relacionados com Redes Avaya BCM 4.0 Networking