Summary: | ASTERISK-30197: PauseMonitor hangs up the call | ||
Reporter: | juanmol (juanmol) | Labels: | |
Date Opened: | 2022-08-31 06:14:14 | Date Closed: | 2022-08-31 06:18:47 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | Applications/app_mixmonitor |
Versions: | 18.5.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Ubuntu 20.04 | Attachments: | |
Description: | PauseMonitor hangs up the call. No error displayed on CLI. For example:
[pruebapause] exten => _X.,1,Answer() same => n,MixMonitor(/tmp/caca.alaw,bi(mixmonitorid)) same => n,PauseMonitor(${mixmonitorid}) same => n,Playback(/tmp/test) same => n,UnPauseMonitor(${mixmonitorid}) same => n,Hangup() At cli: -- Executing [999@pruebapause:1] Answer("Local/999@pruebapause-00000006;2", "") in new stack -- Local/999@pruebapause-00000006;1 answered SIP/1001-0000001a -- Channel Local/999@pruebapause-00000006;1 joined 'simple_bridge' basic-bridge <c4a915f5-29b5-44ad-909e-14d16af3fc83> -- Channel SIP/1001-0000001a joined 'simple_bridge' basic-bridge <c4a915f5-29b5-44ad-909e-14d16af3fc83> -- Executing [999@pruebapause:2] MixMonitor("Local/999@pruebapause-00000006;2", "/tmp/caca.alaw,bi(mixmonitorid)") in new stack -- Executing [999@pruebapause:3] PauseMonitor("Local/999@pruebapause-00000006;2", "0x7f121c00e6a0") in new stack == Begin MixMonitor Recording Local/999@pruebapause-00000006;2 == Spawn extension (pruebapause, 999, 3) exited non-zero on 'Local/999@pruebapause-00000006;2' -- Channel Local/999@pruebapause-00000006;1 left 'simple_bridge' basic-bridge <c4a915f5-29b5-44ad-909e-14d16af3fc83> -- Channel SIP/1001-0000001a left 'simple_bridge' basic-bridge <c4a915f5-29b5-44ad-909e-14d16af3fc83> == MixMonitor close filestream (mixed) == End MixMonitor Recording Local/999@pruebapause-00000006;2 | ||
Comments: | By: Asterisk Team (asteriskteam) 2022-08-31 06:14:17.932-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2022-08-31 06:18:47.536-0500 The PauseMonitor and UnPauseMonitor dialplan applications are for the Monitor application and not for MixMonitor. Dialplan execution is stopping due to Monitor not being active. There is not currently dialplan functionality for pausing MixMonitor like this. Other people stop it, and then restart the recording with the append option set. |