Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

MediaResourceListName : NULL_LIST


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


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
Cisco Employee

MediaResourceListName : NULL_LIST

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

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