Hello,
I didn't try to suggest that what you want won't be useful or rejected
if someone wants to contribute. My explanation was for what exists now.
Also, be aware that you can have one contact per device, which is
feature controlled differently than the max_contacts -- see save()
documentation
Hey Daniel,
This makes sense, thanks for the explanation.
While I can understand why it works the way it does now, I still think
having an option here would be great. My thought is, whether the mobile
phone that re-registers every 10 minutes or the desk phone is "older," the
point is that they're
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 b
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 wheth
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
wrote:
>Hey all,
>
>I know Kamailio's registrar module has a max_contacts parameter that
>will
>limit the number o
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 Kamaili
