[reSIProcate] Problem with client registrations in DUM

[Scott Godin]

This logic was just recently changed - I can't remember if it made it
into 1.0.1 or not, but it should work using the SVN head version.

 

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of
Hagai Sela (TA)
Sent: Tuesday, November 14, 2006 8:43 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] Problem with client registrations in DUM

 

Hi,

I have the following scenario: a resiprocate based client registers
successfully using DUM, with an expiration period of 30. After 25
seconds it tries to re-register, but the second request receives 408.
After a while a third request is sent, and it receives 200 OK. My
application doesn't receive the onSuccess() callback for the third
request.

 

I looked at the DUM code. In ClientRegistration.cxx, line 449. There is
an if statement that checks if this 200 response is a user refresh
request, and only if it is the application is notified. The above
scenario doesn't fit this logic, the application should be notified even
if this is not a refresh request.

 

Hagai.

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