<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>From the wiki:</div><div><br></div>"<span style="font-family: sans-serif; font-size: 13px; line-height: 19px; background-color: rgb(255, 255, 255); ">There IS a wrinkle to this special case: If you have a URL of the form <<a href="sip:user@example.com:5055">sip:user@example.com:5055</a>> the client should NOT look for a NAPTR or SRV, but instead go straight to looking for an A or AAAA for the host <a href="http://example.com">example.com</a> (i"</span><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;"><br></span></font></div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;">This is an error in the RFC that we are trying to fix in the IPV6 wg of the SIP Forum. Software should NOT find A *OR* AAAA. It should look up both and then try them according to Happy Eyeballs - in parallell with a small advantage for IPv6. If we do serial forking here, we have in worst case a 32 second timeout in SIP over UDP, which is not acceptable.</span></font></div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;"><br></span></font></div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;">Every customer should require fixes and every developer should try to fix this...</span></font></div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;"><br></span></font></div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;">Some slides on these issues:</span></font></div><div>* <a href="http://www.slideshare.net/oej/sipforum-sip-ipv6-discussion-slides">http://www.slideshare.net/oej/sipforum-sip-ipv6-discussion-slides</a></div><div>* <a href="http://www.slideshare.net/oej/sip-ipv6-time-for-action">http://www.slideshare.net/oej/sip-ipv6-time-for-action</a></div><div><br></div><div>I hope to see FreeSwitch at SIPit 30 in February so we can test this and other issues!</div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;"><br></span></font></div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;">/O</span></font></div><div><font face="sans-serif"><span style="font-size: 13px; line-height: 19px;"><br></span></font><div><div>9 jan 2013 kl. 00:21 skrev Michael Collins <<a href="mailto:msc@freeswitch.org">msc@freeswitch.org</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite">I couldn't stand it, so I added Lawrence's info to this page:<br><a href="http://wiki.freeswitch.org/wiki/DNS#Explanation_of_DNS.2FSRV.2FNAPTR">http://wiki.freeswitch.org/wiki/DNS#Explanation_of_DNS.2FSRV.2FNAPTR</a><br>
<br>Cheers,<br>MC<br><br><div class="gmail_quote">On Tue, Jan 8, 2013 at 2:56 PM, Michael Collins <span dir="ltr"><<a href="mailto:msc@freeswitch.org" target="_blank">msc@freeswitch.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Lawrence,<br><br>Thanks for this explanation. It was very well written. I'm looking for a place to codify this on the wiki so that it gets preserved... :)<br><br>-MC<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">
On Tue, Jan 8, 2013 at 1:56 PM, Lawrence Conroy <span dir="ltr"><<a href="mailto:lconroy@insensate.co.uk" target="_blank">lconroy@insensate.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi there,<br>
at the risk of butting in on someone else's party ...<br>
Nope; your interpretations is NOT best practice.<br>
I have some sympathy, as the term domain is overloaded within fS.<br>
<br>
A sip address consists of a userpart and a domain part -- e.g., <<a href="sip:user@sipdomain">sip:user@sipdomain</a>><br>
The sip domain is similar to an email domain -- e.g., <mailto:<a href="mailto:user@maildomain" target="_blank">user@maildomain</a>><br>
With email, you need to do a lookup of the MX record in DNS to find the FQDN of the machine that handles mail for the domain.<br>
With SIP (see RFC 3263), you do a lookup on the SRV record (at _sip._udp.<sipdomain>) to find the machine that handles SIP<br>
registrations/incalls for the domain. That also gives you the port on which that machine is listening.<br>
(Yup, you can also have a NAPTR record in the domain to tell you where the SRV record is, but many folks don't bother -- for Best Practice, you should, but ...)<br>
<br>
There IS a "get out" clause in the SIP specs for RFC 2543 (AKA legacy) support that means most SIP clients will look for the SRV and, if it can't be found (or there's an IP address rather than a DNS -style domain, in which case the SIP client won't bother hunting the SRV), the client will guess that the domain has a machine (i.e. it will look for an A or AAAA record), and also guess it's listening on 5060 (the default port).<br>
Email is the same (mail to <a href="mailto:fred@example.com" target="_blank">fred@example.com</a>, and strictly the sender will do a check for a MX and then look for an A record for <a href="http://example.com/" target="_blank">example.com</a>, and try there).<br>
<br>
However, relying on that default "get out" clause is definitely NOT what you should do for BCP.<br>
Using the hostname as the sip domain is a kludge -- the FQDN with A record usually works, but it's not what you want to do.<br>
<br>
SO ... get yourself a domain, put a D2U NAPTR at that domain, put a SRV at _sip._udp.<domain>, and you're done. No need for an A record at that domain at all.<br>
<br>
(RFC 3263 is not too hard to read, for a change -- it's certainly shorter than RFC 3261, and it even has an ASCII art diagram :).<br>
<br>
all the best,<br>
Lawrence<br>
<div><br>
On 8 Jan 2013, at 21:05, Steven Schoch wrote:<br>
<br>
> On Fri, Dec 28, 2012 at 8:47 PM, Tim St. Pierre <<br>
> <a href="mailto:fs-list@communicatefreely.net" target="_blank">fs-list@communicatefreely.net</a>> wrote:<br>
><br>
>> Hi Steven,<br>
>><br>
>> I would recommend using a proper domain name as much as possible. For<br>
>> one, it looks<br>
>> nicer! A SIP URI is supposed to be user@domain like an e-mail address<br>
>> is, and I hope that<br>
>> one day URI dialing will be common place, so we might as well do it right<br>
>> the first time.<br>
>><br>
><br>
> What you're saying is that "domain" should really be a fully-qualified host<br>
> name that points via DNS to the actual host on which FreeSwitch is running.<br>
> That is, the domain should be "<a href="http://pbx.example.com/" target="_blank">pbx.example.com</a>" instead of just "<br>
> <a href="http://example.com/" target="_blank">example.com</a>", as the last example would most likely point to a web server,<br>
> not the SIP server. Do I have that right?<br>
><br>
> Next, in the configuration for Polycom phones (for example), there are 2<br>
> fields that both have the userid. In the example in<br>
> <a href="http://wiki.freeswitch.org/wiki/Polycom_configuration" target="_blank">http://wiki.freeswitch.org/wiki/Polycom_configuration</a> it has:<br>
><br>
> reg.1.auth.userId="1000"<br>
><br>
> and<br>
><br>
> reg.1.address="1000@fs.domain.local"<br>
><br>
> How is the "address" value used? Is that sent in the SIP registration<br>
> message? If that's the case, what does Freeswitch do with it?<br>
><br>
> --<br>
> Steve<br>
</div>> _________________________________________________________________________<br>
> Professional FreeSWITCH Consulting Services:<br>
> <a href="mailto:consulting@freeswitch.org" target="_blank">consulting@freeswitch.org</a><br>
> <a href="http://www.freeswitchsolutions.com/" target="_blank">http://www.freeswitchsolutions.com</a><br>
><br>
> FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
> <a href="http://www.cudatel.com/" target="_blank">http://www.cudatel.com</a><br>
><br>
> Official FreeSWITCH Sites<br>
> <a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br>
> <a href="http://wiki.freeswitch.org/" target="_blank">http://wiki.freeswitch.org</a><br>
> <a href="http://www.cluecon.com/" target="_blank">http://www.cluecon.com</a><br>
><br>
> FreeSWITCH-users mailing list<br>
> <a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
> <a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br>
<br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org" target="_blank">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com/" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com/" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org/" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com/" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Michael S Collins<br>Twitter: @mercutioviz<br><a href="http://www.freeswitch.org/" target="_blank">http://www.FreeSWITCH.org</a><br>
<a href="http://www.cluecon.com/" target="_blank">http://www.ClueCon.com</a><br>
<a href="http://www.ostag.org/" target="_blank">http://www.OSTAG.org</a><br><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Michael S Collins<br>Twitter: @mercutioviz<br><a href="http://www.freeswitch.org/" target="_blank">http://www.FreeSWITCH.org</a><br><a href="http://www.cluecon.com/" target="_blank">http://www.ClueCon.com</a><br>
<a href="http://www.ostag.org/" target="_blank">http://www.OSTAG.org</a><br><br>
_________________________________________________________________________<br>Professional FreeSWITCH Consulting Services:<br><a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>http://www.freeswitchsolutions.com<br><br>FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>http://www.cudatel.com<br><br>Official FreeSWITCH Sites<br>http://www.freeswitch.org<br>http://wiki.freeswitch.org<br>http://www.cluecon.com<br><br>FreeSWITCH-users mailing list<br>FreeSWITCH-users@lists.freeswitch.org<br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org<br></blockquote></div><br></div></body></html>