[reSIProcate] fetching registartion

[Scott Godin]

There is no requirement to use the same from tag and Call-id to query active registrations.  You could just form a new ClientRegistration using the same AOR, then use allContacts to get see the current regisrations.

________________________________

From: Giuseppe Teresi [mailto:giuseppe.Teresi at tti.unipa.it]
Sent: Wed 9/27/2006 1:24 PM
To: Scott Godin
Cc: resiprocate-devel at list.sipfoundry.org
Subject: Re: [reSIProcate] fetching registartion


Hi,

I know the allContacts() method of ClientRegistration class, if during the fetching procedure I obtain a 4xx message to the REGISTER, when I call allContacts() it returns the contacts list contained in the 200 Ok to the first REGISTER.  

Scott Godin wrote: 

	There is an allContacts() method on ClientRegistration that can used to retrieve the Contacts from the 200 response.

________________________________

	From: resiprocate-devel-bounces at list.sipfoundry.org on behalf of Giuseppe Teresi
	Sent: Wed 9/27/2006 1:04 PM
	To: resiprocate-devel at list.sipfoundry.org
	Subject: [reSIProcate] fetching registartion
	
	

	Hi everybody,
	
	I wish to give to my User Agent the possibility to fetch the
	registration (see RFC 3261 section 10.2.3), this procedure is performed
	to send a REGISTER with the same from tag and Call-Id of the first
	REGISTER but without the contact header, but to obtain the contact list
	of UAs registered with an account I need to parse the 200 ok response to
	the REGISTER and this procedure don't tell a virtual method of
	ClientRegistartion class.
	Does someone knows an alternative method to obtain the 200 Ok response?
	
	
	thanks
	Giuseppe T.  
	_______________________________________________
	resiprocate-devel mailing list
	resiprocate-devel at list.sipfoundry.org
	https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060927/9ab97221/attachment.htm>