[reSIProcate] stoping DUM with unsuccessful call

[Scott Godin]

I did some digging around.  This seems to be related to a change committed
by Nash in May sometime which was suspect - but since forgotten (see
attached email).

The problem is that the 408 response triggers a new Dialog and InviteSession
to be created - but since shutdown has been called - the HandleManager
disallows the handle to be created.  Later the handle is accessed and an
assertion is triggered.

I tried removing this change and everything is working good.

I'll discuss this with Jason and figure out how to proceed.

Scott
-----Original Message-----
From: stensil [mailto:stensil at list.ru] 
Sent: Monday, July 04, 2005 5:43 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] stoping DUM with unsuccessful call

Error scenario:

1. Initialize DUM, start DUM'n'SipStack event-processing thread
2. Make INVITE session to invalid SIP URL
3. InviteSessionHandler::onNewSession NOT called
4. Trying to shutdown DUM - onDumCanBeDeleted NOT called
5. After some time assert throws %/

Look at the resiprocate DEBUG LOG for more info.

--------------------------------------------------
foobar2000 v0.8.3 : (foobar2000 is not active ;-)

-------------- next part --------------
An embedded message was scrubbed...
From: Fischl jason <jason.fischl at gmail.com>
Subject: Re: [reSIProcate] DUM DumShutdownHandler does not get triggered
Date: Fri, 6 May 2005 14:43:33 -0400 
Size: 7597
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050704/b839ed6e/attachment.eml>