[asterisk-bugs] [Asterisk 0018800]: Res_musiconhold Kills Mpg123 Upon Initial Start or Reload if a Streaming Source Defined
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun May 15 16:06:26 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18800
======================================================================
Reported By: vmikhelson
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18800
Category: Resources/res_musiconhold
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.8.2.3
JIRA: SWP-3141
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-02-12 17:34 CST
Last Modified: 2011-05-15 16:06 CDT
======================================================================
Summary: Res_musiconhold Kills Mpg123 Upon Initial Start or
Reload if a Streaming Source Defined
Description:
Added a streaming source to MOH. Static MOH works fine, streaming MOH
produces silence.
mpg123 1.13.1
Asterisk 1.8.2.3
FreePBX 2.8.1.0
Was unable to test with branch/1.8 as voicemail application locks up upon
the initial Asterisk load and consequentially prevents full system load.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0019159 [regression] moh custom mode with madpl...
related to 0018884 when using mpg123 as a streaming MOH so...
======================================================================
----------------------------------------------------------------------
(0134948) vmikhelson (reporter) - 2011-05-15 16:06
https://issues.asterisk.org/view.php?id=18800#c134948
----------------------------------------------------------------------
Just in case it helps somebody to figure out what goes wrong.
Figure 1.
Asterisk loaded first time, MOH is idle. res_timing_dahdi.so use count is
1.
pbx*CLI> module show like timing
Module Description
Use Count
res_timing_pthread.so pthread Timing Interface 0
res_timing_dahdi.so DAHDI Timing Interface 1
2 modules loaded
Figure 2.
Asterisk loaded first time, MOH is active, i.e playing.
res_timing_dahdi.so use count is 2.
pbx*CLI> module show like timing
Module Description
Use Count
res_timing_pthread.so pthread Timing Interface 0
res_timing_dahdi.so DAHDI Timing Interface 2
2 modules loaded
Figure 3.
Asterisk reloaded with "core reload", MOH is idle. res_timing_dahdi.so use
count is 2.
pbx*CLI> module show like timing
Module Description
Use Count
res_timing_pthread.so pthread Timing Interface 0
res_timing_dahdi.so DAHDI Timing Interface 2
2 modules loaded
Figure 4.
Asterisk reloaded with "core reload", MOH is active, i.e playing.
res_timing_dahdi.so use count is 3.
pbx*CLI> module show like timing
Module Description
Use Count
res_timing_pthread.so pthread Timing Interface 0
res_timing_dahdi.so DAHDI Timing Interface 3
2 modules loaded
It looks like there maybe some thread stuck in res_timing_dahdi.
-Vladimir
BTW, Asterisk is now 1.8.4, DAHDI 2.4.1.2.
Issue History
Date Modified Username Field Change
======================================================================
2011-05-15 16:06 vmikhelson Note Added: 0134948
======================================================================
More information about the asterisk-bugs
mailing list