
Chapter 44 VoIP trunk gateways 405
BCM 4.0 Networking Configuration Guide
• the unique digit(s) that identify the remote system. This is usually part of the destination code.
PSTN call to remote node
Making a call to a remote node requires any BCM systems between the calling and receiving
nodes to have the correct routing to pass the call on to the next node. This is the same if you use
PSTN lines or VoIP trunks for the network.
Figure 130 shows a call tandeming from the public network (PSTN), through System A
(Santa Clara) and being passed to System B (Ottawa) over a VoIP trunk network. In this case, it
might be a home-based employee who wants to call someone in Ottawa.
You cannot program DISA 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 tandemed
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 130 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
Dial in:
XXX-2244
Remote gateway set
up to Santa Clara
CDP system code for
Ottawa: 2
dedicated VoIP trunk private network
System A
System B
Kommentare zu diesen Handbüchern