Hi Henning,
It's NOT working since 3.2 version.
GET /xcap-root/xcap-caps/global/index HTTP/1.1
Connection: close
Host: 10.120.100.210:5060
User-Agent: Jitsi/2.10.5550
HTTP/1.1 401 Unauthorized
Via: SIP/2.0/TCP 10.120.100.241:54882
WWW-Authenticate: Digest realm="xcap",
Hi,
what would be the reason for the *Un-even* distribution of calls from
kamailio proxy to freeswitches. The dispatcher lists are having the same
weight.
For example: If we are having 4 freeswitches, the calls are evenly
distributing for 3 freeswitches but there is high calls for the 4th
We have the same problem like 1 ~ 2 times a year with some version between
5.4 and 5.5.2, we didn't try the latest yet, and we didn't find a way to
reproduce it yet.
On Wed, Nov 9, 2022 at 11:24 PM Kaufman wrote:
> I encountered a similar problem and I believe that the issues wass with
>
I encountered a similar problem and I believe that the issues wass with
something causing an inconsistent state where kamailio was attempting to UPDATE
a row that doesn't exist.. Try setting db_check_update to 1.
Kaufman
-Original Message-
From: sr-users On Behalf Of Markus Bönke
Yes, I have experienced this as well.
> On Nov 9, 2022, at 6:00 AM, Markus Bönke wrote:
>
>
> Hello NG,
>
> we are using Kamailio 5.4.2 with the USRLOC module configured with db_mode 2
> (Write-Back scheme). The database is Postgres 11. Sometimes some records are
> not written to the
Hello NG,
we are using Kamailio 5.4.2 with the USRLOC module configured with db_mode 2
(Write-Back scheme). The database is Postgres 11. Sometimes some records are
not written to the database, however I can lookup them by "kamcmd ul.lookup
..." . There are no database errors (like constraint
