This document describes the Extension Mobility Cross cluster feature that is introduced in Cisco Unified Communications Manager (CUCM) 8.0 and higher releases.
Preconditions
Required conditions
No specific specification is required for this document.
Components used cisco callmanager
The information in this document is based on these software and hardware versions
CUCM 9.X and higher
The information in this document was created from devices in a specific lab environment. All devices used in this document started with a cleared (default) configuration. If your network is operational, make sure that you understand the potential effect of any command.
General informations
EMCC solution
EMCC addresses the problem of extension mobility cross clusters specifying cross-registration. Cross-registration involves these characteristics:
The home battery user logs in to a visiting battery phone.
The login procedure gives the device information in the home battery database.
The home cluster database builds a temporary device with the user device profile.
The TFTP home cluster server builds the phone configuration file.
After login, the visiting cluster directs the phone to home the TFTP cluster server.
The phone downloads its TFTP configuration from the server and then cross-registers the TFTP home cluster (HC) with the Cisco Unified Communications Manager home cluster.
Configure
1. Service activation
Navigate to Cisco Unified Serviceability> Tools> Service Activation .
Choose a server, and start these services by checking the box next to each service:
Cisco CallManager
Cisco TFTP
Cisco Extension Mobility
Cisco Bulk Provisioning Service (can launch only on publisher)
2. EM telephone service
Navigate to Administration> Device> Device Settings> Phone Services CUCM .
Create an extension mobility telephony service.
In CUCM management, navigate to Device> Device Settings> Phone Services .
Click Add New , and complete the fields in the IP Phone Services configuration window as:
Service name: Extension Mobility.
ASCII service name: Extension mobility.
Service description: Extension mobility.
Service URL: http://10.89.80.19:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#
Secure-service URL: https://10.89.80.19:8443/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#
Check the enable box .
10.Click Save to Save Extension Mobility Telephony Service.
3. Add device profile for users who need EM
Navigate to Administration> Device> Device Settings> CUCM Device Profile
Add a device profile for users who require extension mobility. The device profile gets used to overlap with a real device when the user logs on (both for Extension Mobility and EMCC). Perform the following steps:
1. In CUCM Administration, navigate to Device> Device Settings> Device Profile.
2. Add a new device profile for a specific device type with a specific protocol, assigning a meaningful name to the new device profile. SCCP Device Profile Example: 7971.
3. In the new device profile, configure the EMCC CSS field .
4. This Calling Search Space (CSS) gets applied to the real device configuration when the user travels and uses an IP phone from a different (visiting) cluster.
5. Configure this field as if placing the CSS field in the phone configuration window of a local IP phone.
Refer to the EMCC Call Routing section for more details about the EMCC CSS field.
Add a directory number (DN) to the new device profile. Example: 4001
In the Directory Number Configuration window, choose the Configure device option (<your new device profile name>) from the Related Links drop-down list box .
You return to the Device Profile Configuration window .
In the Configure Device Profile window, choose the Subscribe / Unsubscribe Services option from the Related Links drop-down box .
In the pop-up window that displays, choose Extension Service from the Select a Service drop-down box.
Click on Next .
Click on the backup and close the pop-up window.
The Device Profile Configuration window will look, as shown in this image.
4. Configure the end user
Add the users for Cisco EMCC:
In Cisco Unified Communications Manager Administration , choose User Management> End User .
Click Add New to add a new end user.
In the end user configuration window that displays, configure at least these fields: User-id, Password, PIN, Last name, First name.
In the Extension Mobility pane, check the Enable EMCC check box .
Choose the device profile that you configured in step 3 from the Available Profiles List pane in the Extension Mobility pane.
Use the down arrow to move the device profile to the Controlled Profiles List pane.
Click Save to save the end user configuration.
5.Enable EM on peripherals
Check the EM on the phone page.
Subscribe to the EMCC telephone service.
Navigate to Administration> Device> Phone CUCM .
Subscribe / unsubscribe services
Until now this configuration must be done on the batteries at home and the visit.
6. Configure Bulk Certificate Management
Navigate to CUCM OS Management> Security Management> Bulk Certificate.
7. Export
Certificate Type: All, then export, as shown in this image.
8. Consollidate
Type of certificate: All, consolidate.
9. Import
Type of certificate: All, import.
Note: After you import all the certificates on each cluster, for each cluster, you had to restart CUCM
10. Enable video calls
In order to enable EMCC for video calls, configure common phone profile ( device> device settings> common phone profile ) or configure company phone setup ( system> company phone setup ) to enable video calls .
In either window, set the Visual Abilities combo box as enabled. (This configuration can be enabled by default by battery.)
11. Configure the EMCC model
Add EMCC Devices - Add EMCC Templates:
CUCM Administration, Bulk Administration> EMCC Model> EMCC> Click Add New.
12. Insert / configure EMCC update
Add EMCC devices - Place the default EMCC template.
In CUCM Administration, choose Bulk Administration> EMCC> EMCC Insert / Update .
Click Update EMCC Peripherals .
From the Default EMCC model drop-down list box, choose the EMCC device model that you configured in step 11.
Click Run immediately .
In order to check if the job ran successfully, choose Administration> Bulk Task Scheduler and look up the task identification for your job. Check that your job has worked successfully.
13. Insert / configure EMCC update
Add devices> EMCC insert EMCC devices.
In CUCM Administration, navigate Bulk Administration> EMCC> EMCC Insert / Update .
Click Insert EMCC Peripherals .
Change the value in Number of EMCC devices to be added field.
Click Run immediately .
Refresh this window and verify that the number of EMCC devices already in database value now shows the number of devices you added (for example, 5).
Alternatively, navigate to Administration> Bulk Task Scheduler to check if the job was completed successfully.
Maximum number of EMCC base devices to add.
Include EMCC in the total number of devices that get supported in the cluster, using this calculation: phones + <= MaxPhones (of 2 x EMCC devices).
CUCM systems specify a MaxPhones value of 60,000.
The EMCC login does not affect the number of licenses that get used in the home cluster.
14.Configure Geolocation filter
Configure corporate settings and add a geolocation filter:
In CUCM Administration, choose System> Enterprise Parameters .
For the farm ID business setting, configure a single farm ID for each participating farm.
In CUCM Administration, navigate System> Geolocation Filter .
Click Add New .
Create a new geolocation filter.
Example name: EMCC Geolocation filter.
Specify the criteria for matching, such as country, state, and city.
feature 15.Configure EMCC
Configure the EMCC characteristic parameters:
In Cisco Unified Communications Manager Administration, navigate to Advanced Feature> EMCC Feature Configuration> EMCC .
In the EMCC Feature Configuration window that displays, configure these feature settings: Default TFTP Server for EMCC Login Device, EMCC Geolocation Filter, Default Server for Remote Cluster Update.
Note: Each characteristic parameter must be previously configured before you can choose them from the drop-down list box that associates with each characteristic parameter.
Note: You can keep the default values for other EMCC characteristic parameters or you can change as needed.
16.Configure SIP trunk
Configure one or two intercluster SIP trunks for EMCC.
Note: You can configure one trunk for the PSTN Access and RSVP agent services (in step 17) or one trunk for each service. You do not need more than two SIP EMCC trunks.
In CUCM Administration, choose Device> Trunk .
Click Add New .
Specify these settings: Trunk Type: SIP Trunk, Trunk Service Type: Extension Mobility Cross Batteries
Click on Next .
In the Trunk Configuration window that displays, specify the settings in the Device Information pane. These values show example values. Name: EMCC-ICT-SIP-Trunk-1 and Device Pool: Default
In the SIP Information pane, specify these example settings: SIP Trunk Security Profile: Non-Secure SIP Trunk Profile and SIP Profile: Standard SIP Profile
In the Geolocation configuration pane, specify this configuration: Send Geolocation information: Check this box.
Click Save to save the intercluster SIP trunk for EMCC.
17. Configure the service profile
Configure the EMCC intercluster service profile:
In CUCM Administration, choose Advance Specifications> EMCC Service Profile> EMCC Intercluster.
Check the active box in the EMCC pane.
Check the active box in the PSTN Access pane.
In the SIP PSTN Access Trunk drop-down list box, choose a SIP trunk that you configured in step 16.
Check the active box in the RSVP agent pane.
In the RSVP Agent SIP Trunk drop-down list box, choose another SIP trunk that you configured in step 16.
The click validate to validate your configurations.
If no failure messages display in the pop-up window, click Save .
18.Configure remote battery service
Configure the EMCC remote farm services:
Navigate to Administration> CUCM Features> Remote Cluster.
Click Add New.
In the Remote Cluster Configuration window that displays, configure these settings: Cluster ID: Make sure that this Cluster ID matches the enterprise parameter value of the other Cluster's Cluster ID and fully - name qualified: Use the IP address of the remote farm or a domain name that can resolve them to any node on the remote farm.
Note: TFTP is intentionally disabled because TFTP proxy is not supported with EMCC. The Configure Remote Cluster Services section of the Feature Configuration Guide for Cisco Unified Communications Manager states the following:
For the Extension Mobility Cross cluster, the TFTP check box should always be cleared.
19.Configure service Paramter
Configure the service parameters:
Navigate to > System> CUCM Service Settings.
From the Server drop-down list box , choose a server.
From the Service drop-down list box , choose Cisco Extension Mobility Service.
Click on the advanced button at the top of the window.
As needed, configure these service settings in the Clusterwide settings pane (the settings that apply to all servers): Maximum Inter-Cluster logon time and EMCC enable proxy: Set this value asTrue .
The note for EMCC, the call logs always get cleared.
The note for EMCC is still allowed, from several login procedures.
No comments:
Post a Comment