[asterisk-bugs] [JIRA] Closed: (ASTERISK-16859) Jabber service unable to connect to Zimbra XMPP server

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-16859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp closed ASTERISK-16859.
----------------------------------

    Resolution: Cannot Reproduce

The newest version of Zimbra has done away with the built in XMPP server unfortunately but I have tested with Openfire (which Zimbra used) and confirmed that res_xmpp plays happy. This may have been an issue specifically with res_jabber or a configuration issue.

> Jabber service unable to connect to Zimbra XMPP server
> ------------------------------------------------------
>
>                 Key: ASTERISK-16859
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16859
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Resources/res_jabber
>            Reporter: SplatNIX
>            Assignee: Dave Bowerman
>            Severity: Minor
>         Attachments: issue18198.txt
>
>
> Attempting to configure the Asterisk Jabber integration with a Zimbra Version 6 XMPP server and always failing. What I see when I enable debugging, in Asterisk, is the following:
> voip*CLI> jabber set debug on
> Jabber Debugging Enabled.
> JABBER: asterisk INCOMING: <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="domain.net" id="154c29e6" xml:lang="en" version="1.0"><stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism></mechanisms><compression xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth xmlns="http://jabber.org/features/iq-auth"/></stream:features>
> JABBER: asterisk OUTGOING: <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
> JABBER: asterisk INCOMING: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
> JABBER: asterisk OUTGOING: <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='domain.net' version='1.0'>
> JABBER: asterisk INCOMING: </stream:stream>
> [Oct 23 14:37:43] ERROR[26883]: res_jabber.c:1576 aji_act_hook: aji_act_hook was called with out a packet
> [Oct 23 14:37:43] WARNING[26883]: res_jabber.c:1391 aji_recv: Parsing failure: Hook returned an error.
> [Oct 23 14:37:43] WARNING[26883]: res_jabber.c:2742 aji_recv_loop: JABBER: Got hook event.
> [Oct 23 14:37:43] WARNING[26883]: res_jabber.c:2753 aji_recv_loop: JABBER: socket read error
> and from the Zimbra side:
> 2010-10-23 14:03:22,983 WARN  [AnonymousIoService-15] [] im - Stream error detected
> java.lang.IllegalArgumentException: Illegal JID: asterisk at domain.net/d20d13a7
> 	at org.xmpp.packet.JID.init(JID.java:401)
> If I connect to the same Zimbra service using Pidgin I am prompted to accept a self signed SSL cert and then it works fine.
> Any ideas ? 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira