MediaResourceListName : NULL_LIST

George Banuelos · ‎09-26-2013

Greetings,

Previously, there were MediaResourceListExhausted alarms being possibly triggered by a few misconfigured phones. The mis-configuration found was that a few phones had been moved to a newly built device pool, but the MRGL was not changed on the suspected phones. This was corrected by moving all IP phones to the same device pool and changing the MRGL for all IP Phones to match. Then the new, unused device pools and MRGLs were deleted. This cleared the previous MediaResourceListExhausted alarms, but now... there are new MediaResourceListExhausted alarms:

MediaResourceListName : NULL_LIST <--- new alarm

MediaResourceType : 4 <--- new alarm type

AppID : Cisco CallManager

ClusterID : XXXXXXXX

NodeID : XXXXSU001

Please assist.

Thank you!

"I believe that the greatest work of God has not been in the miraculous, nor in the spectacular, incomprehensible Creation, but rather I believe it was accomplished on the Cross where He Himself purchased the redemption of His Bride... the salvation of m

Manish Gogna · ‎09-26-2013

Hi George,

There are probably a few more devices which do not have the correct MRGL with resources like MOH / Annunciator etc. You should look at the corresponding detailed callmanager trace for the same time stamp and there will be a media manager trace snippet which will show the reource that is either not present in the MRGL or is exhausted. Detailed ccm traces can be collected using the following link

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml

Basically, devices need to be identified using the trace and their configuration corrected so that their MRGL contains appropriate resources.

HTH

Manish