[SR-Users] Limiting Registration Contacts

[Daniel-Constantin Mierla]

Hello,

right now the rule is to reject the registrations that exceed the
max_contacts limit. The main reason behind this policy is the
registration mechanism in SIP which requires periodic update/refresh but
also different expires intervals.

In this way it's hard to select the "old device". Can be a desktop phone
registering every hour and stable connection but also a mobile phone
registering every 10 minutes, changing the ip every now and then. By
just relying on the oldest registration, the desktop phone is likely the
candidate to remove most of the time, but keep other invalid mobile
contacts.

The solution would be to use GRUU (or the instance parameter) for
registration contacts. In this way each new registration from a device
will replace its own old contact, even if it has a different contact
address.

Cheers,
Daniel


On 01/12/2016 23:59, Colin Morelli wrote:
> Hey Alex - not sure I'm quite following what you mean. The bindings
> are only for web clients. Are you suggesting the clients themselves
> de-register? I'd have no problem with that with the exception of the
> fact that there's simply no way to guarantee that happens. It's a race
> condition between whether the unregistration can be sent before the
> browser kills the websocket connection on refresh.
>
> On Thu, Dec 1, 2016 at 5:57 PM, Alex Balashov
> <abalashov at evaristesys.com <mailto:abalashov at evaristesys.com>> wrote:
>
>     Wouldn't it be more fruitful to delete and reach old bindings in
>     such a scenario? Or are these bindings not only for web clients?
>
>     On December 1, 2016 5:54:06 PM EST, Colin Morelli
>     <colin.morelli at gmail.com <mailto:colin.morelli at gmail.com>> wrote:
>     >Hey all,
>     >
>     >I know Kamailio's registrar module has a max_contacts parameter that
>     >will
>     >limit the number of active contacts for an AOR. However, is there any
>     >mechanism to control what happens when that number is hit?
>     >
>     >When using a web client where every page refresh registers a new
>     >contact
>     >with Kamailio, it would be useful to automatically roll off the
>     oldest
>     >registrations and replace to make room for the new ones. I know this
>     >can be
>     >manually accomplished with sqlops, but I was hoping something
>     like this
>     >already existed.
>     >
>     >Best,
>     >Colin
>     >
>     >
>     >------------------------------------------------------------------------
>     >
>     >_______________________________________________
>     >SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
>     mailing list
>     >sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>     >http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>     <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>
>
>     -- Alex
>
>     --
>     Principal, Evariste Systems LLC (www.evaristesys.com
>     <http://www.evaristesys.com>)
>
>     Sent from my Google Nexus.
>
>
>     _______________________________________________
>     SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>     list
>     sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>     <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

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