Yo be precise, rtpengine or rtpproxy. You can use either, unless you are
planning to wss clients
On Thu, 18 Jul 2019 at 08:03, sagar malam wrote:
> Satish,
>
> RTP would bypass Kamailio via asterisk unless you use RTPENGINE with
> Kamailio.Kamailio alone does not support RTP/RTCP protocol.It is
Satish,
RTP would bypass Kamailio via asterisk unless you use RTPENGINE with
Kamailio.Kamailio alone does not support RTP/RTCP protocol.It is a SIP
proxy.
You can get more information here :
https://www.kamailio.org/docs/modules/4.4.x/modules/rtpengine.html
On Thu, Jul 18, 2019 at 11:44 AM
I am configuring kamailio as registar and asterisk for media services.
in kamailio + asterisk integration how two SIP clients RTP traffic
will flow, are they go via Asterisk or directly from kamailio ?
___
Kamailio (SER) - Users Mailing List
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
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
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
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
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
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
>
>
>
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
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
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
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
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
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
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
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
Hello,
kamailio - asterisk integration tutorial is more complex than what you
need to do load balancing of calls to asterisk. For load balancing,
start from the config in the dispatcher module docs:
-
https://www.kamailio.org/docs/modules/stable/modules/dispatcher.html#dispatcher.ex.config
Good morning,
I want to Loadbalance calls equally to asterisk servers,
i have already tried with opensips but didnt work for me,
i want to try kamailio now, i have tried with the tutorial of " Kamailio 4.0.x
and Asterisk 11.3.0 Realtime Integration using Asterisk Database" but i got
some errors
Hello guys,
I'm following this guide:
https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
And I have the following schema:
Phone A -> Kamailio->Asterisk-> Phone B
(10.0.8.249)(10.0.6.123)(10.0.3.144) (10.0.13.23)
I
20 matches
Mail list logo
