Programming access codes
327
Programming Operations Guide
Using the MCDN access codes (tandem calls)
Three special codes exist specifically for programming over PRI and VoIP trunks that are using
the MCDN protocol, and which connect to a call server systems that use specific call codes for
special call types, such as the Meridian 1 (M1). The purpose of the codes is to allow easier
programming of the call server systems when calls are tandemed through a Business
Communications Manager to the local PSTN.
Calls tandeming to the public network through the private network need to retain their dialing
protocol throughout the private network. This means that a call from an M1 node tagged as a local
call gets received by the BCM node and is recognized as a call intended for the public network, but
also as a call that needs to maintain the local call tag until it gets to the BCM node that is directly
connected to the PSTN. This is accomplished by ensuring that the destination code, which starts
with this access code, passes the call on using the route designated with the correct call type. Refer
to
“Defining routes” on page 333
. The following figure charts this process.
Figure 94
Local call tandemed through Business Communications Manager nodes
Local
PSTN
823-2222
Dialout: 9-823-2222
Dialout: <local call>-823-2222
Meridian user
The Meridian system recognizes the call as
a local public call.
Deletes the routing digits.
Tags call as Local call type
Sends out rest of dialout on private network
The Business Communications Manager
Adds Local code to front of called number:
9-823-2222
Dialout: 9-823-2222
The Business Communications Manager
receives the call. The system recognizes
9823 as the destination code for the local
PSTN route. Route drops the leading
digit and dials out over the PSTN trunk.
Dialout: [unknown] 823-2222
The system knows 9823 is the route to the next
system and routes the call through private network.
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...