Summary: | ASTERISK-26258: SIP response | ||
Reporter: | Jaspreet Singh (jaspreet Singh) | Labels: | |
Date Opened: | 2016-08-02 07:29:45 | Date Closed: | 2016-08-02 07:34:34 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | we need "410" SIP response from asterisk dial plan. Please tell me how it is possible. | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-08-02 07:29:46.289-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]. By: Joshua C. Colp (jcolp) 2016-08-02 07:34:26.015-0500 We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Jaspreet Singh (jaspreet Singh) 2016-08-02 07:38:41.292-0500 Hi Joshua, we want to send SIP response 410 GONE from asterisk dial plan instead of BYE response. By: Asterisk Team (asteriskteam) 2016-08-02 07:38:41.455-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Malcolm Davenport (mdavenport) 2016-08-02 07:40:16.791-0500 That doesn't make it a bug. Please see the comment by [~jcolp] above. |