| Summary: | ASTERISK-20193: AMI originate produces error "originated failed" when executing executecommand@asterisk_guitools context used by asterisk-gui to make system call. | ||
| Reporter: | lijingcheng (lijingcheng) | Labels: | |
| Date Opened: | 2012-08-06 03:27:19 | Date Closed: | 2012-08-06 17:07:09 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | General |
| Versions: | 1.8.9.3 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) 20193.patch | |
| Description: | AMI originate command which is used by asterisk-gui to make system call by calling the system application and ending with a hangup in excutecommand@asterisk_guitools context always get error response of "originated failed", but in fact, the dialplan context or system call is excuted successfully. | ||
| Comments: | By: lijingcheng (lijingcheng) 2012-08-06 03:49:50.146-0500 this patch fixes the problem. By: Rusty Newton (rnewton) 2012-08-06 17:07:09.451-0500 I talked with Matt Jordan about this issue, who explained that this patch would cause any call that was originated - via CLI or otherwise - and failed to return success. That would obviously be a bad thing. The Asterisk GUI should answer the call to prevent the originate from failing. The error produced is proper for a scenario where the call is not answered. By: lijingcheng (lijingcheng) 2012-08-06 22:46:48.769-0500 So this is a bug of asterisk-gui. | ||