Avaya BCM 2.0 IP Telephony Manual de usuario descargar pdf (Pagina 46)

46 Engineering guidelines

Enterprise Edge 2.0 IP Telephony Configuration Guide P0911590 Issue 02

In this example, outgoing public network calls dialed from a Enterprise Edge route

to the Meridian M1, and the Meridian M1 is responsible for seizing a public trunk.

For this reason, the ‘9’ prefix remains in the number passed to the Meridian 1.

Note: For IP trunks, ensure the programming selection is Line Pool A.

Set the Private Network Access Code to ‘9’ on each Enterprise Edge system to

ensure the algorithm for outgoing IP calls include this additional digit.

The Meridian M1 must identify incoming 2xxx and 6xxx DID calls, and route the

call over IP trunks to either the East or West end offices.

The Meridian M1 must identify numbers starting with ‘9’ as public numbers, when

the numbers are dialed by Meridian M1 users or by Enterprise Edge Solution users.

Enterprise Edge and a Gatekeeper

Enterprise Edge supports the use of an ITU-H.323 gatekeeper. A gatekeeper is a

third party software installed on a server to centralize IP address configuration

information. Each port on the network receives an aliasname. Instead of having

remote gateway tables on each Enterprise Edge system, the gatekeeper contains the

remote gateway table. The aliasname is linked to an IP address by the gatekeeper.

If an IP address changes, only the gatekeeper need updating as the aliasname

remains the same.

Service/Routing Service Route 001

Use Pool A

External # (leave blank)

DN type Private

Destination Code 4

Normal route 001

Absorb None

To West End:

Service/Routing Service Destination Code 2

Normal route 001

Absorb None

To Public Network:

Service/Routing Service Route 002

Use Pool A

External # (leave blank)

DN type Public

Destination Code 9

Normal route 002

Absorb None

Heading Parameter Setting

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

Sin comentarios

Avaya BCM 2.0 IP Telephony Manual de usuario Pagina 46