Hmmm Well - everybody using the Web Transceiver (and iaxRpt) is using on-board audio aren't they? I have heard some very nice web transceiver audio (and some crappy audio). A lot has to do with the microphone being used - and of course the level must be set right. The reason Echolink generally sounds like a bad cell phone call is that they use the same codec - GSM whereas Asterisk (including the web transceiver) uses ulaw - or at least you can configure it for that. see http://ohnosec.org/drupal/node/80 On top of that, the Echolink coding is converted from GSM to whatever you are using on Asterisk between nodes (ulaw or g726). Passing a voice through two different coding schemes will do double-damage to it. ulaw provide a much nicer sound at the expense of more bandwidth - more than twice the bandwidth of GSM. But over a standard internet connection, that is rarely an issue these days. 73 Ken
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users- bounces@ohnosec.org] On Behalf Of Bob Brown - WØNQX Sent: Monday, December 26, 2011 8:34 AM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Limey Linux on a HP T5630 Thin Client
Hence the reason why we use the the Allstar method of VOIP and the USB device for audio ,
Do you really pay attention to how a lot of the Echolink stations sound?
most use on-board audio , and it sucks, don't get me wrong there are some fine sounding Echolink
systems out there, that is because they used a service monitor and set it up right.
But most use the "By Ear Method" and on-board audio they are all over the place.