Preview Tool

Cisco Bug: CSCuq70698 - CCM process cores, when transfer call to the same partyB

Last Modified

Sep 26, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.0(1.10000.24) 10.5(1.10000.7) 10.5(2.10000.5) 11.0(1.10000.10) 9.1(2.10000.28)

Description (partial)

CCM core dump, when transfer call  to same Party-B,

CUCM version: 10.5.1.X
CSCuo96552 will cause this condition in pre 10.5.1 versions.
Found an issue when try to execute a transfer scenario, and it cause CCM to Coredump.
The steps are:
Party-A (SIP endpoint) makes call to Party-B (SIP-endpoint), and call established.
Party-A transfers call to party-B.
Party-A completes Transfer successfully.
Party-B ends call.
Party-B rings.
Party-B answers.
This cause Core to Party-B ccm.

backtrace - CUCM
#0 0xf7710430 in __kernel_vsyscall ()
#1 0xf691eb11 in raise () from /lib/
#2 0xf69203ea in abort () from /lib/
#3 0x0837c35a in IntentionalAbort () at ProcessCMProcMon.cpp:88
#4 CMProcMon::verifySdlTimerServices () at ProcessCMProcMon.cpp:802
#5 0x0837c9ab in CMProcMon::callManagerMonitorThread (cmProcMon=0x4d4ce910) at ProcessCMProcMon.cpp:431
#6 0xf6c405a8 in ACE_OS_Thread_Adapter::invoke (this=0xd8717b10) at OS_Thread_Adapter.cpp:103
#7 0xf6c005f1 in ace_thread_adapter (args=0xd8717b10) at Base_Thread_Adapter.cpp:126
#8 0xf68d5b39 in start_thread () from /lib/
#9 0xf69d6d6e in clone () from /lib/
Bug details contain sensitive information and therefore require a 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.