Summary: | ASTERISK-25667: Subscription request from endpoint XXX rejected. Expiration of 0 is invalid | ||
Reporter: | Ross Beer (rossbeer) | Labels: | |
Date Opened: | 2016-01-07 11:03:23.000-0600 | Date Closed: | 2016-02-07 05:27:21.000-0600 |
Priority: | Trivial | Regression? | |
Status: | Closed/Complete | Components: | Resources/res_pjsip_pubsub |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | An error message is shown when a Subscription request is sent with an Expiration time of 0 set.
This shouldn't be an error, it is in fact an 'unsubscribe' event and asterisk should expire the subscription when receiving this type of message. [Jan 7 16:45:59] WARNING[20011]: res_pjsip_pubsub.c:2660 pubsub_on_rx_subscribe_request: Subscription request from endpoint XXXX rejected. Expiration of 0 is invalid | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-01-07 11:03:25.525-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]. By: Joshua C. Colp (jcolp) 2016-01-07 11:16:32.181-0600 This message will occur if a SUBSCRIBE is received out of dialog with an expires of 0. In this case the message is correct: res_pjsip_pubsub has no idea about the subscription or the SUBSCRIBE is formatted improperly. This message WILL NOT occur if a resubscription or unsubscribe occurs in-dialog. Do you have a SIP trace showing this occurring? By: Asterisk Team (asteriskteam) 2016-01-21 12:00:19.983-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines |