[asterisk-bugs] [Asterisk 0011644]: 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:                     assigned
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:              12-27-2007 17:03 CST
====================================================================== 
Summary:                    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 - 12-27-07 17:03  
---------------------------------------------------------------------- 
Does your XMPP server restrict users to using SSL?  The reason why I am
asking is that I am surprised that no one else has had a problem since the
change from GNU/TLS to OpenSSL was done a while back.

I too have had a problem and it is because my XMPP server restricts
connections to SSL.  I have traced it down in the code to where after the
SSL socket is setup, a call is made to a iksemel function and iksemel tries
to do a send using SSL but the function in iksemel is trying to use GNU/TLS
in order to send instead of the SSL socket that was setup using OpenSSL. 
That is if I am reading the code properly.

I wish I could put in some more info but I am in a rush right now.  I saw
this bug report and just wanted to help narrow it down.  I will try to add
to this bug report as soon as I can.  I will admit that I hesitated to
report this because I thought that maybe I was missing something somewhere
and didn't have time to keep tracing it down. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-27-07 17:03  elguero        Note Added: 0076073                          
======================================================================