I'm running kamailio 3.X with the following patch for years, works fine to me
with distributed servers and replication:
diff --git a/modules_k/usrloc/udomain.c b/modules_k/usrloc/udomain.c
index b52bb76..e457cc5 100644
--- a/modules_k/usrloc/udomain.c
+++ b/modules_k/usrloc/udomain.c
@@ -318,6 +3
As far as I can tell (when db_mode=3) the timer function calls
synchronize_all_udomains(), which calls get_act_time() and then
db_timer_udomain() in a loop, and db_timer_udomain() just does a
database delete.
Regards,
Peter
On 08/04/13 10:27, Alex Balashov wrote:
On 04/08/2013 04:58 AM, Pet
On 04/08/2013 05:30 AM, Juha Heinanen wrote:
Alex Balashov writes:
In practice, we have found that they seem to get deleted a little before
expiration, and so there is a gap between their being deleted and
re-registration on the part of the UAC.
it is a bug if records are deleted before they
On 04/08/2013 05:30 AM, Juha Heinanen wrote:
Alex Balashov writes:
In practice, we have found that they seem to get deleted a little before
expiration, and so there is a gap between their being deleted and
re-registration on the part of the UAC.
it is a bug if records are deleted before they
Alex Balashov writes:
> In practice, we have found that they seem to get deleted a little before
> expiration, and so there is a gap between their being deleted and
> re-registration on the part of the UAC.
it is a bug if records are deleted before they expire. there should be
a safe margin af
On 04/08/2013 04:58 AM, Peter Dunkley wrote:
Hi,
The timer to delete records only runs if the timer_interval modparam is
> 0.
This means you can have multiple active registrars off the same database
table and use some external process to manage deletion of records (for
example, a stored proce
On 04/08/2013 05:21 AM, Juha Heinanen wrote:
Alex Balashov writes:
The problem is that endpoints register to both registrars simultaneously
in this setup. There is no question that one Kamailio instance
periodically deletes the other's contacts. This has been observed.
in db_mode=3, what d
Alex Balashov writes:
> The problem is that endpoints register to both registrars simultaneously
> in this setup. There is no question that one Kamailio instance
> periodically deletes the other's contacts. This has been observed.
in db_mode=3, what does it matter that a proxy deletes other p
On 04/08/2013 05:01 AM, Juha Heinanen wrote:
have you tried with db_mode=3? i have not noticed problems with it, but
my case be different from yours.
I have, and unfortunately there are still these problems.
The problem is that endpoints register to both registrars simultaneously
in this se
On 04/08/2013 04:58 AM, Peter Dunkley wrote:
This means you can have multiple active registrars off the same database
table and use some external process to manage deletion of records (for
example, a stored procedure triggered from a cron job).
Ah, so! I hadn't thought of that. Good suggesti
Alex Balashov writes:
> The 'location' table is also replicated this way. We know that 'usrloc'
> doesn't work so well with this: one instance of Kamailio will
> periodically delete the other's contacts, even if they have a nonlocal
> SIP domain.
> Is there any db_mode that can be used (other
Hi,
The timer to delete records only runs if the timer_interval modparam is > 0.
This means you can have multiple active registrars off the same database
table and use some external process to manage deletion of records (for
example, a stored procedure triggered from a cron job).
Regards,
P
I know I'm revisiting a problem that has been discussed in multiple
threads from various angles, so I might be rightly accused of laziness
in neglecting to research them all. All the same:
I have proxy1 and proxy2 writing to database A and database B,
respectively. Database A and database B
13 matches
Mail list logo
