[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-11-2008 16:45 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-11-08 16:45  
---------------------------------------------------------------------- 
Can you try chan_sip?  I suspect the issue is that chan_h323
is using the max capability (16 frames in this case) and not
the desired.

I cannot read your capture, so what we are looking for is 
in the openlogicalchannel section of the exchange.  You should
have seen the 16/2 capabilities early in the setup and then
repeated in during the open logical channel phase.

If the 16 is still in the open logical channel phase of the
exchange, then the problem is not in chan_h323, but with your
CCM. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-11-08 16:45  DEA            Note Added: 0085384                          
======================================================================