
Chapter 6 Setting up VoIP trunks for outgoing calls 103
IP Telephony Configuration Guide
PSTN call to remote node
Making a call to a remote node requires any Business Communications Manager systems between
the calling and receiving nodes to have the correct routing to pass the call on to the next node. For
routing details on tandem networks, refer to the Programming Operations Guide, Private
Networking section.
The following figure shows a call tandeming from the public network, through System A
(Santa Clara) and being passed to System B (Ottawa). In this case, it might be a home-based
employee who wants to call someone in Ottawa.
You cannot program DISA or auto-answer for VoIP trunks, therefore, your system cannot be
accessed from an external location over a VoIP trunk. The exception to this is if the call comes into
a tandemned system (system A) from a PSTN, and the call is then sent out across a VoIP trunk to
system B, as in this example. In this case, system A is controlling remote access through remote
access packages and routing, transferring the outside call to a VoIP trunk, which is accessed by an
allowed dial sequence. The VoIP trunk connects directly to system B, where the dialing sequence
is recognized as directed to an internal DN. In this scenario, all remote call features are available to
the caller.
Figure 31 Calling into a remote node from a public location
OttawaSanta Clara
IP network
PSTN
Gateway destination digit: 2
Route 022 (VoIP)
DN type: Private
Destination code: 2, using route 022
Absorb length: 0
Ensure VoIP trunk is set up with remote
filters
DN 2244
Target line XXX recognizes 2244
DN 2244 assigned with target line XXX
Dialout:
2244
Gateway: 2
Gateway: 3
DN 3322
Dialin:
XXX-2244
Remote gateway set
up to Santa Clara
CDP system code for
Ottawa:2
dedicated VoIP trunk private network
Comentarios a estos manuales