Cisco Cisco Smart CallConnector Server and Advanced Client Maintenance Manual
Overview
Administrator Guide 2-7
2.5.1 System SIP Server
The System SIP Server (ccSSS) provides CallConnector client and server applications authentication
(Registrar function) and routing of the SIP messages (Re-Direct Server function).
All CallConnector clients and servers first login to the System SIP Server at startup. This is the central
component that authenticates users and server applications and routes the SIP messages.
A failure of the System SIP Server will affect CallConnector system in the following ways:
(Registrar function) and routing of the SIP messages (Re-Direct Server function).
All CallConnector clients and servers first login to the System SIP Server at startup. This is the central
component that authenticates users and server applications and routes the SIP messages.
A failure of the System SIP Server will affect CallConnector system in the following ways:
1. All CallConnector clients and Server applications starting up will fail and provide ‘unable to
connect’ with SIP Server error message.
2. Existing connections will continue to be in place until the subscriptions or registrations timeout
and need to be renewed. These attempts will fail.
3. The Service Management indicates System SIP Server is stopped.
All CallConnector Server applications should be restarted upon SIP Server
connect’ with SIP Server error message.
2. Existing connections will continue to be in place until the subscriptions or registrations timeout
and need to be renewed. These attempts will fail.
3. The Service Management indicates System SIP Server is stopped.
All CallConnector Server applications should be restarted upon SIP Server
2.5.2 System Tracker Server
The System Tracker supports the automated recovery of the connections in the event of failures.
A failure of the System Tracker applications will affect CallConnector system in the following ways:
A failure of the System Tracker applications will affect CallConnector system in the following ways:
1. CallConnector clients starting up will not be able to receive the CallConnector Server status to
allow them to continue.
2. The CallConnector client user interfaces will be grayed out; as the clients will assume that all
the Server applications are down.
3. Established sessions (clients) will not know; will not get CallConnector Server failure
notifications.
4. Subscription timeouts causing re-subscribe will fail.
5. When the System Tracker returns; all subscriptions will need to be re-established.
6. To recover stop and restart System Tracker.
allow them to continue.
2. The CallConnector client user interfaces will be grayed out; as the clients will assume that all
the Server applications are down.
3. Established sessions (clients) will not know; will not get CallConnector Server failure
notifications.
4. Subscription timeouts causing re-subscribe will fail.
5. When the System Tracker returns; all subscriptions will need to be re-established.
6. To recover stop and restart System Tracker.
2.5.3 Database Server
The CallConnector Database Server provides access to the configuration, contact and transactional data
to all the CallConnector servers and clients.
The Database Server provides gateway functions between SIP messages and the SQL database
command. SIP User Agents such as CallConnector clients’ access configuration, contact and
transaction data from standard SQL databases by sending SIP messages to the Database Server. The
Database Server supports the SIP Message methods. When it receives a database request, it fulfills the
request from the attached SQL database and returns the data/response to the requestor.
Database Server supports synchronization feature; allowing add/delete/updates to be kept current.
to all the CallConnector servers and clients.
The Database Server provides gateway functions between SIP messages and the SQL database
command. SIP User Agents such as CallConnector clients’ access configuration, contact and
transaction data from standard SQL databases by sending SIP messages to the Database Server. The
Database Server supports the SIP Message methods. When it receives a database request, it fulfills the
request from the attached SQL database and returns the data/response to the requestor.
Database Server supports synchronization feature; allowing add/delete/updates to be kept current.