Here is an example: user3001 has $5.00 balance in a central database
In office user3001 is registered. At home the same user3001 register again.
We want to tell to the office user that someone registered in other computer with same user and disallow (office user) outbound calls .
"kamctl ul show" present one deleted an one online user3001, but both can make outbound calls. reg_fetch_contacts("location", "$fu", "caller") return true to the first(deleted) registered user3001. Means registered and it allows to make outbound calls.
How can we catch the event when office user is deleted their AOR when home user register??
Thanks Luis
Daniel-Constantin Mierla escribió:
Hello,
On 01/15/2009 07:34 PM, Luis Guaman wrote:
Hi Daniel, We have already updated 1.4.3 to 1.5.0 version and it is workin great! I have used save() function with flag 0x04 and it allow to register uac again with no previous un-register...cool!
We need just one user concurrent registered per account. We can not use modparam("registrar", "max_contacts", 1) because when the computer hangs we need to wait until register expire to register again. We want to know how to detect the event when some same second ua register, in order to send a reply message to the first registered uac to block outbound calls (just one balance per user).
I am not sure I fully understood what you want to achieve with the last phrase. Can you give an example?
Cheers, Daniel
Thanks in advance
Luis
Daniel-Constantin Mierla escribió:
Hello Luis,
On 01/07/2009 02:53 PM, Luis Guaman wrote:
Hello Daniel, Thanks for replying.. I have a similar case. I am using persitent db registers and max_contacts = 1. When I close my softphone it send a final register but it keeps registered on the proxy server and I needs to use kamctl ul rm "user" to allow register again... How can I let the softphone register again without wait to expire the first register?? (same thing when the pc freeze or when the user close the laptop while remain the softphone open).
you have to use the trunk and save() function with flag 0x04: http://kamailio.org/docs/modules/devel/registrar.html#id2506205
I cannot say if it would be hard to backport registrar+usrloc modules from trunk to 1.4. Anyhow, you don't have to wait too long for 1.5 to be out, so you can try to test trunk and see if it is stable enough.
Cheers, Daniel
New register module looks great!!
Thanks again Luis
Daniel-Constantin Mierla escribió:
Hello,
On 01/05/09 20:02, Luis Guaman wrote:
Thanks Alex, Here is the configuration to allow 1 concurrent register:
modparam("registrar", "max_contacts", 1)
here you should pay attention to contact updates. In some cases, like mobile phones with wi-fi and sip stack, if they crash/lose/migrate to new AP connection, same phone sends a new register with different contact without un-registering the previous one.
If you encounter this, you can use the enhancements of the registrar module in Kamailio trunk (to be released as 1.5 in about 1.5-2months) -- here are more details: http://openser.blogspot.com/2008/10/registrar-enhancements.html
Practically you can iterate through the existing contacts and do more checks or use save() with the proper flag that will overwrite any existing contact and will maintain only one in location table.
Cheers, Daniel
Luis Guaman InterlanCompu Quito - Ecuador +593-2-2526585
Alex Balashov escribió:
> Yes; you can limit concurrent contacts to 1, using a module > parameter for 'registrar.' See the documentation. > > Luis Guaman wrote: > > >> Hi all, >> >> Does anybody let me know how to disable simultaneous registers, >> using the same user login/password in two or more different >> machines? >> >> >> thanks in advance >> Luis Guaman >> Interlancompu >> >> >> _______________________________________________ >> Users mailing list >> Users@lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> >
Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users