[asterisk-bugs] [Asterisk 0011644]: [patch] res_jabber appears to not be working correctly in /trunk

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11644 
====================================================================== 
Reported By:                davevg
Assigned To:                phsultan
====================================================================== 
Project:                    Asterisk
Issue ID:                   11644
Category:                   Resources/res_jabber
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 94978 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-27-2007 15:43 CST
Last Modified:              01-02-2008 21:33 CST
====================================================================== 
Summary:                    [patch] res_jabber appears to not be working
correctly in /trunk
Description: 
I did an in-place upgrade from a recent asterisk/branch/1.4 to
asterisk/trunk.  res_jabber did work correctly with 1.4 svn.  With the
trunk version every 4 seconds I receive this error:
[Dec 27 16:25:02] WARNING[16509]: res_jabber.c:1943 aji_recv_loop: JABBER:
socket read error
Both asterisk and jabber are located on the same server (CentOS 5) in this
instance.  See Additional info for details.
====================================================================== 

---------------------------------------------------------------------- 
 elguero - 01-02-08 21:33  
---------------------------------------------------------------------- 
phsultan:  Yes, branch 1.4 works.  After reinstalling gnutls (I removed it
when trunk switched to OpenSSL) and recompiling iksemel, upon startup 1.4
logged in right away. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-02-08 21:33  elguero        Note Added: 0076240                          
======================================================================