Done! Thanks, MC On Tue, Jan 8, 2013 at 3:35 PM, Lawrence Conroy <lconroy@insensate.co.uk>wrote:
Hi Michael, folks, if you're going to codify it, I did slightly simplify things: (full disclosure -- I disagreed with it at the time which is probably why I forgot to mention it -- honest).
There IS a wrinkle to this special case: If you have a URL of the form < sip:user@example.com:5055> the client should NOT look for a NAPTR or SRV, but instead go straight to looking for an A or AAAA for the host example.com (i.e., there's a machine called example.com, and it is handling SIP traffic for that domainpart). 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>).
I'd put that before the paragraph starting "However, relying on ..."
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.
all the best, Lawrence