Re: [reSIProcate] DUM: Registration is not updated after time out

["Ali Pey" <alipey@xxxxxxxxx>]

Here is the scenario:

1- ClientRegistration registers with a Registrar Server successfully. If calls onSuccess on the handler so your application knows that you are registered. The Re-Registration time is set to 30 second.

2- Registrar Server is not reachable. ClientRegistration can not register any more. It times out and it calls onRequestRetry on the handler. The application now knows that it's not connected to the server.

3- Link is back up. ClientRegistration successfully re-registers with the Registrar Server. The handler/application does not get notified so your application thinks that it's still not registered.

The application or handler needs to be notified that it is registered with the server and can provide service to the user.

Am I missing something?

Regards,
Ali

On 10/11/06, Scott Godin <slgodin@xxxxxxxxxxxx > wrote:

This behavior is intentional.  You normally only get an onSuccess if you did something to invoke the registration.  Automatic re-registrations only callback if there is a failure.

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ali Pey
Sent: Wednesday, October 11, 2006 4:55 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] DUM: Registration is not updated after time out

 

Hi There,

I found and fixed a bug with DUM's ClientRegistration.

ClinentRegistration class calls the handler's onFailure or onRequestRetry if the registration fails or times out. However, it won't call onSuccess when it successfully re-registers.

Is there a process for submitting fixes to resiprocate/DUM?
What do I need to do?

Cheers,
Ali