diff options
| author | David Vossel <dvossel@digium.com> | 2010-07-14 19:51:08 +0000 |
|---|---|---|
| committer | David Vossel <dvossel@digium.com> | 2010-07-14 19:51:08 +0000 |
| commit | d1c9a4b366cea65e044736cc050c3f322019e1c7 (patch) | |
| tree | 002312ddfba7944381e16f9ee6b20a7c0f47d13f /include/asterisk/optional_api.h | |
| parent | cf7bbcc4c667a1fe907b0ec71e9a4fed506b8c23 (diff) | |
handle special case were "200 Ok" to pending INVITE never receives ACK
Unlike most responses, the 200 Ok to a pending INVITE Request is
acknowledged by an ACK Request. If the ACK Request for this Response is not received
the previous behavior was to immediately destroy the dialog and hangup
the channel. Now in an effort to be more RFC compliant, instead of immediately
destroying the dialog during this special case, termination is done with a BYE Request
as the dialog is technically confirmed when the 200 Ok is sent even if the ACK is
never received. The behavior of immediately hanging up the channel remains.
This only affects how dialog termination proceeds for this one special case.
RFC 3261 section 13.3.1.4
"If the server retransmits the 2xx response for 64*T1 seconds without receiving
an ACK, the dialog is confirmed, but the session SHOULD be terminated. This is
accomplished with a BYE, as described in Section 15."
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@276439 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'include/asterisk/optional_api.h')
0 files changed, 0 insertions, 0 deletions