[asterisk-bugs] [Asterisk 0016010]: Call abort after wrong behaviour of VNAK transmission

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16010 
====================================================================== 
Reported By:                ffloimair
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16010
Category:                   Channels/chan_iax2
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.26.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-02 03:22 CDT
Last Modified:              2009-10-14 20:35 CDT
====================================================================== 
Summary:                    Call abort after wrong behaviour of VNAK
transmission
Description: 
Asterisk sends VNAK to signal a retransmission of a packet. After
retransmission the request is sent again and again... Abort of the call is
the result after a few retries.
Overall, asterisk very often sends VNAK after receiving LAGRQ and PING
consecutively. Why does asterisk know that packet 2 after 1 is missing if
there was no packet 3 so far (numbers referring to ascending sequence
numbers in IAX Header)? This is confusing since the RFC states the below
text requiring to retransmit all frames with a higher sequence number than
the one received with the VNAK.

Please see the attached pcap file.

There was no significant output in the asterisk console, so I do not post
this as of now. If required I can post this later.

====================================================================== 

---------------------------------------------------------------------- 
 (0112313) c0rnoTa (reporter) - 2009-10-14 20:35
 https://issues.asterisk.org/view.php?id=16010#c112313 
---------------------------------------------------------------------- 
Attached debug messages with VNAK. There is another interesting line:
"iseqno 11 now within window 12->17"

And can anybody tell me, what does mean "FRAME_CONTROL (-1)"? It seems,
that issue appear after that message.

Thx! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-14 20:35 c0rnoTa        Note Added: 0112313                          
======================================================================