mcu server responds slowing to http request

573 views
Skip to first unread message

Wilbert Jackson

unread,
Nov 26, 2014, 7:19:57 AM11/26/14
to meetech...@googlegroups.com

After I run either the echo test, video call test, video mcu test a couple of times, using remote client apps, the Janus server goes into an unresponsive http request mode, and takes minutes to acknowledge an http request. The client app times out and displays a server down message. I have set up my own server and the only way to enable client apps to connect again, after the server goes into the unresponsive http request mode, is to restart the server. When the server is in the unresponsive mode it repeatedly displays the output shown below.
Even if I enter the server url through the browser manually the server never responds with a display of the http info.

Thanks

Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
...............Rewind! (/opt/janus/share/janus/streams/radio.alaw)
New connection on REST API: xx.xx.xx.xx
New connection on REST API: xx.xx.xx.xx

Lorenzo Miniero

unread,
Nov 26, 2014, 7:23:46 AM11/26/14
to meetech...@googlegroups.com
Are you attaching multiple users from the same browser? If so, read here:


Lorenzo

Wilbert Jackson

unread,
Nov 26, 2014, 11:19:21 AM11/26/14
to meetech...@googlegroups.com
The below response was intended for the group. Will try lock debugging. Some more info about the issue. We use our own web server and start an echo test running on the same machine where the Janus web sever is running. We connect two remote client machines running the echo test. If any of the remote apps fails to connect the remote video then a restart of both of the remote apps will fail to get a Janus Server http response We can observe the Janus Server processing the SSRC data associated with server based running echo test,but never seen any http response data from the requesting remote echo test. 


Was this intended for the group? If so, you only sent it to me :-)

Anyway, it may be a deadlock somewhere, even if it's weird as this has never happened for us with HTTP. You can enable lock debugging using the admin API, if you have it enabled:

curl -X POST -H "Content-Type: application/json" -d '{"janus":"set_locking_debug", "transaction":"a1b2c3d4", "admin_secret":"janusoverlord", "debug":1}' http://127.0.0.1:7088/admin

Probably overly verbose, but it might help to understand whether it's an issue with locking in Janus (it will not help if the deadlock is in libmicrohttpd, though...). Try enabling it and doing a new HTTP request to see if there's a lock that is not subsequently unlocked.

Wilbert Jackson

unread,
Nov 26, 2014, 4:30:32 PM11/26/14
to meetech...@googlegroups.com

Lorenzo,

I setup the admin monitor as you suggested and the monitor shows that echotest is being unlocked for each corresponding lock. It seems that if I refresh the browser and run an echotest I get the error shown below. The MCU server is just refusing any http request. It will show admin and rtcp data but will not accept any http. If stop the server all is weel and good for about 4-5 test the server stops accepting request. 
Initializing library. Sometimes it gets returns the id but not the plugin id and sometimes it does not either.
If I run the admin app the it does not have a problem repeatedly getting a session id. The problem seems to occur after a request to get any plugin id.

wilbert


adapter.js:79 from This appears to be Chrome
janus.js:61 Library adapter.js loaded
janus.js:92 Library initialized: true
janus.js:118 Using REST API to contact Janus
janus.js:339 1. in janus.js create session https://4vision.com:8080/janus-gateway
janus.js:393 calling ajax POST
janus.js:401 ajax POST Create session:
janus.js:402 Object {janus: "success", transaction: "jh69QQdVyHxz", data: Object}
janus.js:410 Created session: 2315839138
janus.js:170 Long poll...
jquery.min.js:4 OPTIONS https://4vision.com:8080/janus-gateway/2315839138 net::ERR_CONNECTION_TIMED_OUT
janus.js:654 error: 
janus.js:206 Got event on session 2315839138
janus.js:207 Object {janus: "keepalive"}
janus.js:170 Long poll...
janus.js:206 Got event on session 2315839138
janus.js:207 Object {janus: "keepalive"}
janus.js:170 Long poll...


Test to get consistent networks access to session id's 
admin.js:80 Got sessions:
admin.js:81 Object
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "mgrPtZkIUmcL", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "VbyCgPt381PP", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "dXd45p1nwldj", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "GyXtkKI3xqWM", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "eqdfDtdaI37t", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "ozSQshVH1ZnM", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "aGE89VW9agsr", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "ylTVUojzFgvY", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "BePNsx8NnnE2", sessions: Array[1]}
admin.js:80 Got sessions:
admin.js:81 Object {janus: "success", transaction: "u5LxiI4Vdc60", sessions: Array[1]}

Lorenzo Miniero

unread,
Nov 27, 2014, 4:40:40 AM11/27/14
to meetech...@googlegroups.com
Is there any webpage I can use to test?
By the way, what do you mean by "connect two remote client machines running the echo test"? The echo test is by definition an isolated scenario, where each user will talk with no one but itself.

Lorenzo

Wilbert Jackson

unread,
Nov 27, 2014, 8:01:56 AM11/27/14
to meetech...@googlegroups.com
Lorenzo,

You can connect to the Janus Server I have setup at:


The echotest.html and echotest.js are the ones you have provided.

I set config parameters currently from the command line as:
~/janus-gateway$ ./janus --secure-port=8080 -c /home/wilbert/janus-gateway/certs/ssl.pem -k /home/wilbert/janus-gateway/certs/ssl.key --base-path=/janus-gateway --debug-level=7 --stun-server=173.194.68.127:19302 --public-ip=108.20.20.72 --admin-port=7088 --admin-secure-port=7089 --admin-base-path=/janus-gateway  --admin-secret="janusoverlord"

The test I setup I am using is as follows:

1. one machine is my office Linux 64 bit with chrome 38 running the echotest.

2. one machine in my office WindowsXP chrome 38 running the echotest.

3. A Nexus tablet with chrome 38 at home, remote from the office, running the echotest.

In the office I started and restarted the echotest app on each machine 5 times and using the janus server console output observed that each connected ok. From home I did the same test with the Nexus tablet and it connected 5 times ok.

I left the machines in my office run over night and from home the next morning I tried to run the echotest on the Nexus tablet and was not able to connect to the Janus server receiving a gateway down error.

I went to my office and observed that both of the echotest apps where runnng ok. I stopped each and attempted to restart each and received a gateway is down error on both machines.

Using the debug console I could see the each echotest app was calling the long polling ajax call to get a session id. But on the Janus server console it displayed the following output show below. No matter how many times I restarted the echotest app on each machine I never saw the normal http info console output, and the echotest app always fails to connect the Janus server.

New connection on REST API: 108.20.20.72
New connection on REST API: 108.20.20.72
New connection on REST API: 108.20.20.72
New connection on REST API: 108.20.20.72
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
Rewind! (/opt/janus/share/janus/streams/radio.alaw)
New connection on REST API: 108.20.20.72

