[SR-Users] Multiple Registrations - Overwrite oldest contact

Olle E. Johansson oej at edvina.net
Fri Apr 1 22:00:54 CEST 2016


> On 01 Apr 2016, at 21:59, Olle E. Johansson <oej at edvina.net> wrote:
> 
> 
>> On 01 Apr 2016, at 21:31, Bruno Emer <brunoemer at gmail.com <mailto:brunoemer at gmail.com>> wrote:
>> 
>> Hello all.
>> 
>> I have problem here and I tried to find a solution and search over internet, but without success.
>> 
>> My scenario is the following: I have an application that must be registered in Kamailio when a user logs in the web interface, so he can get calls (something like a web softphone using webrtc). At this point, we are OK, and everything is working fine.
>> 
>> To get these register functions I am using the parameter "save("location", "0x04")" as described in the REGISTRAR module documentation, so if a user logs in another web browser or computer, only the last one will continue registered and all calls will be forwarded to him.
>> 
>> The point is that now we are creating a phone app that will do almost the same thing as the web interface, allowing users to receive calls using the mobile device, and here is my problem: I want to allow my users to be registered on two devices at the same time, but if a user logs into another device, I don't want to reply with a 503. I want to allow the user to register again, deregistering the oldest contact.
>> 
>> I saw that there is a module named "ims_usrloc_scscf" and on its description it says "implemented overwrite oldest contact behaviour", but I couldn't find any documentation about it.
>> 
>> So, is there a way to get this working today?
> 
> There is a modparam to register the amount of contacts per AOR - which would do what you need.
Sorry - late evening… It’s within the normal registrar module, not in ims.
http://kamailio.org/docs/modules/4.4.x/modules/registrar.html#registrar.p.max_contacts

/O

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160401/b63afdc1/attachment.html>


More information about the sr-users mailing list