Found similar question in archives - so workarounded with $ru modification.
Thank you!
On Fri, Jan 2, 2015 at 4:21 PM, Dmytro Bogovych
wrote:
> Well, I found problem.
> The resumed INVITE transaction was sent to LOCATION route instead of RELAY.
>
> However I see another problem now - t_relay() at
Well, I found problem.
The resumed INVITE transaction was sent to LOCATION route instead of RELAY.
However I see another problem now - t_relay() attempts to send resumed
transaction to bad destination address.
Jan 2 13:41:37 voipobjects /usr/local/sbin/kamailio[18186]: ERROR: tm
[../../forward.h
Greetings.
I'm trying to adopt kamailio to handle incoming calls / generate push
notifications for softphone running on Windows Phone 8.
Starting point was this publication
http://www.kamailio.org/events/2014-KamailioWorld/day2/26-Daniel-Constantin.Mierla-Kamailio.cfg-Async.pdf
I adopted the scrip
On 12/13/2014 01:01 PM, Ahmed Salem wrote:
I expect about 300,000 to 400,000 end points and maybe 10% of them will
send simultanoues requests per second, so will one instance still be
enough?
It's hard to say due to the multitude of variables involved, but
personally, I think you can do this
Hi Alex,
Thanks for your help.
I think t_replicate is the best option for me.
I expect about 300,000 to 400,000 end points and maybe 10% of them will
send simultanoues requests per second, so will one instance still be
enough?
And what is the ratio between shared memory and available RAM if my mac
On 12/13/2014 12:33 PM, Ahmed Salem wrote:
Is there any other way other than t_suspend/t_continue that I can use to
scale kamailio and still support push notifications.
Well, one factor is that Kamailio is very high-performant and scales
very well in just one instance. Just how many clients d
Hi Alex,
Thanks for your reply.
Is there any other way other than t_suspend/t_continue that I can use to
scale kamailio and still support push notifications.
Thanks
Ahmed
On Sat, Dec 13, 2014 at 6:57 PM, Alex Balashov
wrote:
>
> The servers don't share transactions; just having the index and l
The servers don't share transactions; just having the index and label
stored in a shared DB isn't enough. What really has to be shared are the
data structures and other metadata stored in the runtime instance of
Kamailio.
So, you can't do that.
On 12/13/2014 04:14 AM, Ahmed Salem wrote:
Hi,
Hi,
I have 2 kamailio servers behind a load balancer.
How can I use t_suspend on one server and t_continue on the other one. I
already have the index and label of the transaction saved in a common
database shared by the two kamailio servers.
The reason I want to do this is for push notifications
