Call never reaches callee
See original GitHub issueCallee never notices that there’s a call for them.
Caller watches spinner forever.
Which jsxc version number do you use?
git master eeab8355e54582cf610f9091160f8c951faf6bfb
I have updated from git several times in last few weeks, so this seems to be constant state of affairs.
In which system do you use jsxc? (e.g. owncloud, sogo, …)
example login page
Can you reproduce your issue? If yes, how?
See below
Which browser and browser version do you use?
Google Chrome Version 57.0.2987.13 dev (64-bit)
Same with Firefox 51.0 (64-bit)
Do you have any browser plugins enabled?
In Chrome, no.
Do you see any errors in your javascript console?
jsxc.dep.js:4809 POST https://dev.decent.im/http-bind/ 504 (Gateway Time-out)
Setup:
I run my own XMPP server (dev.decent.im) based on Prosody from upstream hg trunk (changeset 7909:428d4abee723 of Feb 20 at the moment). mod_bosh is enabled, nginx forwards BOSH connections to https 5281 port as follows (conforming to JSXC recommendations):
location /http-bind {
proxy_pass https://localhost:5281/http-bind;
proxy_set_header Host $host;
proxy_buffering off;
tcp_nodelay on;
}
I open two Chrome sessions: one regular and one incognito. In both, I navigate to https://dev.decent.im/jsxc/example/ , set XMPP server to dev.decent.im and BOSH URL to /http-bind/ , and log in using Box Login widget (others don’t work as they produce POST request to login.html which is static page).
I log in as users andrey.utkin@dev.decent.im and andrey.utkin.2@dev.decent.im . They have each other in roster and can message each other. When I make call between them, it never passes. I have read the note that JSXC’s default STUN server, stunprotocol.net, has banned Russia and Ukraine, but I’m in the UK at the moment. From chrome://webrtc-internals it seems like STUN processing accomplishes, however I am ready to provide more info on that on request.
I suspect there may be something wrong with XMPP connection via HTTP proxied by nginx. See combined logs in jsxc_call.log, and browser console logs in caller.js_log and callee.js_log .
Note these messages - probably that is what’s wrong, but I have no idea what to do about that.
==> /var/log/nginx/dev.decent.im.error_log <==
2017/02/27 23:16:00 [warn] 31562#0: *1015 upstream server temporarily disabled while reading response header from upstream, client: 188.221.179.100, server: dev.decent.im, request: "POST /http-bind/ HTTP/1.1", upstream: "https://[::1]:5281/http-bind/", host: "dev.decent.im", referrer: "https://dev.decent.im/jsxc/example/"
2017/02/27 23:16:00 [error] 31562#0: *1015 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 188.221.179.100, server: dev.decent.im, request: "POST /http-bind/ HTTP/1.1", upstream: "https://[::1]:5281/http-bind/", host: "dev.decent.im", referrer: "https://dev.decent.im/jsxc/example/"
In clients’ browser console, I see such messages:
jsxc.dep.js:4809 POST https://dev.decent.im/http-bind/ 504 (Gateway Time-out)
still it seems the clients are somewhat resilient to these errors, as later buddies presence updates happen and are logged to console.
Thanks in advance for any help with this.
Also, a quick question - is mailing list actually a thing? I’ve subscribed to it only to see that archive is empty, which discouraged me from posting there.
Issue Analytics
- State:
- Created 7 years ago
- Comments:23 (9 by maintainers)
Top GitHub Comments
It indeed works now with latest master. Thanks again!
Thanks for heads up, will test soon.