January 31, 2001
|CallManager Version 3.0(6)||No comments.|
Problem DescriptionUnder certain conditions, the CallManager may restart. The problem is a race condition that can be encountered in normal operation with H323/Intercluster trunks. The problem will be noticed when dialing a number associated with a route list to an H323 gateway or another CallManager cluster via an intercluster trunk. If the calling party performs an onhook/offhook sequence during the setup phase of the call, the CallManager's Signal Distribution Layer (SDL) router process will enter a race condition and the CallManager service will terminate unexpectedly.
BackgroundWhen stationD process receives the ccNotifyReq message and there is no chassis interface (CI) associated with the StationCdpc process, then before we display the information in CcNotifyReq message, another check is made to make sure there is a valid CI to route pattern association; otherwise, it will crash the CallManager.
Problem SymptomsThe CallManager service may crash and restart. The Cisco CallManager (CCM) trace file on the CallManager will indicate:
SDL Router Services Declared dead
Workaround/SolutionThis is resolved in 3.0(7), now available on Cisco.Com. Due to the severity of this bug, you are advised to upgrade to Call Manager 3.0(7) by following the instructions below:
- Read the 3.0(7) Readme First Document. The filename is "ciscocm-fmu.3-0-7ReadmeFirst.pdf".
- Upgrade to Call Manger 3.0(7). The image name is "ciscocm-fmu.3-0-7.exe".
DDTSTo follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
|CSCds92393||SDL Router Services Declared dead....CM will restart|
For More InformationIf you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods: