
Appendix A: Network Examples 345
P0911588 Issue 01 Enterprise Edge 2.0 Programming Operations Guide
Additional Configuration to Enterprise Edge systems
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.
This necessitates that the Public DN lengths table on each Enterprise Edge be
modified to account for the extra leading digit. Essentially, the eight pre-configured
entriesare modified to include aleading ‘9’ in the prefix digits, and the length value
for each entry is increased by one. The new entries are listed below. Note that
regulatory requirements may demand an entry for 911. The Public DN lengths table
is specific to individual market profiles.
Guidelines to setting up PRI networking to Meridian M1
When setting up PRI networking with Meridian M1s, you must consider the
following:
• Meridian M1 is the timing master for the private network PRI connections.
• Meridian M1 uses descending mode for PRI B-channel selection.
• The Meridian M1 must recognize calls dialed to 2xxx and 6xxx numbers, and
route the call over PRI to either the East or West end offices. The same applies
to incoming DID calls from the public network.
• 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.
DN type Public
Destination Code 9
Normal route 002
Absorb 0
Prefix Length
Default 8
90 12
900 13
901 18
9011 19
91 12
9411 4
9911 4
Heading Parameter Setting
Komentarze do niniejszej Instrukcji