Nortel BCM 3.7, Руководство пользователя

Страница: 542 / 1004

542 Using SL-1 with MCDN to network with a Meridian system
N0008589 3.3
Note that the Private Network Identifier (PNI) is programmed at each end of the links. The PNI
identifies the Business Communications Manager to the Meridian 1 system.
Routing is set up such that network calls are made by dialing a four-digit private network DN. For
example, if a user in the west end branch wishes to call a user in the east end branch within the
private network, they dial 6221. The figure above illustrates this example.
The implications on the configuration on each node to access the PSTN through one network node:
• Each node must have the Private Network Access Code set to the value 9.
• Each node must have destination code(s) that match the Private Network Access Code plus
digits corresponding to calls terminating in the local PSTN. For example, if the Private
Network Access Code is 9, the node in Ottawa would require a destination code of 91613.
Similarly, Toronto would require the following destination code: 91416.
Business Communications Manager module settings: The following table lists the module
settings that are required to set up the network described in the previous figure. Refer to
“Configuring resources — media bay modules” on page 135 .
Business Communications Manager dialing plan settings: The following table lists the dialing
plan settings that are required to set up the network described in the figure in the previous section.
Also refer to
“Configuring the public and private dialing plans” on page 312 .
Table 122 Module settings for MCDN network
West End office:
Module programming DTM PRI
Protocol SL-1
BchanSeq Ascend
ClockSrc Primary
East End office:
Module programming DTM PRI
Protocol SL-1
BchanSeq Ascend
ClockSrc Primary
Table 123 MCDN dialing plan settings
West End office:
Dialing Plan programming Type UDP
Private Network ID 1
Location Code <unique three digits> (becomes part of
destination code)
Private DN Length 4
Public DN Length 7