Do you have any server that is timing out?
The registrations are handled sequentialy and if a server is timing
out, then it will take a long time for opensips to handle all the
records in a slot and it may overide with the next scheduled timer
task for the next slot.
Try to increase the number of
Hi, Ovidiu.
Yes, I use FQDN for registrar and somebody already said me here, that is the
possible problem.
I see next errors in the log:
Mar 16 03:48:36 node1 opensips[25954]: CRITICAL:core:timer_ticker: timer
handler lasted (218 us) for more than timer tick (100
us) -> potential
On Tue, Mar 15, 2016 at 8:09 AM, Alexander Mustafin
wrote:
> Hi there!
>
> Perhaps I don’t understand logic of this module, but I have strange problem:
>
> version: opensips 1.11.6-tls (x86_64/linux)
>
> I have 223 entries in my db. Previously, preferences of module
Hi there!
Perhaps I don’t understand logic of this module, but I have strange problem:
version: opensips 1.11.6-tls (x86_64/linux)
I have 223 entries in my db. Previously, preferences of module was like these:
modparam("uac_registrant", "hash_size", 2)
modparam("uac_registrant", "db_url",