Hi
I have created a kamailio container with docker and two asterisk container
And this is my dispatcher list:
*1 sip:asterisk:50601 sip:asterisk2:5060*
and this is my both asterisk SIP.conf
*[Kamailio]host=kamailioport=5060insecure=invitetype=friendcontext=from-internal*
The problem is that
The error indicates kamailio can not resolve the location of asterisk2. Try
checking the dns (can you resolve it on the kamailio box?) or using the IP.
-- Fred
> On Jul 13, 2019, at 07:09, Amir wrote:
>
> Hi
> I have created a kamailio container with docker and two asterisk container
> And t
Hello,
Did you add SRV record for each server in your DNS server?
On Sat, Jul 13, 2019 at 6:07 PM Fred Posner wrote:
>
> The error indicates kamailio can not resolve the location of asterisk2. Try
> checking the dns (can you resolve it on the kamailio box?) or using the IP.
>
> -- Fred
>
>
> On
I do not have a DNS server, Docker User-defined networks has it's own built
in DNS server,
The problem is when I stop a container its DNS record would be deleted and
therefore kamailio server could not check server health.
I think if I could tell kamailio server that IF you did not find a DNS
recor
Hello Amir,
what is your issue exactly:
- because of the missing DNS entry the dispatcher module would not detect the
asterisk server as "down"
- because of the missing DNS entry your Kamailio would not (re)start properly
You could try with flag 16 to disable DNS resolution at startup in your
Hi Henning
Thank you for clearing that up, I have 3 problem which you have mentioned 2
of them:
- because of the missing DNS entry your Kamailio would not (re)start
properly: I tried flag 16 as you mentioned but still dose not work
1 sip:asterisk:7060 16
1 sip:asterisk2:7060 16
1 sip:asterisk3:706
Sorry for mistyping :
I can make it work like this:
Start Kamailio first Then start asterisk containers Then restart *KAMAILIO*
On Sun, Jul 14, 2019 at 2:50 PM Amir wrote:
> Hi Henning
> Thank you for clearing that up, I have 3 problem which you have mentioned
> 2 of them:
> - because of the mi
as option you can reload dispatcher table instead of kamailio restart.
kamctl dispatcher reload
On Sun, Jul 14, 2019 at 1:27 PM Amir wrote:
> Sorry for mistyping :
> I can make it work like this:
> Start Kamailio first Then start asterisk containers Then restart
> *KAMAILIO*
>
>
> On Sun, Jul
Thank you, Maybe I should develop a health check mechanism and save the
result in kamailio db and after that:
kamctl dispatcher reload
On Sun, Jul 14, 2019 at 3:23 PM Sergey Safarov wrote:
> as option you can reload dispatcher table instead of kamailio restart.
> kamctl dispatcher reload
>
>
>
>
If the dns resolution fails, don’t you get the event route
dispatcher:dst-down
fired?
You could use that route to remove the entry from the dispatcher list.
David
On Sun, 14 Jul 2019 at 12:29, Amir wrote:
> Thank you, Maybe I should develop a health check mechanism and save the
> result in kam
All of these seem like hacks to resolve the problem of you not being able to
resolve the hostname.
Perhaps there’s a docker setting or dns you can use to provide stability or
investigate why the host isn’t being resolved.
If the host doesn’t exist when you start kamailio then clearly it will
Thank you David, I would try that later.
On Sun, Jul 14, 2019 at 6:06 PM Fred Posner wrote:
> All of these seem like hacks to resolve the problem of you not being able
> to resolve the hostname.
>
> Perhaps there’s a docker setting or dns you can use to provide stability
> or investigate why the
Thank you Fred, Yes I think I would go for that.
On Sun, Jul 14, 2019 at 6:06 PM Fred Posner wrote:
> All of these seem like hacks to resolve the problem of you not being able
> to resolve the hostname.
>
> Perhaps there’s a docker setting or dns you can use to provide stability
> or investigate
The easiest solution is to add in the kamailio machine /etc/hosts file the ip
addresses associated to asterisk and asterisk2 hosts.
Hope to have helped.
Kind regards
Federico Santulli
NHM s.r.l.
Via Raffaello Sanzio, 88
81031 Aversa (CE)
Italy
E-Mail federico.santu...@nhm.it
Mobile +39.335.466
i think the bestway is static ip for ip nodes in dispatcher
сб, 13 июл. 2019 г. в 14:10, Amir :
>
> Hi
> I have created a kamailio container with docker and two asterisk container
> And this is my dispatcher list:
> 1 sip:asterisk:5060
> 1 sip:asterisk2:5060
> and this is my both asterisk SIP.conf
15 matches
Mail list logo
