Cisco CallManager is the only component you need to collect traces from, unless you want the syslog that has a copy of the alarm (get Application Event Logs in that case).
When you collect Cisco CallManager traces there will only be two files, sdi (ccm*.txt) and sdl (SDL*.txt). You don't need to worry about the SDL traces, so find the timestamp your alarm was generated, then look for the ccm*.txt file that covers that timestamp. Your alarm will be located in the file, work backwards from there to see what was going on. -Ryan On Aug 6, 2014, at 1:12 PM, Carlo via cisco-voip <[email protected]<mailto:[email protected]>> wrote: What I was looking for is which of the 30 or so files has the Media resource logs in it. Sent from my iPad On Aug 6, 2014, at 7:52 AM, Brian Meade <[email protected]<mailto:[email protected]>> wrote: Set CallManager traces to Detailed on all nodes then pull Cisco CallManager Traces using RTMT under Trace&Log Central->Collect Files next time the issue occurs. On Wed, Aug 6, 2014 at 10:41 AM, Carlo via cisco-voip <[email protected]<mailto:[email protected]>> wrote: I have CUCM 8.6 and getting media resources exhausted. Which log file can I look at to see were the problem is. Thanks Carlo Sent from my iPad _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
