the parameter desc_time_order ( set to 1) order the conctact in descending time order, and use the most recently updated/created user. and, if I understand, if the user A register from address 1 (Home), and more later register from address 2 (work) (the REGISTER is sent every minute from two address) and the soft re-send the register from address 1
how recognize openser that address 2 is the valid address? I attach the doc from this two parameters.
1.3.12. desc_time_order (integer) If set to 1 then all contacts will be ordered in descending modification time order. In this case the most recently updated/created contact will be used.
Default value is 0.
Example 1-12. Set desc_time_order parameter
... modparam("registrar", "desc_time_order", 1)
1.3.9. append_branches (integer) The parameter controls how lookup function processes multiple contacts. If there are multiple contacts for the given username in usrloc and this parameter is set to 1, Request-URI will be overwritten with the highest-q rated contact and the rest will be appended to sip_msg structure and can be later used by tm for forking. If the parameter is set to 0, only Request-URI will be overwritten with the highest-q rated contact and the rest will be left unprocessed.
Default value is 1.
Example 1-9. Set append_branches parameter
... modparam("registrar", "append_branches", 0) ... ----- Original Message ----- From: Bogdan-Andrei Iancu To: Steve Blair Cc: users Sent: Thursday, September 28, 2006 10:52 AM Subject: Re: [Users] UN-REGISTER
of course there is contact timeout as each contact is registered for a limited time period.
a more elegant solution is to use the "desc_time_order" and "append_branches" module parameter in order to retrieve from usrloc only the latest contact. See: http://openser.org/docs/modules/1.1.x/registrar.html
regards, bogdan
Steve Blair wrote:
You could also get creative and upon successful registration exec a script that will examine the location table and remove (or manipulate as you want) specific registrations. If these moves happen often this approach will not scale well. If you only need one registration per user then setting the max_contacts parameter is the easiest way to accomplish this goal.
_Steve
Max Gregorian wrote:
Perhaps implement Registration Timeouts.
If the aim is to stop the user from connecting using that IP address, then you could, on OpenSER, do something along the lines of:
if(src_ip==192.168.0.55 http://192.168.0.55/) { sl_send_reply("404", "User not found..");
};
On 9/28/06, *Bogdan-Andrei Iancu* <bogdan@voice-system.ro mailto:bogdan@voice-system.ro> wrote:
Hi Javier, that must be done by the phone. regards, bogdan Javier wrote: > can I unregister the the firsth register ? > > > ----- Original Message ----- > *From:* Daniel-Constantin Mierla <mailto:daniel@voice-system.ro <mailto:daniel@voice-system.ro>> > *To:* Javier Ramirez <mailto: jvr_78@yahoo.com.ar <mailto:jvr_78@yahoo.com.ar>> > *Cc:* users <mailto:users@openser.org <mailto:users@openser.org>> > *Sent:* Saturday, September 23, 2006 5:36 PM > *Subject:* Re: [Users] UN-REGISTER > > If the user closes the sip client on 0.55, then the client should > automatically un-register. If not, then the user will have two > contacts > and both phones will ring. > > If you want to limit the number of registered contacts, you can do it > via max_contacts parameter of registrar module: > >http://www.openser.org/docs/modules/1.1.x/registrar.html#AEN233 > > Cheers, > Daniel > > > On 09/22/06 23:47, Javier Ramirez wrote: > > Hi, I have a question: > > > > the user A is register, the ip of register is 192.168.0.55 http://192.168.0.55. > > the user change PC, and this PC have the ip 192.168.0.66 http://192.168.0.66 > > > > the user register again, in the new machine, but, how to unregister > > the firsth registration from 192.168.0.55 http://192.168.0.55 ? > > > > best regards > > Javier > >
_______________________________________________ Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
__________ NOD32 1.1776 (20060926) Information __________
This message was checked by NOD32 antivirus system. http://www.eset.com