gateway issuing a hangup message

1,171 views
Skip to first unread message

Wilbert Jackson

unread,
Dec 4, 2014, 10:07:14 AM12/4/14
to meetech...@googlegroups.com
Hi Lorenzo,

I am receiving a gateway hangup message automatically from the gateway during application sendTrickleCandidate calls, which terminates the call. Is there some timeout setting that triggers the gateway to send an automatic hangup message?

thanks

wilbert

Wilbert Jackson

unread,
Dec 5, 2014, 7:55:35 AM12/5/14
to meetech...@googlegroups.com
Found problem of gateway hanging up. During trickle gathering an audio stream was not found. Not sure why this happens after quite a few successful test runs. Have to reset the gateway to fix problem. Question: Why does the error as show below happen? I see it  lot on some disconnects? Uncaught TypeError: Cannot read property 'readyState' of null dlspproxy.js:1138

Ooops: 466 Trickle error: no data stream 4vision.com:3004/dlspproxy.js:873
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Got event on session 2521172237 dlspproxy.js:282
Object dlspproxy.js:283
  -- Event is coming from 3422954682 (janus.plugin.videocall) dlspproxy.js:363
Object dlspproxy.js:365
Notifying application... dlspproxy.js:378
 ::: Got a message ::: videocalltest.js:429
{"videocall":"event","result":{"event":"calling"}} videocalltest.js:430
Waiting for the peer to answer... videocalltest.js:454
Object dlspproxy.js:869
Candidate sent! dlspproxy.js:870
Long poll... dlspproxy.js:241
Got event on session 2521172237 dlspproxy.js:282
Object dlspproxy.js:283
  -- Event is coming from 3422954682 (janus.plugin.videocall) dlspproxy.js:363
Object dlspproxy.js:365
Handling SDP as well... dlspproxy.js:373
Object dlspproxy.js:374
Notifying application... dlspproxy.js:378
 ::: Got a message ::: videocalltest.js:429
{"videocall":"event","result":{"event":"accepted","username":"tj"}} videocalltest.js:430
tj accepted the call! videocalltest.js:487
Handling Remote Stream: dlspproxy.js:1096
MediaStreamEvent dlspproxy.js:1097
Starting bitrate monitor dlspproxy.js:1101
 ::: Got a remote stream ::: videocalltest.js:579
{"onremovetrack":null,"onaddtrack":null,"onended":null,"ended":false,"id":"janus","label":"janus"} videocalltest.js:580
Remote description accepted! dlspproxy.js:1388
Long poll... dlspproxy.js:241
Got event on session 2521172237 dlspproxy.js:282
Object dlspproxy.js:283
Cleaning WebRTC stuff dlspproxy.js:1509
Stopping local stream dlspproxy.js:1522
 ::: Got a cleanup notification ::: videocalltest.js:662
Uncaught TypeError: Cannot read property 'readyState' of null dlspproxy.js:1138
Long poll... dlspproxy.js:241
Got event on session 2521172237 dlspproxy.js:282
Object dlspproxy.js:283
  -- Event is coming from 3422954682 (janus.plugin.videocall) dlspproxy.js:363
Object dlspproxy.js:365
Notifying application... dlspproxy.js:378
 ::: Got a message ::: videocalltest.js:429
{"videocall":"event","result":{"event":"hangup","username":"tj","reason":"Remote hangup"}} videocalltest.js:430
Call hung up by tj (Remote hangup)! videocalltest.js:498
Cleaning WebRTC stuff dlspproxy.js:1509

Gatecrasher777

unread,
Dec 5, 2014, 2:28:09 PM12/5/14
to meetech...@googlegroups.com
This might be related to the trickle ICE issue that was very recently resolved. I used to have frequent "hangup"s in Firefox. An updated build will fix that. But it is also important to use latest versions of browsers as these are more likely to employ trickle ICE.

Gatecrasher777

unread,
Dec 5, 2014, 2:33:26 PM12/5/14
to meetech...@googlegroups.com
That tickle ICE issue is here

Wilbert Jackson

unread,
Dec 5, 2014, 2:34:46 PM12/5/14
to meetech...@googlegroups.com
Thanks

