[asterisk-bugs] [Asterisk 0012380]: [patch] T.38 support for chan_h323 with t.38 - t30 conversion

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12380 
====================================================================== 
Reported By:                may213
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12380
Category:                   Channels/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 112599 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-07-2008 19:33 CDT
Last Modified:              04-08-2008 16:51 CDT
====================================================================== 
Summary:                    [patch] T.38 support for chan_h323 with t.38 - t30
conversion
Description: 
Hello!

There is patch for h323 channel code which enable t.38 proto support,
translate t.38 packets to alaw sound packets. 
====================================================================== 

---------------------------------------------------------------------- 
 may213 - 04-08-08 16:51  
---------------------------------------------------------------------- 
sergee,

about alaw - h323 channel setup own nativeformat to alaw, but it is not
meaning what * can send to this channel only alaw. * setup codec converter
what may be ulaw->alaw, g726->alaw, g729->alaw or any others. But fax will
work only on fax-ready audio codecs that are *law and g726-32. I think that
ulaw is not problem here.

about module for addons - i will try to make patch in this way but later.

I know and agree, that this model is not the best, but others it is even
more complex, as i think. 
I think we can talk about it in irc channel. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-08-08 16:51  may213         Note Added: 0085170                          
======================================================================