Will do.
On Mon, Mar 26, 2012 at 2:57 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
>
> On 3/24/12 2:35 PM, Krishna Kurapati wrote:
>
> Thanks Daniel for the suggestions. To make the script manageable, I am
> thinking of implementing last option.
> Have another flag to "save". May be 0x8?
>
>
Hi,
An alternative to the C/Module version would be the following:
# Allow no more than 2 contacts per AOR
modparam("registrar", "max_contacts", 2)
# Order usr-loc entries by the order of registration, not the Q-Value:
modparam("usrloc", "desc_time_order", 1)
# Table holding last selected AOR per
Hello,
On 3/24/12 2:35 PM, Krishna Kurapati wrote:
Thanks Daniel for the suggestions. To make the script manageable, I am
thinking of implementing last option.
Have another flag to "save". May be 0x8?
yes, it is ok.
Perhaps this should have lower priority than 0x4, just in case someone
sets
Thanks Daniel for the suggestions. To make the script manageable, I am
thinking of implementing last option.
Have another flag to "save". May be 0x8?
We will still use max_contacts = 2 in mod params.
And when the save("location", "0x08") is called, the oldest contact is
removed and the new contact
Hello,
On 3/23/12 3:21 PM, Krishna Kurapati wrote:
Hi,
Is there a way to set up maximum of 2 active roll over contacts per
user? Currently when I setup max contacts param as 2,
The third one is responding with 503 error for 3rd Register. How can
we remove one of the contacts and replace it wi
Hi,
Is there a way to set up maximum of 2 active roll over contacts per user?
Currently when I setup max contacts param as 2,
The third one is responding with 503 error for 3rd Register. How can we
remove one of the contacts and replace it with the
new one.
I need it when the device is switching