diff options
author | Mark Michelson <mmichelson@digium.com> | 2010-06-23 17:08:34 +0000 |
---|---|---|
committer | Mark Michelson <mmichelson@digium.com> | 2010-06-23 17:08:34 +0000 |
commit | 2c798f321a4f5b9b7a4a9d5a527b97c975c21488 (patch) | |
tree | 7bd9827b41c0ed9bc1bdb31aadbdd11143b1ce59 /apps/app_meetme.c | |
parent | 746d8e6013ed4bba639ff20e20f847a845f7d45b (diff) |
Add extra protection for reinvite glare scenario.
Testing proved that if Asterisk sent a connected line reinvite, and
the endpoint to which the reinvite were being sent sent a reinvite, Asterisk
would not properly respond with a 491 response.
The reason is that on connected line reinvites, we set the dialog's invitestate
to INV_CALLING to prevent Asterisk from sending a rapid flurry of connected line
reinvites. For other reinvites we do not do this. Because of the current invitestate,
when Asterisk received the reinvite, we interpreted this as a spiraled INVITE, and thus
did not behave properly.
The fix for this is to not enter the loop detection or spiral logic in handle_request_invite
if the channel state is currently up. This way, no mid-call reinvites will be misinterpreted,
no matter what the nature of the reinvite may have been.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@272090 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'apps/app_meetme.c')
0 files changed, 0 insertions, 0 deletions