Hello John, The dispatcher module will simply push the configured destination SIP uri (from dispatcher table) as destination for the call ($du or $ru) - it is the t_relay() which will evaluate the destination from DNS point of view, doing NAPTR, SRV and A lookup - if there are multiple choices, weights will be used to select the result, but at the end only one IP will be used at a time. The other IPs may be used via dns-based failover if first IP results in timeout or 502 replies. The dns-based failover, if activated, will be automatically done by TM (as serial forking), totally transparent for the script.
Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05/07/2013 12:03 PM, John Quick wrote: > Sorry, I just realised there may be other factors in this duplicate INVITE > problem so it may not be connected with the DNS resolving to two IP's. > I would still be interested to know how dispatcher should behave when using > a host name that resolves to more than one IP. > > John Quick > Smartvox Limited > Web: www.smartvox.co.uk > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