I was going to next try these same tests using your server.

Thanks

Wilbert

Lorenzo Miniero

unread,
Nov 27, 2014, 8:06:39 AM11/27/14
to meetech...@googlegroups.com
So you indeed are opening the same application from the same browser multiple times? As I said, due to the limitation of HTTP/TCP connections you can make towards the same server from the same Chrome profile, it will stop working for the same Chrome instance when you open more. Other browsers or different profiles of Chrome would be unaffected, as it's not a server side issue, so if you need extensive testing you'll actually need more clients. Please make sure that's not what you're experiencing. Anyway, I'll try to so some quick test later.

Lorenzo

Wilbert Jackson

unread,
Nov 27, 2014, 9:17:24 AM11/27/14
to meetech...@googlegroups.com
Maybe I misunderstand about opening the app from the browser multiple times. I have 3 separate machines each with its own browser running the app. Since I see the same problem when I run the videocall app I am using the echotest to simulate multiple call and recall tests. I run an echotest , then close the test with the stop button, closing the browser or refreshing the browser to simulate a call hangup. I then run the test again to simulate a new call and repeat the hangup. Are you saying this scenario cannot be done using Chrome and the Janus server? 

Thanks


On Wednesday, November 26, 2014 7:19:57 AM UTC-5, Wilbert Jackson wrote:

Lorenzo Miniero

unread,
Nov 27, 2014, 9:23:52 AM11/27/14
to meetech...@googlegroups.com
The reason I ask is because you said, for instance, that you opened five pages from the same browser, five pages from the same tablet and so on. Since all these are served by the same web server and the same Janus instance, it means that, if we consider the browser, that same browser is opening 6 if not more connections towards the same server: in fact, it's at least six, since you have to take into account the long poll for each which keeps the connection busy most of the time (5 of them) plus an additional request that each page does for pro-active requests (e.g., configure, negotiate). Chrome only allows six connections towards the same server, meaning that any additional page requesting the same service (web server+Janus) won't start, even thouh Janus would safely accept them, as Chrome will not open any more connection towards it until the previous ones are closed. The same applies to the tablet, for instance.

For this reason, you should limit the number of pages you open from the same device or browser instance: e.g., 4 on one browser, 4 on the tablet, 4 somewhere else, etc., and in case it seems to be blocked as you said, try with a completely different machine to be sure the issue is not in what I just described.

Lorenzo

Lorenzo Miniero

unread,
Nov 27, 2014, 9:24:55 AM11/27/14
to meetech...@googlegroups.com
PS: Of course, I'm talking of scenarios where the same page is opened over and over in parallel, at the same time. My explaination does not apply to sequential attempts, where you try one, close it, and then open a new one or the same one after that.

L.

Wilbert Jackson

unread,
Nov 27, 2014, 9:31:49 AM11/27/14
to meetech...@googlegroups.com
I understand as I explain in post sent before this explanation I am closing each session, I believe, by using the echotest stop button, refreshing the browser and closing the browser before a new app run.

thanks 

Wilbert Jackson

unread,
Nov 28, 2014, 9:06:42 AM11/28/14
to meetech...@googlegroups.com
Lorenzo,

I ran the same tests of starting and stopping the echotest on 3 of my computers about 30 times using your Janus Server. I did not experience the problem of any of the test machines failing to connect to the Janus Server. It appears my problem is caused by something in way I have configured my Janus Server.

I am configuring the server using command line parameters currently with the settings below. I have included server start up outputs from different debug levels and noticed when I set debug to level 2 I get an error about the Stun server setting.

wilbert@wilbert-Gazelle-Professional:~/janus-gateway$ ./janus --secure-port=7090 -c /home/wilbert/janus-gateway/certs/ssl.pem -k /home/wilbert/janus-gateway/certs/ssl.key --base-path=/janus-gateway --debug-level=2 --stun-server=173.194.68.127:19302 --public-ip=108.20.20.72 --admin-port=7088 --admin-secure-port=7089 --admin-base-path=/janus-gateway 
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Gateway) v0.0.6
---------------------------------------------------

Reading configuration from /opt/janus/etc/janus/janus.cfg
Checking command line arguments...
Debug/log level is 2
STUN unknown: 0 mandatory attribute(s)!

wilbert@wilbert-Gazelle-Professional:~/janus-gateway$ ./janus --secure-port=7090 -c /home/wilbert/janus-gateway/certs/ssl.pem -k /home/wilbert/janus-gateway/certs/ssl.key --base-path=/janus-gateway  --stun-server=173.194.68.127:19302 --public-ip=108.20.20.72 --admin-port=7088 --admin-secure-port=7089 --admin-base-path=/janus-gateway --debug-level=3
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Gateway) v0.0.6
---------------------------------------------------

Reading configuration from /opt/janus/etc/janus/janus.cfg
Checking command line arguments...
Debug/log level is 3
STUN unknown: 0 mandatory attribute(s)!
[WARN] WebSockets support not compiled
[WARN] RabbitMQ support not compiled
[WARN] Admin/monitor HTTP webserver disabled

~/janus-gateway$ ./janus --secure-port=7090 -c /home/wilbert/janus-gateway/certs/ssl.pem -k /home/wilbert/janus-gateway/certs/ssl.key --base-path=/janus-gateway  --stun-server=173.194.68.127:19302 --public-ip=108.20.20.72 --admin-port=7088 --admin-secure-port=7089 --admin-base-path=/janus-gateway --debug-level=4
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Gateway) v0.0.6
---------------------------------------------------

Reading configuration from /opt/janus/etc/janus/janus.cfg
Checking command line arguments...
Debug/log level is 4
Adding 'vmnet' to the ICE ignore list...
Using 192.168.1.2 as local IP...
Initializing ICE stuff (IPv6 candidates disabled)
ICE port range: 0-0
STUN server to use: 173.194.68.127:19302
Testing STUN server: message is of 20 bytes
STUN unknown: 0 mandatory attribute(s)!
  >> Our public address is 108.20.20.72
