Avaya BCM 2.0 IP Telephony Bedienungsanleitung PDF herunterladen (Seite 47)

Engineering guidelines 47

P0911590 Issue 02 Enterprise Edge 2.0 IP Telephony Configuration Guide

See the gatekeeper’s software documentation for information about changing IP

addresses.

Figure 7 Enterprise Edge systems with a gatekeeper

A user in Tokyo at DN300 dials DN400. The least cost routing is over the internet.

The Tokyo Meridian M1 connects to the destination IP address in its remote

gateway table for DN4xx. That address is the gatekeeper. The gatekeeper identifies

DN4xx as a Santa Clara DN. The gatekeeper performs address resolution from the

Santa Clara aliasname to the IP address 10.10.10.11. The call connects to the Santa

Clara Enterprise Edge, routed to DN400.

Toll bypass with VoIP telephony

This example shows a private network with one Enterprise Edge system in Toronto

and one system in Ottawa, connected over IP trunks through a corporate IP network.

Each system has a PRI trunk to the Central Office, and IP trunks to the other system.

Calls arrive from Toronto to the Ottawa and the Ottawa public network over IP

trunks with fallback to the PRI trunks when IP trunks are overflowed. This

configuration allows for reduced costs, using the corporate IP network when

possible, bypassing toll charges and other charges when using the public network.

Note: When a call gets rerouted over the PSTN as a result of congestion, the user

can see a prompt "Expensive route." The warning indicates that toll charges

can apply to this call.

Enterprise Edge

Santa Clara DN 4xx

IP: 10.10.10.11

Enterprise Edge

Ottawa DN 5xx

IP: 10.10.10.12

Enterprise Edge

Raleigh DN 6xx

IP: 10.10.10.13

Meridian M1

Tokyo DN 3xx

IP: 10.10.10.18

Gatekeeper

IP: 10.10.10.10

Intranet

Gatekeeper

WAN

1 2 ... 42 43 44 45 46 47 48 49 50 51 52 ... 75 76

Keine Kommentare

Avaya BCM 2.0 IP Telephony Bedienungsanleitung Seite 47