[Asterisk-Dev] app_rpt and iaxcomm ptt

[hwstar at rodgers.sdcoxmail.com]

Multiple reasons:

aa. The control frames help prevent transmitters from being keyed by unauthorized individuals with standard softphone programs. (We would like to keep our licenses). 

bb. High levels of background noise could key a transmitter
and cause interference. Commercially viable designs would never allow a transmitter to be keyed on the contents of an audio frame. A separate out-of-band keying mechanism is a very prudent thing to do.

cc. The CNG approach would be full of corner cases and need many days/weeks of debugging, as users complain about the
weaknesses mentioned in aa. and bb. above.

dd. The system as it is implemented works well, it is stable
and given that there is no reason to support a second method of keying.


Steve Rodgers
QRV Communications
 

> 
> From: Andreas Bayer <angel_azrael at gmx.de>
> Date: 2005/08/26 Fri AM 06:21:44 EDT
> To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Subject: Re: [Asterisk-Dev] app_rpt and iaxcomm ptt
> 
> Am Freitag, 26. August 2005 03:02 schrieb Steve Rodgers:
> > We really cannot sign up to this. It's not going to happen with app_rpt.
> >
> So why not ??
> 
> i thought it must be easier to implement it in app_rpt and switch between the 
> two signaling types then implement it in "all" clients with ptt functions.
> 
> Is there a technical barrier?
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>