[reSIProcate] DUM REFER crash

Jason Fischl jason at counterpath.com
Mon Aug 21 17:46:13 CDT 2006


On 8/21/06, Matt Porter <mporter at calltower.com> wrote:
>
> Guys, the DUM does not respond with any error code, it asserts in
> debug.. and crashes in release.
> I verified this with the very latest code in SVN.
>
Have you got some test code that demonstrates this problem.

> In my opinion....
> 1.      the stack should never crash/assert because of a faulty message
> from the wire.
agreed

> 2.      the stack should check for a Handler (in Dialog.cxx) before
> pushing ClientSubscription's in the list.
this should be an assert

> 3.      the stack should throw a UsageUseException if
> InviteSession::refer is called when there is no handler for the event.
>
this should also be an assert

> Take it or leave it, I think this is going to the same "Blackhole" that
> all my other comments on the stack go and that's fine.
> I don't why there is so much push back from the maintainers about things
> like this / feature requests.
>
Please suggest code. i.e. send a patch and somebody will apply it.



More information about the resiprocate-devel mailing list