Cisco Cisco Unified CallConnector for Microsoft Windows
Cisco Systems, Inc.
Page
42
42
Cisco Unified CallConnector Mobility Service
Technical Overview
CME/CUE Setup Summary for Mobility Service
Function
What needs to be setup
Radius Accounting Parameters
RADIUS messages can be generated by CME for calls that
originate or terminate on the CME endpoints. The UCC system
uses these messages to obtain the call state and calling/called
numbers. The UCC Server includes the RADIUS server
functionality and requires the CME to be setup to send the
RADIUS messages of the required format, type and frequency.
The section on ‘Setting Up Radius Accounting’ provides details
on the CME setup, UCC configuration and verifying that the
messages are being received.
originate or terminate on the CME endpoints. The UCC system
uses these messages to obtain the call state and calling/called
numbers. The UCC Server includes the RADIUS server
functionality and requires the CME to be setup to send the
RADIUS messages of the required format, type and frequency.
The section on ‘Setting Up Radius Accounting’ provides details
on the CME setup, UCC configuration and verifying that the
messages are being received.
Mobility ephones and ephone-
DN
DN
The Mobility Service uses ephones for answering the Single
Number Reach calls and for making the reach out calls. These
ephones need to be configured in the CME and then selected
and associated with the Mobility application using the Server
Wizard.
Number Reach calls and for making the reach out calls. These
ephones need to be configured in the CME and then selected
and associated with the Mobility application using the Server
Wizard.
The mobility-ephones have specific attributes:
a. A ‘virtual MAC-address’ is assigned to each mobility-
ephone.
b. Each ephone needs to have at-least three single-line
ephone-DN configured
c. Ephones need to have Ad-hoc conference control capability
Note: In multiple router configurations, mobility-ephones have to
be provisioned from each of the routers as the Mobility Service
uses ephones that are on the same router as the user’s ephone.
be provisioned from each of the routers as the Mobility Service
uses ephones that are on the same router as the user’s ephone.
CME Conferencing Options
The Mobility Service uses the CME conferencing feature to
bridge the caller and user calls. Both hardware and software
conferencing is supported by the Mobility Service. However
hardware conferencing is required for the Mid-call and DISA
features. If hardware conferencing is enabled on the CME, then
ad-hoc conferencing has to be configured for use by the mobility-
ephones.
bridge the caller and user calls. Both hardware and software
conferencing is supported by the Mobility Service. However
hardware conferencing is required for the Mid-call and DISA
features. If hardware conferencing is enabled on the CME, then
ad-hoc conferencing has to be configured for use by the mobility-
ephones.