[asterisk-bugs] [Asterisk 0013732]: IAX2 qualify problems between 1.6 and 1.4 boxes

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13732 
====================================================================== 
Reported By:                jsmith
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   13732
Category:                   Channels/chan_iax2
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     assigned
Target Version:             1.6.0.5
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 150606 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-17 12:34 CDT
Last Modified:              2009-06-19 17:19 CDT
====================================================================== 
Summary:                    IAX2 qualify problems between 1.6 and 1.4 boxes
Description: 
I have two boxes... one is running 1.4.22 and the other is running 1.6.0. 
Both are sending IAX2 POKEs to the other (as part of the qualification
process), but neither seems to be responding correctly to the other.  On
Tilghman's advice, I upgraded the 1.6.0 box to the 1.6.1 branch in SVN
(r150606), and am seeing the same thing.

I'm attaching two captures... the first is simply a packet capture of all
port 4569 traffic on the 1.6.1 box.  The second is the same thing, but with
both an "iax2 reload" and a "restart now" thrown in for good measure.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013918 [patch] IAX2 not conforming to standard
related to          0014041 [patch] IAXy runs ok for a while, then ...
====================================================================== 

---------------------------------------------------------------------- 
 (0106739) dvossel (administrator) - 2009-06-19 17:19
 https://issues.asterisk.org/view.php?id=13732#c106739 
---------------------------------------------------------------------- 
I believe my patch for https://issues.asterisk.org/view.php?id=15361 may
have to do with this. From what I understand, PONGS should contain the
timestamp of the POKE just like an ACK.  In the packet captures above, the
PONG's TS is 0ms which is not correct.  Issue
https://issues.asterisk.org/view.php?id=15361 resulted from
converting the TS for a RX:POKE message to host byte order using ntohs()
rather than ntohl() (TS in a Full Frame is a 32bit field requiring network
to host long function).  On x86 systems this usually results in a 0ms TS
depending on the TS's size, on Power PC systems this results in the first 2
bytes being truncated which kind of masks the issue until the TS grows
larger.


Not sure if this resolves anything, but It may have something to do with
it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-19 17:19 dvossel        Note Added: 0106739                          
======================================================================