Using 108.20.20.72 as our public IP in SDP
Fingerprint of our certificate: 49:E6:0B:3C:7B:B6:02:06:A3:96:DB:32:52:5F:14:E2:38:DC:15:E6:DD:1B:35:04:AD:9E:FE:0B:8E:CD:96:AB
Plugins folder: /opt/janus/lib/janus/plugins
Loading plugin 'libjanus_voicemail.so'...
JANUS VoiceMail plugin initialized!
Loading plugin 'libjanus_recordplay.so'...
VoiceMail watchdog started
JANUS Record&Play plugin initialized!
Record&Play watchdog started
Loading plugin 'libjanus_streaming.so'...
JANUS Streaming plugin initialized!
Loading plugin 'libjanus_audiobridge.so'...
Streaming watchdog started
JANUS AudioBridge plugin initialized!
Loading plugin 'libjanus_videocall.so'...
AudioBridge watchdog started
JANUS VideoCall plugin initialized!
Loading plugin 'libjanus_echotest.so'...
VideoCall watchdog started
JANUS EchoTest plugin initialized!
Loading plugin 'libjanus_videoroom.so'...
Echotest watchdog started
JANUS VideoRoom plugin initialized!
Loading plugin 'libjanus_sip.so'...
VideoRoom watchdog started
JANUS SIP plugin initialized!
SIP watchdog started
HTTP webserver started (port 8088, /janus-gateway path listener)...
HTTPS webserver started (port 7090, /janus-gateway path listener)...
[WARN] WebSockets support not compiled
[WARN] RabbitMQ support not compiled
[WARN] Admin/monitor HTTP webserver disabled
Sessions watchdog started
Admin/monitor HTTPS webserver started (port 7089, /janus-gateway path listener)...

~/janus-gateway$ ./janus --secure-port=7090 -c /home/wilbert/janus-gateway/certs/ssl.pem -k /home/wilbert/janus-gateway/certs/ssl.key --base-path=/janus-gateway  --stun-server=173.194.68.127:19302 --public-ip=108.20.20.72 --admin-port=7088 --admin-secure-port=7089 --admin-base-path=/janus-gateway --debug-level=5
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Gateway) v0.0.6
---------------------------------------------------

Reading configuration from /opt/janus/etc/janus/janus.cfg
[janus.cfg]
    [general]
        configs_folder: /opt/janus/etc/janus
        plugins_folder: /opt/janus/lib/janus/plugins
        debug_level: 4
    [webserver]
        base_path: /janus
        threads: unlimited
        http: yes
        port: 8088
        https: no
        ws: yes
        ws_port: 8188
        ws_ssl: no
    [rabbitmq]
        enable: no
        host: localhost
        to_janus: to-janus
        from_janus: from-janus
    [admin]
        admin_base_path: /admin
        admin_threads: unlimited
        admin_http: no
        admin_port: 7088
        admin_https: no
        admin_secret: janusoverlord
    [certificates]
        cert_pem: /opt/janus/share/janus/certs/mycert.pem
        cert_key: /opt/janus/share/janus/certs/mycert.key
    [nat]
        ice_ignore_list: vmnet
Checking command line arguments...
[janus.cfg]
    [general]
        configs_folder: /opt/janus/etc/janus
        plugins_folder: /opt/janus/lib/janus/plugins
        debug_level: 5
    [webserver]
        base_path: /janus-gateway
        threads: unlimited
        http: yes
        port: 8088
        https: yes
        ws: yes
        ws_port: 8188
        ws_ssl: no
        secure_port: 7090
    [rabbitmq]
        enable: no
        host: localhost
        to_janus: to-janus
        from_janus: from-janus
    [admin]
        admin_base_path: /janus-gateway
        admin_threads: unlimited
        admin_http: no
        admin_port: 7088
        admin_https: yes
        admin_secret: janusoverlord
        admin_secure_port: 7089
    [certificates]
        cert_pem: /home/wilbert/janus-gateway/certs/ssl.pem
        cert_key: /home/wilbert/janus-gateway/certs/ssl.key
    [nat]
        ice_ignore_list: vmnet
        stun_server: 173.194.68.127
        stun_port: 19302
        public_ip: 108.20.20.72
Debug/log level is 5
Adding 'vmnet' to the ICE ignore list...
Available interfaces:
lo: 127.0.0.1
eth0: 192.168.1.2
Using 192.168.1.2 as local IP...
Initializing ICE stuff (IPv6 candidates disabled)
ICE port range: 0-0
STUN server to use: 173.194.68.127:19302
Testing STUN server: message is of 20 bytes
  >> Sent 20 bytes 173.194.68.127:19302, waiting for reply...
  >> Got 32 bytes...
STUN unknown: 0 mandatory attribute(s)!
  >> XOR-MAPPED-ADDRESS: 0
  >> Our public address is 108.20.20.72
Using 108.20.20.72 as our public IP in SDP
Using certificates:
/home/wilbert/janus-gateway/certs/ssl.pem
/home/wilbert/janus-gateway/certs/ssl.key
Fingerprint of our certificate: 49:E6:0B:3C:7B:B6:02:06:A3:96:DB:32:52:5F:14:E2:38:DC:15:E6:DD:1B:35:04:AD:9E:FE:0B:8E:CD:96:AB
Plugins folder: /opt/janus/lib/janus/plugins
Loading plugin 'libjanus_voicemail.so'...
JANUS VoiceMail plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.voicemail.cfg
[janus.plugin.voicemail.cfg]
    [general]
        path: /tmp/voicemail/
        base: /voicemail/
Recordings path: /tmp/voicemail/
Recordings base: /voicemail/
JANUS VoiceMail plugin initialized!
VoiceMail watchdog started
Joining thread
Version: 4 (0.0.4)
  [janus.plugin.voicemail] JANUS VoiceMail plugin
  This is a plugin implementing a very simple VoiceMail service for Janus, recording Opus streams.
Loading plugin 'libjanus_recordplay.so'...
JANUS Record&Play plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.recordplay.cfg
[janus.plugin.recordplay.cfg]
    [general]
        path: /opt/janus/share/janus/recordings
Updating recordings list in /opt/janus/share/janus/recordings
Importing recording '1234.nfo'...
JANUS Record&Play plugin initialized!
Version: 1 (0.0.1)
  [janus.plugin.recordplay] JANUS Record&Play plugin
Joining thread
Record&Play watchdog started
  This is a trivial Record&Play plugin for Janus, to record WebRTC sessions and replay them.
Loading plugin 'libjanus_streaming.so'...
JANUS Streaming plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.streaming.cfg
[janus.plugin.streaming.cfg]
    [gstreamer-sample]
        type: rtp
        id: 1
        description: Opus/VP8 live stream coming from gstreamer
        audio: yes
        video: yes
        audioport: 5002
        audiopt: 111
        audiortpmap: opus/48000/2
        videoport: 5004
        videopt: 100
        videortpmap: VP8/90000
        secret: adminpwd
    [file-live-sample]
        type: live
        id: 2
        description: a-law file source (radio broadcast)
        filename: /opt/janus/share/janus/streams/radio.alaw
        audio: yes
        video: no
        secret: adminpwd
    [file-ondemand-sample]
        type: ondemand
        id: 3
        description: mu-law file source (music)
        filename: /opt/janus/share/janus/streams/music.mulaw
        audio: yes
        video: no
        secret: adminpwd
Adding stream 'gstreamer-sample'
Audio enabled, Video enabled
Audio enabled, Video enabled
Adding stream 'file-live-sample'
Starting relay thread
Adding stream 'file-ondemand-sample'
  ::: [1][gstreamer-sample] Opus/VP8 live stream coming from gstreamer (live, RTP source)
  ::: [2][file-live-sample] a-law file source (radio broadcast) (live, file source)
