asterisk users - Mar 2006 - Problem with chan_iax.cimplimentationcausesbadaudio?

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Andrew
Kohlsmith
Sent: Tuesday, March 21, 2006 11:36 AM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] Problem with
chan_iax.cimplimentationcausesbadaudio?

On Tuesday 21 March 2006 11:19, Adam Robins wrote:
> All switches and routers give highest priority to traffic on IAX2 port
> 4569.  We use DSCB values over the IP-VPN to prioritize it as well.
> This did not change with the upgrade, as we can still see proper 
> packet coding.
Right, I wouldn't suspect otherwise.
> The softphone is provided by our vendor Aheeva.  It is the same IAX2 
> softphone they use in their own call centers.  Funny thing is that 
> they say that moving to Asterisk 1.2.4 tremendously IMPROVED their 
> call quality with IAX2.
I wonder what the hell is going on then, that is definitely something
strange.
> Headsets are Plantronics H251N tops with DA60 USB adapters.  All 
> Desktops are at least 2.0 GHz P4 with 512MB RAM
Thanks for the information.  I feel bad for not having a good solid
answer for why it's occurring.  As the saying goes: I don't have an
answer, but I admire the problem...

-A.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

The contents of this email message and any attachments are confidential and are
intended solely for addressee. The information may also be legally privileged.
This transmission is sent in trust, for the sole purpose of delivery to the
intended recipient. If you have received this transmission in error, any use,
reproduction or dissemination of this transmission is strictly prohibited. If
you are not the intended recipient, please immediately notify the sender by
reply email and delete this message and its attachments, if any.

Thanks for the offer.  We deleted all of our Ethereal traces once we
switched to SIP.  On a bad call call there were tens of thousands of
checksum errors and packets out of sequence.  This occurred both with
and without IAX2 trunking and trunktimestamps.

Complaints of poor quality were from both the agent and customer sides.
Mostly cutting in and out - typical of dropped packets.



-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Tim Panton
Sent: Tuesday, March 21, 2006 1:06 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Problem with
chan_iax.cimplimentationcausesbadaudio?


On 21 Mar 2006, at 16:19, Adam Robins wrote:
> All switches and routers give highest priority to traffic on IAX2 port
> 4569.  We use DSCB values over the IP-VPN to prioritize it as well.
> This did not change with the upgrade, as we can still see proper 
> packet coding.
>
> The softphone is provided by our vendor Aheeva.  It is the same IAX2 
> softphone they use in their own call centers.  Funny thing is that 
> they say that moving to Asterisk 1.2.4 tremendously IMPROVED their 
> call quality with IAX2.
>
> Headsets are Plantronics H251N tops with DA60 USB adapters.  All 
> Desktops are at least 2.0 GHz P4 with 512MB RAM
I don't suppose you have an ethereal packet capture from a bad call ???

Or a description of the 'badness'?

I'm doing stuff in IAX2 at the moment and might be able to spot a
problem.

Tim.

Tim Panton
tim@mexuar.com



_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

The contents of this email message and any attachments are confidential and are
intended solely for addressee. The information may also be legally privileged.
This transmission is sent in trust, for the sole purpose of delivery to the
intended recipient. If you have received this transmission in error, any use,
reproduction or dissemination of this transmission is strictly prohibited. If
you are not the intended recipient, please immediately notify the sender by
reply email and delete this message and its attachments, if any.