It was the port in the LCR table! You're the man! Thanks so much for your
help.
On Mon, Jan 23, 2017 at 12:45 AM, Carsten Bock wrote:
> Hi,
>
> can you try the sip-dig command on that particular domain?
> If you set that domain in script or from a module (e.g. Dispatcher),
> don't set a port. Ac
Hi,
can you try the sip-dig command on that particular domain?
If you set that domain in script or from a module (e.g. Dispatcher),
don't set a port. According to RFC 3263, the DNS-records are treated
differently, if no port is set (e.g. "redacted.hostname.here.com:5060"
will produce a different r
Thanks for the response!
DNS lookups work in Kamailio as long as use_dns_failover is set to "off."
It's only when the failover is enabled that they break. I think this means
it's not a DNS issue, but something in Kamailio.
I should mention we're pointing to Verizon's services with many many
thous
Hi,
we have the following settings and those work fine for us (Kamailio 4
and later):
# Do SRV-Loadbalancing:
dns_srv_lb=yes
# Always prefer IPv6:
dns_try_ipv6=yes
# DNS-Based failover
use_dns_failover=yes
# Query NAPTR-Records as well (we use NAPTR, so the client can detect
the outbound Proxy (P
Hello, everyone!
I'm trying to enable dns_srv_lb but I'm stuck just before I can get there.
If I don't enable use_dns_failover, lookups work and calls route but always
to the first host. We need to load balance, so that doesn't work very well.
If I enable use_dns_failover, the lookups stop workin
