782
IPSec
N0008589 3.3
Creating a tunnel between a Business Communications Manager
and a Contivity Extranet Switch v02_61
The following are an examples of a how to connect a Business Communications Manager to a
Contivity Extranet Switch using an IPSec tunnel.
In this example, the IPSec tunnel connects a Business Communications Manager with a LAN 2 IP
address of 47.81.20.50 and a Contivity Extranet Switch with a Public IP address of 47.82.30.60.
LAN 1 on the Business Communications Manager is on the subnet 10.10.11.0. The Contivity
Extranet Private LAN is on the subnet 14.14.14.0.
Configuring the Business Communications Manager
1
Set the Local Endpoint to
47.81.20.50
.
2
Set the Remote Endpoint to
47.82.30.60
.
3
Set the Preshared Key to
123
.
4
Set the Key Type to
Text
.
5
Set the Local Accessible Networks to
10.10.11.0
with mask
255.255.255.0
.
6
Set the Remote Accessible Networks to
14.14.14.0
with mask
255.255.255.0
.
Configuring the Contivity Extranet Switch
1
Go to Profiles->Network and create a Network with the IP address 14.14.14.0 with mask
255.255.255.0. You will use this for the Local Accessible Networks for your Branch Office
Connection.
2
Under Profiles->Branch Office, create a Group based on the Base class.
3
In the IPSec section of this new Group, change the Vendor ID to Disabled and change
Compression to Disabled. Business Communications Manager does not support Vendor ID or
Compression.
4
In the Connectivity section of this new group, change the Nailed Up setting to Disabled.
Business Communications Manager does not support the Nailed Up functionality.
5
Select Define Branch Office Connection.
6
Set the routing type to be Static.
7
Set the Local Endpoint to 47.82.30.60 and the Remote Endpoint to 47.82.20.50.
8
Under Local Accessible Networks, select the Network that was created earlier.
9
Set the Remote Accessible Networks to 10.10.11.0 with mask 255.255.255.0.
10
For the Preshared Key, select the Text button and set the key to '123'. This must match the
BCM key.
11
Mark the box for Enable Branch Office Connection.
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...