Summary: | ASTERISK-30098: res_agi: DTMF input does not exit loop once I enter max input | ||
Reporter: | Arun Gupta (Arun1201) | Labels: | |
Date Opened: | 2022-06-06 03:40:17 | Date Closed: | 2022-06-20 12:00:05 |
Priority: | Minor | Regression? | Yes |
Status: | Closed/Complete | Components: | Resources/res_agi |
Versions: | 16.3.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Operating System : 3.10.0-1160.45.1.el7.x86_64 Software Platform: Asterisk certified/16.8-cert3 Hardware: x86 server | Attachments: | |
Description: | I am trying to run the AGI command: 'GET DATA ' through my PHP script but it is not exiting even though I have specified the max digit as 6. Consider the below case:
My user will enter 6 digits as DTMF and it will be stored in the variable. Ideal case: GET DATA should exit the loop once he receives 6 digits (max digits). Actual case: Even if the user enters 6 digits it waits for timeout seconds and exits the command loop. So even after hitting max digits by the user, it has to wait idle until a timeout, and then it goes to the following command. This is not right. | ||
Comments: | By: Asterisk Team (asteriskteam) 2022-06-06 03:40:18.783-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-06-06 04:20:11.559-0500 Certified is not supported on the Asterisk issue tracker. If you have a support agreement you will need to contact Sangoma support to receive assistance. If you do not have a support agreement you will need to upgrade to the latest version of Asterisk 16 and retest. If this still occurs, then you will need to provide an example AGI application that reproduces the issue and Asterisk console output. By: Asterisk Team (asteriskteam) 2022-06-20 12:00:05.572-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines |