- Bash Script – OpenMCU-ru Service Monitor -OR- Monitor and Automatically Restart a Service Upon Failure
- OpenMCU-ru – DSCP Based QoS Packet Tagging Rules for Linux IP Tables
- Polycom RealPresence Desktop – Do Not Minimize to Taskbar Tray
- Polycom RealPresence Desktop – Windows QoS Registry Settings
- Startup Script for OpenMeetings Open-Source Video Conferencing Server
Table of Contents - Conferencing
Most Popular - Conferencing
- Startup Script for OpenMeetings Open-Source Video Conferencing Server 936 views
- Polycom RealPresence Desktop – Windows QoS Registry Settings 791 views
- OpenMCU-ru – DSCP Based QoS Packet Tagging Rules for Linux IP Tables 346 views
- Bash Script – OpenMCU-ru Service Monitor -OR- Monitor and Automatically Restart a Service Upon Failure 341 views
- Polycom RealPresence Desktop – Do Not Minimize to Taskbar Tray 249 views
In Ubuntu, the best way to ensure that the firewall is up and running and that your packet filtering or mangling rules are in place any time the network connection comes up, you should create a rule in the /etc/network/if-up.d folder. An alternative approach to that would be to put a “post-up” rule on whatever interface in you /etc/network/interfaces file. From my experience, so that your firewall rules can be easily maintained as well having the ability to make comments for each rule, it’s ideal to take advantage of the iptables-save and iptables-restore functionality.
In order to follow this procedure, the first time you set up the firewall, you will have to manually add all the firewall rules and then issue the iptables-save command. For sake of saving time, I will just provide you with the contents of my config file that can be restored with the iptables-restore < config_file command. View Post
Bash Script – OpenMCU-ru Service Monitor -OR- Monitor and Automatically Restart a Service Upon Failure
I threw this service monitoring script together because occasionally the OpenMCU-ru process in the developmental versions can crash out on my Ubuntu Server from time to time, so I wanted it to auto-restart. The script could easily be modified and used for any other service you like, but it was written specifically for OpenMCU-ru and Debian based operating systems.
There are two pieces to this puzzle (which makes for an awfully pathetic and simplistic puzzle), the “/etc/init.d/mcu-monitor” startup script to run the monitoring script as a daemon and the “/usr/local/bin/mcu-monitor.sh” monitoring script itself, both are fairly simple and straight forward. View Post
Last week, I had to call Polycom support for two issues. One of which I mentioned in another post (Automatic Gain Control issue) and the other was because I wanted to find out why their user manual showed some QoS settings that my version did not have access to.
After waiting on hold for ten minutes, the first tech support person I reached was a little cocky, arrogant, smart ass of a prick who was less than helpful with either of my support requests. At one point, he literally told me “we can’t control Windows” (which brings up the question, “Well why in the fuck did Polycom even make software in the first place then?”) in regards to my AGC issue even after I told him that I had disabled all of the Windows settings that take control of the audio interface. He also said that you can set up QoS in Windows “somewhere in the network settings” (which turned out to be completely erroneous) without giving an ounce of help or direction.
Towards the end of our call, he was just trying to get me off the phone basically with an answer of “you’re fucked” to all my questions. At that point, I got pissed off and demanded to speak to somebody else. Finally, I got put on the phone with one of their product engineers and they actually addressed my issues. Long story short, the engineer ended up having to do a remote support session and did indeed acknowledge my AGC issue and gave me an explanation of why I couldn’t see the QoS settings mentioned in the manual. It turns out, those settings only show up if you use their provisioning server and they don’t even set the QoS settings in Windows like I needed.
/etc/init.d/openmeetings startup script for Ubuntu Server 12.04.2
OpenMeetings Version 2.0-INCUBATING
A few notes:
– Make sure to change path for RED5_HOME variable
– Make sure to chmod +x the init script
– This assumes openmeetings is running under a user/group with the same name
– This assumes you are using libreoffice (not openoffice) for the whiteboard file import service
#!/bin/bash # # Author: Nathan Thomas # ### BEGIN INIT INFO # Provides: red5 # Required-Start: $local_fs $remote_fs $network $syslog $named $time # Required-Stop: $local_fs $remote_fs $network $syslog $named $time # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # X-Interactive: true # Short-Description: Start/stop OpenMeetings java based conferencing webapp ### END INIT INFO PROG=red5 DESC="Red5 flash streaming server" RED5_HOME=/usr/local/openmeetings DAEMON=$RED5_HOME/$PROG.sh PIDFILE=/var/run/$PROG.pid # Plugin Variables #OO_HOME=/usr/lib/openoffice/program OO_HOME=/usr/lib/libreoffice/program View Post