Avaya BCM 4.0 Networking Konfigurationsanleitung PDF herunterladen (Seite 258)

100

101

258 Chapter 24 Dialing plans

N0060606N0060606

• You can define up to 30 entries.

• Each entry consists of a DN prefix string (1 to 10 digits) and a length value (two digits,

1to25).

• Several entries are predefined in the North America profile. These defaults can handle most

regions in North America without the need for additional programming. If required, you can

remove or modify these entries.

• The table always contains one default entry. You cannot remove this entry. You can only

modify the length parameter associated with this entry. The default entry specifies the length

of any dialing string that does not match one of the other table entries.

Outgoing call routing

Outgoing calls require line pool access codes or destination code (with defined routes) to leave the

system.

• Access codes provide direct, unscheduled access to an analog, digital (T1).

• Destination codes also provide access to line pools, but they also allow more flexibility in

dialing, which allows for more complex routing options, such as scheduling, fallback routing

(VoIP trunks), call definition, and multiple routing (least-cost routing). Routing also allows

you to minimize the dialout for the user, especially to systems on the same private network.

Outgoing calls can be either public or private, which is defined by the route. The public or private

designation determines which dialing plan is used to determine the validity of the call. Normally,

public calls are routed over PSTN trunks and private calls are routed over a private network.

However, MCDN trunks can also pass calls designated as public to allow remote nodes on the

network to call out of the PSTN of a local node. This is called tandem dialing.

• If the outgoing call is designated as private, the system checks the beginning of the string for a

destination code that routes to a private network. It also checks that the dial string is the correct

length. The destination code routing determines what the final dial string will be, adding or

removing digits, as required.

• If the outgoing call is designated as public, the system checks the beginning of the string for a

destination code that routes to a PSTN or an MCDN trunk. If the call routes to a public route,

the system checks the public dialing table to ensure that the dialout string has legitimate

leading digits and is the correct length. If the call routes to an MCDN trunk, the call is passed

as dialed, minus the private networking codes. The call will pass through the system until the

system with the matching destination code receives it, at which point it will be sent through the

local PSTN of that system.

How the system identifies the call depends on the type of trunk chosen for the route. Refer to the

table below.

Dialing plan setting NPI/TON Private called number length based on

MCDN trunks send private calls in this way:

None Private/Subscriber Private DN length (set on Private Network panel)

1 2 ... 253 254 255 256 257 258 259 260 261 262 263 ... 757 758

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya BCM 4.0 Networking Konfigurationsanleitung Seite 258

Kommentare zu diesen Handbüchern

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