[gstreamer-sample] Audio listener bound to port 5002
  ::: [3][file-ondemand-sample] mu-law file source (music) (on demand, file source)
Filesource RTP thread starting...
[gstreamer-sample] Video listener bound to port 5004
Opening file source /opt/janus/share/janus/streams/radio.alaw...
Streaming audio file: /opt/janus/share/janus/streams/radio.alaw
JANUS Streaming plugin initialized!
Version: 3 (0.0.3)
  [janus.plugin.streaming] JANUS Streaming plugin
  This is a streaming plugin for Janus, allowing WebRTC peers to watch/listen to pre-recorded files or media generated by gstreamer.
Streaming watchdog started
Loading plugin 'libjanus_audiobridge.so'...
Joining thread
JANUS AudioBridge plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.audiobridge.cfg
[janus.plugin.audiobridge.cfg]
    [1234]
        description: Demo Room
        secret: adminpwd
        sampling_rate: 16000
        record: false
Adding audio room '1234'
Created audiobridge: 1234 (Demo Room, secret: adminpwd)
  ::: [1234][Demo Room] 16000 (will NOT be recorded)
Audio bridge thread starting...
Thread is for mixing room 1234 (Demo Room)...
JANUS AudioBridge plugin initialized!
Version: 4 (0.0.4)
  [janus.plugin.audiobridge] JANUS AudioBridge plugin
  This is a plugin implementing an audio conference bridge for Janus, mixing Opus streams.
Loading plugin 'libjanus_videocall.so'...
AudioBridge watchdog started
Joining thread
JANUS VideoCall plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.videocall.cfg
[janus.plugin.videocall.cfg]
JANUS VideoCall plugin initialized!
Version: 3 (0.0.3)
Joining thread
  [janus.plugin.videocall] JANUS VideoCall plugin
VideoCall watchdog started
  This is a simple video call plugin for Janus, allowing two WebRTC peers to call each other through the gateway.
Loading plugin 'libjanus_echotest.so'...
JANUS EchoTest plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.echotest.cfg
[janus.plugin.echotest.cfg]
JANUS EchoTest plugin initialized!
Version: 4 (0.0.4)
Joining thread
Echotest watchdog started
  [janus.plugin.echotest] JANUS EchoTest plugin
  This is a trivial EchoTest plugin for Janus, just used to showcase the plugin interface.
Loading plugin 'libjanus_videoroom.so'...
JANUS VideoRoom plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.videoroom.cfg
[janus.plugin.videoroom.cfg]
    [1234]
        description: Demo Room
        secret: adminpwd
        publishers: 6
        bitrate: 128000
        fir_freq: 10
        record: false
Adding video room '1234'
Created videoroom: 1234 (Demo Room, secret: adminpwd)
  ::: [1234][Demo Room] 128000, max 6 publishers, FIR frequency of 10 seconds
JANUS VideoRoom plugin initialized!
Version: 4 (0.0.4)
Joining thread
  [janus.plugin.videoroom] JANUS VideoRoom plugin
VideoRoom watchdog started
  This is a plugin implementing a videoconferencing MCU for Janus, something like Licode.
Loading plugin 'libjanus_sip.so'...
JANUS SIP plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.sip.cfg
[janus.plugin.sip.cfg]
    [general]
        autodetect_ignore: vmnet
Adding 'vmnet' to the c-line ignore list...
Autodetecting through available interfaces...
Going to use 192.168.1.2 as a c-line in the SDPs
JANUS SIP plugin initialized!
Version: 3 (0.0.3)
Joining thread
  [janus.plugin.sip] JANUS SIP plugin
SIP watchdog started
  This is a simple SIP plugin for Janus, allowing WebRTC peers to register at a SIP server and call SIP user agents through the gateway.
Using a thread per connection for the HTTP webserver
HTTP webserver started (port 8088, /janus-gateway path listener)...
Using a thread per connection for the HTTPS webserver
HTTPS webserver started (port 7090, /janus-gateway path listener)...
[WARN] WebSockets support not compiled
[WARN] RabbitMQ support not compiled
[WARN] Admin/monitor HTTP webserver disabled
Using a thread per connection for the admin/monitor HTTPS webserver
Sessions watchdog started
Admin/monitor HTTPS webserver started (port 7089, /janus-gateway path listener)...

/janus-gateway$ ./janus --secure-port=7090 -c /home/wilbert/janus-gateway/certs/ssl.pem -k /home/wilbert/janus-gateway/certs/ssl.key --base-path=/janus-gateway  --stun-server=173.194.68.127:19302 --public-ip=108.20.20.72 --admin-port=7088 --admin-secure-port=7089 --admin-base-path=/janus-gateway --debug-level=6
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Gateway) v0.0.6
---------------------------------------------------

Reading configuration from /opt/janus/etc/janus/janus.cfg
[janus.cfg]
    [general]
        configs_folder: /opt/janus/etc/janus
        plugins_folder: /opt/janus/lib/janus/plugins
        debug_level: 4
    [webserver]
        base_path: /janus
        threads: unlimited
        http: yes
        port: 8088
        https: no
        ws: yes
        ws_port: 8188
        ws_ssl: no
    [rabbitmq]
        enable: no
        host: localhost
        to_janus: to-janus
        from_janus: from-janus
    [admin]
        admin_base_path: /admin
        admin_threads: unlimited
        admin_http: no
        admin_port: 7088
        admin_https: no
        admin_secret: janusoverlord
    [certificates]
        cert_pem: /opt/janus/share/janus/certs/mycert.pem
        cert_key: /opt/janus/share/janus/certs/mycert.key
    [nat]
        ice_ignore_list: vmnet
Checking command line arguments...
[janus.cfg]
    [general]
        configs_folder: /opt/janus/etc/janus
        plugins_folder: /opt/janus/lib/janus/plugins
        debug_level: 6
    [webserver]
        base_path: /janus-gateway
        threads: unlimited
        http: yes
        port: 8088
        https: yes
        ws: yes
        ws_port: 8188
        ws_ssl: no
        secure_port: 7090
    [rabbitmq]
        enable: no
        host: localhost
        to_janus: to-janus
        from_janus: from-janus
    [admin]
        admin_base_path: /janus-gateway
        admin_threads: unlimited
        admin_http: no
        admin_port: 7088
        admin_https: yes
        admin_secret: janusoverlord
        admin_secure_port: 7089
    [certificates]
        cert_pem: /home/wilbert/janus-gateway/certs/ssl.pem
        cert_key: /home/wilbert/janus-gateway/certs/ssl.key
    [nat]
        ice_ignore_list: vmnet
        stun_server: 173.194.68.127
        stun_port: 19302
        public_ip: 108.20.20.72
