| Summary: | ASTERISK-28304: app_voicemail. Issue with NOTIFYs | ||
| Reporter: | Taras Kupybida (tk) | Labels: | |
| Date Opened: | 2019-02-25 10:33:25.000-0600 | Date Closed: | 2019-02-27 09:33:39.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Applications/app_voicemail |
| Versions: | 13.25.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | We had a problem with voicemail NOTIFYs messages. This issue was described in
ASTERISK-28215 In Asterisk 13.25 it should be resolved. But after installing Asterisk 13.25 from scratch the issue still persist. We are using chan_sip. Before that we were using Asterisk 13.24. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2019-02-25 10:33:26.287-0600 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-02-25 10:38:51.050-0600 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Taras Kupybida (tk) 2019-02-27 09:32:30.166-0600 Hello, Sorry for the delay. We did couple tests to grab debug information and during the tests we found a problem. It was related to Asterisk 13 configuration features. Now it works. At this point I think you can close this issue. Thanks. By: Taras Kupybida (tk) 2019-02-27 09:33:39.474-0600 It was related to Asterisk 13 configuration features | ||