Wilbert Jackson

unread,
Dec 5, 2014, 2:45:30 PM12/5/14
to meetech...@googlegroups.com
Where is Janus log located? How do I update to get the latest version?

Thanks for the response.


On Friday, December 5, 2014 2:28:09 PM UTC-5, Gatecrasher777 wrote:

Wilbert Jackson

unread,
Dec 5, 2014, 4:30:15 PM12/5/14
to meetech...@googlegroups.com
Level 7 log shown below. My problem with the gateway hanging looks like on ICE stream failure. Not sure of what causes the problem but If I reset the computer that I was trying to connect with the problem goes away. I am wondering if it could be related to a low memory buffering issue or long polling timing issue? When computers are the same network as opposed to be remotely connected to each other the problem still occurs.

wilbert

New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
Request completed, freeing data
New connection on REST API: 108.20.20.72
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... Just parsing headers for now...
Content-Type: application/json
Content-Length: 245
Connection: keep-alive
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
  -- Uploaded data (245 bytes)
  -- Data we have now (245 bytes)
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
Done getting payload, we can answer
{"janus":"trickle","candidate":{"sdpMLineIndex":0,"sdpMid":"audio","candidate":"candidate:3894397742 1 tcp 1518280447 192.168.1.7 0 typ host tcptype active generation 0"},"transaction":"rgrvOEsNqb86","sessionId":2215234259,"handleId":3253666903}
[3253666903] Trickle candidate (audio): candidate:3894397742 1 tcp 1518280447 192.168.1.7 0 typ host tcptype active generation 0
[3253666903] Adding remote candidate for component 1 to stream 1
[3253666903]   -- Ignoring this candidate, the component is already ready
Request completed, freeing data
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 117 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
    ... and read -1 of them from SSL...
[3253666903] DTLS check pending: 1887
[3253666903] >> Going to send DTLS data: 1887 bytes
[3253666903] >> >> Read 1887 bytes from the write_BIO...
[3253666903] >> >> ... and sent 1887 of those bytes on the socket
Initialization not finished yet...
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 973 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
    ... and read -1 of them from SSL...
[3253666903] DTLS check pending: 91
[3253666903] >> Going to send DTLS data: 91 bytes
[3253666903] >> >> Read 91 bytes from the write_BIO...
[3253666903] >> >> ... and sent 91 of those bytes on the socket
[3253666903] DTLS established, yay!
[3253666903] Computing sha-256 fingerprint of remote certificate...
[3253666903] Remote fingerprint (sha-256) of the client is D8:E4:3F:F8:B6:32:86:0E:B6:46:51:65:F3:6D:97:07:38:15:52:6F:42:22:AB:AB:CB:4E:48:9B:74:B0:74:AA
[3253666903]  Fingerprint is a match!
[3253666903] Created inbound SRTP session for component 1 in stream 1
[3253666903] Created outbound SRTP session for component 1 in stream 1
[3253666903] The DTLS handshake for the component 1 in stream 1 has been completed
[3253666903] The DTLS handshake has been completed
[3253666903] Telling the plugin about it (JANUS VideoCall plugin)
WebRTC media is now available
[3253666903] Adding event to queue of messages...
[3253666903] Started thread: setup of the SCTP association
[3253666903] Connecting the SCTP association
[3253666903] Data from SCTP to DTLS stack: 100 bytes
[3253666903] Starting thread for SCTP association
[3253666903] DTLS check pending: 157
[3253666903] >> Going to send DTLS data: 157 bytes
[3253666903] >> >> Read 157 bytes from the write_BIO...
[3253666903] >> >> ... and sent 157 of those bytes on the socket
New connection on REST API: 108.20.20.72
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... Just parsing headers for now...
Content-Type: application/json
Content-Length: 244
Connection: keep-alive
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
  -- Uploaded data (244 bytes)
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 157 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
    ... and read 100 of them from SSL...
[3253666903] DTLS check pending: 0
Any data available?
Sending data (100 bytes) to the SCTP stack...
[3253666903] Data from DTLS to SCTP stack: 100 bytes
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... Just parsing headers for now...
Content-Type: application/json
Content-Length: 263
Connection: keep-alive
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
  -- Uploaded data (263 bytes)
  -- Data we have now (263 bytes)
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
Done getting payload, we can answer
{"janus":"trickle","candidate":{"sdpMLineIndex":1,"sdpMid":"video","candidate":"candidate:264484875 1 udp 1686052607 108.20.20.72 4665 typ srflx raddr 192.168.1.7 rport 4665 generation 0"},"transaction":"Nt9HCHd040nn","sessionId":2215234259,"handleId":3253666903}
[3253666903] Trickle candidate (video): candidate:264484875 1 udp 1686052607 108.20.20.72 4665 typ srflx raddr 192.168.1.7 rport 4665 generation 0
[3253666903] Got a video candidate but we're bundling, ignoring...
Request completed, freeing data
  -- Data we have now (244 bytes)
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
Done getting payload, we can answer
{"janus":"trickle","candidate":{"sdpMLineIndex":2,"sdpMid":"data","candidate":"candidate:3894397742 1 tcp 1518280447 192.168.1.7 0 typ host tcptype active generation 0"},"transaction":"vP7yuvDAyPJN","sessionId":2215234259,"handleId":3253666903}
[3253666903] Trickle candidate (data): candidate:3894397742 1 tcp 1518280447 192.168.1.7 0 typ host tcptype active generation 0
[3253666903] Got a data candidate but we're bundling, ignoring...
Request completed, freeing data
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 461 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
    ... and read 404 of them from SSL...
[3253666903] DTLS check pending: 0
Any data available?
Sending data (404 bytes) to the SCTP stack...
[3253666903] Data from DTLS to SCTP stack: 404 bytes
[3253666903] Data from SCTP to DTLS stack: 412 bytes
[3253666903] Data from SCTP to DTLS stack: 316 bytes
[3253666903] DTLS check pending: 477
[3253666903] >> Going to send DTLS data: 477 bytes
[3253666903] >> >> Read 477 bytes from the write_BIO...
[3253666903] >> >> ... and sent 477 of those bytes on the socket
[3253666903] DTLS check pending: 381
[3253666903] >> Going to send DTLS data: 381 bytes
[3253666903] >> >> Read 381 bytes from the write_BIO...
[3253666903] >> >> ... and sent 381 of those bytes on the socket
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 429 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
    ... and read 368 of them from SSL...
[3253666903] DTLS check pending: 0
Any data available?
Sending data (368 bytes) to the SCTP stack...
[3253666903] Data from DTLS to SCTP stack: 368 bytes
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 77 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
    ... and read 16 of them from SSL...
