[Home]

Summary:ASTERISK-24888: Revision 422070 and 425503 are not merged to Asterisk 11 branch
Reporter:Makoto Dei (makoto)Labels:
Date Opened:2015-03-17 01:10:52Date Closed:2015-04-08 11:41:06
Priority:MinorRegression?
Status:Closed/CompleteComponents:Core/General
Versions:11.16.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:
Description:The following changes should be merged to Asterisk 11 branch.

http://svnview.digium.com/svn/asterisk?view=revision&revision=422070
http://svnview.digium.com/svn/asterisk?view=revision&revision=425503
Comments:By: Matt Jordan (mjordan) 2015-03-23 09:43:24.438-0500

[~makoto]: Have you seen this causing a problem in 11?
By: Rusty Newton (rnewton) 2015-04-08 11:39:11.090-0500

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: Rusty Newton (rnewton) 2015-04-08 11:40:55.151-0500

Since Matt hasn't received a response and we don't have any of the information described above I'm going to go ahead and close the issue out.

If you do get the required information then you can contact a bug marshal in the irc.freenode.net channels #asterisk-bugs to request that the issue be reopened.