[asterisk-bugs] [JIRA] (ASTERISK-19942) SIP Session Timers do not honour refresher
Jon Bonilla (JIRA)
noreply at issues.asterisk.org
Wed Oct 17 16:16:18 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-19942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198688#comment-198688 ]
Jon Bonilla commented on ASTERISK-19942:
----------------------------------------
Taken from a comment in another place where I've been talking about this issue and interoperability tests:
it's the Session-Expires header that indicates how
SST are applied, and if the UAS says 'refresher=uas' then the UAS is
supposed to do the refresh.
The bit regarding the Require and why it's a MUST is explicitely
explained:
"""
If the refresher parameter in the Session-Expires header field in the
2xx response has a value of 'uac', the UAS MUST place a Require
header field into the response with the value 'timer'. This is
because the uac is performing refreshes and the response has to be
processed for the UAC to know this.
"""
If asterisk doesn't compute the refresher role properly, it should not
add Session-Expires header in the first place (it can still do
refreshes as it likes, regardless of what intervals are negotiated or
not).
> SIP Session Timers do not honour refresher
> ------------------------------------------
>
> Key: ASTERISK-19942
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-19942
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/Interoperability
> Affects Versions: SVN, 1.8.8.2, 1.8.10.1, 1.8.13.0
> Environment: SIP communication between Asterisk 1.8 versions and Sems 1.4.X stable releases. Used Linux Debian 6.0
> Reporter: Jon Bonilla
> Assignee: Jon Bonilla
> Attachments: scenario4_asterisk_log_full.txt, scenario4_asterisk_sip.conf, scenario4.pcap, scenario5_asterisk_log_full.txt, scenario5_asterisk_sip.conf, scenario5.pcap
>
>
> Tested different session-timer settings in sip.conf and asterisk does not honour refresher. It sends INVITE requests when it should not ot does not send any when it should. Depends on the configuration or scenario. Tested several scenarios to report. I'll add scenarios in notes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list