[asterisk-users] Problem with (asterisk1.8-iksemel1.4-GoogleVoice)

neo haux neo.haux at gmx.com
Tue Aug 2 12:06:16 CDT 2011


Hi,

I´ve compiled asterisk-1.8.5.0   on my Debian based distro (Pinguy)
I also compiled iksemel (v1.4) with the option 2./configure
--with-libgnutls-prefix=/usr"
As explained in this link (to avoid compilation error )
http://code.google.com/p/iksemel/issues/detail?id=29#c3

I configured jabber.conf and gtalk.conf as explained in
wiki.asterisk.org, but I have this error when starting :
asterisk -vvvvc
...
...
JABBER: asterisk INCOMING: <stream:stream from="gmail.com"
id="57A17D99ADBC6814" version="1.0"
xmlns:stream="http://etherx.jabber.org/streams"
xmlns="jabber:client"><stream:features><starttls
xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism><mechanism>X-OAUTH2</mechanism></mechanisms></stream:features>
[Aug  2 12:57:40] ERROR[31479]: res_jabber.c:1610 aji_act_hook:
OpenSSL not installed. You need to install OpenSSL on this system, or
disable the TLS option in your configuration file
[Aug  2 12:57:40] WARNING[31479]: res_jabber.c:1391 aji_recv: Parsing
failure: Hook returned an error.
[Aug  2 12:57:40] WARNING[31479]: res_jabber.c:2742 aji_recv_loop:
JABBER: Got hook event.
[Aug  2 12:57:56] WARNING[31479]: res_jabber.c:2753 aji_recv_loop:
JABBER: socket read error


But I have already openssl :
root at mohamed-desktop:/usr/src# dpkg -l |grep -i openssl
ii  libcurl3           7.21.0-1ubuntu1.1
Multi-protocol file transfer library (OpenSSL)
ii  libxmlsec1-openss  1.2.14-1+squeeze1build0.10.10.1       Openssl
engine for the XML security library
ii  openssl            0.9.8o-1ubuntu4.4                     Secure
Socket Layer (SSL) binary and related cryptographic tools
ii  python-op          0.10-1                                Python
wrapper around the OpenSSL library
ii  ssl-cert           1.0.26                                simple
debconf wrapper for OpenSSL


Have you any idea where is the problem ?
NB: I didn´t have that problem with asterisk 1.6

Thx



More information about the asterisk-users mailing list