[asterisk-bugs] [JIRA] (ASTERISK-26609) Wrong handling of 488 Not Acceptable Here during reINVITE

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26609:
------------------------------------------

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].

> Wrong handling of 488  Not Acceptable Here during reINVITE
> ----------------------------------------------------------
>
>                 Key: ASTERISK-26609
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26609
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.12.0
>            Reporter: Andrzej Marchlewski
>
> When r option is used in Dial application asterisk always issues re-Invite after initial dialog setup. If UA responds with 488 Not Acceptable Here asterisk will hangup the call immediately. Due to rfc3261 this behavior is incorrect. In section 14.1 it stands:
>  If a UA receives a non-2xx final response to a re-INVITE, the session
>    parameters MUST remain unchanged, as if no re-INVITE had been issued.
> Also section 4 of mentioned rfc it says:
> If the other  party does not accept the change, he sends an error response such as 488 (Not Acceptable Here), which also receives an ACK.  However, the  failure of the re-INVITE does not cause the existing call to fail -   the session continues using the previously negotiated characteristics.
> 488 response is handled in handle_response_invite function in chan_sip.c
> and causes execution of ast_queue_hangup_with_cause function
> We tested this behavior in version 11.12 however I can see in chan_sip.c that this scenario is handled in the same way in trunk and also in v13 branch.



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