[reSIProcate] To DUM or not to DUM

[Jason Fischl]

It is probably more on the revolutionary side of things but it would
not be too difficult to port from v1 to v2. v2 will probably be
several months in the making so I would advise to proceed with v1.



On 5/30/06, Craig Scott <Craig.Scott at telephonetics.co.uk> wrote:
> Thanks for that Jason. Is DUMv2 evolution of revolution - should I wait
> for v2?
>
> Thanks
>
> Craig
>
> -----Original Message-----
> From: jason.fischl at gmail.com [mailto:jason.fischl at gmail.com] On Behalf
> Of Jason Fischl
> Sent: 30 May 2006 17:18
> To: Craig Scott
> Cc: resiprocate-devel at list.sipfoundry.org
> Subject: Re: [reSIProcate] To DUM or not to DUM
>
> dum is appropriate for any user agent application and is highly
> recommended. It will be supported going forward although we are having
> a coding session this coming weekend to work on a dumv2.
>
> On 5/30/06, Craig Scott <Craig.Scott at telephonetics.co.uk> wrote:
> >
> >
> >
> >
> > Hi,
> >
> >
> >
> > Can anyone point me (a resip newbie) to any information regarding when
> to
> > use DUM (and when not to) Is there anything significant in terms of
> > functionality or scalability that I will not be able to do if I use
> the DUM
> > (I'm thinking B2BUA, Voicemail and call routing apps - autoattendants
> etc.)
> > Is DUM something that will be 'supported' going forward?
> >
> >
> >
> > Thanks for any pointers.
> >
> >
> >
> > Regards
> >
> >
> >
> > Craig
> >
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel at list.sipfoundry.org
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >
> >
>