Cisco Cisco Smart CallConnector Server and Advanced Client Release Notes
Cisco Smart CallConnector Server®, 2.1.010 Version
Release Notes for Cisco Smart CallConnector Server®, 2.1.010 Version
Page 11
Configuration Manager is the Server Setup Utility. This is automatically started after
installation. If not running, then start it from Program Files->Cisco Systems-> Smart
CallConnector Server.
Changing login account or server IP address requires re-boot. Connection Error may
also require re-boot
Trail vs. Full-License: The Login dialog displays number of days left. If the trial period
has expired, you will be prompted to enter the PAK-ID or serial number
Default Administrator username = cisco and Password = cisco. Click on Login.
If you get the message “Establishing Connection to Database” and it does not clear;
Try restarting the CallConnector Services from Windows Services
CallConnector Service Applications
The CallConnector Server applications include the following:
Database Server – provides SIP-based access to the user profile and configuration,
directory data and read/write access to CME configuration
CallController Server maintains all the SCCP connections to the CME. Clients receive
call state information and can send commands to make, answer calls
Presence Server includes Radius Server. It receives telephone status information from
CME, maintains and broadcasts presence, location and phone status to the clients
Instant Message Server enables the group chat features for clients; One-to-One IM is
peer-to-peer
SIP Server is a standard SIP registrar; System Tracker supports error recovery by
notifying service up/down
The application and the debug file names are shown in the table below:
Server Application
Application File Name
Debug Trace File
Database Server
ccDatabaseServer
ccdatabaseserver.log
CallController Server
ccCallControllerServer
cccallcontrollerserver.log
Presence Server
ccPresenceServer
ccpresenceserver.log,
ccradiusserver.log
Instant Message Server
ccIMServer
ccIMserver.log
System SIP Server
ccSystemSIPServer
ccsystemsipserver.log
System Tracker
ccSystemTracker
ccsystemtracker.log
Local SIP Server
ccLocalSIPServer
cclocalsipserver.log
Note: Do not delete the administrative account. You will not be able to log in to the
Configuration Manager. You will need one administrative account to log in to the
Configuration Manager.