RE: [reSIProcate] stoping DUM with unsuccessful call
I've reversed the previous change and committed. Let me know if you are
still experiencing this.
Scott
-----Original Message-----
From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Monday, July 04, 2005 4:00 PM
To: 'stensil'; 'jason@xxxxxx'; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] stoping DUM with unsuccessful call
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@xxxxxxx]
Sent: Monday, July 04, 2005 5:43 AM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
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 ;-)