[asterisk-bugs] [Asterisk 0012130]: Transcoded G.722 calls unintelligible

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12130 
====================================================================== 
Reported By:                rickross
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   12130
Category:                   Codecs/codec_g722
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0-beta4 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-03-2008 20:53 CST
Last Modified:              03-04-2008 23:03 CST
====================================================================== 
Summary:                    Transcoded G.722 calls unintelligible
Description: 
Ever since moving from 1.4.13 to 1.6.0b4 my users have been unable to use
G.722 successfully. The transcoding seems fine from other formats like
ulaw/gsm into G.722, but the other direction is almost completely garbled
and makes it sound like the speaker is under water. It is barely
intelligible (with some good guesswork.)

I'd be happy to give someone a call to demonstrate, if that would help.
For now we're simply disabling G.722 completely (a pity, since it sounds so
good when it works.) We had been using a backported G.722 under 1.4.x for
many months, so we know it can work. SOmething seems to have changed in the
1.6 beta.
====================================================================== 

---------------------------------------------------------------------- 
 russell - 03-04-08 23:03  
---------------------------------------------------------------------- 
That fix was probably unrelated.  It was just something I noticed while
looking around.  I haven't had a chance to test for this issue yet, but I'm
hoping to do it tomorrow.  Definitely this week, though ... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-04-08 23:03  russell        Note Added: 0083400                          
======================================================================