[asterisk-bugs] [Asterisk 0014703]: sip call setup bug
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Apr 1 21:20:59 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14703
======================================================================
Reported By: genie
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14703
Category: Channels/chan_sip/General
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.6.0.6
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-03-19 08:04 CDT
Last Modified: 2009-04-01 21:20 CDT
======================================================================
Summary: sip call setup bug
Description:
I'm testing SIP protocol on Asterisk. While performing tests on performance
with packet loss I came across a bug of Asterisk while call initiation. In
my Asterisk SIP configuration I have 'canreinvite=no' set. That is why
normal call setup looks like that:
student.agh.edu.pl/~genie/Visio-call_setup_no_reinvite.pdf
However, if the first ACK packet of the flow is lost and the ClientA who
does not know it sends Invite_with_authorisation packet the call will never
be set up, ending up with a infinte loop where client sends ACK messages
and asterisk '491 request pending' message. The wireshark files captured on
both ClientA and Asterisk can be found here:
http://student.agh.edu.pl/~genie/asterisk/
regards,
genie
======================================================================
----------------------------------------------------------------------
(0102590) genie (reporter) - 2009-04-01 21:20
http://bugs.digium.com/view.php?id=14703#c102590
----------------------------------------------------------------------
i'm not sure if i got you right ravindrad but i did some extra tests and
here is what i've found:
UserA start one sesion (CSeq = 1) and without finishing it starts another
one (CSeq = 2). Therefore astersik sends '491 request pending'. However the
491 message holds Cseq=2 info. When i was using ekiga, it resonded fur such
a 491 message with ACK-Cseq=2, while it was ACK-CSeq=1 missing. So as for
me the bug is that '491 messages' hold wrong CSeq.
I hope it was the same what you have found out.
Issue History
Date Modified Username Field Change
======================================================================
2009-04-01 21:20 genie Note Added: 0102590
======================================================================
More information about the asterisk-bugs
mailing list