Done!<br>Thanks,<br>MC<br><br><div class="gmail_quote">On Tue, Jan 8, 2013 at 3:35 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 Michael, folks,<br>
if you're going to codify it, I did slightly simplify things:<br>
(full disclosure -- I disagreed with it at the time which is probably why I forgot to mention it -- honest).<br>
<br>
There IS a wrinkle to this special case: If you have a URL of the form <<a href="http://sip:user@example.com:5055" target="_blank">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" target="_blank">example.com</a> (i.e., there's a machine called <a href="http://example.com" target="_blank">example.com</a>, and it is handling SIP traffic for that domainpart).<br>
Basically, if you see a colon in the domainpart, you're looking for a machine -- otherwise you're looking for a NAPTR (and/or a SRV at _sip._udp.<sipdomain>).<br>
<br>
I'd put that before the paragraph starting "However, relying on ..."<br>
<br>
Curiously enough, the old 2543-compliant servers did hunt the SRV rather than giving up and looking for an A, so this was a change. Such fun was had re-writing implementations (plural) and testing them yet again. Sigh.<br>
<br>
all the best,<br>
Lawrence<br></blockquote><br>
</div><br>