[Home]

Summary:ASTERISK-17901: [patch] Timout or error on INFO or MESSAGE transaction causes call to be lost
Reporter:Emmanuel BUU (neutrino88)Labels:
Date Opened:2011-05-20 17:27:38Date Closed:2011-06-22 13:47:26
Priority:MinorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:1.8.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) info_message.patch
( 1) jira_asterisk-17901_v1.8.patch
Description:When exchanging INFO or MESSAGE primitives in call, 4xx error causes call to be cut although RFC 3261 explicitly states that such transaction do not modify the state of the dialog.

****** ADDITIONAL INFORMATION ******

patch attached that partially fix the matter in the most common cases
Comments:By: Richard Mudgett (rmudgett) 2011-06-07 19:58:33.891-0500

The [^jira_asterisk-17901_v1.8.patch] is a more complete patch to prevent INFO and MESSAGE responses to disconnect an active call.

Untested.
By: Richard Mudgett (rmudgett) 2011-06-22 13:47:26.266-0500

Merged revisions 324481 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8

Also fixed a reference leak in an error path in sip_msg_send().

........
 r324481 | rmudgett | 2011-06-22 13:41:20 -0500 (Wed, 22 Jun 2011) | 19 lines

 Timout or error on INFO or MESSAGE transaction causes call to be lost.

 When exchanging INFO messages within a call, 4xx error causes the call to
 be disconnected although RFC 2976 explicitly states that such transactions
 do not modify the state of the dialog.

 When exchanging MESSAGE messages within a call, 4xx error causes the call
 to be disconnected.  To provide least surprise, we should not disconnect
 the call since a MESSAGE is like INFO in this case.  (Implied by RFC 3428
 Section 2)

 (closes issue ASTERISK-17901)
 Reported by: neutrino88

 Review: https://reviewboard.asterisk.org/r/1257/
 Review: https://reviewboard.asterisk.org/r/1258/

 JIRA SWP-3486
........