This looks perfect, Bogdan. Thanks again for the fast response. Best regards,
--
Kobi Eshun
Senior Architect, SightSpeed, Inc.
918 Parker Street, Suite A14
Berkeley, CA 94710
+1.415.713.8431 (m)
+1.510.649.9569 (f) <--- Note: updated FAX #




On Sep 19, 2006, at 1:56 AM, Bogdan-Andrei Iancu wrote:

Hi guys,

I just applied the patch on the cvs, the devel version. The docs are updated. So see:

regards,
bogdan

Mahesh Paolini-Subramanya wrote:

Actually, this sounds like a great soln. for stuff that i'm doing today - don't know if it solves Kobi's problem, but it would certainly solve mine...

cheers
----- Original Message -----
From: Bogdan-Andrei Iancu <[EMAIL PROTECTED]>
To: Kobi Eshun <[EMAIL PROTECTED]>, devel <[email protected]>
Sent: Thursday, September 14, 2006 3:25:57 AM GMT-0600
Subject: Re: [Devel] Use of 'registered()' while processing REGISTER request

Hi Kobi,

I have a patch you might find useful - instead of taking the AOR from the request ( registered () and lookup() from RURI and save() from To), you may push via an AVP what ever AOR you want. So you can take the TO uri, place it in an AVP and pass it to registered() as AOR.

does it sound reasonable?

regards,
Bogdan

Kobi Eshun wrote:

 

Thanks for the suggestion, Bogdan, but the setting the max_contacts parameter doesn't help me determine, at the script level, whether or not the client is currently registered while processing a REGISTER request. 
Do you foresee any issues with patching the 'registered()' function to operate on the To header in the case of a REGISTER request? Thanks,
--
kobi


On Sep 13, 2006, at 10:55 AM, Bogdan-Andrei Iancu wrote:

   

Hi Kobi,

use the max_contacts param to limit the number of registrations:


regards,
bogdan

Kobi Eshun wrote:

     

Hi,

I need to determine whether or not a client is currently already registered while processing a REGISTER request from that client. The obvious solution would be to invoke the 'registered()' predicate funciton -- unfortunately, that function only searches for an address-of-record in the R-URI, rather than the To header, and so it does not work as expected. a) Does anyone know of a different way to accomplish this query? b) Is there a conceptual problem with patching the 'registered()' function to extract the AOR from the To header in the case of REGISTER requests? Best regards -- kobi


------------------------------------------------------------------------

_______________________________________________
Devel mailing list


       



_______________________________________________
Devel mailing list



 



_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel

Reply via email to