[asterisk-bugs] [Asterisk 0018347]: ooh323 crashes with segmentation fault every 2-3 days
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Nov 25 07:54:06 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18347
======================================================================
Reported By: celtic69
Assigned To: may213
======================================================================
Project: Asterisk
Issue ID: 18347
Category: Addons/chan_ooh323
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.14
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-11-21 22:14 CST
Last Modified: 2010-11-25 07:54 CST
======================================================================
Summary: ooh323 crashes with segmentation fault every 2-3
days
Description:
Server using Asterisk 1.6.2.14 and asterisk-addons 1.6.2.2 (both tarball
releases). The server receives inbound ooh323 calls (20 calls per minute)
which are terminated by the caller before the call is answered. After 2 to
3 days the asterisk will core dump with segmentation fault.
======================================================================
----------------------------------------------------------------------
(0129137) zeero (reporter) - 2010-11-25 07:54
https://issues.asterisk.org/view.php?id=18347#c129137
----------------------------------------------------------------------
Hi May,
I have installed "Asterisk SVN-branch-1.8-r296230" and ooh323 is currently
processing calls. I will need to monitor for at least 3 days to measure
stability.
I have 2 concerns with version 1.8:
1) ooh323 would not accept any calls (chan_ooh323.c:1797
ooh323_onReceivedSetup: Unacceptable ip 10.87.63.255) until I configured a
"user profile" and IP address for every Cisco gateway in the network. Is
there a way to change this behaviour as this will be an issue for customers
with many h.323 gateways and no gatekeeper.
2) The asterisk process was initially running at 98.9% cpu utilisation for
at least 1 hour but was still processing calls. I then restarted the
asterisk process and it is currently running at 0.2%. I will monitor and
see if the high cpu reoocurs.
Issue History
Date Modified Username Field Change
======================================================================
2010-11-25 07:54 zeero Note Added: 0129137
======================================================================
More information about the asterisk-bugs
mailing list