[reSIProcate] How does a client build a DNS lookup that restr icts the responses to UDP?

[Dave Mason]

Woohoo!  That works.  I took a look at RFC 2396 but couldn't really tell
what the valid parameters are that come after the ";" in a URI.  I see
"transport" used as an example in RFC 3261.  Is there a place where the SIP
URI spec is fully defined?  Maybe I missed it.

In response to your last comment, I find that if there are no TCP SRVs
defined, it will use the IP address from the A record for domain.com, with
port 5060, transport UDP.  That looks right to me - I guess UDP and 5060 are
pre-defined for that case?

Thanks,
Dave 

-----Original Message-----
From: Byron Campen [mailto:bcampen at estacado.net] 
Sent: Tuesday, December 05, 2006 5:04 PM
To: Dave Mason
Cc: resiprocate-devel at list.resiprocate.org
Subject: Re: [reSIProcate] How does a client build a DNS lookup that
restricts the responses to UDP?

	Well, you can always do sip:user at domain.com;transport=udp. Also, if
your stack doesn't support TCP, it should use UDP instead. Lastly, if there
are no TCP SRVs in DNS, you should also get UDP results.

Best regards,
Byron Campen

> Hi,
>
> I find that if a DNS server is set up with NAPTR records for a domain 
> that specify TLS/TCP is most preferred, then TCP, the UDP last, and a 
> client does a DNS lookup for sip:user at domain.com (through 
> DnsInterface), the DNS server only returns records for TLS/TCP.
>
> How do you configure the lookup on the client side to ask for only UDP 
> records, even if they are least preferred on the server?
>
> Regards,
> Dave
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel