<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I resolved it. Forgot to uncomment one very important part of the cfg file.<div><br></div><div><pre class="escaped">if (!save("location"))
sl_reply_error();
exit;
}</pre><div><br></div><div><br></div><div><div>On Jul 3, 2011, at 11:31 AM, Mark Holloway wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I have OpenSIPS 1.6.4 configured as a SIP Registrar with mysql. It is configured to challenge SIP registrations with authentication. Keeping it simple, I've used opensipsctl to add user 1000 with password 1000 and set the IP/SIP Domain of OpenSIPS is 192.168.1.20. I am attempting to register using Counterpath Bria 3.1 (Mac). Bria sends the initial registration to OpenSIPS and it properly responds with a 401 Unauthorized, but after Bria responds to the 401 challenge OpenSIPS responds with 484 Address Incomplete.<div><br></div><div>Looking at the docs I noticed OpenSIPS will send 484 if the username is not in the Request-Line. For example, OpenSIPS wants 1000@192.168.1.20 but Bria sends 192.168.1.20. The way Bria registers, the username portion (1000 in this case) is only in the Contact, To, and From headers. The R-URI line does not include the username portion. Has anyone else encountered this?</div><div><br></div><div><br></div><div>==</div><div>Bria's response to 401 challenge</div><div>==</div><div><br></div><div><div>Session Initiation Protocol</div><div> <b> Request-Line: REGISTER <a href="sip:192.168.1.20">sip:192.168.1.20</a> SIP/2.0</b></div><div> Method: REGISTER</div><div> [Resent Packet: False]</div></div><div><br></div><div><br></div><div><div> Contact: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp</a>></div><div> Contact Binding: <<a href="sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp</a>></div><div> To: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20</a>></div><div> SIP Display info: "Mark"</div><div> SIP to address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20</a></div><div> From: "Mark"<<a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20</a>>;tag=fbaf644d</div><div> SIP Display info: "Mark"</div><div> SIP from address: <a href="sip:1000@192.168.1.20">sip:1000@192.168.1.20</a></div><div> SIP tag: fbaf644d</div></div><div><br></div><div><br></div></div>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br></blockquote></div><br></div></body></html>