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
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
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@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@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt
We cant, and we are not going to leave letigousness out of this. Plain and simply, no matter what
else, if asked about use of our technology or products in any way that might put you, your customer, us or anyone else for that matter at risk of harm or liability due to failure or anything else, thats the only answer youre going to get out of us. DONT DO IT!
Perhaps you need to ask a different question :-).
···
From: "Eric Fort" <eric.fort@gmail.com>
Reply-To: Asterisk Repeater Controler <app_rpt@lists.illiana.net>
To: "Asterisk Repeater Controler" <app_rpt@lists.illiana.net>
Subject: Re: [App_rpt] progress and stability of asterisk and app_rpt
Date: Mon, 3 Jul 2006 23:15:28 -0700
MIME-Version: 1.0
Received: from lists.illiana.net ([207.227.243.140]) by bay0-mc1-f2.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue, 4 Jul 2006 00:26:12 -0700
Received: (qmail 5531 invoked from network); 4 Jul 2006 06:15:31 -0000
Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 4 Jul 2006 06:15:31 -0000
Received: (qmail 5522 invoked from network); 4 Jul 2006 06:15:29 -0000
Received: from py-out-1112.google.com (64.233.166.182)by 0 with SMTP; 4 Jul 2006 06:15:29 -0000
Received: by py-out-1112.google.com with SMTP id c39so1508182pydfor <app_rpt@lists.illiana.net>; Mon, 03 Jul 2006 23:15:28 -0700 (PDT)
Received: by 10.35.129.19 with SMTP id g19mr2070663pyn;Mon, 03 Jul 2006 23:15:28 -0700 (PDT)
Received: by 10.35.90.18 with HTTP; Mon, 3 Jul 2006 23:15:28 -0700 (PDT)
X-Message-Info: txF49lGdW42rLVfBPSHRD3y9PJ6hjrcqa9Fx6tsctTc=
Return-Path: <eric.fort@gmail.com>
Delivered-To: mailman-app_rpt@lists.illiana.net
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;b=e/+uWrwCgCQCBA2xea5ZayHy1klqiwazXCM3IkwEvGSajr4BK7+CXGCBWrMcs7zz+XzpH3rMgRqL/zhsIETxcoaB/ZLMx/g70DPH2sDPc0eTFUty7tA4tVOSAkOHfPWSOycLDqAbYM7qy2uL/JVxMQiVTEEguvtzWSyxU6f4igU=
References: <2ad2af430607031339h3fc053edw7715303380da0342@mail.gmail.com><200607031941.58987.hwstar@rodgers.sdcoxmail.com>
X-BeenThere: app_rpt@lists.illiana.net
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: Asterisk Repeater Controler <app_rpt.lists.illiana.net>
List-Unsubscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app\_rpt\-request@lists\.illiana\.net?subject=unsubscribe>
List-Archive: <http://lists.illiana.net/pipermail/app_rpt>
List-Post: <mailto:app_rpt@lists.illiana.net>
List-Help: <mailto:app_rpt-request@lists.illiana.net?subject=help>
List-Subscribe: <http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app\_rpt\-request@lists\.illiana\.net?subject=subscribe>
Errors-To: app_rpt-bounces@lists.illiana.net
X-OriginalArrivalTime: 04 Jul 2006 07:26:13.0007 (UTC) FILETIME=[20DFE9F0:01C69F3B]
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@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@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________
App_rpt mailing list
App_rpt@lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt
