(18:22:51) backend-fs2: Creating hash table for participants
(18:22:51) backend-fs2: Setting stun-ip on new stream: 132.177.123.6
(18:22:51) backend-fs2: Could not set transmitter nice: Could not create the nicesrc element.
(18:22:51) backend-fs2: Error creating the stream.
(18:22:51) media: Error adding stream.
(18:22:51) backend-fs2: connecting pad: success
(18:22:51) backend-fs2: Setting stun-ip on new stream: 132.177.123.6
(18:22:51) backend-fs2: Could not set transmitter nice: Could not create the nicesrc element.
(18:22:51) backend-fs2: Error creating the stream.
(18:22:51) media: Error adding stream.
So there is no way to establish the connection, it seems like.
Honestly, I've never used audio/video in Pidgin myself, since I
run a windows client most of the time. Just trying to break down
the debug messages as best I can though. I'm chopping it down a
bit to highlight what I find to be the interesting parts.
(18:22:54) jabber: Sending (ssl) ([email protected]/727ce02):
<iq type='set' id='purple221dd57f' from='[email protected]/727ce02'
to='[email protected]/a53e4eb'>
<jingle xmlns='urn:xmpp:jingle:1'
action='' initiator='[email protected]/727ce02'
responder='[email protected]/a53e4eb'
sid='purple221dd57e'>
<transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'/>
(18:23:03) jabber: Recv (ssl)(4095):
<iq type="set" id="purple50e73b97" from="[email protected]/a53e4eb"
to="[email protected]/727ce02">
<jingle xmlns="urn:xmpp:jingle:1"
action="" initiator="[email protected]/727ce02"
responder="[email protected]/a53e4eb"
sid="purple221dd57e">
<transport xmlns="urn:xmpp:jingle:transports:ice-udp:1"
pwd="mgnve2uX+W052TcSAmLkYX" ufrag="p1KR">
<candidate component="2" foundation="1" generation="0"
id="purple50e73b8f" ip="192.168.2.104" network="0" port="46559"
priority="2013266430" protocol="udp" type="host"/>
<candidate component="1" foundation="1" generation="0"
id="purple50e73b90" ip="192.168.2.104" network="0" port="60362"
priority="2013266431" protocol="udp" type="host"/>
</transport>
(18:23:03) media: purple_media_add_remote_candidates: couldn't
find stream audio-session [email protected]/a53e4eb.
(18:23:03) jingle-rtp: stream-info: type 1 id: (null) name: (null)
(18:23:03) media: purple_media_add_remote_candidates: couldn't
find stream video-session [email protected]/a53e4eb.
(18:23:03) jingle-rtp: stream-info: type 1 id: (null) name: (null)
Seems like a transport negotiation issue... I'm not sure how to
resolve such an issue, but I suspect this is the cause of your
problems. It seems like your client isn't offering any transport
candidates though. Again, I'm not sure if this is normal or not,
but it seems like a point of interest.
According to: http://xmpp.org/extensions/xep-0176.html#protocol-initiate
In order for the initiator in a Jingle exchange to start the
negotiation, it sends a Jingle "session-initiate" stanza that
includes at least one content type, as described in XEP-0166. If
the initiator wishes to negotiate the ice-udp transport method for
an application format, it MUST include a <transport/> child
element qualified by the 'urn:xmpp:jingle:transports:ice-udp:1'
namespace (see Namespace Versioning regarding the possibility of
incrementing the version number). This element SHOULD in turn
contain one <candidate/> element for each of the initiator's
higher-priority transport candidates as determined in accordance
with the ICE methodology, but MAY instead be empty (with each
candidate to be sent as the payload of a transport-info message).
It looks like Pidgin may be in the fault though, because a child
candidate is not provided? Hopefully someone else can shed further
light on this.
---
Jingle: http://xmpp.org/extensions/xep-0166.html
Jingle Raw UDP Transport Method: http://xmpp.org/extensions/xep-0177.html
Jingle ICE-UDP Transport Method: http://xmpp.org/extensions/xep-0176.html
--
Steven
[email protected]
On 4/6/2013 10:40 AM, Thomas Koch
wrote:
Hi,
I just had a chat with a young linux enthusiast trying videochat and it failed
for us. I've copied the part from pidgin --debug that might be of interest:
https://gist.github.com/anonymous/5326914
If anybody could give us some hints what went wrong?
We're both on normal IPv4 home networks (german telekom/swisscom) with recent
pidgin versions (linux mint 14/debian testing).
Regards,
Thomas Koch, http://www.koch.ro
_______________________________________________
[email protected] mailing list
Want to unsubscribe? Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support
_______________________________________________
[email protected] mailing list
Want to unsubscribe? Use this link:
http://pidgin.im/cgi-bin/mailman/listinfo/support
