I just did it, if you use git, you can pull and have it. Nightly built
Debian packages will make it available tomorrow if you use
apt repository with nightly builds.
Cheers,
Daniel
On 03.12.18 11:37, Patrick Murphy wrote:
Thanks for the fix Daniel,
Any ETA on when this will be backported to 5.2?
------------------------------------------------------------------------
*From:* Daniel-Constantin Mierla <miconda(a)gmail.com>
*Sent:* Thursday, November 29, 2018 10:54 AM
*To:* Patrick Murphy; Henning Westerholt; sr-users(a)lists.kamailio.org
*Cc:* José Seabra
*Subject:* Re: [SR-Users] Dispatcher with a naptr address as destination
Hello,
a solution for the moment would be to add a new flag to mark the
destination for no-keepalive, so it is considered to be active always.
Right now the issue is created by the fact that keepalive is enabled
and the implementation needs the IP at start up.
However, for NAPTR/SRV records, there can be a different IP returned
for each query, so it might not bring much benefits to do keepalives
in such cases. This can be added if someone wants to develop it.
Then, just to refresh, you can do SRV based load balancing without
dispatcher, it is done by tm and core automatically.
Cheers,
Daniel
On 29.11.18 11:32, Patrick Murphy wrote:
Here you
go:
https://github.com/kamailio/kamailio/issues/1743
The reason I posted here first was that I wanted to rule out any
obvious thing I was missing here since there already was a thread
open on it.
Cheers,
Pat
------------------------------------------------------------------------
*From:* Henning Westerholt <hw(a)kamailio.org> <mailto:hw@kamailio.org>
*Sent:* Wednesday, November 28, 2018 9:06 PM
*To:* sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
*Cc:* Patrick Murphy; José Seabra; miconda(a)gmail.com
<mailto:miconda@gmail.com>
*Subject:* Re: [SR-Users] Dispatcher with a naptr address as destination
Am Mittwoch, 28. November 2018, 15:06:03 CET schrieb Patrick Murphy:
I ran into the exact same issue. DNS resolution
is just stuck on A
records
for OPTIONS pings irrespective of DNS options. I
can see correct DNS
resolution with kamcmd dns.lookup but kamcmd dispatcher.list
command does
not even list the gateways which have a NAPTR/SRV
DNS name.
Dispatching INVITEs also fails because none of the trunks are actually
loaded in memory for kamailio to process or for me to be able to
set its
state manually to active.
Any plans on fixing this behavior?
Hi Patrick,
the best would be probably to file a issue about this behavior on our
GitHub
tracker. Then it could be analyzed in more details.
Best regards,
Henning
--
Henning Westerholt -
https://skalatan.de/blog/
Kamailio services -
https://skalatan.de/services
Kamailio security assessment -
https://skalatan.de/de/assessment --
Daniel-Constantin Mierla --
www.asipto.com <http://www.asipto.com>
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
Kamailio World Conference --
www.kamailioworld.com <http://www.kamailioworld.com>
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --
www.asipto.com
<http://www.asipto.com>