[OpenSIPS-Users] Registration questions
cinthia721 at gmail.com
Sat Mar 5 03:22:22 CET 2011
Thanks for your reply. You're right, I didn't change the usrloc setting to memory only. I only add a "m" flag in registered() and save() functions. I no longer see "deleted" or "expired" registrations anymore.
However, that didn't seem to fix the other call-id storage issue. I rebooted my phone and it came back online while the registration was still valid. The phone sent a new REGISTER with a different call-id. There's no new registration created as far as I can tell, because otherwise I would expect to see two entries, one new and one expiring, instead of just one listing. The old call-id showed up when I use "opensipsctl ul show".
This is what I use to save the registration: save("mydomain.com", "m");
On Feb 28, 2011, at 4:00 PM, Bogdan-Andrei Iancu wrote:
> Hello Cinthia,
> Cinthia Leung wrote:
>> I have a couple of questions regarding registrations and the registrar module. We store the registrations in memory only.
>> 1. When a registration is gone (expired, manually removed...), how long does it stay in the memory before it completely goes away. If I do "opensipsctl ul show", I see those registrations that are supposed to be gone are still in the result, with Expires = "deleted" or "expired" for the next 10+ seconds.
> You can see deleted records still kept in memory only when using DB persistence - records (even deleted) are kept in mem until DB flush is performed again, so that the records are deleted from DB also - so maximum to stay is the DB flush interval.
>> 2. I noticed that save() does not update the call-id if everything else (contact, received...) stays the same. Say a device has been registered the whole time. A power blip knocked it out for a short while. The registration in OpenSIPS becomes "expired". The device is now back online and tries to register with a new call-id before the old reg disappears from OpenSIPS. What I'm seeing is that the current registration still has the old call-id. It is causing issues when we use the callid option of registered().
> A different call-id means a different registration, so in the scenario you mentioned, after the device come back online, a new registration will be created for it (the old one will be not touched).
>> Any comments are appreciated. Thanks.
>> Users mailing list
>> Users at lists.opensips.org
> Bogdan-Andrei Iancu
> OpenSIPS eBootcamp - 28th February 2011
> OpenSIPS solutions and "know-how"
> Users mailing list
> Users at lists.opensips.org
More information about the Users