Escolar Documentos
Profissional Documentos
Cultura Documentos
Introduction .................................................................................................................................1
Technology Use Case ................................................................................................................. 1
Use Case: Mobile & Remote Access and Business-to-Business Collaboration
with Desktop and Multipurpose Room Systems...................................................................... 1
Design Overview ......................................................................................................................... 2
Solution Details ....................................................................................................................... 2
Cisco Unified Communications Manager ................................................................................ 3
Cisco Video and TelePresence Endpoints .............................................................................. 3
Cisco Expressway-E and Expressway-C ................................................................................ 3
Domain Name System Server ................................................................................................ 3
Cisco Adaptive Security Appliance ......................................................................................... 4
Dial Plan ................................................................................................................................. 4
Table of Contents
Preface
Cisco Validated Designs (CVDs) provide the foundation for systems design based on common use cases or
current engineering system priorities. They incorporate a broad set of technologies, features, and applications to
address customer needs. Cisco engineers have comprehensively tested and documented each CVD in order to
ensure faster, more reliable, and fully predictable deployment.
CVDs include two guide types that provide tested and validated design and deployment details:
Technology design guides provide deployment details, information about validated products and
software, and best practices for specific types of technology.
Solution design guides integrate or reference existing CVDs, but also include product features and
functionality across Cisco products and may include information about third-party integration.
Both CVD types provide a tested starting point for Cisco partners or customers to begin designing and deploying
systems using their own setup and configuration.
Long commands that line wrap are underlined. Enter them as one command:
police rate 10000 pps burst 10000 packets conform-action set-discard-class-
transmit 48 exceed-action transmit
Noteworthy parts of system output or device configuration files appear highlighted, as follows:
interface Vlan64
ip address 10.5.204.5 255.255.255.0
For the most recent CVD guides, see the following site:
http://www.cisco.com/go/cvd/collaboration
Use Cases
This guide addresses the following technology use cases: Related CVD Guides
Mobile & Remote Access and Business-to-Business
Collaboration with Desktop and Multipurpose Room
Systems - Organizations want to reap the budgetary and Cisco Preferred Architecture
productivity gains that a remote workforce allows, without for Collaboration
compromising the benefits of face-to-face interaction. They
want to allow the flexibility for an employee to work remotely
while still maintaining the familiar in-person contact of their Unified Communications
peers and managers. They also want to extend the benefits Using Cisco BE 6000
of collaboration to engage effectively in Business-to-Business Technology Design Guide
conversations with partners/suppliers and customers.
For more information, see the Use Cases section in this guide. Video Conferencing Using
Cisco BE 6000
Scope
This guide covers the following areas of technology and products:
Unified call agent
Desktop video endpoints and mobile clients
Multipurpose room systems
Collaboration edge systems
Session Initiation Protocol (SIP) signaling
Proficiency
This guide is for people with the following technical proficienciesor
equivalent experience:
CCNA Video1 to 3 years configuring voice devices and
video single-screen endpoints, supporting telephony and
video applications, and troubleshooting.
CCNA Voice1 to 3 years designing, installing, and To view the related CVD guides,
troubleshooting voice and unified communications click the titles or visit the following site:
applications, devices, and networks. http://www.cisco.com/go/cvd/collaboration
Collaboration with video provides a higher level of user interaction. Providing functionality to mobile users
by leveraging the Internet has increased significantly over the past few years, and for many organizations,
connectivity is a fundamental requirement for conducting day-to-day activities. Moreover, securely connecting
mobile workers and remote site workers to each other and to headquarters are critical functions that enable
organizations to accomplish their business goals.
The Cisco solution for remote workers has until now relied upon VPN clients to provide a secure tunnel into
the corporate network. The tunnel has allowed an array of diverse protocols to be carried to service delivery
transport mechanisms.
In addition, teleworkers can use their Cisco TelePresence devices without a VPN, making collaboration at home
as easy as in the office. Cisco Expressway makes collaboration as easy outside the enterprise as it is inside
by simplifying the end-user experience. Using secure mobile access based on Transport Layer Security (TLS),
Jabber mobile users can access all their collaboration workloads (video, voice, content, instant messaging,
and presence) without requiring the extra step of a VPN, leaving the flexibility for users to route all other traffic
directly via the Internet.
This means that users, regardless of location, can gain instant access to all of Cisco collaboration toolshelping
to make communications happen faster and more efficiently.
Use Case: Mobile & Remote Access and Business-to-Business Collaboration with
Desktop and Multipurpose Room Systems
Organizations want to reap the budgetary and productivity gains that a remote workforce allowswithout
compromising the benefits of face-to-face interaction. They want to allow the flexibility for an employee to
work remotely while still maintaining the familiar in-person contact of their peers and managers. They also
want to enrich the collaboration experience in their meeting rooms, boardrooms, auditoriums and other shared
environments. They need a solution that is fast to deploy and easy to manage from a central location without
replicating costly components at their remote sites.
Solution Details
This Collaboration Edge Using Cisco BE6000 Technology Design Guide includes the following components:
Cisco Unified Communications Manager (CUCM), for call control and SIP endpoint registrations
Cisco Expressway-C and Cisco Expressway-E, for VPN-less mobile and remote access
Cisco Expressway-E, for business to business collaboration
Network time protocol (NTP) server, for clock synchronization
Public and enterprise domain name system (DNS) servers, for name-to-IP resolution and SRV records
that are used by the endpoints for discovering the Cisco Expressway server
CUCM is the primary call agent in this CVD. CUCM supports session initiation protocol (SIP), and the
configurations in this document use SIP as signaling protocol for the endpoints.
Currently, remote and mobile access are only supported on Jabber for Windows and Jabber for iOS, but in future
TC 7.x releases, mobile and remote access will be supported on all devices supporting the TC software.
Cisco Expressway-E acts as a traversal server and allows secure communication through to your business and
provides other services, such as DNS SRV lookup.
Cisco Expressway-C acts as the traversal client for Cisco Expressway-E (required in all Cisco Expressway E
deployments). It acts as a video gateway providing interworking with third party industry standard H.264 SVC,
H.323, AVC devices & systems (including Microsoft Lync 2013).
In this design, you create separate traversal client and server zones for mobile and remote access and for
business-to-business communications.
SIP and H.323 ALGs are disabled on the Cisco ASA appliance carrying network traffic to or from the Cisco
Expressway-E. When enabled, this is frequently found to negatively affect the built in traversal functionality of
the Cisco Expressway-E, because much of the SIP messaging is encrypted and Cisco ASA cannot inspect the
payload.
Dial Plan
This design follows a single-cluster centralized call processing model. The endpoints use a seven-digit phone
number for dialing, which preserves the capability to receive calls from devices that only support numeric dialing.
The numbers are in the following pattern:
800xxxx
For URI dialing, the endpoints are assigned the URI in the following pattern:
800xxxx@cisco.local
This document will help you deploy both mobile and remote access and business-to-business collaboration.
However to deploy mobile and remote access please go through the following processes:
Installing Cisco Expressway-C
Installing Cisco Expressway-E
Configuring CUCM
Deploying Mobile and Remote access
Before getting started, you need to collect certain information specific to your site. You can fill in the following
table.
This procedure represents a typical installation. The Deploy OVF Template dynamically changes to reflect host
configuration.
Step 3: Click Browse, find the location of the .ova file, click Open, and then click Next.
Step 6: If an End User License Agreement page appears, read the EULA, click Accept, and then Next.
Step 7: On the Name and Location page, enter EXPc1 and the Inventory Location where the virtual machine will
reside.
Step 9: On the Deployment Configuration page, select Small (e.g. BE 6000) as the configuration option.
Step 10: On the Disk Format page, ensure that the default disk format of Thick Provision Lazy Zeroed is
selected, and then click Next.
Tech Tip
Because the VM performance may degrade during the resizing of a partition, Thin
Provision is not recommended.
Step 11: If Network Mapping is listed, configure it and select the network mapping that applies to your
infrastructure (default is VM Network) and then click Next.
Step 13: Select Power on after deployment, and then click Finish.
Step 1: Right-click the VM guest and click Open Console. The VM guest will take some time to boot.
Step 2: Create its second hard disk partition, and then reboot to a login prompt.
Step 3: At the login prompt, enter the username admin, and the password TANDBERG.
Step 5: Using the Install Wizard, enter the following information. Configure other entries as required.
Run install wizard: y
Do you wish to change the system password: y
Password: [Password]
IP Protocol: IPv4
IP Address LAN1: 192.168.1.29
Subnet Mask LAN1: 255.255.255.0
Default Gateway Address: 192.168.1.1
Ethernet Speed: auto
Run ssh daemon: y
Step 6: Log into the Expressway-C as admin, and then type the following command to reboot the VM guest:
Xcommand boot
You should now be able to access Expressway-C via a web browser.
Step 1: Navigate to Maintenance> Option keys, enter the provided release key, and then click Set release key.
Step 2: For each option key provided, in Add option key, enter the option key value, and then click Add option.
Step 1: Navigate to System> DNS and in the DNS settings section, enter the following values. Leave the other
fields as their default values.
System host nameEXPc1
Domain namecisco.local
Step 2: In the Default DNS servers section, enter the following values. Leave the other fields as their default
values.
Address 1192.168.1.10
Before getting started, you need to collect certain information specific to your site. You can fill in the following
table.
Expressway-E sits in the DMZ network and is NATed to a publically routable IP. Once NAT is configured on the
Expressway-E, all communication to and from Expressway-E will use the NATed IP.
This procedure represents a typical installation. The Deploy OVF Template dynamically changes to reflect host
configuration.
Step 3: Click Browse, find the location of the .ova file, click Open, and then click Next.
Step 6: If an End User License Agreement page appears, read the EULA, click Accept, and then click Next.
Step 7: On the Name and Location page, enter the name EXPe1 and the inventory location where the virtual
machine will reside.
Step 8: On the Storage page, select the datastore onto which the Expressway-E VM Guest will be deployed,
and then click Next.
Step 10: On the Disk Format page, ensure that the default disk format of Thick Provision Lazy Zeroed is
selected, and then click Next.
Tech Tip
Because the VM performance may degrade during the resizing of a partition, Thin
Provision is not recommended.
Step 11: If Network Mapping is listed, configure it and select the network mapping that applies to your
infrastructure (default is VM Network), and then click Next.
Step 1: Right-click the VM guest and click Open Console. The VM guest will take some time to boot.
Step 2: Create its second hard disk partition, and then reboot to a login prompt.
Step 3: At the login prompt, enter the username admin, and the password TANDBERG.
Step 5: Enter IP information by following the Install Wizard. Enter the following in the relevant fields. Configure
other entries as required.
Run install wizard: y
Do you wish to change the system password: y
Password: [Password]
IP Protocol: IPv4
IP Address LAN1: 192.168.4.18
Subnet Mask LAN1: 255.255.255.252
Default Gateway Address: 192.168.4.17
Ethernet Speed: auto
Run ssh daemon: y
Step 6: Log into the Expressway-E as admin, and then type the following command to reboot the VM guest.
Xcommand boot
You should now be able to access Expressway-E via a web browser.
Step 1: Navigate to Maintenance> Option keys, enter the provided release key, and then click Set release key.
Step 2: For each option key provided, enter the option key value in the Add option key field, and then click Add
option.
Step 1: Navigate to System> DNS and in the DNS settings section, enter the following. Leave the other fields
as their default values.
System host nameEXPe1
Domain namecisco.local
Step 2: In the Default DNS servers section, enter the following. Leave the other fields as their default values.
Address 1192.168.6.5
Step 1: Navigate to System> IP and enter the following into the relevant fields. Leave the other fields at their
default values.
Use Dual Network InterfacesNo
IPv4 static NAT modeOn
IPv4 static NAT address192.168.6.18
For the installation and basic configuration of Cisco Unified Communications Manager (CUCM), please refer the
Unified Communications Using BE6000 Technology Design Guide.
This process lists the prerequisite configuration on the CUCM before you can start configuring either, mobile and
remote access or business-to-business communications.
First, you log in to Cisco Unified Communications Manager Administration page and create a separate region for
video traffic to allow more bandwidth for intra or inter region calls.
Step 1: Navigate to System> Region Information> Region and click Add New.
Procedure 2 Configure device pool in CUCM for video and add the video region
Step 2: Enter the following into the relevant fields, leaving the other fields at their default values:
Device Pool NameVideo_DP
Date/Time GroupCMLocal
RegionVideo_Reg
Procedure 3 Select the above device pool for all video endpoints
Step 1: Navigate to Device> Phone, click Find, and select the video endpoint.
Cisco Unified Communications mobile and remote access allows endpoints like Cisco Jabber to have
their registration, call control, provisioning, messaging and presence services provided by Cisco Unified
Communications Manager when the endpoint is not within the enterprise network. The Expressway-C and
Expressway-E provides secure firewall traversal and line side support for Unified CM registrations.
Tech Tip
For a VPN based remote access, you can refer the Cisco Validated Designs for
Enterprise WAN CVD for the appropriate VPN related configurations.
Mobile and remote access endpoints use domain name servers in order to determine whether the client is inside
or outside the enterprise. It finds the internal or external name servers when inside or outside the enterprise. The
endpoints will query the name server for SRV records in order to locate available services. When the endpoint is
inside the enterprise, the endpoint will look for the _cisco-uds. service in order to discover the CUCM and IM&P
server.
The local DNS server should have the following SRV and A records so that the endpoints can discover the
CUCM.
_cisco-uds._tcp.cisco.local. SRV 10 10 8443 CUCM-Pub.cisco.local
_cuplogin._tcp.cisco.local. SRV 10 10 8443 CUCM-IMP1.cisco.local
CUCM-Pub.cisco.local. IN A 192.168.1.16
CUCM-IMP1.cisco.local. IN A 192.168.1.27
Procedure 2 Configure public DNS server with relevant SRV & A records
When the endpoint is outside the enterprise, it will look for the _collab-edge. service in order to discover the
Expressway-E for remote access.
The public DNS server should have the following SRV and A records so that the endpoints can discover the
Expressway-E to for mobile and remote access.
_collab-edge._tls.cisco.local. SRV 10 10 8443 EXPe1.cisco.local
EXPe1.cisco.local. IN A 192.168.6.18
Configure the firewall to allow traffic on following ports between your inside network (where the Expressway-C is
located) and the DMZ (where the Expressway-E is located) and between the DMZ and the public Internet.
Expressway-E
Purpose Protocol Expressway-C (source) (listening)
XMPP (IM and Presence) TCP 7400 7400
SSH (HTTP/S tunnels) TCP Ephemeral port 2222
Expressway-C Expressway-E
Purpose Protocol (source) (listening)
SIP media UDP 36012 to 59999 UDP port
SIP signaling TLS 25000 to 29999 TLS listening port
Expressway-C Expressway-E
Purpose Protocol (source) (listening)
XMPP (IM and Presence) TCP TCP source port 5222
UDS (provisioning/phonebook) TCP TCP source port 8443
Media UDP UDP source port 36012 to 59999
SIP signaling TLS TLS source port 5061
HTTPS (administrative access) TCP TCP source port 443
Tech Tip
The default media port range of 36000 to 59999 applies to new installations of X8.0 or
later. The first 2 ports in the range are used for multiplexed traffic only (with Large VM
deployments the first 12 ports in the range36000 to 36011are used). Prior to X8.0
the default range is 50000 to 54999.
Tech Tip
Ports 8191/8192 TCP and 8883/8884 TCP are used internally within the VCS
application for communications between the VCS Control and the VCS Expressway.
There is no firewall requirement, but these ports must not be allocated for any other
purpose.
Step 1: Navigate to Configuration> Unified Communications> Configuration and set Mobile and Remote
Access to On.
Step 1: Navigate to Configuration> Unified Communications> Unified CM Servers, and then click New.
Step 4: Navigate to Configuration> Unified Communications> IM and Presence servers, and then click New.
Reader Tip
For more information about IM&P, see Unified Communications Using Cisco BE 6000
Technology Design Guide.
Step 1: Navigate to Configuration> Unified Communications> Configuration, and then set Mobile and remote
access to On.
Remote and mobile clients must verify (by validating the server certificate) the identity of the Expressway-E to
which they are connecting. To do this, in their list of trusted CAs, the clients must have the certificate authority
that was used to sign the Expressway-Es server certificate.
This design requires secure communications between Expressway-C and Expressway-E, as well as between
Expressway-E and endpoints located outside the enterprise.
Step 1: To generate a CSR and/or to upload a server certificate to the Expressway-C/E, navigate to
Maintenance> Security certificates> Server certificate and click Generate CSR.
Step 2: To upload trusted Certificate Authority (CA) certificates on to the Expressway-C/E, navigate to
Maintenance> Security certificates> Trusted CA certificate.
Reader Tip
For more information, see the Cisco Expressway Certificate Creation and Use
Deployment Guide.
Step 2: Enter the following into the relevant fields, leaving the other fields at their default values:
Under Configuration section
NameTraversalServer (MRA)
TypeTraversal Server
Under Connection credentials
Usernameadmin
Under H.323 section
ModeOff
Under SIP section
ModeOn
Port7001
TransportTLS
Mobile and remote accessYes
TLS verify modeOn
TLS verify subject nameEXPc1.cisco.local
Media encryption modeForce Encrypted
ICE supportOff
Poison modeOff
For information about configuring Jabber endpoints and DNS, see Configure DNS for
Cisco Jabber.
Mobile and remote access is now configured. You can now register Jabber endpoints to the CUCM without the
VPN now.
Deploying B2B
1. Configure SIP profile on CUCM for Cisco Expressway-C
2. Configure SIP trunk security profile on CUCM for Cisco Expressway-C
3. Configure SIP trunk on CUCM to Expressway-C
4. Configure SIP route pattern on CUCM for B2B
5. Configure firewall
PROCESS
Step 1: Navigate to Device> Device Settings> SIP Profile, and click Add New.
Procedure 2 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 4: Enter the following into the relevant fields. Leave the other fields at their default values.
Device NameSIP_Trunk_ExpC
DescriptionSIP_Trunk_ExpC for B2B Calls
Device PoolVideo_DP
Calling and Connected Party Info FormatDeliver URI only in connected party, if available
Destination Address192.168.1.29
SIP Trunk Security ProfileNon Secure SIP Trunk Profile port 5560
SIP ProfileCustom SIP Profile for Cisco Expressway-C
DTMF Signaling MethodRFC 2833
Normalization Scriptvcs-interop
The following SIP route pattern is configured to route all B2B calls towards the Expressway-C, which doesnt
match any existing route patterns.
Step 1: Navigate to Call Routing> SIP Route Pattern and click Add New.
Step 2: Enter the following into the relevant fields, leaving the other fields at their default values:
Pattern UsageDomain Routing
IPv4 Pattern*
SIP Trunk/Route ListSIP_Trunk_ExpC
The firewall must be configured to allow traffic on following ports between your inside network (where the
Expressway-C is located) and the DMZ (where the Expressway-E is located) and between the DMZ and the
public Internet.
Tech Tip
The first 2 ports in the media port range of 36000 to 59999 are used for only for
multiplexed traffic (with Large VM deployments, the first 12 ports in the range of 36000
to 36011 are used).
Step 2: Enter the following into the relevant fields, leaving the other fields at their default values:
NameTraversalClient (B2B)
TypeTraversal Client
Usernameb2badmin
Password[Password]
H.323 Port6011
SIP Port7011
Mobile and remote accessNo
TransportTLS
Peer 1 Address192.168.6.18
Step 1: Navigate to Configuration> Dial Plan> Search Rules, and click New.
Step 2: Enter the following into the relevant fields, leaving the other fields at their default values:
Rule NameB2B-to-cisco.com
DescriptionB2B calls to cisco.com
Priority101
ModeAlias Pattern Match
Pattern typeRegex
Pattern String(?!.*@%localdomains%.*$)(.*)
Pattern BehaviorLeave
On Successful MatchStop
TargetTraversalClient (B2B)
StateEnabled
For a B2B call, the Expressway-E doesnt know where to route a call for a different domain; it doesnt have a
neighbor created for that domain. Thus it routes all the call via the public DNS server.
Step 2: Enter the following into the relevant fields, leaving other fields at their default values:
NameDNS Zone (B2B)
TypeDNS
H.323 ModeOn
SIP ModeOn
Fallback Transport ProtocolTCP
Step 1: Navigate to Configuration> Dial Plan> Search Rules, and click New.
Ensure that the public DNS server have the following SRV and A records so that the endpoints can discover the
Expressway-E to route business-to-business calls.
_sip._tcp.cisco.local. SRV 10 10 5060 expe1.cisco.local
_sip._udp.cisco.local. SRV 10 10 5060 expe1.cisco.local
expe1.cisco.local. IN A 192.168.6.18
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco Website at www.cisco.com/go/offices.
ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, DESIGNS) IN THIS MANUAL ARE PRESENTED AS IS,
WITH ALL FAULTS. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF MERCHANTABILITY, FITNESS FOR
A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS
SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR
DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS. THE DESIGNS
DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS. USERS SHOULD CONSULT THEIR OWN TECHNICAL
ADVISORS BEFORE IMPLEMENTING THE DESIGNS. RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
B-470-COL-1 04/14