Download Print this page

Deploy B2B Collaboration - Cisco BE6000 Design Manual

Collaboration edge
Hide thumbs Also See for BE6000:

Advertisement

Pre-deployment Checklist and Tasks
Contents

Deploy B2B Collaboration

Configure SIP trunk security profile on CUCM for Cisco Expressway-C
1.
Configure SIP trunk on CUCM to Expressway-C
2.
Configure SIP route pattern on CUCM for B2B
3.
Configure firewall
4.
Configure neighbor zone on Expressway-C for CUCM
5.
Configure traversal client on Expressway-C
6.
Configure search rules on Expressway-C
7.
Configure transform on Expressway-C
8.
Configure traversal server zone on Expressway-E
9.
Configure DNS zone on Expressway-E
10.
Configure search rules on Expressway-E
11.
Configure transform on Expressway-E
12.
Procedure 1
Configure SIP trunk security profile on CUCM for Cisco Expressway-C
For B2B calls to be routed, you must create a SIP trunk between CUCM and Expressway-C.
In this design, the Expressway-C is already configured for mobile and remote access. Port 5060 is used
for line-side registrations of endpoints in mobile and remote access scenario. A SIP trunk cannot be
formed between Expressway-C and CUCM by using port 5060 because the CUCM cannot accept line-
side and trunk-side communication from the same device using the same port.
Thus the SIP trunk from Expressway-C to CUCM has to use another SIP port on the CUCM incoming side.
This design uses
5560
as the SIP trunk incoming port. You can change the SIP incoming port by creating a
new SIP trunk security profile and assigning this profile to the SIP trunk created between CUCM and
Expressway-C.
Step 1.
Navigate to System > Security > SIP Trunk Security Profile and click Add New.
Step 2.
Enter the following values in the relevant fields:
Name—Non Secure SIP Trunk Profile port 5560
Description—SIP Profile with listening port 5560
Incoming
Port—5560
Deploy MRA and B2B Collaboration
Deployment Details
Deploy CUBE
PAGE 42

Advertisement

loading