[SR-Users] NAPTR priorities doesn't seem to work properly

[Iñaki Baz Castillo]

2011/6/9 Iñaki Baz Castillo <ibc at aliax.net>:
> According to NAPTR:
>
>  ~$ host -t naptr oversip.net
>  oversip.net has NAPTR record 5 50 "S" "SIPS+D2T" "" _sips._tcp.oversip.net.
>  oversip.net has NAPTR record 10 50 "S" "SIP+D2T" "" _sip._tcp.oversip.net.
>  oversip.net has NAPTR record 20 50 "S" "SIP+D2U" "" _sip._udp.oversip.net.
>  oversip.net has NAPTR record 40 50 "S" "SIP+D2S" "" _sip._sctp.oversip.net.
>  oversip.net has NAPTR record 50 50 "S" "SIPS+D2S" "" _sips._sctp.oversip.net.
>
> So it should try TLS over TCP first, if it fails try TCP and if it
> fails try UDP.

Just to confirm, the above NAPTR record for "SIPS+D2T" has order 5 and
preference 50. According to RFC 2915:

   Order
      A 16-bit unsigned integer specifying the order in which the NAPTR
      records MUST be processed to ensure the correct ordering of
      rules.  Low numbers are processed before high numbers

   Preference
      A 16-bit unsigned integer that specifies the order in which NAPTR
      records with equal "order" values SHOULD be processed, low
      numbers being processed before high numbers.


So as my domain oversip.net has no entries with same order, preference
value doesn't matter. And of course, SIP over TLS should take
preference.

-- 
Iñaki Baz Castillo
<ibc at aliax.net>