Libjingle-0.4.0 connection problems with Ejabberd

We're are unable to connect to Ejabberd with the 'call' program supplied by Google.

We always get a SEC_I_INCOMPLETE_CREDENTIALS error.

Question 1: Does anyone have an idea on how to solve this problem.

Question 2: We've compiled Ejabberd with debug but there does not seem to be any error messages.
Are there some other options that might give better diagnostics?

Question 3: Has anyone successfully used any version of LibJingle to connect with Ejabberd?

Thanks in advance....

Scott

Here's the log from the 'call' program

Signalled with kfConnect: 6
SChannelAdapter::OnConnectEvent
XmppLoginTask::Advance - No error
XmppLoginTask::Advance - LOGINSTATE_STREAMSTART_SENT
SEND >>>>>>>>>>>>>>>>>>>>>>>>> : Fri Feb 09 18:45:13 2007
   <stream:stream to="doclinx.com" xml:lang="*" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
RECV <<<<<<<<<<<<<<<<<<<<<<<<< : Fri Feb 09 18:45:13 2007
   <?xml version='1.0'?>
     <stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='2255943561' from='doclinx.com' version='1.0' xml:lang='en'>
XmppLoginTask::Advance - LOGINSTATE_STREAMSTART_SENT
RECV <<<<<<<<<<<<<<<<<<<<<<<<< : Fri Feb 09 18:45:13 2007
   <stream:features>
     <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
     <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
       <mechanism>
         DIGEST-MD5
       </mechanism>
       <mechanism>
         PLAIN
       </mechanism>
     </mechanisms>
     <register xmlns='http://jabber.org/features/iq-register'/>
   </stream:features>
XmppLoginTask::Advance - LOGINSTATE_STARTED_XMPP
XmppLoginTask::Advance - LOGINSTATE_TLS_INIT
XmppLoginTask::Advance - LOGINSTATE_TLS_REQUESTED
SEND >>>>>>>>>>>>>>>>>>>>>>>>> : Fri Feb 09 18:45:13 2007
   <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
RECV <<<<<<<<<<<<<<<<<<<<<<<<< : Fri Feb 09 18:45:13 2007
   <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
XmppLoginTask::Advance - LOGINSTATE_TLS_REQUESTED
BeginSSL: doclinx.com
SChannel cipher strength: 40 - 168
SChannel supported algorithms:
  rc4 (26625)
  3des (26115)
  rc2 (26114)
  des (26113)
  md5 (32771)
  sha1 (32772)
  RSA (9216)
  ESDH (43522)
InitializeSecurityContext error: SEC_I_CONTINUE_NEEDED
XmppLoginTask::Advance - No error
XmppLoginTask::Advance - LOGINSTATE_STREAMSTART_SENT
SEND >>>>>>>>>>>>>>>>>>>>>>>>> : Fri Feb 09 18:45:13 2007
   <stream:stream to="doclinx.com" xml:lang="*" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
ContinueSSL
Input Buffer (
  (1342, SECBUFFER_TOKEN, 01045608)
  (0, SECBUFFER_EMPTY, 00000000)
)
InitializeSecurityContext error: SEC_I_INCOMPLETE_CREDENTIALS
<b>Warning(schanneladapter.cc:448): SChannelAdapter::Error(ContinueSSL, SEC_I_INCOMPLETE_CREDENTIALS)</b>
The thread 'Win32 Thread' (0x184) has exited with code 0 (0x0).

Here's the log from Ejabberd

&lt;I(&lt;0.224.0>:ejabberd_listener:90): (#Port&lt;0.338>) Accepted connection {{192,168,
1,174},2432} -> {{192,168,1,174},5222}
*DBG* &lt;0.292.0> got all_state_event become_controller in state wait_for_stream
*DBG* &lt;0.292.0> switched to state wait_for_stream
D(&lt;0.293.0>:ejabberd_receiver:261) : Received XML on stream = "&lt;stream:stream to
=\"doclinx.com\" xml:lang=\"*\" version=\"1.0\" xmlns:stream=\"http://etherx.jab
ber.org/streams\" xmlns=\"jabber:client\">\r\n"
*DBG* &lt;0.292.0> got event {xmlstreamstart,
                              "stream:stream",
                              [{"to","doclinx.com"},
                               {"xml:lang","*"},
                               {"version","1.0"},
                               {"xmlns:stream",
                                "http://etherx.jabber.org/streams"},
                               {"xmlns","jabber:client"}]} in state wait_for_str
eam
D(&lt;0.292.0>:ejabberd_c2s:1207) : Send XML on stream = "&lt;?xml version='1.0'?>&lt;str
eam:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
id='2255943561' from='doclinx.com' version='1.0' xml:lang='en'>"
D(&lt;0.292.0>:ejabberd_c2s:1207) : Send XML on stream = "&lt;stream:features>&lt;starttl
s xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>&lt;mechanisms xmlns='urn:ietf:params:xm
l:ns:xmpp-sasl'>&lt;mechanism>DIGEST-MD5&lt;/mechanism>&lt;mechanism>PLAIN&lt;/mechanism>&lt;/m
echanisms>&lt;register xmlns='http://jabber.org/features/iq-register'/>&lt;/stream:fea
tures>"
*DBG* &lt;0.292.0> switched to state wait_for_feature_request
D(&lt;0.293.0>:ejabberd_receiver:261) : Received XML on stream = "&lt;starttls xmlns=\
"urn:ietf:params:xml:ns:xmpp-tls\"/>"
*DBG* &lt;0.292.0> got event {xmlstreamelement,
                              {xmlelement,
                                  "starttls",
                                  [{"xmlns",
                                    "urn:ietf:params:xml:ns:xmpp-tls"}],
                                  []}} in state wait_for_feature_request
D(&lt;0.293.0>:ejabberd_receiver:261) : Received XML on stream = []
D(&lt;0.292.0>:ejabberd_c2s:1207) : Send XML on stream = "&lt;proceed xmlns='urn:ietf:
params:xml:ns:xmpp-tls'/>"
*DBG* &lt;0.292.0> switched to state wait_for_stream
D(&lt;0.293.0>:ejabberd_receiver:261) : Received XML on stream = []

Libjingle-0.4.0 connection problems with Ejabberd

I've been able to get it working with plain authentication.

Be sure to call set_use_tls(false) and set_allow_plain(true) on your XmppClientSettings object. That worked for me.

Anyone know a way to get it working withoutout using plain?

Syndicate content