[asterisk-bugs] [Asterisk 0013918]: [patch] IAX2 not conforming to standard

[Asterisk Bug Tracker]

The following issue has been set as RELATED TO issue 0013732. 
====================================================================== 
http://bugs.digium.com/view.php?id=13918 
====================================================================== 
Reported By:                ffloimair
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   13918
Category:                   Channels/chan_iax2
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.21.2 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-11-18 04:02 CST
Last Modified:              2009-01-20 13:21 CST
====================================================================== 
Summary:                    [patch] IAX2 not conforming to standard
Description: 
We're using IAX2 to establish a trunk connection between our proprietary
system and an Asterisk server. However since Asterisk version 1.4.21.2,
which fixed the "IAX POKE resource exhaustion" (AST-2008-10), we're having
troubles using POKE requests.

I am aware that the fixes incorporated in 1.4.21.2 include a change in the
call number usage for POKE requests (call number 1). However when sending a
POKE from our system to the Asterisk server with destination caller ID 0 we
do get a PONG in return from caller ID 1. The problem is that Asterisk does
not increase the Inbound Stream Sequence Number from 0 to 1 when responding
with a PONG. As a result we run into a timeout after three unsuccessful
tries. An ACK would be sent by our system only if the ISeqNo is also
increased to 1 in the PONG.

The same issue remains for 1.6.x so far. This clearly is not conforming to
the IAX2 standard (draft). 
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013732 IAX2 qualify problems between 1.6 and 1...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-20 13:21 blitzrage      Relationship added       related to 0013732  
======================================================================