Luke Weber

Ill try to help with the cleanup in clientsignalingthread when you've got a patch that's more ready. As well, you could filter for iq stanzas that contain a jingle stanza....

So if you're using google, I think google talk brokers the call if I recall for gmail. Basically, you could check the invite that's sent out, but I'm pretty sure...

I actually think your issue is that iq's need to be sent to a full jid(jid/resource), and you're only sending to a bare jid.

Okay, now I'm actually seeing it. No, it's something about the client. You're sending duplicate data. In clientsignalingthread.cc -> session->set_current_protocol(cricket::PROTOCOL_HYBRID); -> try cricket::PROTOCOL_JINGLE I hadn't looked at this, and I'm...

This client is xmpp based, using the jingle in libjingle. Let me explain a bit. Jingle is xmpp based, and libjingle contains an implementation of jingle based on the spec,...

We switched to the java audio driver. This could be due to registering java objects into c++, which we do in the init java callback. My guess is we only...

Pull request #47 may resolve this issue via workaround, but there's no reason calling login twice should crash things. I'll leave this open and try to fix this on the...

Maybe this helps. https://github.com/lukeweber/webrtc-jingle-client/issues/125 I would check client_defines.h xmpp_comptibility as the current system was geared to connect to gmail.

I haven't done any work on that. I'd look at the base webrtc project and socket.io.

In the build command, did you specifically target arm? I don't have any iOS devices to test with. ./build/gyp_chromium --depth=. -DOS=ios -Dinclude_tests=0 -Denable_protobuf=0 -Denable_video=0 -Dtarget_arch=arm webrtcjingle.gyp