PRI networking using Call-by-Call services
519
Programming Operations Guide
PRI networking using Call-by-Call services
The example shown in the following figure highlights the use of PRI Call-by-Call services. It
shows two offices of a company, one in New York and one in Toronto. Each office is equipped
with a Business Communications Manager system and a PRI line. Each office has to handle
incoming and outgoing calls to the public network. In addition, employees at each office often
have to call colleagues in the other office.
Figure 182
PRI networking using Call-by Call Services
To reduce long distance costs, and to allow for a coordinated dialing plan between the offices,
private lines are used to handle interoffice traffic. Refer to
“Configuring the public and private
dialing plans” on page 312
.
If call-by-call services were
not
used, each Business Communications Manager system might have
to be equipped with the following trunks:
•
12 T1 DID lines needed to handle peak incoming call traffic.
•
eight T1 E&M lines needed to handle inter-office calls.
•
eight lines needed to handle outgoing public calls
The total required is thus 28 lines. If the Business Communications Manager systems were using
T1 trunks, then two T1 spans would be required at each office. Note that the total of 28 lines
represents the worst case value for line usage. In reality, the total number of lines in use at any one
time will generally be less than 28. For example, during periods of peak incoming call traffic, the
demand for outgoing lines will be low.
With PRI Call-by-call services, it is not necessary to configure a fixed allocation of trunks. Each of
the 23 lines on the PRI can be used for DID, private Tie, or outgoing public calls. This
consolidation means that it may be possible for each office to use a single PRI span, rather than
Network # 2221
Received # 2221
Internal # 2221
DID # 763-2221
Network # 6221
Received # 6221
Internal # 6221
DID # 562-6221
Toronto office
New York office
Tie Connection
Public Network
PRI
PRI
Business Communications Manager
Central
Office
Central
Office
Summary of Contents for BCM 3.7
Page 4: ...4 Software licensing N0008589 3 3...
Page 32: ...32 Contents N0008589 3 3 W 937 Index 939...
Page 46: ...46 Tables N0008589 3 3...
Page 64: ...64 How to get help N0008589 3 3...
Page 90: ...90 Manually activating Telnet N0008589 3 3...
Page 116: ...116 Delayed system restart N0008589 3 3...
Page 194: ...194 Configuring a data module N0008589 3 3...
Page 276: ...276 Setting line telco features N0008589 3 3...
Page 310: ...310 Using COS passwords N0008589 3 3...
Page 364: ...364 Enhanced 911 E911 configuration N0008589 3 3...
Page 380: ...380 Renumbering DNs N0008589 3 3...
Page 398: ...398 Saving wizard pages on your computer N0008589 3 3...
Page 458: ...458 Voice Mail settings N0008589 3 3...
Page 488: ...488 Setting system telco features N0008589 3 3...
Page 508: ...508 Other programming that affects public networking N0008589 3 3...
Page 522: ...522 PRI networking using Call by Call services N0008589 3 3...
Page 592: ...592 Monitoring Hunt groups N0008589 3 3...
Page 636: ...636 Configuring Double Density N0008589 3 3...
Page 640: ...640 Using the Network Update Wizard N0008589 3 3...
Page 666: ...666 Importing and Exporting DHCP data N0008589 3 3...
Page 722: ...722 Restarting the router N0008589 3 3...
Page 726: ...726 Important Web Cache considerations N0008589 3 3...
Page 748: ...748 Configuring an Interface with NAT N0008589 3 3...
Page 794: ...794 IPSec N0008589 3 3...
Page 818: ...818 Configuring the Policy Agent characteristics N0008589 3 3...
Page 832: ...832 Firewall rules for Business Communications Manager with Dialup interfaces N0008589 3 3...
Page 876: ...876 ISDN Programming N0008589 3 3...
Page 1004: ...1004 Index N0008589 3 3...