< Previous by Date	Date Index	Next by Date >
< Previous in Thread	Thread Index	Next in Thread >

[reSIProcate-users] Always "waiting for usages to be deleted (3)" during resip shutdown after deregistration and un-subscription

From: "Wong Kok Meng-a17866" <kokmeng.wong@xxxxxxxxxxxx>
Date: Fri, 31 Jul 2009 15:30:47 +0800

Hi,

My device, at power-up, does a SIP REGISTER and a SIP SUBSCRIBE, and receives a SIP NOTIFY for the SUBSCRIBE request. Then, the device is powered down. It does a deregistration and subscription, and it also receives the final notification for the subscription (state is terminated). But the resip does not call my API onDumCanBeDeleted(). It seems to be waiting for something to be released, my log is in the attachment.

In the log, the usages (at the point of powering down) is 5, after un-subscribe and deregister, it becomes 3 and it gets stuck in 3.

What is the reason? What is resip waiting for? Did I miss out anything? Please advise. Thank you very much for your time.

Regards,

Kok Meng

Attachment: shutdown.log
Description: shutdown.log

Follow-Ups:
- Re: [reSIProcate-users] Always "waiting for usages to be deleted (3)" during resip shutdown after deregistration and un-subscription
  - From: Scott Godin

References:
- [reSIProcate-users] Failing to exec anything in resip/dum/test or resip/stack/test under cygwin
  - From: Stuart Whelan
- Re: [reSIProcate-users] Failing to exec anything in resip/dum/test or resip/stack/test under cygwin
  - From: Stuart Whelan

Prev by Date: Re: [reSIProcate-users] Failing to exec anything in resip/dum/test or resip/stack/test under cygwin
Next by Date: [reSIProcate-users] does BYE will be re-send if no 200 OK received?
Previous by thread: Re: [reSIProcate-users] Failing to exec anything in resip/dum/test or resip/stack/test under cygwin
Next by thread: Re: [reSIProcate-users] Always "waiting for usages to be deleted (3)" during resip shutdown after deregistration and un-subscription
Index(es):
- Date
- Thread