| Summary: | ASTERISK-28491: Allow in and out file descriptors to be used in AGI - Create XAGI | ||
| Reporter: | Dan Jenkins (danjenkins) | Labels: | |
| Date Opened: | 2019-07-31 10:41:38 | Date Closed: | |
| Priority: | Minor | Regression? | No |
| Status: | Open/New | Components: | Resources/res_agi/NewFeature |
| Versions: | 16.5.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Allow the use of reading audio from Asterisk using FD3 and pushing audio in using FD4 in AGI
Someone had already done some of this work 10 years ago https://repo.or.cz/asterisk-bristuff.git/commit/0e998fdff62b4a399a514d948c00698caaf53807 This brings it up to working in 16 & 15 PR incoming | ||
| Comments: | By: Asterisk Team (asteriskteam) 2019-07-31 10:41:40.529-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. 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. By: Joshua C. Colp (jcolp) 2019-07-31 10:51:45.392-0500 Before being reviewed and accepted we need to clear up any licensing concerns. Is the change you are proposing written by you, or the code you linked to merely updated? If it's the code you linked then we'll need to ensure the individual who wrote it has a license agreement signed. Looking at the commit shows [~tzafrir] but I'm not sure if he was the one who made the change. [~tzafrir] Can you comment on the history and such? By: Dan Jenkins (danjenkins) 2019-07-31 11:07:38.440-0500 updated, changed, enhanced but its based on that code and there will be lines that are the same. However few now. By: Dan Jenkins (danjenkins) 2019-07-31 15:42:29.999-0500 For some reason my earlier comment didnt get submitted. I'm going to get in contact with K. P. Junghanns to ask him to sign a License Agreement for the original code | ||