<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">Hi,</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "><br></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">We also use Bria as SIP client and OpenSIPs and works very well together, so if you see errors like registering or so on, that is on your side.</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">Possible problems:</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">1. Bria incorrect settings, for Presence set Presence Agent (not peer2peer)</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">2. Incorrect
script in opensips.cfg</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "><br></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "><br></div><div><font class="Apple-style-span" face="arial, helvetica, sans-serif" size="2">We started few month ago from the ground to build a NAT traversal solution and I can list here few resources will help you pass the </font><font class="Apple-style-span" face="arial, helvetica, sans-serif" size="2">beginners problems: </font></div><div></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">1. Building telephony systems with OpenSIPs: <span class="Apple-style-span" style="font-family: 'Times New Roman'; font-size: medium; "><a
href="http://www.amazon.com/Building-Telephony-Systems-OpenSIPS-1-6/dp/1849510741">http://www.amazon.com/Building-Telephony-Systems-OpenSIPS-1-6/dp/1849510741</a></span></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "> Will help you to solve: basic script for REGISTER/PUBLISH/NOTIFY, MySQL authorization, far-end NAT traversal with rtpproxy, accounting</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">2. Examples from the above book, should be downloaded</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">3. This user list, usually we got quick answers, mostly from developers of ag-projects</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">4. Book: SIP Handbook. Services, Technologies, and Security of Session Initiation Protocol (CRC Press 2009)</div><div style="color:
black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">5. Book: Wiley.Internet.Communications.Using.SIP.Delivering.VoIP.and.Multimedia.Services.with.Session.Init</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "><br></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "><br></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">Regards,</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; ">Liviu</div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "><br></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; "><br><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Mark Holloway
<mh@markholloway.com><br><b><span style="font-weight: bold;">To:</span></b> OpenSIPS users mailling list <users@lists.opensips.org><br><b><span style="font-weight: bold;">Sent:</span></b> Mon, July 4, 2011 6:23:56 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [OpenSIPS-Users] SIP Registration Failure - 484 Address Incomplete<br></font><br>
Odd, even though I now get 200 OK from OpenSIPS after registering I still receive 484 Address Incomplete after the 200 OK even though the endpoint is registered. <div><br></div><div><br><div><div>On Jul 3, 2011, at 11:35 AM, Mark Holloway wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap:break-word;">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;">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 rel="nofollow">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 rel="nofollow">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp</a>></div><div> Contact Binding: <<a rel="nofollow">sip:1000@192.168.1.116:62018;rinstance=3b31a8f560e5c3bc;transport=udp</a>></div><div> To:
"Mark"<<a rel="nofollow">sip:1000@192.168.1.20</a>></div><div> SIP Display info: "Mark"</div><div> SIP to address: <a rel="nofollow">sip:1000@192.168.1.20</a></div><div> From: "Mark"<<a rel="nofollow">sip:1000@192.168.1.20</a>>;tag=fbaf644d</div><div> SIP Display info: "Mark"</div><div> SIP from address: <a rel="nofollow">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 rel="nofollow" ymailto="mailto:Users@lists.opensips.org" target="_blank" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br><span><a target="_blank"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></span><br></blockquote></div><br></div></div>_______________________________________________<br>Users mailing list<br><a rel="nofollow" ymailto="mailto:Users@lists.opensips.org" target="_blank" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br><span><a target="_blank" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></span><br></blockquote></div><br></div></div></div><div style="color: black; font-family: arial, helvetica, sans-serif; font-size: 10pt; position: fixed; "></div>
</div></body></html>