[asterisk-bugs] [Asterisk 0012415]: chan_h323 doesn't respect rtp packetization settings

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12415 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12415
Category:                   Channels/chan_h323
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 113980 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-10-2008 17:01 CDT
Last Modified:              04-13-2008 01:58 CDT
====================================================================== 
Summary:                    chan_h323 doesn't respect rtp packetization settings
Description: 
chan_h323 ignores codecs payload settings eg. 'allow=g729:20'
h323 trace, when I call from h323 endpoint to asterisk:
Found peer capability G.729 <1>, Asterisk code is 256, frame size (in ms)
is 160

If I call from asterisk to another endpoing (eg. cisco gw), trace shows,
that is using 20ms g729 frame size, but still doesn't invoke p2p bridging
between sip and h323 channel

sip--->(g729/chan_sip)-asterisk-(chan_h323/g729)--->callmanager/(cisco gw
or cisco phone)
only g729 is allowed in h323 and sip config

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

---------------------------------------------------------------------- 
 DEA - 04-13-08 01:58  
---------------------------------------------------------------------- 
PJ,
  I forget that not everyone was as quick to CCM 6.X as I was.

I was thinking a test even with G.711 would be worthwhile.
I am sure the problem is not with CCM.  The issue is 99.9%
likely that chan_h323 is setting up the packetization too
early in the call setup.  It should not be pulling the max
framing value, but should compare the local configuration
against the remotes endpoints advertised max.  The correct
time to setup the packetization is in the openlogicalchannel
phase.

I am familiar with the concepts from adding packetization
support to chan_ooh323, but I do not know my way around
the chan_h323 code. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-13-08 01:58  DEA            Note Added: 0085416                          
======================================================================