Please excuse the re-post...
Greetings,
After adding a new Device Pool and corresponding MRGL, Region, Location, Physical location, etc... the RTMT notification utility has consistently reported MediaResourceListExhausted events. These notifcations were never triggered before the addition of the new programming. Please provide any insight as to what is causing and how to correct.
The new Device Pool was built for a deployment of phones in an adjacent building within the campus and not for true 'off-site' deployment.
Thank you!
If you click on the event, you should be able to see what kind of resource has exhausted ie. Conference bridge, MTP etc.
Please rate useful posts.
Thank you, I can right click the Alert Central notification but it doesn't mention the specific resource. The e-mail notifications mention it is a:
MediaResourceType : 9
and it lists both Device Pools, the original and the new one, but nothing else. The help file for this alert mentions that this can be triggered by a media resource not being available or a mis-configuration but not much else is listed.
The threshold for the notification was increased to 8 per hour in an attempt to decrease the warnings, nevertheless it triggered due to the
accumulation. Here is the body of the notification:
Number of MediaResourceListExhausted events exceeds configured threshold during configured interval 8 within 60 minutes on cluster BPGUSCRU.
There are 12 MediaResourceListExhausted events (up to 30) received during the monitoring interval From Wed Sep 11 14:34:37 PDT 2013 to Wed Sep 11 15:34:37 PDT 2013:
MediaResourceListName : MRGL_NMB
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:15:01 PDT 2013
MediaResourceListName : MRGL-CBU
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:15:01 PDT 2013
MediaResourceListName : MRGL_NMB
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:14:37 PDT 2013
MediaResourceListName : MRGL-CBU
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:14:37 PDT 2013
MediaResourceListName : MRGL_NMB
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:14:14 PDT 2013
MediaResourceListName : MRGL-CBU
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:14:14 PDT 2013
MediaResourceListName : MRGL_NMB
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:14:02 PDT 2013
MediaResourceListName : MRGL-CBU
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:14:02 PDT 2013
MediaResourceListName : MRGL_NMB
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:11:50 PDT 2013
MediaResourceListName : MRGL-CBU
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 15:11:50 PDT 2013
MediaResourceListName : MRGL_NMB
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 14:36:22 PDT 2013
MediaResourceListName : MRGL-CBU
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Wed Sep 11 14:36:22 PDT 2013
MRGL_NMB is the new MRGL built and associated to a new Device Pool addition (DP_NMB) intended to be used for an adjacent building (Building B). The IP deployment in Buidling B was begun last year and when all IP phones were assigned to the only Device Pool at that time, there were close to zero notifications of this type - none that I can remember.
The alarms began after the new Device Pool DP_NMB was built and a test batch of phones were changed from the original Device Pool over to the new Device Pool.
1 thing that is noteworthy: all notifications include both MRGLs every time... as if a call from a phone in 1 device pool made to a phone in another device pool triggers the alarm - ??? don't know but trying to make sense of the alarms. I've grouped these by coloring the matches - please note the time stamps on the pairs as they are the same.
Here is the body of an older notification. Please note that this was before the threshold was changed. Every notification included the following match or pair of MRGL's.
Number of MediaResourceListExhausted events exceeds configured threshold during configured interval 0 within 60 minutes on cluster BPGUSCRU.
There are 2 MediaResourceListExhausted events (up to 30) received during the monitoring interval From Tue Sep 10 12:34:20 PDT 2013 to Tue Sep 10 13:34:20 PDT 2013:
MediaResourceListName : MRGL_NMB
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Tue Sep 10 12:54:31 PDT 2013
MediaResourceListName : MRGL-CBU
MediaResourceType : 9
AppID : Cisco CallManager
ClusterID : XXXX
NodeID : XXXXXXSU001
TimeStamp : Tue Sep 10 12:54:31 PDT 2013
Thank you for your help!
"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