Debug/log level is 6
Adding 'vmnet' to the ICE ignore list...
Available interfaces:
lo: 127.0.0.1
eth0: 192.168.1.2
Using 192.168.1.2 as local IP...
Initializing ICE stuff (IPv6 candidates disabled)
ICE port range: 0-0
STUN server to use: 173.194.68.127:19302
Testing STUN server: message is of 20 bytes
  >> Sent 20 bytes 173.194.68.127:19302, waiting for reply...
  >> Got 32 bytes...
STUN unknown: 0 mandatory attribute(s)!
  >> XOR-MAPPED-ADDRESS: 0
  >> Our public address is 108.20.20.72
Using 108.20.20.72 as our public IP in SDP
Using certificates:
/home/wilbert/janus-gateway/certs/ssl.pem
/home/wilbert/janus-gateway/certs/ssl.key
Fingerprint of our certificate: 49:E6:0B:3C:7B:B6:02:06:A3:96:DB:32:52:5F:14:E2:38:DC:15:E6:DD:1B:35:04:AD:9E:FE:0B:8E:CD:96:AB
Plugins folder: /opt/janus/lib/janus/plugins
Loading plugin 'libjanus_voicemail.so'...
JANUS VoiceMail plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.voicemail.cfg
[janus.plugin.voicemail.cfg]
    [general]
        path: /tmp/voicemail/
        base: /voicemail/
Recordings path: /tmp/voicemail/
Recordings base: /voicemail/
JANUS VoiceMail plugin initialized!
Version: 4 (0.0.4)
  [janus.plugin.voicemail] JANUS VoiceMail plugin
  This is a plugin implementing a very simple VoiceMail service for Janus, recording Opus streams.
Loading plugin 'libjanus_recordplay.so'...
Joining thread
JANUS Record&Play plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.recordplay.cfg
[janus.plugin.recordplay.cfg]
    [general]
        path: /opt/janus/share/janus/recordings
Updating recordings list in /opt/janus/share/janus/recordings
Importing recording '1234.nfo'...
JANUS Record&Play plugin initialized!
Version: 1 (0.0.1)
  [janus.plugin.recordplay] JANUS Record&Play plugin
  This is a trivial Record&Play plugin for Janus, to record WebRTC sessions and replay them.
Loading plugin 'libjanus_streaming.so'...
JANUS Streaming plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.streaming.cfg
[janus.plugin.streaming.cfg]
    [gstreamer-sample]
        type: rtp
        id: 1
        description: Opus/VP8 live stream coming from gstreamer
        audio: yes
        video: yes
        audioport: 5002
Joining thread
        audiopt: 111
        audiortpmap: opus/48000/2
        videoport: 5004
VoiceMail watchdog started
Record&Play watchdog started
        videopt: 100
        videortpmap: VP8/90000
        secret: adminpwd
    [file-live-sample]
        type: live
        id: 2
        description: a-law file source (radio broadcast)
        filename: /opt/janus/share/janus/streams/radio.alaw
        audio: yes
        video: no
        secret: adminpwd
    [file-ondemand-sample]
        type: ondemand
        id: 3
        description: mu-law file source (music)
        filename: /opt/janus/share/janus/streams/music.mulaw
        audio: yes
        video: no
        secret: adminpwd
Adding stream 'gstreamer-sample'
Audio enabled, Video enabled
Audio enabled, Video enabled
Adding stream 'file-live-sample'
Starting relay thread
Adding stream 'file-ondemand-sample'
[gstreamer-sample] Audio listener bound to port 5002
[gstreamer-sample] Video listener bound to port 5004
Filesource RTP thread starting...
Opening file source /opt/janus/share/janus/streams/radio.alaw...
  ::: [1][gstreamer-sample] Opus/VP8 live stream coming from gstreamer (live, RTP source)
Streaming audio file: /opt/janus/share/janus/streams/radio.alaw
  ::: [2][file-live-sample] a-law file source (radio broadcast) (live, file source)
  ::: [3][file-ondemand-sample] mu-law file source (music) (on demand, file source)
JANUS Streaming plugin initialized!
Version: 3 (0.0.3)
  [janus.plugin.streaming] JANUS Streaming plugin
Streaming watchdog started
  This is a streaming plugin for Janus, allowing WebRTC peers to watch/listen to pre-recorded files or media generated by gstreamer.
Joining thread
Loading plugin 'libjanus_audiobridge.so'...
JANUS AudioBridge plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.audiobridge.cfg
[janus.plugin.audiobridge.cfg]
    [1234]
        description: Demo Room
        secret: adminpwd
        sampling_rate: 16000
        record: false
Adding audio room '1234'
Created audiobridge: 1234 (Demo Room, secret: adminpwd)
  ::: [1234][Demo Room] 16000 (will NOT be recorded)
Audio bridge thread starting...
Thread is for mixing room 1234 (Demo Room)...
JANUS AudioBridge plugin initialized!
Joining thread
Version: 4 (0.0.4)
AudioBridge watchdog started
  [janus.plugin.audiobridge] JANUS AudioBridge plugin
  This is a plugin implementing an audio conference bridge for Janus, mixing Opus streams.
Loading plugin 'libjanus_videocall.so'...
JANUS VideoCall plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.videocall.cfg
[janus.plugin.videocall.cfg]
JANUS VideoCall plugin initialized!
Version: 3 (0.0.3)
  [janus.plugin.videocall] JANUS VideoCall plugin
Joining thread
  This is a simple video call plugin for Janus, allowing two WebRTC peers to call each other through the gateway.
VideoCall watchdog started
Loading plugin 'libjanus_echotest.so'...
JANUS EchoTest plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.echotest.cfg
[janus.plugin.echotest.cfg]
JANUS EchoTest plugin initialized!
Version: 4 (0.0.4)
Joining thread
  [janus.plugin.echotest] JANUS EchoTest plugin
Echotest watchdog started
  This is a trivial EchoTest plugin for Janus, just used to showcase the plugin interface.
Loading plugin 'libjanus_videoroom.so'...
JANUS VideoRoom plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.videoroom.cfg
[janus.plugin.videoroom.cfg]
    [1234]
        description: Demo Room
        secret: adminpwd
        publishers: 6
        bitrate: 128000
        fir_freq: 10
        record: false
Adding video room '1234'
Created videoroom: 1234 (Demo Room, secret: adminpwd)
  ::: [1234][Demo Room] 128000, max 6 publishers, FIR frequency of 10 seconds
JANUS VideoRoom plugin initialized!
Version: 4 (0.0.4)
VideoRoom watchdog started
Joining thread
  [janus.plugin.videoroom] JANUS VideoRoom plugin
  This is a plugin implementing a videoconferencing MCU for Janus, something like Licode.
