[asterisk-bugs] [Asterisk 0010433]: g726 appears broken between 1.4.x and 1.2.x

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10433 
====================================================================== 
Reported By:                eeman
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10433
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-12-2007 11:50 CDT
Last Modified:              08-12-2007 12:13 CDT
====================================================================== 
Summary:                    g726 appears broken between 1.4.x and 1.2.x
Description: 
Platform A : 

asterisk 1.2.24
centos/redhat 4.5
intel motherboard
white box assembly

Platform B:
asterisk 1.4.10.1
centos/redhat 4.5
dell poweredge 2650

when trying to use g726 on an IAX2 channel between a 1.4.10 and 1.2.24

platform B is setup to allow both g726 and ulaw, g726 is preferred. 

if, on platform A, I 

disallow=all
allow=g726,ulaw

ulaw always gets chosen w/ a preference of 'unknown'

if I force only g726 

disallow=all
allow=g726 

I get

incoming audio call:
Aug 12 12:39:19 WARNING[18838]: channel.c:509 ast_best_codec: Don't know
any of 0xe800 formats
Aug 12 12:39:19 ERROR[18838]: chan_iax2.c:7478 socket_read: No best format
in 0xe800???

outgoing audio call:
the following shows up on the receiving side (asterisk 1.4.10)
[Aug 12 12:59:02] WARNING[18775]: channel.c:718 ast_best_codec: Don't know
any of 0xe000 formats
[Aug 12 12:59:02] ERROR[18775]: chan_iax2.c:7486 socket_process: No best
format in 0xe000???



could this be a result of 1.2.x referring to g726 as 0xe000 and 1.4.x
referring to g726 as 0xe800? Would that result in the preferred codec
showing up as 'unknown' ? 


====================================================================== 

---------------------------------------------------------------------- 
 eeman - 08-12-07 12:13  
---------------------------------------------------------------------- 
the following comment indicates that g726aal2 as the codec on the 1.4
system should resolve the issue. However, it only seems to resolve the
codec negotiation.. the actual call fails to produce audio after codec
negotiation.

* It has been determined that previous versions of Asterisk used the wrong
codeword packing order for G726-32 data. This version supports both
available packing orders, and can transcode between them. It also now
selects the proper order when negotiating with a SIP peer based on the
codec name supplied in the SDP. However, there are existing devices that
improperly request one order and then use another; Sipura and Grandstream
ATAs are known to do this, and there may be others. To be able to continue
to use these devices with this version of Asterisk and the G726-32 codec, a
configuration parameter called 'g726nonstandard' has been added to
sip.conf, so that Asterisk can use the packing order expected by the device
(even though it requested a different order). In addition, the internal
format number for G726-32 has been changed, and the old number is now
assigned to AAL2-G726-32. The result of this is that this version of
Asterisk will be able to interoperate over IAX2 with older versions of
Asterisk, as long as this version is told to allow 'g726aal2' instead of
'g726' as the codec for the call. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-12-07 12:13  eeman          Note Added: 0068755                          
======================================================================