[Home]

Summary:ASTERISK-04265: [request] mpg123 should only be spawned once per music on hold class
Reporter:Chris Hozian (chozian)Labels:
Date Opened:2005-05-24 10:03:23Date Closed:2011-06-07 14:05:14
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Currently mpg123 will be spawned for each occurrence of music on hold.  I would like to see only one process of mpg123 spawned per music on hold class.

This is especially important if you stream music using mpg123.  There is no need to pull multiple streams using mpg123 just because there are multiple occurrences of music on hold.  They should share the same process if possible.

Comments:By: Chris Hozian (chozian) 2005-05-24 10:06:37

Darn, forgot to put [request] in the title.   Sorry!  =-(
By: Russell Bryant (russell) 2005-05-24 13:31:17

Multiple instances will be spawned when there are multiple music classes.  Please do not place feature requests without patches to the Asterisk bug tracker.
By: Chris Hozian (chozian) 2005-05-24 14:04:06

I was given -2 karma for the reason of "submitting something as a bug which was not a bug".  That is not the case.  I submitted a feature request.

The bug guidelines do not state that you are only allowed to submit a feature request if you submit a patch.  If it is your intent to only allow those who will submit patches to suggest feature requests, you should update the bug guidelines to reflect this change of policy.

I would appreciate it if the -2 karma that I received could be taken off of my account since it was inappropriately assigned to me in the first place.

It is sad that the only people who can provide suggestions for improving Asterisk through this bug tracker are those who can provide patches for their suggestions.  I do believe there are a lot of good suggestions that can be given from members of the Asterisk community who would be unable to provide patches.

I assume from the updated bug guidelines which have been implied in this ticket that it will be unneccessary for me to use this bug tracker in the future.