[reSIProcate] DUM: handling createAppDialogSet() failure

[Dmitry Semyonov]

Derek,

There could be some other resources (hardware DSPs, logical lines, 
etc.) associated with SIP calls. In case of lack of the resources we 
can refuse to create AppDialogSet or we can send 400 response from 
e.g. onNewSession() callback. I'm just asking what is the best current 
practice for this case.

I found that raising an exception from within createAppDialogSet() 
will result in '400 <Exception text>' response to UAC, and dialog set 
will not be created. There is no similar catch for createAppDialog(). 
It looks a bit inconsistent to me.

On Fri, 5 Nov 2004, Derek MacDonald wrote:

> There needs to be an AppDialogSet present for DUM to function successfully;
> we could have a catch that creates the default AppDialogSet when such an
> exception occurs.  Otoh, I can't really think of a circumstance where
> failing the creation of an AppDialogSet(barring allocation problems) is the
> correct thing to do. Do you have a use case for this?
> 
> --Derek
> 
> > -----Original Message-----
> > From: resiprocate-devel-bounces at list.sipfoundry.org [mailto:resiprocate-
> > devel-bounces at list.sipfoundry.org] On Behalf Of Dmitry Semyonov
> > Sent: Thursday, November 04, 2004 5:41 AM
> > To: resiprocate-devel at list.sipfoundry.org
> > Subject: [reSIProcate] DUM: handling createAppDialogSet() failure
> > 
> > Hello.
> > 
> > It is assumed that createAppDialogSet() always returns "good" pointer.
> > Should an exception be thrown from overridden createAppDialogSet()
> > function in case when dialog set creation fails by some reason?
> > 
> > The same question applies to createAppDialog().
> > TIA.
> > 
> > --
> > ...Bye..Dmitry.
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel at list.sipfoundry.org
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> 
> 

-- 
...Bye..Dmitry.