I believe it's still open also on the bugtracker. There are a few reported senarios with these kind of problems.
Some of them where solved with the recent 'ast_gethostbyname' fix. Are you running a recent version?
Btw, Ignoring OPTIONS is not a valid option (:-) whether sip proxy or not, Asterisk doesn't do it correctly either.
The host should respond with 200/OK if the call >could< succeed theoretically if it were an INVITE or else it should send a
404 or maybe a 487(? hmm, have to look) see the RFC for details.
Brett Nemeroff wrote:
Hi All,
I had an unusual problem today; I'm sure it's a configuration problem.
I had 2 phones behind a nat device and I had qualify=300 in both extensions config. The device I was talking to was an edgewater traffic shaper,/Sip Proxy. Since it is acting as a sip proxy, it was ignoring the OPTIONS messages that * was sending, and thus * interpreted that as the extensions being down.
I removed the qualify lines and sip reload [ed]. The extension still showed up as "UNREACHABLE" instead of "UNMONITORED". I had to do a full restart to get it to stop sending the OPTIONS messages.
What did I do wrong here? How can I make a change to qualify without restarting?
Thanks all,
Brett
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
