[asterisk-bugs] [Asterisk 0015285]: [patch] reworked chan_ooh323

Asterisk Bug Tracker noreply at bugs.digium.com
Sun Jun 14 16:12:55 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15285 
====================================================================== 
Reported By:                may213
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   15285
Category:                   Addons/chan_ooh323
Reproducibility:            random
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.1.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-06-07 18:51 CDT
Last Modified:              2009-06-14 16:12 CDT
====================================================================== 
Summary:                    [patch] reworked chan_ooh323
Description: 
There is patch to asterisk-addons-1.6.1.0 for reworked version of 
chan_ooh323 channel module.

main subject of changes is performance and scalability improvement.
one processing thread is replaced with many threads (one for cmdChannel
of EndPoint, one for incoming call creation, one for call processing).

chan_ooh323 with this reworking is more stable and have good performance
in compare with chan_h323.
chan_h323 have memory leaks in all my asterisk systems (which have
versions from 1.2 up to 1.6.1) and grow more than 2Gb virtual memory after
proccessing about 200000 calls. After many years of solving this trouble i
cancel this work and begin work on chan_ooh323.

asterisk 1.6.1 with this version of chan_ooh323 have uptime 4 days and
proccess about 400 000 calls and have 98Mb virtual memory with 4 active
channels and no memory leak detected by asterisk malloc debug system.
(all modules include OOH323 stack code are compiled with MALLOC_DEBUG
options)
Before testing 1.6.1 i work with 1.4 version and had 8 days uptime
asterisk with more than 1000000 calls processed without leaks.

Also there is small changes for new options - incoming call limit, 
numbering of calls, t35country code and vendor/version identification
(albania code is not liked for me ;))

More detail list of changes/improvements is in Changes-ooh323.eng.

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

---------------------------------------------------------------------- 
 (0106380) may213 (reporter) - 2009-06-14 16:12
 https://issues.asterisk.org/view.php?id=15285#c106380 
---------------------------------------------------------------------- 
uploaded two incremental (ooh323-patch-20090612 and  ooh323-patch-20090615)
and full (ooh323-fullpatch-20090615) patches.  ooh323-fullpatch-20090615 is
for original asterisk-addons-1.6.1.0

There are changes in read/write/native formats setting process and
g.726/amr-nb codecs support (non standard codecs are supported by common
code now).
amr-nb support is optionally compiled and compatible with patch from
http://sip.fontventa.com/. I don't known right name of this codec and
i wrote "AMRNB".


channel format setting procces have this rules:
all formats are 0 when channel is created because we don't know which
codec will be negotiated.
OLC of write channel set native format and adopt writeformat.
OLC of read channel do nothing because all read channels call OLC
functions before codec negotiation.
ooh323_write adopt writeformat if needed.
ooh323_read set native format if it changed from rtp side. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-14 16:12 may213         Note Added: 0106380                          
======================================================================




More information about the asterisk-bugs mailing list