Guest

Preview Tool

Cisco Bug: CSCtb72590 - CallBackManager generated core dump after ssInfoInd

Last Modified

Feb 01, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

6.1(3.2103.1)

Description (partial)

Symptom:

<P>CUCM 6.1(3) CCM service crashes with Core Dump generated.</P>

<P>Core Dump analysis points CallBackManager exception.</P>

Conditions:

<P>Crash happens while we try to access the mDeviceNameToPidTable for an offspring associated with a phone device.</P>

<P>mOffspring= mDeviceNameToPidTable.find(std::string(ssInfoInd.deviceName1.ea))->second;</P>

<P>This happens when both the cborig as well as cbterm is stopped. The corresponding info is removed from CallBack hash.</P>

<P>Later when we receive SsInfoInd for the phone device ( Eg: SEP001F9E26AC67) we search mDeviceNameToPidTable.</P>

<P>3530092209| 2009/08/24 14:21:48.496| 004| SdlSig    | SsInfoInd                             | wait                          | CallBackManager(4,100,44,1)     | Cdcc(4,100,175,4290939)         | (4,100,81,1).542395564-(SEP001F9E26AC67:172.19.134.116)| [R:NP - HP: 0, NP: 3, LP: 3, VLP: 1, LZP: 0 DBP: 0]</P>

<P>Since there is no entry for this device in the hash we would crash at this line :
mOffspring = mDeviceNameToPidTable.find(std::string(ssInfoInd.deviceName1.ea))->second;</P>
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.