Cisco Bug: CSCvu14309 - CUCM cores due to memory leaking DMMSStationD and MobileClientD process instances
Sep 01, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
10.5(2.10000.5) 11.5(1.10000.6) 11.5(1.15075.1) 12.0(1.10000.10) 12.5(1.10000.22)
Symptom: The Cisco CallManager Service Cores due to memory leaking DMMSStationD and MobileClientD process instances. The core file created should be 4GB (the point at which the service cores when the VmSize of the CCM process reaches the maximum amount of memory) CUCM Detailed traces will show the below signal in the singlereg_wait state: 46863102.000 |10:25:20.135 |SdlSig |DeviceDeleteInd |singlereg_wait |DMMSStationD(2,100,218,125896) |SIPStationInit(2,100,75,1) |2,100,42,1.2340162^*^* |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] Name=TCTCISCO123 DeleteOrReset Type=1 However in the example above, the DMMSStationD(2,100,218,125896) instance will not be stopped. Conditions: Registered mobile Jabber devices (TCT or BOT) reseting or restarting due to changes in hunt group login, call forward, or any other change notification, etc...
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases