[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 11:44 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 11:44  
---------------------------------------------------------------------- 
I have a CCM cluster, but I used chan_ooh323 and not chan_h323.
I wondered about that '160' in your report.  That appears to be
samples and not ms.

I am going out on a limb and assume the CCM connected phone is
a 7940/7960 and you can use the call statistics feature on those
phones.  Are you seeing the 160ms reported on the phone during a call? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-11-08 11:44  DEA            Note Added: 0085358                          
======================================================================