Activity

"Address family not supported by protocol binaddr=192.168.82.1" from the messages log sounds a bit strange. It's bindaddr in both sip.conf and iax.conf but that's not a protocol. Is there a spelling error in your dialplan or config files?

Jonas Bofjäll
added a comment - 25/Oct/10 3:19 AM "Address family not supported by protocol binaddr=192.168.82.1" from the messages log sounds a bit strange. It's bindaddr in both sip.conf and iax.conf but that's not a protocol. Is there a spelling error in your dialplan or config files?

Leif Madsen
added a comment - 01/Nov/10 2:34 PM Ya that's what I'm thinking as well. I don't even see bindaddr in the unistim.conf.sample file at all, so it's looking to me like there is some error in the configuration files.
Additionally, you should provide a backtrace using:
bt
bt full
thread apply all bt

Paul Belanger
added a comment - 01/Nov/10 3:04 PM I might be able to patch this, do you mind attaching a debug log (see below)?
—
We require a complete debug log to help triage the issue.
This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue:
http://svn.digium.com/svn/asterisk/trunk/doc/HOWTO_collect_debug_information.txt