[Home]

Summary:ASTERISK-25933: res_pjsip_pubsub: Asterisk ignores expires header value
Reporter:Bill Neely (ceo_xantek)Labels:
Date Opened:2016-04-17 14:52:32Date Closed:2020-01-14 11:14:07.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:13.8.0 13.8.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:OS=centos7 Yealink T-22 phoneAttachments:
Description:Asterisk sends the following error message:
Received subscription for extension "xxxxxxx" context "xxxxxx" with Expire header less than 'subminexpire' limit. Received "Expire: 30" min is 60

even though the sip client (Yealink T-22) has the Sip Server Expires set to 60

The SUBSCRIBE packet looks like this:
{noformat}
<--- SIP read from UDP:xx.xx.xx.xx:5070 --->
[Apr 17 19:48:43] SUBSCRIBE sip:xxxxxx@xxx.xxxx.xxx:5060 SIP/2.0
[Apr 17 19:48:43] Via: SIP/2.0/UDP 192.168.10.218:5070;rport;branch=z9hG4bK1205608596
[Apr 17 19:48:43] From: "Bill" <sip:xxxxxxxx@xxxr.net>;tag=831028773
[Apr 17 19:48:43] To: "Bill" <sip:xxxxxxxx@xxx.net>
[Apr 17 19:48:43] Call-ID: 746099495@192.168.10.218
[Apr 17 19:48:43] CSeq: 1 SUBSCRIBE
[Apr 17 19:48:43] Contact: <sip:xxxxxxx@192.168.10.218:5070>
[Apr 17 19:48:43] Accept: application/simple-message-summary
[Apr 17 19:48:43] Max-Forwards: 70
[Apr 17 19:48:43] User-Agent: Yealink SIP-T22P 7.72.0.50
[Apr 17 19:48:43] Expires: 30
[Apr 17 19:48:43] Event: message-summary
[Apr 17 19:48:43] Content-Length: 0
{noformat}

Note the Expires:30 even though the phone is set to 60
Comments:By: Asterisk Team (asteriskteam) 2016-04-17 14:52:33.633-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-04-17 17:25:35.346-0500

Can you clarify on what the problem is here? This appears to be with the phone...

The message you've provided is the message as received from the phone itself, which has an expires of 30.
By: Bill Neely (ceo_xantek) 2016-04-18 09:40:39.948-0500

It is not really a great problem, just unusual. WHen registering this same phone to asterisk 13.2.0 and asterisk 11, the expires header is reported correctly. It is only in asterisk 13.8 and 13.8.1 that the expires header is overwritten to 30 sec
By: Joshua C. Colp (jcolp) 2016-04-18 09:44:03.685-0500

If you do a packet capture before it hits Asterisk, is it still 30? If so then Asterisk isn't overwriting the Expires header.
By: Bill Neely (ceo_xantek) 2016-04-19 16:45:46.476-0500

We did a packet capture as you suggested. The expires header shows 60. When asterisk reports the packet it shows expires:30
By: Joshua C. Colp (jcolp) 2016-04-20 12:20:48.444-0500

Please attach the packet trace, configuration, as well as console output including "pjsip set logger on".
By: Asterisk Team (asteriskteam) 2016-05-05 12:00:01.911-0500

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