Re: [reSIProcate-users] NAPTR for TLS only
TLS transports are not just reserved for SIPS uris. If TLS is the only NAPTR record, it should be used, even for a sip: URI. If you using resip, it must of course have TLS transport enabled before it will do that.
Scott
On Fri, Jan 11, 2013 at 2:06 PM, Daniel Pocock
<daniel@xxxxxxxxxxxxx> wrote:
I'm just wondering if anyone can comment on expected and actual behavior
if there is only a NAPTR record for TLS, e.g. I have:
sip5060.net. IN NAPTR 10 0 "s" "SIPS+D2T" ""
_sips._tcp.sip5060.net.
and I don't have any entry for "SIP+D2U" or "SIP+D2T"
If some third party repro instance (e.g. sip-server.example.org)
receives a request from a user trying to call sip:user@xxxxxxxxxxx, with
a sip: rather than sips: URI, should it use the "SIPS+D2T" result, if no
other result is available?
Or should it ignore the NAPTR record and try to find the default SRV
record such as _sip._udp.sip5060.net ?
Should there be another NAPTR record to translate sip: to sips: using a
regex perhaps, or would such a NAPTR be a bad thing?
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/