Cisco Cisco Smart CallConnector Server and Advanced Client Maintenance Manual
Chapter 4 Cisco UC500/CME-ISR Configuration
4-12 Cisco CallConnector Server
Username and password are required to allow a TAPI connection to the IP Phone.
Username and password have to be less than 15 characters in length. (This is a Cisco
router restriction.)
router restriction.)
The IP-Phone has to be in service and registered for the ‘TAPI’ to be successful. If the
phone is disconnected, after a timeout the TAPI connection will fail.
phone is disconnected, after a timeout the TAPI connection will fail.
The Cisco router supports only one ‘TAPI’ connection to an ephone. Any additional
connection requests get rejected.
connection requests get rejected.
When a TAPI session is established, the TAPI client information can be viewed using
the ‘Show Ephone TAPI’ command. The TAPI client information displays the status
‘REGISTERED’ and the Client IP address.
the ‘Show Ephone TAPI’ command. The TAPI client information displays the status
‘REGISTERED’ and the Client IP address.
The Cisco router enforces unique usernames for the ephones; however in multiple
router environments, the system administrator will need to ensure that the usernames
are unique across the routers. The CallConnector Server will change duplicate
username to DUP-ip-address-username.
router environments, the system administrator will need to ensure that the usernames
are unique across the routers. The CallConnector Server will change duplicate
username to DUP-ip-address-username.
Ephone soft-key templates do not affect the CallConnector Client as the soft-keys are
available to the TAPI session even if they are not configured for the ephone.
available to the TAPI session even if they are not configured for the ephone.
4.6.1.3 Pre-Requisites for Connecting to Ephones:
Ephone must be configured with user name and password
There must be a phone device registered to that ephone
There must be network access for the TCP connections between the Cisco
There must be a phone device registered to that ephone
There must be network access for the TCP connections between the Cisco
router and the CallConnector Server
There must be no existing TAPI connections to that ephone. (The Cisco router
supports only one TAPI connection per ephone.)
The ephones must be selected using the Server Administration Wizard for it to be
controlled and must be associated with a user for the user to manage call using
the client.
the client.
4.6.1.4 Connection Recovery and Timeouts
The CallConnector Server tries to establish connections to all the ephones configured for the
CallConnector Server. Normally these ephones will be a sub-set of all the ephones in the Cisco
router. In the event these connections fail either at startup or during operation, the CallConnector
CallController Sever will try to re-establish these connections. The recoveries of these ephone
connections follow these rules:
CallConnector Server. Normally these ephones will be a sub-set of all the ephones in the Cisco
router. In the event these connections fail either at startup or during operation, the CallConnector
CallController Sever will try to re-establish these connections. The recoveries of these ephone
connections follow these rules:
The CallConnector Server will try to establish connection to the ephone multiple
times up to the Max-Retry count – an internal configurable parameter.
When the Max-Retry count is exceeded, the CallConnector Server will stop trying
to connect to the Cisco router for a period of time. This interval between the
retries is a configurable period and is set to 6 minutes by default.
retries is a configurable period and is set to 6 minutes by default.
If the connection cannot be re-established within the maximum retries, then
CallConnector Server will wait for a configurable time period and then return to
trying to re-establish the ephone connection.
trying to re-establish the ephone connection.
Note