Am Montag, 18. März 2019, 19:42:30 CET schrieb Kevin Olbrich:
> I rolled back the change and Kamailio still sends the challenge. Seems
> I took the wrong transaction during debug...
>
> Am Mo., 18. März 2019 um 19:16 Uhr schrieb Kevin Olbrich :
> > Hi!
> >
> > I am implementing forwarding of
On Mon, Mar 18, 2019 at 12:43:25PM +0200, Володимир Іванець wrote:
> I found much better description of the problem here
> https://lists.kamailio.org/pipermail/users/2008-August/019070.html.
Wow. That is some rather ancient history. And I think reflects a
different place in the evolution of my
I rolled back the change and Kamailio still sends the challenge. Seems
I took the wrong transaction during debug...
Am Mo., 18. März 2019 um 19:16 Uhr schrieb Kevin Olbrich :
>
> Hi!
>
> I am implementing forwarding of SUBSCRIBE (BLF) to an Asterisk behind
> Kamailio.
> This works but Kamailio
Hi!
I am implementing forwarding of SUBSCRIBE (BLF) to an Asterisk behind Kamailio.
This works but Kamailio is not requesting for Auth.
I then added SUBSCRIBE to:
https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg#L746
And it now challenges the client correctly.
Why does this
Hello,
I am not sure I understand what you are looking for? A variable that you
can use as a key per branch? Or per call? Maybe you can give an example
how you want to use it and expected behavior, then we may be able to
give some hints about what can be used.
Cheers,
Daniel
On 18.03.19 11:43,
On 3/18/19 7:23 AM, Daniel-Constantin Mierla wrote:
>
> Hello,
>
> this should be fixed by commit
> 2e3e72cfe906bf08b0c940d4e461890dd54b30c6 in branch 5.2 (fixed in
> master as well). I will backport to 5.1 and try to plan a new release
> in the near future.
>
> Cheers,
> Daniel
>
Indeed, it is
Hi,
I wanted to achieve the following scenario with Kamailio and
Asterisk/FreeSwitch
Kamailio as a trunk for Receiving incoming calls and forward to Asterisk and
Make outgoing calls. My current working setup like this
VoIP Provider -> Kamailio -> Asterisk Clusters
Where Kamailio(NAT for
Hello,
setting tcp_children=1 is not a god option for scallability, practically
you set kamailio to process a single tcp message at one time, on high
traffic, that won't work well.
Maybe try to set tcp_children to 2 or 4, that should make an eventual
race appear faster.
Regarding the pid, if it
I found much better description of the problem here
https://lists.kamailio.org/pipermail/users/2008-August/019070.html.
Also I figured that calling *reg_fetch_contacts* and saving appropriate
*$(ulc(callee=>addr)[$var(i)])* in
*event_route[tm:branch-failure:FAILURE]* will
allow to match
Am Donnerstag, 14. März 2019, 14:19:22 CET schrieb Alex Balashov:
> Perhaps a component-orientated view is not the correct one here. It
> almost sounds like what is being sought is a kind of "cookbook of
> Kamailio patterns"[1], if you like. This answers a lot of questions
> that also capture
Hi,
I am new at Kamailio, I have installed a vicidial goautodial box and having
some headaches.
I can see at starup logs the following message:
Mar 18 02:12:34 edialer1 /usr/sbin/kamailio[4028]: ERROR: db_mysql
[km_my_con.c:129]: db_mysql_new_connection(): driver error: Can't connect to
Hello,
ok, I will have it in mind and try to implement before freezing 5.3.
Cheers,
Daniel
On 16.03.19 13:34, Ilie Soltanici wrote:
> Daniel,
>
> Sounds good, would be nice to have some improvements on usrloc module,
> like requested in this topic:
>
>
Hello,
this should be fixed by commit 2e3e72cfe906bf08b0c940d4e461890dd54b30c6
in branch 5.2 (fixed in master as well). I will backport to 5.1 and try
to plan a new release in the near future.
Cheers,
Daniel
On 17.03.19 23:09, Jon Bonilla (Manwe) wrote:
> Hi all
>
> A customer of mine has some
13 matches
Mail list logo
