Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STUN server not used on filetransfer #555

Closed
mikerhyner opened this issue Jun 14, 2017 · 2 comments
Closed

STUN server not used on filetransfer #555

mikerhyner opened this issue Jun 14, 2017 · 2 comments

Comments

@mikerhyner
Copy link

mikerhyner commented Jun 14, 2017

When trying to transfer a file, and no HTTP file transfer is possible, a STUN server won't be used when clients are on different networks (not the same LAN). When clients are on the same network, transfer works. Peer I sen't a file to (receiving side) only sees an incoming file event, but cannot download ifile sent. On sending side, get the message within JS console:
ICE failed, add a STUN server and see about:webrtc for more details

When I go to "about:webrtc" on sending side, below ICE statistics there's only:

192.168.101.212:35978/udp(host)	10.128.160.30:39466/udp(host)	failed	9115005270282354000		
192.168.101.212:35978/udp(host)	194.230.159.138:39466/udp(serverreflexive)	failed	7241540810645045000	

And I can't see any stun server involved and within protocol section.

But the interesting thing is, that when using video chat function with the same peer (not on the same network), STUN will be used and communication works perfectly!

Within "about:webrtc", I got this below ICE statistics:

Lokaler Kandidat Externer Kandidat ICE-Status Priorität Nominiert Ausgewählt
192.168.101.229:60634/udp(host) 10.128.160.30:48319/udp(host) failed 9115005270282354000
192.168.101.229:60634/udp(host) 194.230.159.138:48319/udp(serverreflexive) inprogress 7241540810645045000
213.213.163.30:60634/udp(serverreflexive) 194.230.159.138:48319/udp(serverreflexive) succeeded 7241540809772646000 true true
					10.128.160.30:9/tcp(host) 

And within protocol section there can be seen one of the configured STUN server involved:
STUN-CLIENT(n7z6|IP4:213.213.163.30:60634/UDP|IP4:194.230.159.138:48319/UDP(srflx(IP4:192.168.101.229:60634/UDP|stun.l.google.com:19302)|a=candidate:1871324864 1 UDP 1686052607 194.230.159.138 48319 typ srflx raddr 10.128.160.30 rport 48319 generation 0 )): Received response; processing

Note: I'm using jsxc roundcube plugin (which is on version 3.0.1 only), and this release seems not to have implemented httpUpload functionality yet, so I'm forced to use WebRTC method for filetransfer there. But also on the most current build 3.2.1, when httpUpload is configurative turned off or not available on xmpp server, the same problem as described persists.

Can you shed some light on that or tell me what I need to configure that STUN/TURN servers will also be used for FileTransfers?

Thank you in advance & greets
Mike Rhyner / konzeptplus GmbH

@sualko sualko added the bug label Jun 14, 2017
@sualko
Copy link
Member

sualko commented Jun 14, 2017

Thanks for reporting and the detailed information. I will have a look at this.

@sualko
Copy link
Member

sualko commented Jun 26, 2017

I opened upstream a pull request for this: otalk/jingle.js#36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants