[OpenSIPS-Users] ACK Timer
M.Khaled W Chehab
kchehab at icucall.com
Mon Mar 11 12:09:40 CET 2013
Dear Nicolas,
I am using opensips 1.8.2 tls version ,the problem still exist while even
while I am using the timer ,please update me if you have a solution .
if (has_totag()) {
if ( is_method("INVITE")) {
$avp(timeout2) = 3;
} else if (is_method("ACK")) {
$avp(timeout2) = 3540;
}
Regards
Khaled chehab
From: Brito Nicolas [mailto:nicolas.brito at andrexen.com]
Sent: Tuesday, February 12, 2013 4:52 PM
Cc: M.Khaled W Chehab
Subject: Re: [OpenSIPS-Users] ACK Timer
Hi Khaled,
What you posted at first seems good so far the dialog will be dropped after
3 second which is not bad.
The only other possibility is to actually make a detection in OpenSIPS for
CANCEL emition instead of ACK.
If you are using FreeSWITCH i offer to send you a patch that solve this
behaviour.
Regards
Nicolas
Le 12/02/2013 15:02, Muhammad Shahzad a écrit :
Ah, again typo, in last line of previous email, i meant to recover loss of
few seconds between 200 OK and CANCEL from caller, (not ACK from caller,
since ACK establishes a billable call).
Thank you.
On Tue, Feb 12, 2013 at 2:54 PM, Muhammad Shahzad <shaheryarkh at gmail.com>
wrote:
Sorry i didn't see you are setting dialog timeout for sequential INVITE,
instead of initial INVITE, so this timeout would actually have no effect on
new call, it will effect only established call (e.g. when caller or callee
sets call on hold etc.) and when that sequential INVITE comes in the
destination has to accept it within 3 seconds, which is OK, since call is
already established, only its state being changed.
Secondly, a call is not considered established till ACK arrives from caller
party. Since caller never sends ACK, so destination should end call (after
32 seconds per RFC 3261) even if it does not receives CANCEL from caller.
And if destination receives CANCEL, then call should end anyway. Such call
can not be billed, since it was never established.
More information about the Users
mailing list