diff options
| author | oej <oej@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-09-09 12:44:36 +0000 |
|---|---|---|
| committer | oej <oej@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-09-09 12:44:36 +0000 |
| commit | 4937dd7f4bd04a9ff1567a1e903f839c43ac136e (patch) | |
| tree | 88b07ba3d4690f3cb0288895afb81553394250cb /LICENSE | |
| parent | 73317c595052ebdadb360eefe2e18cb717053822 (diff) | |
Don't destruct sessions prematurely. Especially not when we want reliable retransmissions...
If this works properly, we might have to check 1.2 to implement a backport.
The theory is that if you get a final reply in a session, it is ok to destroy the session.
If you send a final reply, you need to keep the session open for potential retransmits
from the other side. If you send a HANGUP/CANCEL, wait to the other side confirms
or until you have a timeout. If you send HANGUP/CANCEL/ACK reliably, don't destroy
the session so that you cancel the needed retransmits.
I will have to change the timer to 64*T1, but that will be a separate patch. That will
mean that if we know the roundtrip time, we can destroy sessions quicker.
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@42537 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions