| Summary: | ASTERISK-19483: Hangup during Read() or Record() causes hangup extension failure | ||
| Reporter: | var (var) | Labels: | |
| Date Opened: | 2012-03-05 16:40:35.000-0600 | Date Closed: | 2015-03-13 19:47:12 |
| Priority: | Major | Regression? | Yes |
| Status: | Closed/Complete | Components: | Applications/app_read Applications/app_record |
| Versions: | 1.8.9.2 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Debian 6.0.4, libpri 1.4.12, dahdi linux/tools 2.6.0, PRI ISDN line setup | Attachments: | ( 0) record_debug.log |
| Description: | When a user hangs up during a Read() or Record() the hangup (h) extension is not executed, this causes issues for creation and tear-down development (e.g. not being able to track current channels in use via dialplan without AMI). The hangup extension should always be executed. | ||
| Comments: | By: Matt Jordan (mjordan) 2012-03-05 16:58:12.364-0600 We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: var (var) 2012-03-05 17:06:01.025-0600 The asterisk version in use is 1.8.9.2, however this is a regression issue as it has been a development blocker on specific types of dialplan functionality over asterisk versions. By: Matt Jordan (mjordan) 2012-03-05 17:09:57.196-0600 I had accidentally pasted in the wrong question here. What I meant to ask for previously was a DEBUG log. By: var (var) 2012-03-05 17:18:23.861-0600 record debug log file, read() has the same approach. By: var (var) 2012-03-05 17:18:41.037-0600 record debug log file attached as requested. By: Joshua C. Colp (jcolp) 2015-03-13 19:47:12.961-0500 I've tested this across recent versions and confirmed it's working as expected. | ||