asterisk users - Mar 2006 - Problem with chan_iax.c implimentationcausesbadaudio?

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

 

-----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:08 AM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] Problem with chan_iax.c
implimentationcausesbadaudio?

On Tuesday 21 March 2006 10:55, Adam Robins wrote:
> End users use an IAX2 softphone on their desktop PCs.  Agents are 
> VLANed
If there were significant changes to chan_iax2 and these were not
upgraded to match, this could explain the trouble.
> Point is that it worked fine for 6-9 months before the Asterisk 1.2.4 
> upgrade.
Oh, I understand the point.  I'm not defending a protocol change causing
such breakage, I am just trying to identify why the breakage occurred
when Asterisk was upgraded.

Out of curiosity, which softphones do you use?  What kind of interface
to the user, just a cheap headset plugged into the speaker/mic on a
soundcard (which soundcard? I've had trouble with some) or something
fancier such as a Plantronics USB headset or bluetooth one?

Regards,
Andrew
_______________________________________________
--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.

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.

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