[3253666903] DTLS check pending: 0
Any data available?
Sending data (16 bytes) to the SCTP stack...
[3253666903] Data from DTLS to SCTP stack: 16 bytes
New connection on REST API: 108.20.20.72
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... Just parsing headers for now...
Content-Type: application/json
Content-Length: 245
Connection: keep-alive
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
  -- Uploaded data (245 bytes)
  -- Data we have now (245 bytes)
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
Done getting payload, we can answer
{"janus":"trickle","candidate":{"sdpMLineIndex":1,"sdpMid":"video","candidate":"candidate:3894397742 1 tcp 1518280447 192.168.1.7 0 typ host tcptype active generation 0"},"transaction":"tCWpJPr3Wklj","sessionId":2215234259,"handleId":3253666903}
[3253666903] Trickle candidate (video): candidate:3894397742 1 tcp 1518280447 192.168.1.7 0 typ host tcptype active generation 0
[3253666903] Got a video candidate but we're bundling, ignoring...
Request completed, freeing data
Association change [3253666903] Connected to the DataChannel peer
SCTP_COMM_UP, streams (in/out) = (1023/16), supports PR AUTH ASCONF MULTIBUF RE-CONFIG.
[3253666903] Opened channel 'JanusDataChannel' (id=0) (1/0/0)
[3253666903] Data from SCTP to DTLS stack: 32 bytes
[3253666903] DTLS check pending: 93
[3253666903] >> Going to send DTLS data: 93 bytes
[3253666903] >> >> Read 93 bytes from the write_BIO...
[3253666903] >> >> ... and sent 93 of those bytes on the socket
New connection on REST API: 108.20.20.72
New connection on REST API: 108.20.20.72
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... Just parsing headers for now...
Content-Type: application/json
Content-Length: 263
Connection: keep-alive
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
  -- Uploaded data (263 bytes)
  -- Data we have now (263 bytes)
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
Done getting payload, we can answer
{"janus":"trickle","candidate":{"sdpMLineIndex":0,"sdpMid":"audio","candidate":"candidate:264484875 1 udp 1686052607 108.20.20.72 4665 typ srflx raddr 192.168.1.7 rport 4665 generation 0"},"transaction":"D4qgHHSInav1","sessionId":2215234259,"handleId":3253666903}
[3253666903] Trickle candidate (audio): candidate:264484875 1 udp 1686052607 108.20.20.72 4665 typ srflx raddr 192.168.1.7 rport 4665 generation 0
[3253666903] Adding remote candidate for component 1 to stream 1
[3253666903]   -- Ignoring this candidate, the component is already ready
Request completed, freeing data
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... Just parsing headers for now...
Content-Type: application/json
Content-Length: 262
Connection: keep-alive
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
  -- Uploaded data (262 bytes)
  -- Data we have now (262 bytes)
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
Done getting payload, we can answer
{"janus":"trickle","candidate":{"sdpMLineIndex":2,"sdpMid":"data","candidate":"candidate:264484875 1 udp 1686052607 108.20.20.72 4665 typ srflx raddr 192.168.1.7 rport 4665 generation 0"},"transaction":"foJnloFBj1xa","sessionId":2215234259,"handleId":3253666903}
[3253666903] Trickle candidate (data): candidate:264484875 1 udp 1686052607 108.20.20.72 4665 typ srflx raddr 192.168.1.7 rport 4665 generation 0
[3253666903] Got a data candidate but we're bundling, ignoring...
Request completed, freeing data
New connection on REST API: 108.20.20.72
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... Just parsing headers for now...
Content-Type: application/json
Content-Length: 124
Connection: keep-alive
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
  -- Uploaded data (124 bytes)
  -- Data we have now (124 bytes)
Got a HTTP POST request on /janus/2215234259/3253666903...
 ... parsing request...
