>>> On 1/26/2011 at 6:05 PM, in message <[email protected]>, "Matthew >>> Kitchin (public/usenet)" <[email protected]> wrote: >> >>I've attached some wireshark call flow graphs of a couple different scenarios. >>I have the pcap files for each one and would be glad to share them. >> >>I will work on sip-traces tonight or tomorrow. I'm just a little more >>familiar with wireshark.
Yeah, these call flows aren't that helpful. You can see that the phone at 10.81.3.253 (the phone that should be getting the transfer) sends a 180 ringing but there is never a 200 OK. It never picks up. But we need to see what is in the invite packet. A sipx-trace is very simple. - Putty to sipx - Rotate logs so you can narrow down the results with: logrotate -f /etc/logrotate.d/sipxchange - Make a test call - cd to the logs directory: cd /var/log/sipxpbx - Trace that specific call using the phone number (its best to use the call-id but phone number works if its unquite): sipx-trace --all-components --output trace.xml 777-123-4567 - Use Winscp and copy the trace.xml to your desktop. - open in sipviewer If you have the actual wiresharks you can email them to me offlist if you like. -M _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
