Cisco Cisco Smart CallConnector Server and Advanced Client
Cisco Smart CallConnector Server®, 2.1.010 Version
Release Notes for Cisco Smart CallConnector Server®, 2.1.010 Version
Page 36
A reproducible step to recreate the problem is to establish a two-way call and place
the call hold and resume more than 10 times then the STOP packets won't be sent by
the router due to the following error occurred (The same problem can happen when a
CXFER/CALLFORWARD flow occurred more than certain number of times):
575149: Mar 2 22:02:38.148: %AAA-3-BUFFER_OVERFLOW: Radius I/O buffer has overflowed -
Traceback= 0x826D8938z 0x826D94FCz 0x826D9EF8z 0x80D90C44z 0x80D962FCz 0x80D91F10z
0x802D560Cz 0x802BBEB4z
575150: Mar 2 22:02:38.148: RADIUS/ENCODE(00043785): build from list; FAIL
575151: Mar 2 22:02:38.148: RADIUS/ENCODE(00043785): build packet; FAIL
575152: Mar 2 22:02:38.148: RADIUS/ENCODE(00043785): unable to build packet; FAIL
575153: Mar 2 22:02:38.148: RADIUS/ENCODE(00043785): send packet; FAIL_NO_RETRIES
As a workaround, you can set the automatic clearing of call longer than the specified
period. These settings are under Cisco Systems->ccRDSTSP->SetupInfo
Ring Time Parameter= MaxSetupCallStateTimeout (Default value is 240)
Connected State Timeout= MaxConnectedCallStateTimeout (Default value is
3600)
Another option is to schedule automatic stop and restarts of the services nightly using
the Windows Task Scheduler to run the Configuration Manager with these command
parameters. Example: "C:\Program Files\Cisco Systems\Cisco Smart CallConnector
Server\ConfigurationManager.exe" /stopSvrs /startSvrs
CSCtn97678
Change the ephone username and after import using Schedule Task->Configuration
Manager. There are now two records – the user original record and a 2nd one is the
modified one.
During the SCC Server Configuration Manager import users from CME, a user is
associated with an ephone that has a username and password. If the user name
changes, the import does not have a way to differentiate between manually added
user records and these user records resulting from CME Config changes.
As a workaround, you will need to review the User Configuration from the
Configuration Manager and manually correct duplicates or incorrect user records.
CSCtn97675
Restart all the CallConnector Servers, the clients do not show connected calls.
There is no workaround, this situation will clear automatically once the call is dropped
and new calls are started.
CSCtn97673
Configuration Manager prompts "Registry is being written by a previous process.
Please wait a few seconds and try again" after restart all the CallConnector Servers
and is stuck in this state until click OK.
As a workaround, click on OK to continue.
Configuration Manager
Sometimes Configuration Manager is stuck at “Establish connection to Database
Server” step when Configuration Manager is started up or Configuration Manager