
Appendix A: Network Examples 351
P0911588 Issue 01 Enterprise Edge 2.0 Programming Operations Guide
In this example, outgoing public network calls dialed from an Enterprise Edge set
are passed to the Meridian M1, and the Meridian M1 is responsible for seizing a
public trunk. For this reason, the “9” prefix is left in the number passed to the
Meridian 1.
Note: Ensure that Line Pool A is used for IP trunks.
Guidelines to setting up Meridian M1 in this example
In order for the digit counting algorithm for outgoing IP calls to take into account
this extra digit, the Private Network Access Code must be set to “9” on each
Enterprise Edge system.
The Meridian M1 must recognize 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 recognize numbers starting with “9” as public numbers,
whether the numbers are dialed by Meridian M1 users or by Enterprise Edge users.
Toll bypass with Enterprise Edge VoIP Gateway
This example shows a private network composed of one Enterprise Edge system in
Toronto and one Enterprise Edge system in Ottawa, connected over IP trunks
through a corporate IP network.
In this network, each Enterprise Edge system has a PRI trunk to the Central Office,
and IP trunks to the other Enterprise Edge system. Calls from the Toronto system
to the Ottawa system and the Ottawa public network are made over IP trunks with
fallback to the PRI trunks when IP trunks are congested. This configuration allows
for cost savings by using the corporate IP network whenever possible, thereby
bypassing toll charges that would be incurred by using the public network.
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
Commenti su questo manuale