Loading plugin 'libjanus_sip.so'...
JANUS SIP plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.sip.cfg
[janus.plugin.sip.cfg]
    [general]
        autodetect_ignore: vmnet
Adding 'vmnet' to the c-line ignore list...
Autodetecting through available interfaces...
Going to use 192.168.1.2 as a c-line in the SDPs
JANUS SIP plugin initialized!
Version: 3 (0.0.3)
  [janus.plugin.sip] JANUS SIP plugin
Joining thread
SIP watchdog started
  This is a simple SIP plugin for Janus, allowing WebRTC peers to register at a SIP server and call SIP user agents through the gateway.
Using a thread per connection for the HTTP webserver
HTTP webserver started (port 8088, /janus-gateway path listener)...
Using a thread per connection for the HTTPS webserver
HTTPS webserver started (port 7090, /janus-gateway path listener)...
[WARN] WebSockets support not compiled
[WARN] RabbitMQ support not compiled
[WARN] Admin/monitor HTTP webserver disabled
Using a thread per connection for the admin/monitor HTTPS webserver
Sessions watchdog started
Admin/monitor HTTPS webserver started (port 7089, /janus-gateway path listener)...

~/janus-gateway$ ./janus --secure-port=7090 -c /home/wilbert/janus-gateway/certs/ssl.pem -k /home/wilbert/janus-gateway/certs/ssl.key --base-path=/janus-gateway  --stun-server=173.194.68.127:19302 --public-ip=108.20.20.72 --admin-port=7088 --admin-secure-port=7089 --admin-base-path=/janus-gateway --debug-level=7
---------------------------------------------------
  Starting Meetecho Janus (WebRTC Gateway) v0.0.6
---------------------------------------------------

Reading configuration from /opt/janus/etc/janus/janus.cfg
[janus.cfg]
    [general]
        configs_folder: /opt/janus/etc/janus
        plugins_folder: /opt/janus/lib/janus/plugins
        debug_level: 4
    [webserver]
        base_path: /janus
        threads: unlimited
        http: yes
        port: 8088
        https: no
        ws: yes
        ws_port: 8188
        ws_ssl: no
    [rabbitmq]
        enable: no
        host: localhost
        to_janus: to-janus
        from_janus: from-janus
    [admin]
        admin_base_path: /admin
        admin_threads: unlimited
        admin_http: no
        admin_port: 7088
        admin_https: no
        admin_secret: janusoverlord
    [certificates]
        cert_pem: /opt/janus/share/janus/certs/mycert.pem
        cert_key: /opt/janus/share/janus/certs/mycert.key
    [nat]
        ice_ignore_list: vmnet
Checking command line arguments...
[janus.cfg]
    [general]
        configs_folder: /opt/janus/etc/janus
        plugins_folder: /opt/janus/lib/janus/plugins
        debug_level: 7
    [webserver]
        base_path: /janus-gateway
        threads: unlimited
        http: yes
        port: 8088
        https: yes
        ws: yes
        ws_port: 8188
        ws_ssl: no
        secure_port: 7090
    [rabbitmq]
        enable: no
        host: localhost
        to_janus: to-janus
        from_janus: from-janus
    [admin]
        admin_base_path: /janus-gateway
        admin_threads: unlimited
        admin_http: no
        admin_port: 7088
        admin_https: yes
        admin_secret: janusoverlord
        admin_secure_port: 7089
    [certificates]
        cert_pem: /home/wilbert/janus-gateway/certs/ssl.pem
        cert_key: /home/wilbert/janus-gateway/certs/ssl.key
    [nat]
        ice_ignore_list: vmnet
        stun_server: 173.194.68.127
        stun_port: 19302
        public_ip: 108.20.20.72
Debug/log level is 7
Adding 'vmnet' to the ICE ignore list...
Available interfaces:
lo: 127.0.0.1
eth0: 192.168.1.2
Using 192.168.1.2 as local IP...
Initializing ICE stuff (IPv6 candidates disabled)
ICE port range: 0-0
STUN server to use: 173.194.68.127:19302
Testing STUN server: message is of 20 bytes
  >> Sent 20 bytes 173.194.68.127:19302, waiting for reply...
  >> Got 32 bytes...
STUN unknown: 0 mandatory attribute(s)!
  >> XOR-MAPPED-ADDRESS: 0
  >> Our public address is 108.20.20.72
Using 108.20.20.72 as our public IP in SDP
Using certificates:
/home/wilbert/janus-gateway/certs/ssl.pem
/home/wilbert/janus-gateway/certs/ssl.key
Fingerprint of our certificate: 49:E6:0B:3C:7B:B6:02:06:A3:96:DB:32:52:5F:14:E2:38:DC:15:E6:DD:1B:35:04:AD:9E:FE:0B:8E:CD:96:AB
Plugins folder: /opt/janus/lib/janus/plugins
Loading plugin 'libjanus_voicemail.so'...
JANUS VoiceMail plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.voicemail.cfg
[janus.plugin.voicemail.cfg]
    [general]
        path: /tmp/voicemail/
        base: /voicemail/
Recordings path: /tmp/voicemail/
Recordings base: /voicemail/
JANUS VoiceMail plugin initialized!
Version: 4 (0.0.4)
VoiceMail watchdog started
Joining thread
  [janus.plugin.voicemail] JANUS VoiceMail plugin
  This is a plugin implementing a very simple VoiceMail service for Janus, recording Opus streams.
Loading plugin 'libjanus_recordplay.so'...
JANUS Record&Play plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.recordplay.cfg
[janus.plugin.recordplay.cfg]
    [general]
        path: /opt/janus/share/janus/recordings
Updating recordings list in /opt/janus/share/janus/recordings
Importing recording '1234.nfo'...
JANUS Record&Play plugin initialized!
Version: 1 (0.0.1)
Record&Play watchdog started
Joining thread
  [janus.plugin.recordplay] JANUS Record&Play plugin
  This is a trivial Record&Play plugin for Janus, to record WebRTC sessions and replay them.
Loading plugin 'libjanus_streaming.so'...
JANUS Streaming plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.streaming.cfg
[janus.plugin.streaming.cfg]
    [gstreamer-sample]
        type: rtp
        id: 1
        description: Opus/VP8 live stream coming from gstreamer
        audio: yes
        video: yes
        audioport: 5002
        audiopt: 111
        audiortpmap: opus/48000/2
        videoport: 5004
        videopt: 100
        videortpmap: VP8/90000
        secret: adminpwd
    [file-live-sample]
        type: live
        id: 2
        description: a-law file source (radio broadcast)
        filename: /opt/janus/share/janus/streams/radio.alaw
        audio: yes
        video: no
        secret: adminpwd
    [file-ondemand-sample]
        type: ondemand
        id: 3
        description: mu-law file source (music)
        filename: /opt/janus/share/janus/streams/music.mulaw
        audio: yes
        video: no
        secret: adminpwd
