[App_rpt] progress and stability of asterisk and app_rpt

[Eric Fort]

Leaving letigousness out of this, how far off is asterisk and app_rpt from
being there and what would it take to get it to this level of reliability
and stability?  a bounty may be an option as well.

Eric

On 7/3/06, Steve Rodgers <hwstar at rodgers.sdcoxmail.com> wrote:
>
>
> My personal opinion, is that you would probably be better off buying a
> solution from someone who you could hold accountable should the system
> fail
> at the worst possible moment. Sometimes there are reasons for going with a
> proprietary and costly solution. I believe your application is one where
> this
> would be the prudent thing to do.
>
> Steve WA6ZFT
>
> On Monday 03 July 2006 13:39, Eric Fort wrote:
> > I am looking at asterisk and app_rpt as a solution for a ship to shore
> > communications platform where safety of life and property may be an
> issue
> > at times.  We will be using dispatch remote from multiple radio sites.
> > Dispatch is now and would continue to be linked to the remotes via VoIP
> > links.  at each site there is also phone patch capability for ship to
> shore
> > phone calls, the main service offered, along with radios for amtor,
> telex,
> > sitor, and pactor modes for data, email etc.  Is asterisk and app_rpt up
> to
> > the task?  bottom line it just has to work.  Is it good enough that you
> > would trust it to work if your boat was sinking and you needed a
> dispatcher
> > to send help before the circling fishes found you tasty (propigation
> from
> > dispatch to rescue not withstanding)?
> >
> > Eric
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20060703/857e2112/attachment.html>