| Summary: | ASTERISK-25153: Asterisk originate with Application/data does not go to dialplan | ||
| Reporter: | Abhay Gupta (agupta) | Labels: | |
| Date Opened: | 2015-06-06 03:47:37 | Date Closed: | 2015-06-08 11:10:33 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/ManagerInterface Resources/res_agi |
| Versions: | Frequency of Occurrence | Constant | |
| Related Issues: | |||
| Environment: | Asterisk 13.4.0 with PJSIP and AGI | Attachments: | ( 0) agi.txt ( 1) debugdmp.txt |
| Description: | WE do a originate command with Application Data as in the example
Action: originate Channel: PJSIP/4001 Application: AGI Data: agi://192.168.1.220/ In AGI when we set extension , context and priority it does not land on that extension but on agi completion the channel is HANGUP . which means with originate and apllication data , the call does not go back to dialplan . | ||
| Comments: | By: Abhay Gupta (agupta) 2015-06-06 04:00:41.729-0500 debugdmp.txt has all the details when extension 4001 is called and then AGI sets extension 4002 but instead of it going to dialplan the extension 4001 is disconnected as well . The same problem is with AMI redirect command and only happens if originate is with Application AGI . By: Matt Jordan (mjordan) 2015-06-08 11:10:33.293-0500 This is not a bug. When you originate to an application, exiting the application *always* hangs up the channel. Changing the priority, context, or extension of the channel does not change this fact: changing the location of the channel in the dialplan only has semantic meaning *if* the channel existed in the dialplan. When you originate to an application, the channel never ran in the dialplan; hence, those operations have no effect. | ||