Preview Tool

Cisco Bug: CSCta98856 - CCM core calling out MGCP PRI when receiving empty UserUser IE

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)

ccm process cores when calling out an MGCP PRI.

output of CLI command <cmdBold>utils core analyze<nocmdBold> shows:
 #0  0x00dc97a2 in _dl_sysinfo_int80 () from /lib/
#1  0x00649815 in raise () from /lib/tls/
#2  0x0064b279 in abort () from /lib/tls/
#3  0x00bb353b in __gnu_cxx::__verbose_terminate_handler () from /usr/local/cm/lib/
#4  0x00bb1251 in __cxxabiv1::__terminate () from /usr/local/cm/lib/
#5  0x00bb1286 in std::terminate () from /usr/local/cm/lib/
#6  0x00bb13cf in __cxa_throw () from /usr/local/cm/lib/
#7  0x00b6d2a4 in stlp_std::__stl_throw_length_error () from /usr/local/cm/lib/
#8  0x08205a8b in stlp_priv::_String_base<char, stlp_std::allocator<char> >::_M_throw_length_error (this=0xec7e398) at /vob/ccm_tpl/release/include/stlport/stl/_string.c:615
#9  0x08205d10 in stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >::_M_append (this=0xec7e398, __first=0xec7a064 "", __last=0xec7a063 "�") at /vob/ccm_tpl/release/include/stlport/stl/_string.c:137
#10 0x08205feb in stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >::_M_assign (this=0xec7e398, __f=0xec7a064 "", __l=0xec7a063 "�") at /vob/ccm_tpl/release/include/stlport/stl/_string.h:479
#11 0x09a0ce3e in retrieveUuie (fSdlMsgData=0xec79794 "", fUuie=@0xec7e390, fSignalMsgDataSize=@0x2ba2748) at /vob/ccm_tpl/release/include/stlport/stl/_string.h:664
#12 0x08b6d1e0 in MGCPBhHandler::handleTranslateIsdnToSdlRes (this=0xec78910, s=@0x2bac170) at ProcessMGCPBhHandler.cpp:2780
#13 0x08b8cb53 in MGCPBhHandler::wait_SdlDataInd (this=0xec78910, s=@0xfb96938) at ProcessMGCPBhHandler.cpp:1787
#14 0x08bac87c in MGCPBhHandler::fireSignal (this=0xec78910, sdlSignal=@0xfb96938) at /vob/ccm/Common/Include/Sdl/SdlProcessBase.hpp:174
#15 0x0a04c6e8 in SdlProcessBase::inputSignal (this=0xec78910, rSignal=0xfb96938, traceType=SdlSystemLog::SignalRouterThread, highPriority=0, normalPriority=0, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:397
#16 0x0a0544b2 in SdlRouter::callProcess (this=0xe191428, _sdlSignal=0xfb96938, _deleteSignal=@0x2bb2d07, _traceType=SdlSystemLog::SignalRouterThread, _hp=0, _np=0, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:371
#17 0x0a053ed7 in SdlRouter::scheduler (sdlRouter=0xe191428) at SdlRouter.cpp:281
#18 0x0055d5fb in ACE_OS_Thread_Adapter::invoke (this=0xec2ec80) at OS_Thread_Adapter.cpp:94
#19 0x0051fcbf in ace_thread_adapter (args=0x0) at Base_Thread_Adapter.cpp:137
#20 0x003d93cc in start_thread () from /lib/tls/
#21 0x006eb1ae in clone () from /lib/tls/

CM SDI traces show reception of an empty UserUser IE:
07/23/2009 14:00:19.547 CCM|In  Message -- PriAlertingMsg -- Protocol= Pri4essProtocol|<CLID::CUCM1-Cluster><NID::><LVL::Significant><MASK::0040>
07/23/2009 14:00:19.547 CCM|Ie - Q931UserUserIe -- IEData= 7E 00 |<CLID::CUCM1-Cluster><NID::><LVL::State Transition><MASK::0040>

The empty UserUserIE could potentially be in messages other than Alerting.

CUCM receives an empty UserUser IE from the PSTN
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.