Session: 2215234259
Handle: 3253666903
Processing POST data (application/json)...
Done getting payload, we can answer
{"janus":"trickle","candidate":{"completed":true},"transaction":"VzPPNxcTHd1L","sessionId":2215234259,"handleId":3253666903}
No more remote candidates for handle 3253666903!
Request completed, freeing data
[3253666903]  Got an RTCP packet (bundled stream)!
[3253666903]  Got an RTCP packet (bundled stream)!
[ERR] [ice.c:janus_ice_send_thread:1366:] [2093138664]     audio stream (#1) component has no valid SRTP session (yet?)
New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
Request completed, freeing data
[3253666903]  DTLS already set up, disabling retransmission timer!
New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
... handling long poll...
[2093138664] Component state changed for component 1 in stream 1: 5 (failed)
[ERR] [ice.c:janus_ice_cb_component_state_changed:634:] ICE failed for handle 2093138664...
[2093138664] Telling the plugin about it (JANUS VideoCall plugin)
No WebRTC media anymore
Pushing event to peer: {
   "videocall": "event",
   "result": {
      "event": "hangup",
      "username": "wj",
      "reason": "Remote hangup"
   }
}
[3253666903] Adding event to queue of messages...
  >> 0 (Success)
[2093138664] Adding event to queue of messages...
[2093138664] ICE send thread leaving...
We have a message to serve...
{
   "janus": "event",
   "session_id": 2215234259,
   "sender": 3253666903,
   "plugindata": {
      "plugin": "janus.plugin.videocall",
      "data": {
         "videocall": "event",
         "result": {
            "event": "hangup",
            "username": "wj",
            "reason": "Remote hangup"
         }
      }
   }
}
Request completed, freeing data
[3253666903]  Got an RTCP packet (bundled stream)!
[3253666903]  Got an RTCP packet (bundled stream)!
[3253666903]  Got an RTCP packet (bundled stream)!
[3253666903]  Got an RTCP packet (bundled stream)!
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 109 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
    ... and read 48 of them from SSL...
[3253666903] DTLS check pending: 0
Any data available?
Sending data (48 bytes) to the SCTP stack...
[3253666903] Data from DTLS to SCTP stack: 48 bytes
Looks like DTLS!
[3253666903] DTLS check pending: 0
    Written 61 of those bytes on the read BIO...
[3253666903] DTLS check pending: 0
[3253666903] DTLS alert received on stream 1, closing...
[3253666903] Telling the plugin about it (JANUS VideoCall plugin)
No WebRTC media anymore
Pushing event to peer: {
   "videocall": "event",
   "result": {
      "event": "hangup",
      "username": "rj",
      "reason": "Remote hangup"
   }
}
[2093138664] Adding event to queue of messages...
  >> 0 (Success)
    ... and read 0 of them from SSL...
[3253666903] DTLS check pending: 0
Any data available?
[3253666903] ICE thread ended!
[3253666903] Stream reset event: flags = 1, incoming stream ids = 0.
[3253666903] Data from SCTP to DTLS stack: 60 bytes
[3253666903] DTLS check pending: 125
[3253666903] >> Going to send DTLS data: 125 bytes
[3253666903] >> >> Read 125 bytes from the write_BIO...
[3253666903] >> >> ... and sent 125 of those bytes on the socket
[3253666903] ICE send thread leaving...
New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
... handling long poll...
[3253666903] Destroying SCTP association
[3253666903] Data from SCTP to DTLS stack: 20 bytes
[3253666903] Data from SCTP to DTLS stack: 20 bytes
[3253666903] WebRTC resources freed
[3253666903] Leaving SCTP association thread
Long poll time out for session 2215234259...
We have a message to serve...
{"janus" : "keepalive"}
Request completed, freeing data
New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
... handling long poll...
Timeout expired for session 2510398859...
Cleaning up session 2510398859...
Destroying session 2510398859
Detaching handle from JANUS VideoCall plugin
Removing user wj session...
No WebRTC media anymore
[2093138664] ICE thread ended!
  -- Removed: 1
[2093138664] Adding event to queue of messages...
Handle detached (0), scheduling destruction
Checking 1 old sessions
[2093138664] WebRTC resources freed
[2093138664] Handle and related resources freed
Checking 1 old sessions
Checking 1 old sessions
Checking 1 old sessions
Long poll time out for session 2215234259...
We have a message to serve...
{"janus" : "keepalive"}
Request completed, freeing data
New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
... handling long poll...
Long poll time out for session 2215234259...
We have a message to serve...
{"janus" : "keepalive"}
Request completed, freeing data
New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
... handling long poll...
Long poll time out for session 2215234259...
We have a message to serve...
{"janus" : "keepalive"}
Request completed, freeing data
New connection on REST API: 108.20.20.72
Got a HTTP GET request on /janus/2215234259...
 ... Just parsing headers for now...
User-Agent: Super Agent/0.0.1
Content-Type: application/x-zip
Connection: keep-alive
Got a HTTP GET request on /janus/2215234259...
 ... parsing request...
Session: 2215234259
Session 2215234259 found... returning up to 1 messages
... handling long poll...


On Friday, December 5, 2014 2:28:09 PM UTC-5, Gatecrasher777 wrote:

Lorenzo Miniero

unread,
Dec 6, 2014, 8:14:21 AM12/6/14
to meetech...@googlegroups.com
git pull to update (you'll need to recompile obviously)
There's no Janus log, just look at the console and at the admin interface that is documented online to see if there's any issue with ICE or DTLS.

L.

Gatecrasher777

unread,
Dec 9, 2014, 11:09:28 AM12/9/14
to meetech...@googlegroups.com

You can have a "log" if you want to run Janus as a long term background process, something like this:

nohup ./janus > ./janus.log 2>&1 &

Lorenzo Miniero

unread,
Dec 9, 2014, 11:30:10 AM12/9/14
to meetech...@googlegroups.com
As an alternative, you can launch Janus in a screen and have the screen redirect the output to a log.

L.
Reply all
Reply to author
Forward
0 new messages