[reSIProcate] fetching registartion

[Byron Campen]

	I beg to differ: see section 10.3 bullets 6 and 8. I am somewhat  
surprised that neither product supports fetch. In any case, this is a  
bug, and it should be reported to the maintainers. In the meantime,  
you may be able to force a registration refresh, and you will get the  
current contacts in the 200.

Best regards,
Byron Campen

> In the RFC 3261 there are no requirements about the fetching  
> registration procedure. I try this procedure with SER  and Asterisk  
> proxy for the first if I send a REGISTER out of dialog created for  
> the first REGISTER it respond with a 401 Unauthrized while Asterisk  
> don't support this procedure.
> On the other hand if I form a new ClientRegistration my problem  
> persist, in fact if you suppose that:
>
> 1)at time T1 I perform a registration with the  UA1 for  
> alice at biloxi.com , the allContacts() return 1 binding
>
> 2)at time T2 I perform a registration with the UA2 for  
> alice at biloxi.com,  the allContacts() return 2 bindings
>
> 3)at time T3 I perform a fetching registartion with UA1 for  
> alice at biloxi.com
>        a) if the proxy response is 200 Ok the allContacts return 2  
> bindings
>
>        b) if the proxy response is a 4xx the allContacts return 1  
> binding
>
> If there aren't any way to know the last response sending from the  
> register server I don't be sure that the list returned by the  
> allContacts() is the real list of the UAs logged with the same  
> account.
>
> I hope for I'm clear and excuse me for my poor english.
>
>
>
>
> Scott Godin ha scritto:
>> 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
>>>
> _______________________________________________
> 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/20060928/d84aeab7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2369 bytes
Desc: not available
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060928/d84aeab7/attachment.bin>