[asterisk-bugs] [JIRA] (ASTERISK-26841) chan_sip: Call not cancelled after receiving a 422 response

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235797#comment-235797 ] 

Friendly Automation commented on ASTERISK-26841:
------------------------------------------------

Change 5133 merged by Joshua Colp:
chan_sip: Call not cancelled after receiving a 422 response

[https://gerrit.asterisk.org/5133|https://gerrit.asterisk.org/5133]

> chan_sip: Call not cancelled after receiving a 422 response
> -----------------------------------------------------------
>
>                 Key: ASTERISK-26841
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26841
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.7.2, 14.3.0
>         Environment: Centos 7
>            Reporter: Jean Aunis - Prescom
>
> When using RFC 4028 with chan_sip, an INVITE from Asterisk may be replied with 422, in order to negotiate session timers.
> When the 422 is received, if Asterisk hangs up the channel before a final response (200 OK or other) is received, no CANCEL request is sent.
> Detailed steps to reproduce :
> - Given SIP Session timers are enabled
> - Given Asterisk does a Dial() to an RFC 4028-compliant endpoint
> - Given Asterisk receives a 422 response and Asterisk replies to it
> - Given Asterisk receives a 100/180 response
> - When Asterisk hangs up the channel (before it has been answered with a 200 OK)
> - Then Asterisk does not send a CANCEL request
> Expected : Asterisk sends a CANCEL request
> I am going to submit a fix on Gerrit.



--
This message was sent by Atlassian JIRA
(v6.2#6252)