Adding stream 'gstreamer-sample'
Audio enabled, Video enabled
Audio enabled, Video enabled
Adding stream 'file-live-sample'
Starting relay thread
Adding stream 'file-ondemand-sample'
Filesource RTP thread starting...
[gstreamer-sample] Audio listener bound to port 5002
Opening file source /opt/janus/share/janus/streams/radio.alaw...
  ::: [1][gstreamer-sample] Opus/VP8 live stream coming from gstreamer (live, RTP source)
  ::: [2][file-live-sample] a-law file source (radio broadcast) (live, file source)
  ::: [3][file-ondemand-sample] mu-law file source (music) (on demand, file source)
Streaming audio file: /opt/janus/share/janus/streams/radio.alaw
[gstreamer-sample] Video listener bound to port 5004
JANUS Streaming plugin initialized!
Version: 3 (0.0.3)
  [janus.plugin.streaming] JANUS Streaming plugin
  This is a streaming plugin for Janus, allowing WebRTC peers to watch/listen to pre-recorded files or media generated by gstreamer.
Loading plugin 'libjanus_audiobridge.so'...
Joining thread
JANUS AudioBridge plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.audiobridge.cfg
[janus.plugin.audiobridge.cfg]
    [1234]
        description: Demo Room
        secret: adminpwd
        sampling_rate: 16000
        record: false
Adding audio room '1234'
Created audiobridge: 1234 (Demo Room, secret: adminpwd)
  ::: [1234][Demo Room] 16000 (will NOT be recorded)
Audio bridge thread starting...
Thread is for mixing room 1234 (Demo Room)...
JANUS AudioBridge plugin initialized!
Version: 4 (0.0.4)
  [janus.plugin.audiobridge] JANUS AudioBridge plugin
Joining thread
AudioBridge watchdog started
  This is a plugin implementing an audio conference bridge for Janus, mixing Opus streams.
Loading plugin 'libjanus_videocall.so'...
JANUS VideoCall plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.videocall.cfg
[janus.plugin.videocall.cfg]
JANUS VideoCall plugin initialized!
Version: 3 (0.0.3)
VideoCall watchdog started
Joining thread
  [janus.plugin.videocall] JANUS VideoCall plugin
Streaming watchdog started
  This is a simple video call plugin for Janus, allowing two WebRTC peers to call each other through the gateway.
Loading plugin 'libjanus_echotest.so'...
JANUS EchoTest plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.echotest.cfg
[janus.plugin.echotest.cfg]
JANUS EchoTest plugin initialized!
Version: 4 (0.0.4)
Joining thread
Echotest watchdog started
  [janus.plugin.echotest] JANUS EchoTest plugin
  This is a trivial EchoTest plugin for Janus, just used to showcase the plugin interface.
Loading plugin 'libjanus_videoroom.so'...
JANUS VideoRoom plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.videoroom.cfg
[janus.plugin.videoroom.cfg]
    [1234]
        description: Demo Room
        secret: adminpwd
        publishers: 6
        bitrate: 128000
        fir_freq: 10
        record: false
Adding video room '1234'
Created videoroom: 1234 (Demo Room, secret: adminpwd)
  ::: [1234][Demo Room] 128000, max 6 publishers, FIR frequency of 10 seconds
JANUS VideoRoom plugin initialized!
Version: 4 (0.0.4)
  [janus.plugin.videoroom] JANUS VideoRoom plugin
VideoRoom watchdog started
Joining thread
  This is a plugin implementing a videoconferencing MCU for Janus, something like Licode.
Loading plugin 'libjanus_sip.so'...
JANUS SIP plugin created!
Configuration file: /opt/janus/etc/janus/janus.plugin.sip.cfg
[janus.plugin.sip.cfg]
    [general]
        autodetect_ignore: vmnet
Adding 'vmnet' to the c-line ignore list...
Autodetecting through available interfaces...
Going to use 192.168.1.2 as a c-line in the SDPs
JANUS SIP plugin initialized!
Version: 3 (0.0.3)
Joining thread
SIP watchdog started
  [janus.plugin.sip] JANUS SIP plugin
  This is a simple SIP plugin for Janus, allowing WebRTC peers to register at a SIP server and call SIP user agents through the gateway.
Using a thread per connection for the HTTP webserver
HTTP webserver started (port 8088, /janus-gateway path listener)...
Using a thread per connection for the HTTPS webserver
HTTPS webserver started (port 7090, /janus-gateway path listener)...
[WARN] WebSockets support not compiled
[WARN] RabbitMQ support not compiled
[WARN] Admin/monitor HTTP webserver disabled
Using a thread per connection for the admin/monitor HTTPS webserver
Sessions watchdog started
Admin/monitor HTTPS webserver started (port 7089, /janus-gateway path listener)...

Any help is much appreciated.

wilbert

On Thursday, November 27, 2014 9:24:55 AM UTC-5, Lorenzo Miniero wrote:

Lorenzo Miniero

unread,
Nov 28, 2014, 9:14:30 AM11/28/14
to meetech...@googlegroups.com
The STUN related message is nothing to worry about, it's just a warning.

About the configuration, why use command line instead of configuring janus.cfg accordingly? The configuration that is printed is the one that is read from file, and gets overwritten by your command line settings, which means what we see in the log is not what is going to be used. Try integrating your settings in janus.cfg, and just change the debug level on the command line if you need so.

The only setting that may mess with the HTTP limited response behaviour is the HTTP threading model. By default this is unlimited, but I wonder if any of your command line configuration values are changing that. In fact, limited threads for HTTP might mean that the web erver would stop responding if they were all busy.

Lorenzo
 
...

Wilbert Jackson

unread,
Nov 28, 2014, 9:19:46 AM11/28/14
to meetech...@googlegroups.com
Ok

thanks
...

Wilbert Jackson

unread,
Nov 28, 2014, 11:08:49 AM11/28/14
to meetech...@googlegroups.com
Lorenzo,

I setup a janus.cfg which shown below. When I run the echotest app, on 3 machines that I have been running, I notice the janus server will stop responding to https post plugin request if any of the apps has the following error occur when closing the app. I have to restart the server.

Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Got event on session 864309665 janus.js:206
Object janus.js:207
Long poll... janus.js:170
Destroying session 864309665 (sync=false) janus.js:441
Destroying handle 2984151212 (janus.plugin.echotest) janus.js:460
Destroying handle 2984151212 (sync=false) janus.js:836
Cleaning WebRTC stuff janus.js:1348
Stopping local stream janus.js:1361
 ::: Got a cleanup notification ::: echotest.js:274
