summaryrefslogtreecommitdiff
path: root/channels/chan_mgcp.c
diff options
context:
space:
mode:
authorMark Michelson <mmichelson@digium.com>2012-05-14 19:27:58 +0000
committerMark Michelson <mmichelson@digium.com>2012-05-14 19:27:58 +0000
commitfef9a32fb410b47da4cb195f0af2f63f8cac0f03 (patch)
tree18b8f7d0fe242909d12e58c58acc862820d45a99 /channels/chan_mgcp.c
parentc79bafa9e0922f8b56f2d3626a3b5e27b8781b33 (diff)
Fix broken reinvite glare scenario.
To make a long story short, reinvite glares were broken because Asterisk would invert the To and From headers when ACKing a 491 response. The reason was because the initreq of the dialog was being changed to the incoming glared reinvite instead of being set to the outgoing glared reinvite. This change has three parts * In handle_incoming, we never will reject an ACK because it has a to-tag present, even if we think the request may be out of dialog. * In handle_request_invite, we do not change the initreq when receiving a reinvite to which we will respond with a 491. * In handle_request_invite, several superflous settings up pendinginvite have been removed since this is dones automatically by transmit_response_reliable Review: https://reviewboard.asterisk.org/r/1911 ........ Merged revisions 366389 from http://svn.asterisk.org/svn/asterisk/branches/1.8 ........ Merged revisions 366390 from http://svn.asterisk.org/svn/asterisk/branches/10 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@366401 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'channels/chan_mgcp.c')
0 files changed, 0 insertions, 0 deletions