I like great audio quality that's way I stopped using Echolink (with a
sound card) and went with Allstar. I have Echolink enabled on my Allstar
but dislike must Echolink connection because of the poor audio quality
and I will disconnect them quickly. I have also disconnected Allstar
(nodes and web transceiver) with poor audio. So I think Allstar should
have some kind of audio quality polices and standards. <br>
<br>
<br>
ulaw at what 64kb/s v GSM 13kb/s over DSL or higher. Most internet is
unlimited anymore at high speeds unless your using a cell carrier. Does
anyone use QOS on there router?<br>
<br>
Anyways Audio Quality is always better.<br>
<br>
David<br><br><div class="gmail_quote">On Mon, Dec 26, 2011 at 6:12 AM, Ken <span dir="ltr"><<a href="mailto:ke2n@cs.com">ke2n@cs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hmmm<br>
<br>
Well - everybody using the Web Transceiver (and iaxRpt) is using on-board<br>
audio aren't they?<br>
<br>
I have heard some very nice web transceiver audio (and some crappy audio).<br>
A lot has to do with the microphone being used - and of course the level<br>
must be set right.<br>
<br>
The reason Echolink generally sounds like a bad cell phone call is that they<br>
use the same codec - GSM whereas Asterisk (including the web transceiver)<br>
uses ulaw - or at least you can configure it for that.<br>
see<br>
<a href="http://ohnosec.org/drupal/node/80" target="_blank">http://ohnosec.org/drupal/node/80</a><br>
<br>
On top of that, the Echolink coding is converted from GSM to whatever you<br>
are using on Asterisk between nodes (ulaw or g726). Passing a voice through<br>
two different coding schemes will do double-damage to it.<br>
<br>
ulaw provide a much nicer sound at the expense of more bandwidth - more than<br>
twice the bandwidth of GSM. But over a standard internet connection, that is<br>
rarely an issue these days.<br>
<br>
73<br>
<br>
Ken<br>
<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:app_rpt-users-bounces@ohnosec.org">app_rpt-users-bounces@ohnosec.org</a> [mailto:<a href="mailto:app_rpt-users-">app_rpt-users-</a><br>
> <a href="mailto:bounces@ohnosec.org">bounces@ohnosec.org</a>] On Behalf Of Bob Brown - WØNQX<br>
> Sent: Monday, December 26, 2011 8:34 AM<br>
> To: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>
> Subject: Re: [App_rpt-users] Limey Linux on a HP T5630 Thin Client<br>
><br>
> Hence the reason why we use the the Allstar method of VOIP and the USB<br>
> device for audio ,<br>
><br>
> Do you really pay attention to how a lot of the Echolink stations<br>
> sound?<br>
><br>
> most use on-board audio , and it sucks, don't get me wrong there are<br>
> some fine sounding Echolink<br>
><br>
> systems out there, that is because they used a service monitor and set<br>
> it up right.<br>
><br>
> But most use the "By Ear Method" and on-board audio they are all over<br>
> the place.<br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
</blockquote></div><br>