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 32
Important Notes
Windows Computer System for CallConnector Server
The computer system performance and memory requirements are dependent on the
number of users configured for the CallConnector Mobility Service. See the
CallConnector Server datasheet for details.
Ports, UDP and TCP Connections
The CallConnector Server applications, including the Mobility Service, setup UDP and
TCP connections to UC500/CME and the each of the CallConnector Clients. See the
CallConnector Server Administrator Guide for the list of the ports that must be
available for the CallConnector Server applications to provide services. If the default
port is not available, then you must change the port setting from the CallConnector
Server wizard to an available port.
Additional Configuration of Cisco Smart CallConnector Operators
Function
What needs to be setup
Configure the
Operator’s IP
Phone(s)
The CallConnector Operator application allows the operators to control the
calls on their IP phone from the PC. This requires the phone to be
configured with directory numbers and features suitable for the operator
call handling functions, These include:
Personal Directory Number
Directory Numbers for the incoming call of each category (call queues)
Directory Numbers for the incoming call of each category (call queues)
Softkey Features including Transfer-to-Voicemail
Call Routing to
the Operator
Phones
Phones
There can be several categories of calls received by the operators each
requiring a distinct call treatment. Examples of such call categories might
include the Main Number calls, Customer Support calls, Sales calls or
include the Main Number calls, Customer Support calls, Sales calls or
Internal calls. The routing of these calls to the operator phones needs to
be configured in the Cisco Router. Generally these calls will be directed to
different extension numbers in the operator’s phone.
Multiple
Operators
Deployments
If the organization has multiple operators, the calls need to be distributed
to the operators. The recommended method is to use a hunt group for
each operator call queue.
Busy and Night
Service Routing
When the operators are not available during the work day the incoming
calls need to be routed either to an alternate number or to voice mail. For
off-hour call routing, the Cisco router night service routing can be enabled.
off-hour call routing, the Cisco router night service routing can be enabled.
Park and Page
Numbers
Park slots or directory numbers need to be configured on the router to
allow the operators to park the calls and make overhead announcements.
This requires:
Setting up the Park Ephone-DN in the router
Setting up the Park Ephone-DN in the router
Setting up the overhead paging circuits and their associated DNs
Telephony
Service
Parameters
Parameters
Voicemail number and Fac Standard need to be enabled to allow
operators transfer calls directly to CUE.
Hunt-group logout HLog is required for operators to perform hunt-group
Hunt-group logout HLog is required for operators to perform hunt-group
logout operation.