Nortel BCM 3.7, Manual

Page: 524 / 1004

524 System numbering plans
N0008589 3.3
System numbering plans
Both these types of networks require similar setups for dialing plans and routing. Each node must
have a way to route external calls to the adjacent node or nodes. To do this, all nodes must have the
same Private DN lengths.
You use routing and a private dialing plan to control calls over the network. Refer to “Configuring
the public and private dialing plans” on page 312 for a description of the two types of dialing plans
available for private networking over SL-1 and SL-1 MCDN networks. Each example in this
section describes the routing configurations that are required to support calls over the network.
Depending on the type of dialing plan you choose, each node must also have a unique location or
steering code so the calls can be correctly routed through the nodes of the network. MCDN
networks also require a Private Network ID, which is supplied by the Meridian network
administrator to define how the Meridian system identifies each node.
Creating tandem private networks
You can tie a number of Business Communications Manager systems together with SL-1 lines.
This tandem network provides you with the benefits of end-to-end name display and toll-free
calling over the SL-1 private link. Each Business Communications Manager becomes a node in the
network. The following figure demonstrates a tandem configuration.
Figure 183 Private tandem network of Business Communications Managers
SL-1 line
SL-1 line
SL-1 line
SL-1 line
SL-1 line
Calgary Toronto
Local
PSTN
Local
PSTN
Node A
Node B
Node E
Node C
Node D
Node F
Public: 403-765-XXXX
Private ID: 395
Public: 403-762-XXXX
Private ID: 392
Public: 403-761-XXXX
Private ID: 391
Calgary network routes only area
codes 403 and 604
Public: 613-766-XXXX
Private ID: 396
Public: 613-764-XXXX
Private ID: 394
Public: 613-763-XXXX
Private ID: 393
Ottawa network routes all area
codes except 403 and 604