[Users] t_relay does not follow RFC3263 "Locating SIP Servers"
franz.edler at ycn.com
Mon Sep 5 13:19:20 CEST 2005
> 1. openser does not do NAPTR lookups as defined in step 1 of 3263. It
> starts with step 2 (SRV lookups)
Yes, I know meanwhile. But it only makes an SRV lookup for _sip._udp, not
for _sip._tcp, if URI contains no transport parameter (as usual).
> 2. Are you sure there are NAPTR records for your domain?
> $ dig fenet2.at NAPTR
> ; <<>> DiG 9.2.4 <<>> fenet2.at NAPTR
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 60927
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
I indeed had a problem in my zone-file. Meanwhile the NAPTR records are
> 3. If the URI contains the transport=tcp paramter, SRV lookups for _tcp
> will be done, otherwise _udp will be used.
Yes, this is what I observed. I did not try with a URI containing a
> IMO, if no transport paprameter is present, openser should also try _tcp
> if _udp fails.
Yes. This is also my suggestion to be RFC 3263 compliant.
More information about the Users