sipx-trace -a -o tracefile.xml CALLID if you don't know the call id the to/from phone number works too.
rotate the logs before you make the test call and then when you use the phone number as the call-id you wont pick up any other calls in the trace. As an FYI, a sipx-trace is the starting point with all failed calls/trunk issues. So spend time learning to read them. -M >>> "[email protected]" <[email protected]> 05/10/12 12:10 PM >>> On Wed, 9 May 2012 17:50:29 -0500, [email protected] wrote: > Have not had the chance to do a trace but I did get their pcap. Ok, so I don't often have to run traces so I've forgotten how to. Searching, I've come up with lots of examples but am not sure which one is best for this purpose. Can someone give me a lead, url, on what I should run for a trace to find this problem? http://wiki.sipfoundry.org/display/sipXecs/Network+trace+capture+tool I gave the above a shot but am not sure this is all I need. I also gave this a try but same thing, not sure if this is what I need to post the results of. sipx-trace -P . -o merged.xml callid1 callid2 Mike _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
