On 1/18/10 1:15 PM, Dale Worley wrote:
As with any problem like this, the best diagnostic is to run a trace of
a failed call, and see what went wrong:
http://sipx-wiki.calivia.com/index.php/Display_SIP_message_flow_using_Sipviewer
Dale
installed and working, see lots of pretty xml using more when I trace a
call that went through.
but, when I trace the failed calls:
sipx-trace --all-components --output /tmp/sipxtrace.txt 561706xxxx@
I get this:
more /tmp/sipxtrace.txt
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<sipTrace>
</sipTrace>
so, I don't think its sip, I think its dialplan or permissions.
I can't find anything that will help diagnose that.
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best Anti-Spam Product 2008, Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
