[Devel] SRV defaults to UDP only

Tim tim at zattco.com
Thu Apr 5 16:30:56 CEST 2007


Thanks Bogdan
this is exactly what I needed to know
In this case the DNS records are pointing to a customer network and they own
the entries.
My intention was to ask them to publish NAPTR records specifically resolving
to TCP so I can take out the hack in resolve.c
Now I am better equipped to explain.

Tim

On 4/5/07, Bogdan-Andrei Iancu <bogdan at voice-system.ro> wrote:
>
> Hi Tim,
>
> if there is no NAPTR record, the protocol to be used is selected based
> on RUR information - if this does not contain any specific info (like
> transport parameter), UDP is used by default.
>
> when doing DNS failover, you do not do it based on your server
> capabilities, but on the destination server capabilities. If NAPTR is
> not available, you have no clue what proto the destination server
> supports, so you cannot do a failover based on protocol.....
>
> at least this is my understanding :)
>
> regards,
> bogdan
>
> Tim Missner wrote:
> > Hello,
> >
> > While trying to implement failover using DNS SRV records we have found
> > only udp is resolved as a transport, even if the proxy is configured
> > to use TCP.
> >
> > In resolve.c function sip_resolvehost it appears when no protocol is
> > set udp is the default.
> >
> > Is this by design?
> >
> > We never see _sip._tcp.domain.com being resolved.
> >
> > I was able to force this by setting *proto = PROTO_TCP sip_resolvehost.
> >
> > So my question is this, with the absence of NAPTR records how can we
> > get openser to lookup both upd and tcp SRV records?
> >
> > Thanks,
> >
> > Tim
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Devel mailing list
> > Devel at openser.org
> > http://openser.org/cgi-bin/mailman/listinfo/devel
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openser.org/pipermail/devel/attachments/20070405/562d433b/attachment.htm


More information about the Devel mailing list