Cisco Cisco Unified CallConnector for Microsoft Windows

 

Cisco Systems, Inc.

 Page 

99 

 

99 

Overview 

This chapter describes the common error conditions that occur with the Unified 
CallConnector Mobility Service and steps to solving these problems. 

Description 

The SNR does not launch after a personal routing policy is created. 

Possible 
Causes 

•  Automation server is not running  
•  The ephones in CME are not available  
•  The personal routing policy is not setup correctly 

Procedures 

Step 1.  Launch the CTIServer Server Manager to check the 

automation server status making sure it is “Started”. If not, 
click Stop and wait until all servers are stopped then click 
Start. 

Step 1.  Launch the Cisco CallConnector Server Wizard and go to the 

Automation Ephone Pool setup page to verify the ephone pool 
setup making sure the ephones are assigned correctly. Also, it 
is required to assign SNR application to at least one ephone 
pool. 

Step 2.  Check the personal routing policy’s condition checks. Making 

sure all the enabled conditions are matched. 

 

Description 

The Mid-Call Features doesn’t respond to the user’s input once an SNR 
session is established. 

Possible 
Causes 

•  Mid-Call Features is not enabled 
•  Hardware Conferencing is not enabled 

Procedures 

Step 1.  Launch the Cisco CallConnector Server Wizard and go to the 

Automation Mobility Service setup page.  

Step 2.  Check the “Allow mid-call to access features” option is enabled 

in the Single Number Reach Options section. 

Step 3.  Go to the Settings to Access CME/US500 Features setup 

page making sure that the option “Use Hardware