We tried to get https://sipcapture.org/ up and going for doing sip traces across multiple clusters, but it just didn't speak CUCM very well and we just didn't have time to work with them on getting it to work. This was probably 18 months ago. It may be a solution, if you can get it to run.
On Mon, Sep 30, 2019 at 10:57 AM Sreekanth Narayanan (sreenara) via cisco-voip <cisco-voip@puck.nether.net> wrote: > Hey All! > > I'm reaching out to understand how call issues are troubleshot today > end-to-end within an enterprise. I wanted to get a sense of whether you all > use any applications that act as Central Logging servers for all the > applications that provide Collaboration services. > > For example, CUCM, UCCE/X, CUBE, GW (or other vendors like Mitel, Avaya > etc) all dumping their logs or CDRs to a central application that could > help you troubleshoot a call failure all the way from the Edge to the phone. > > Do you use some 3rd party logging applications that make the job easier > and get to the root cause quickly? > Or do you follow the traditional methods which involve checking the logs > on the first application in the call flow and then using the Session-ID / > Call-ID to correlate the same call on the next hop and so on? > > Regards > Sreekanth > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