Destroyed handle: janus.js:864
Object janus.js:865
Destroyed session: janus.js:480
Object janus.js:481
Uncaught TypeError: Cannot read property 'readyState' of null janus.js:978
Closing window janus.js:41
Got event on session null janus.js:206
Object janus.js:207
  -- Event is coming from 2984151212 (janus.plugin.echotest) janus.js:285
Object janus.js:287
This handle is not attached to this session janus.js:290


janus.cfg file settings
; General configuration: folders where the configuration and the plugins
; can be found, default interface to use, debug/logging level and, if
; needed, shared apisecret between application(s) and Janus.
[general]
configs_folder = /opt/janus/etc/janus ; Configuration files folder
plugins_folder = /opt/janus/lib/janus/plugins ; Plugins folder
;interface = 1.2.3.4 ; Interface to use (will be used in SDP)
debug_level = 4 ; Debug/logging level, valid values are 0-7
;apisecret = janusrocks ; String that all Janus requests must contain
; to be accepted/authorized by the Janus core.
; Useful if you're wrapping all Janus API requests
; in your servers (that is, not in the browser,
; where you do the things your way) and you
; don't want other application to mess with
; this Janus instance.


; Web server and WebSockets stuff: whether either one should be enabled,
; which ports they should use, whether security should be handled directly
; or demanded to an external application (e.g., web frontend) and what
; should be the base path for the Janus API protocol (plain HTTP only).
; You can also specify the threading model to use for the HTTP webserver:
; by default this is 'unlimited' (which means a thread per connection, as
; specified by the libmicrohttpd documentation), using a number will make
; use of a thread pool instead. Since long polls are involved, make sure
; you choose a value that doesn't keep new connections waiting.
; Please beware that the WebSockets server will only be available if you
; built Janus compiling support for it.
[webserver]
base_path = /janus-gateway ; Base path to bind to in the web server (plain HTTP only)
threads = unlimited ; unlimited=thread per connection, number=thread pool
http = no ; Whether to enable the plain HTTP interface
port = 8088 ; Web server HTTP port
https = ; Whether to enable HTTPS (default=no)
secure_port = 7090 ; Web server HTTPS port, if enabled
ws = yes ; Whether to enable the WebSockets interface
ws_port = 8188 ; WebSockets server port
ws_ssl = no ; Whether to enable secure WebSockets
;ws_secure_port = 8989; ; WebSockets server secure port, if enabled


; Recent versions of Janus now also support RabbitMQ based messaging as
; an alternative "transport" for API requests, responses and notifications.
; This is only useful when you're wrapping Janus requests in your server
; application, and handling the communication with clients your own way.
; At the moment, only a single "application" can be handled at the same
; time, meaning that Janus won't implement multiple queues to handle
; multiple concurrent "application servers" taking advantage of its
; features. Support for this is planned, though (e.g., through some kind
; of negotiation to create queues on the fly). Right now, you can only
; configure the address of the RabbitMQ server to use, and the queues to
; make use of to receive (to-janus) and send (from-janus) messages
; from/to an external application. If you're using the same RabbitMQ
; server instance for multiple Janus instances, make sure you configure
; different queues for each of them (e.g., from-janus-1/to-janus-1 and
; from-janus-2/to-janus-2), or otherwise both the instances will make
; use of the same queues and messages will get lost. The integration
; is disabled by default, so set enable=yes if you want to use it.
[rabbitmq]
enable = no ; Whether the support must be enabled
host = localhost ; The address of the RabbitMQ server
;port = 5672 ; The port of the RabbitMQ server (5672 by default)
to_janus = to-janus ; Name of the queue for incoming messages
from_janus = from-janus ; Name of the queue for outgoing messages


; Janus can also expose an admin/monitor endpoint, to allow you to check
; which sessions are up, which handles they're managing, their current
; status and so on. This provides a useful aid when debugging potential
; issues in Janus. The configuration is pretty much the same as the one
; already presented above for the webserver stuff, as the API is very
; similar: choose the base bath for the admin/monitor endpoint (/admin
; by default), ports, threading model, etc. Besides, you can specify
; a secret that must be provided in all requests as a crude form of
; authorization mechanism, and partial or full source IPs if you want to
; limit access basing on IP addresses. For security reasons, this
; endpoint is disabled by default, enable it by setting admin_http=yes.
[admin]
admin_base_path = /janus-gateway ; Base path to bind to in the admin/monitor web server (plain HTTP only)
admin_threads = unlimited ; unlimited=thread per connection, number=thread pool
admin_http = no ; Whether to enable the plain HTTP interface
admin_port = 7088 ; Admin/monitor web server HTTP port
admin_https = no ; Whether to enable HTTPS (default=no)
;admin_secure_port = 7889 ; Admin/monitor web server HTTPS port, if enabled
admin_secret = janusoverlord ; String that all Janus requests must contain
;  to be accepted/authorized by the admin/monitor.
;admin_acl = 127.,192.168.0. ; Only allow requests coming from this comma separated list of addresses


; Certificate and key to use for DTLS and/or HTTPS/WSS.
[certificates]
;cert_pem = /opt/janus/share/janus/certs/mycert.pem
;cert_key = /opt/janus/share/janus/certs/mycert.key

cert_pem = /home/wilbert/janus-gateway/certs/ssl.pem
cert_key = /home/wilbert/janus-gateway/certs/ssl.key


; Media-related stuff: right now, you can only configure whether you want
; to enable IPv6 support (still WIP, so handle with care) and the range of
; ports to use for RTP and RTCP (by default, no range is envisaged).
; If you change any setting in the lines below, remember to uncomment the
; [media] category as well, which is commented by default!
;[media]
;ipv6 = true
;rtp_port_range = 20000-40000


; NAT-related stuff: specifically, you can either manually specify the 
; public IP of the machine (i.e., what would be used in SDP) or
; configure the STUN server to use to gather candidates if the gateway
; is behind a NAT, and srflx candidates are needed. By default, this
; section is commented as the gateway is assumed to be deployed on a
; public network. When configuring the public IP or the STUN
; configuration, remember to uncomment the [nat] categoty line as well!
[nat]
;public_ip = 173.194.68.127
stun_server = stun.l.google.com
stun_port = 19302

; You can also choose which interfaces or IP addresses should be excluded
; and ignored by the gateway for the purpose of ICE candidates gathering.
; To do so, use the 'ice_ignore_list' setting and pass it a comma-separated
; list of interfaces or IP addresses to ignore. This is especially useful
; if the server hosting the gateway has several interfaces you already
; know will not be used or will simply always slow down ICE (e.g., virtual
; interfaces created by VMware). Partial strings are supported, which
; means that any of the following examples are valid:
;     ice_ignore_list = vmnet8,192.168.0.1,10.0.0.1
;     ice_ignore_list = vmnet,192.168.
; By default, we ignore all interfaces whose name starts with 'vmnet':
ice_ignore_list = vmnet
...
Reply all
Reply to author
Forward
0 new messages