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(a)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(a)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(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Alex
--
Principal, Evariste Systems LLC (
www.evaristesys.com)
Sent from my Google Nexus.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users