544
VoIP networking
N0008589 3.3
VoIP networking
When you choose voice over IP (VoIP) trunks to make network connections, the process is very
much the same as using land lines, except that you must also create a Remote Gateway record
which identifies the IP address for the target system. Note: If the IP system has a Gatekeeper, the
Remote Gateway record is not required. You need to supply the IP parameters of your system to
the Gatekeeper administrator instead.
You also need a VoIP keycode before you can activate VoIP trunks.
MCDN networking over VoIP, which is always between a Meridian 1 and one or more Business
Communications Managers, is set up and works the same way as it does over PRI lines. You still
require the MCDN and IP telephony software keys and compatible dialing plans on all networked
systems. Refer to
“Understanding MCDN network features” on page 532
.
The major difference between a PRI MCDN line and a VoIP MCDN connection is that the VoIP
trunk requires Local and Remote Gateway settings. Under
Services
,
IP Telephony
,
H.323
Trunks
,
Remote Gateway
, ensure that
Gateway Protocol
is set to
CSE
if you want MCDN
functionality for the VoIP connection to the Meridian system (BCM 3.5 and newer software). The
Gateway Type
would be set to
IPT
(M1 IP Telephony), as it would for any non-MCDN VoIP
connection to a Meridian system. You can also use MCDN VoIP to other Business
Communications Managers. There is a Gateway Type for each version of Business
Communications Manager software that supports this function.
For details about setting up gateways and configuring VoIP trunks, refer to the
IP Telephony Configuration Guide.
East End office:
Trunk/Line Data
Line 245
Target line
Private Received #
6221
Line Access
DN 6221
L245:Ring only
Line pool access
Line pool PRI-A
Routing Services
Private Network
Public Network
Head Office to West End
Route
001
002
Dial out #
No number
No number
Use
Pool PRI-A
Pool PRI-A
DN type
Private
Public
Head Office to M1
Head Office to West End
Call terminates at M1
Destination Code
4 (contains location code) 2
9
Normal route
001
001
002
Absorb
0
0
0
Table 124
Network routing information (Continued)
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...