| Summary: | ASTERISK-26135: ari: Event subscribe and unsubscribe are not symmetric | ||
| Reporter: | Sean Bright (seanbright) | Labels: | |
| Date Opened: | 2016-06-21 16:58:25 | Date Closed: | 2017-05-31 14:57:27 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_ari_applications |
| Versions: | 13.10.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | N/A | Attachments: | |
| Description: | An application can subscribe to all bridge events using something like this:
{noformat} POST http://localhost:8088/ari/applications/foobar/subscription?eventSource=bridge: {noformat} But attempting to unsubscribe using the same format fails: {noformat} DELETE http://localhost:8088/ari/applications/foobar/subscription?eventSource=bridge: {noformat} If you pass the "magic" value that Asterisk uses internally, it works: {noformat} DELETE http://localhost:8088/ari/applications/foobar/subscription?eventSource=bridge:__AST_BRIDGE_ALL_TOPIC {noformat} But this is not intuitive. I assume the behavior is the same for other event sources, but I haven't tested them. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-06-21 16:58:25.921-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]. | ||