Before you plan the mobility deployment, make sure that you:
Review and have access to the Solution Reference Network Design for Cisco Hosted Collaboration Solution. Review these specific sections:
"Mobility" in the Applications chapter
"IMS network integration" in the Network infrastructure chapter
Complete the actions outlined in previous sections of this guide including:
Initial system requirements and planned growth
Data Center requirements
Customer premise equipment
Backup and restore
Unified Communications applications
Plan the mobility deployment
Determine which mobile networks that you will support. Cisco HCS offers the following network choices:
IP Multimedia Subsystem (IMS)
VoLTE and 4G
Determine the mobility offerings for your Cisco HCS deployment model.
Determine how you want to implement mobility in your deployment.
Determine how Cisco HCS integrates with the mobile network. Different integrations have different ways of obtaining the call from the mobile network, for example, Intelligent Network trigger or routing configuration.
Determine the mobility endpoints that will be provisioned.
Users will want a VPN when they are outside of the enterprise network.
Cisco HCS integrates with the IMS network through the IMS phone types. The subscriber provisioned in the IMS network must be provisioned as an IMS client in HCS so that HCS can act as Application Server for the IMS subscribers.
The Cisco HCS Features for Cisco Unified Communications Manager does not include carrier-integrated mobile or IMS-supported endpoints.
Identify the UC application-based mobility features to be implemented.
Dial via Office Reverse Callback
Dial via Office Forward
Reroute Remote Destination Call to enterprise network
Enterprise Feature Access
Least Cost Routing with Dial via Office Reverse Callback
Least Cost Routing with Dial via Office Forward
Send Call to Mobile
Identify the cloud-based collaboration applications to implement with Cisco HCS.
Cisco WebEx, the Cisco Collaboration cloud-based infrastructure, is a collaboration solution that does not require any hardware deployment on the enterprise premises. All services (audio, video, and content sharing) are securely hosted in the Internet or the cloud. All the content, voice, and video traffic from every client traverses the Internet and is mixed and managed in the cloud at the WebEx data center.
The Cisco Collaboration cloud infrastructure provides WebEx capabilities to mobile clients and devices. WebEx Meetings provides web-based voice and video conferencing with content sharing. WebEx Messenger provides XMPP-based IM and presence as well as point-to-point audio and video calling.
Identify considerations for the Home Subscriber Server (HSS):
The public ID of the IMS client is provisioned in the HSS with the subscriber profiles.
The HSS provisioning should have Cisco HCS as the name of the application server.
See the Cisco HCS documentation for information on how to set up ISC trunks, the Cisco Unified Border Element-Service Provider (CUBE-SP), and IMS clients on Cisco Unified Communications Manager. Setup considerations include:
IMS network operators must provision their equipment and provide the Cisco HCS administrator with all the required data to provision Cisco HCS.
The trunk between the S-CSCF and Cisco HCS should be configured in the IMS network with the DNS name of the CUBE-SP.
When the CUBE-SP resolves that name within the Cisco HCS internal network, it must point to Cisco Unified Communications Manager.
Identify any CUBE-SP media anchoring requirements.
Determine if additional application servers must be included. If you are chaining together more than one application server, review the feature interaction.
Review Unified Mobility offerings and IMS client features for IMS clients. The IMS client features are:
Originating Identification Presentation
Terminating Identification Presentation
Originating Identification Restriction
Terminating Identification Restriction
Communication Diversion Unconditional
Communication Diversion on not Logged in
Communication Diversion on Busy
Communication Diversion on not Reachable
Communication Diversion on No Reply
Barring of All Incoming Calls
Barring of All Outgoing Calls
Barring of All Incoming Calls When Roaming
Barring of Outgoing International Calls
Call Forward All Activation
3rd Party Registration
Message Waiting Indication
Ad-Hoc Multi Party Conference
Determine the CDR Billing parameters. Consider the P-Charging-Vector support in Cisco HCS.
Determine the IMS licensing requirements.
Plan carrier-integrated mobile integration
Carrier-integrated mobile is a device type introduced in the Cisco Unified Communications Manager that extends mobility features outside of your UC network without the requirement to provision Cisco Jabber. This device sends and receives calls through the SIP trunk. The Unified Mobility features available in Unified Communications Manager are applicable to this device. This device type offers mobility in the same way as a remote destination offers mobility and uses fixed mobile convergence (FMC).
Determine your mobility requirements for carrier integrated mobile.
Identify requirements for the Intelligent Network trigger. The call must be directed to the CUBE-SP.
Identify requirements for SIP trunks. The P-Charging-Vector value must be set.
Identify any CUBE-SP media anchoring requirements.
Determine if an application server will be included.
Review the Unified Mobility offerings for carrier-integrated mobile clients.
Determine the CDR Billing parameters.
Determine carrier-integrated mobile licensing requirements.