Thank you everyone, I appreciate that input. With the line changed to the
following it does distribute load evenly; we'll try adding different sets
soon.
#!define RTPENGINE_ADDR "udp:22.22.22.22:7724 udp:33.33.33.33:7724"
On Fri, 10 Nov 2023 at 05:11, Daniel-Constantin Mierla via sr-users <
You might be right.
I haven't used second parameter for set_rtpengine_set(), I don't recall
who implemented it, but maybe someone else can confirm if it is like
that and eventually add a clearer sentence there.
Cheers,
Daniel
On 09.11.23 16:26, Ben Kaufman wrote:
>
> From a strictly linguistic
On 08/11/2023 15.33, [EXT] David Cunningham via sr-users wrote:
Hello,
We have a Kamailio configuration with the following, however all the
load is going to the server at 22.22.22.22 (hiding the real IP
obviously) instead of being shared evenly between 22.22.22.22 and
33.33.33.33. Can anyone
Check your firewall. According the screenshot and your description - it
seems it is not delivered to kamailio service. So very possible blocked by
firewall.
On Thu, 9 Nov 2023, 12:53 Aaron Soto, wrote:
> I enabled CFGTRACE, but the logs don't show this BYE; the only BYE that
> appears is after
I enabled CFGTRACE, but the logs don't show this BYE; the only BYE that
appears is after 5 minutes, which is sent by Asterisk to Kamailio. It's
confusing because it seems like Kamailio isn't processing the BYE when i
make a hangup with my phone.
El 9/11/23 a las 11:46, Yuriy G escribió:
Hi Yurig,
Yes, GET/SET is working normally from kamailio if not using JSON.
Honestly, I didn’t get what do you mean by the below. Can you please elaborate
how to fix the issue?
Regards,
From: Yuriy G
Sent: Thursday, November 9, 2023 10:55 AM
To: Kamailio (SER) - Users Mailing List
Cc: Ali
Screenshot doesn't help more than raw BYE request would.
But mostly you need to look into kamailio service logs. Better with
CFGTRACE debugger parameter enabled. It will show you on which step BYE
handling was dropped. Also it may show you some meaningful output regarding
the reason it wss
Thank you for your response,
I have confirmed that the dialog module is indeed loaded. However, as I
mentioned before, after 2 minutes, the BYE messages are no longer
recognized by Kamailio, and I'm uncertain why this is occurring. Perhaps
sharing a screenshot from sngrep could offer more
Thank you, Daniel!
I was just confused because I do use set_rtpengine_set() with
rtpengine_manage() quite a lot, for some years now, and it works fine...
-- Alex
> On 9 Nov 2023, at 03:24, Daniel-Constantin Mierla via sr-users
> wrote:
>
> Hello,
> not sure why that remark is there, because
If you not involve dialog module, then kamailio won't care about dialog (
as it is Proxy, not UA)
The Indialog requests processing is done over proxy routing mechanisms (
rfc3261 paragraph 16 )
So, after mentioning above:
What you mean under "unrecognised" ?
On Thu, 9 Nov 2023, 10:18
Did you try to use not JSON but usual GET/SET? Do you have the same issue?
AFAIK - ndb_redis is a wrapper oven hiredis wrapper and doesn't implement
serialisation protocol for redis, so, whatever you send delivered to redis
being only wrapped via hirer's client library.
Btw if uou use lua < 5.2
Hi
> I have a scenario on wich requires sequential fork (up to 30 possible
> destinations) with different
> Call-ID for each leg. I am using topoh module enabled, but it always puts the
> same Call-ID.
> Someone have a solution for this scenario?
AFAIK that is not possible as Kamailio, being a
I'm encountering an issue with dialog handling in Kamailio. Initially,
everything functions correctly, and if a connection terminates within two
minutes, the BYE method works as expected. However, if the call exceeds two
minutes, the BYE method doesn't seem to be recognized, and there are no
Hello,
not sure why that remark is there, because contradicts with the first
paragraph that has:
"Sets the ID of the RTP proxy set to be used for the next
rtpengine_delete(), rtpengine_offer(), rtpengine_answer() or
rtpengine_manage() command."
-
14 matches
Mail list logo
