[asterisk-bugs] [Asterisk 0016534]: mixmonitor CLI command is broken

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16534 
====================================================================== 
Reported By:                jlaguilar
Assigned To:                mvanbaak
====================================================================== 
Project:                    Asterisk
Issue ID:                   16534
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.2.0 
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-01-02 21:30 CST
Last Modified:              2010-01-05 09:27 CST
====================================================================== 
Summary:                    mixmonitor CLI command is broken
Description: 
In asterisk 1.6.2.0 the mixmonitor CLI command is being registered
incorrectly.

app_mixmonitor.c (Line 593):
e->command = "mixmonitor {start|stop} {<chan_name>} [args]";

It is expecting the 3rd argument to be exactly "<chan_name>". If it isn't,
asterisk will report that the command does not exist. And if you set it to
be "<chan_name>" it will find the command but it will obviuosly return that
the channel was not found.

Resgitering the command as:
e->command = "mixmonitor {start|stop}";

Fixes the problem.



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

---------------------------------------------------------------------- 
 (0116049) mvanbaak (manager) - 2010-01-05 09:27
 https://issues.asterisk.org/view.php?id=16534#c116049 
---------------------------------------------------------------------- 
This is indeed the correct fix.
Thanks for reporting it, fixing it now. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-05 09:27 mvanbaak       Note Added: 0116049                          
======================================================================