[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. 
====================================================================== 
http://bugs.digium.com/view.php?id=13732 
====================================================================== 
Reported By:                jsmith
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13732
Category:                   Channels/chan_iax2
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 150606 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-17 12:34 CDT
Last Modified:              2008-12-17 09:34 CST
====================================================================== 
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.
====================================================================== 

---------------------------------------------------------------------- 
 (0096531) ffloimair (reporter) - 2008-12-17 09:34
 http://bugs.digium.com/view.php?id=13732#c96531 
---------------------------------------------------------------------- 
Does not really explain that the fix with rsa is working, but otherwise to
me it seems it is associated with the bug report I filed a few weeks ago
(http://bugs.digium.com/view.php?id=13918). Version 1.4.22 does not have
the fix for that unless you patch it
(http://bugs.digium.com/file_download.php?file_id=20761&type=bug) manually
while 1.6.1 in SVN certainly does have this fix included.