Thanks Daniel.
I was thinking SQL is an overkill for route lookup.
If an instance of Kamailio is setup as a Registrar/Redirect with a Redis
(Pub/Sub) backend, is there a way for a Kamailio proxy instance to subscribe to
dynamic routes from the Redis which can be injected into call variables?
Why would you go through the trouble of encapsulating that in some sort of
presence layer? Just query Redis directly with redis_cmd() from the ndb_redis
module.
Whether you need an SQL database or can get by with Redis is a complex topic.
It's ultimately a question of how complicated a feature
Hello,
you can consider mtree module if you don't need to restart very often.
Eventually you can run it in an instance of kamailio that is used as
redirect server, having the main proxy instances routing to it and
handling the redirect responses.
Another option is using some nosql system,
Hi,
I'm finding a problem submitting a HTTP POST using the http_query(). Currently
running on kamailio version: 4.1.8 on Debian wheezy.
Normally this command has been worked fine, but since the body of the message
increased (the POST data size is around 2000 bytes ) I start to get the
I thought I made a patch to address this:
https://github.com/kamailio/kamailio/commit/56c417b5ae29f0dd0387d59a6e9d8d203deb8855
although it was on 14 Dec 2014, which I think is after 4.1.8.
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Hi Daniel,
Thanks for the quick answer. I've just set the http_query_timeout to 30 sec
as I also need to do a long pulling.
Regards,
Joao
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: quinta-feira, 11 de Junho de 2015 20:22
To:
I don't know if you want to do that. That's going to block the given Kamailio SIP receiver process, of which there are a small, fixed number, for up to 30 seconds. http_query() is not implemented in an
I had realized that later on. However for the time being just using this for
demo purposes. I’ll lower down the value nonetheless.
Thanks!
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Alex
Balashov
Sent: quinta-feira, 11 de Junho de 2015 20:38
To: Joao Alves
Hi,
I'm looking for an option to mark CANCELs which are generated locally by
Kamailio after receiving a 200 OK for another fork of the same call.
In the tm module documentation I found the option
local_cancel_reason
which enables this. This option is available (and turned on by default) in
Hello,
On 11/06/15 14:27, Sebastian Damm wrote:
Hi,
I'm looking for an option to mark CANCELs which are generated locally
by Kamailio after receiving a 200 OK for another fork of the same call.
In the tm module documentation I found the option
local_cancel_reason
which enables this.
Yes, 4.3 should have all fixes in 4.2.
Cheers,
Daniel
On 12/06/15 06:06, Ding Ma wrote:
OK, we’ll try to update and report back. Wonder if the latest 4.3 has
all the fixes went into the latest 4.2.x. We already have plan to
upgrade to 4.3.
Thanks.
On Jun 10, 2015, at 10:01 AM,
Note that there is another module named CURL in a personal branch by
Olle (look in git repository for branches starting with oej/) -- that
module should do async http query -- for some demos it might be enough.
Otherwise, you can use the existing async mechanisms for doing the query
with utils
OK, we’ll try to update and report back. Wonder if the latest 4.3 has all the
fixes went into the latest 4.2.x. We already have plan to upgrade to 4.3.
Thanks.
On Jun 10, 2015, at 10:01 AM, Daniel-Constantin Mierla mico...@gmail.com
wrote:
It was a fix for maxload during 4.2.x, but don't
13 matches
Mail list logo
