Last month, a reader commented on my post Exchanging Protocols: The Latest on Lync and Skype Integration. Matthew mentioned RHUB as a secure conferencing software provider, billed as ‘unprecedented’ security.
This week I had time to test out RHUB’s TurboMeeting conferencing software. Glad I did too.
Secure? Yes, though I have questions here.
How does it stack up to Lync Server? Well, let’s go through my findings and determine that.
The TurboMeeting Demo
I signed up for a demo on RHUBCom.com – there are “Try It Free” and “Demo” buttons right on their homepage. I downloaded the TurboMeeting demo file, but it wouldn’t load for some reason (maybe my Windows 8.1). A zipped version of the download worked OK.
Here’s what the TurboMeeting client looks like on loading:
I entered my email and password. The meeting server address is “demo.rhubcom.com” for their Demo. Had to locate this in the Quick User Guide.
Now we have the main client window:
Huh, no meetings listed in the demoâ€¦let’s make one!
“Interactive Meeting” is the default, so let’s try that first. (I’m also curious about the “Remote Access to This Computer” option.)
I invited myself to join on another computer (henceforth the “attendee”) via email. Two things to note right away:
- The email text looks very similar to Lync and WebEx. This is good; it encourages familiarity and gives simple instructions on how to join a meeting.
- This is an impromptu meeting; a way to schedule the meeting for later is not immediately apparent.
On my other computer (“attendee”) I accepted the meeting request. The RHUB demo prompted me to download & run the TurboMeeting client. Like Lync Meeting and WebEx, it went through the automatic process of loading the meeting client in a snap.
But here’s the interesting thing. When the client finished loading on my attendee computerâ€¦my host PC shared its desktop!
Look at the top left of this screenshot. See how it says “Share My: [Screen]”?
I didn’t choose that option. TurboMeeting defaulted to Desktop Sharing on its own.
There’s an advantage and a disadvantage to this default.
Advantage: Fewer steps for sharing in a meeting. (Note: You can choose between open applications to share as well, with a click.)
Disadvantage: Maybe you didn’t want to start a meeting with a shared desktop. It happens. If so, there is an option under Tools > Preferences: “Show my desktop when a meeting starts”. Uncheck this to avoid defaulting to Desktop Sharing.
The meeting caused a little bit of lag between the host and the attendee computers. Just enough to notice; maybe a quarter of a second. Not a big deal.
Finally, I tested the voice quality. Since it’s just me on the calls, I got some echo (both computers are in the same room). I expected that. Voice quality is good; comparable to Lync’s.
Remote Control: 2 Ways to Achieve Remote Access
While in this two-computer/single-person meeting, I decided try out the “Give Control” button.
Clicking it gives a small drop-down with two options: “Reclaim Controller” and names of attendees. Click another attendee to grant them control of your keyboard & mouse.
Caveat: The computer which controls another must be set as Presenter. Use the “Change Presenter” button to do this. Then, Give Control to another attendee. (I typed this paragraph remotely from the attendee, while my host PC was Presenter and had Given Control to the other.)
This works similarly to using Lync for remote access, as I blogged about before.
The meeting suddenly ended after I returned control to the host. There’s a 15-minute timeout on the demo. I decided to reconnect and try out the “Remote Access to This Computer” option.
It starts up the same way – create a meeting, enter a password for access. Instead of a meeting Subject, you enter a name for your computer. And Invite by Email is not available this time. TurboMeeting does allow you to copy the meeting information though, which you can then email to attendees.
In the case of remote access, the password is encrypted & not shown to the attendees. You must give it to them another way – either in the email you send, or via IM/phone/yelling it across the hall (I don’t recommend the last option).
Once the meeting connects, you’re immediately granted access to the host’s computer. Again, I’m typing this paragraph from the attendee via TurboMeeting Remote Access.
The lag I mentioned before grew worse this time. About half a second on the attendee. I’m sure corrections can be made to improve the response time.
An attendee TurboMeeting window has different options than the host. Here you see the buttons for File Transfer, Start Webcam and Record along the top:
Better test these too. I initiated a file transfer between my other computer and the host. (What file to send…how about a screenshot of the process?)
I also did a test Record of both typing remotely, and a brief activation of the webcam. (Not brave enough to post it though!)
TurboMeeting automatically prompted me for a save location when I stopped recording. It saves as a .exe file though – a file format many spam filters will not allow through. Easy to share other ways, but sharing a recording via email could prove difficult.
The Security Question
RHUB places high value on making their conferencing software secure. It’s called out frequently on their site, and in product descriptions. I also found mention of it in a press release on MarketWatch.com: Why RHUB Web Conferencing and Remote Servers are so Secure.
There is one point which I must question here. RHUB points to access security as a weak point. “Practically anyone” can get in with a meeting ID and password. RHUB’s response is to create a virtual VPN limited to specified IP addresses. While that is indeed good security, it can seriously cramp remote conferencing capability.
Since the default option (at least in their demo) is to immediately start a meeting instead of scheduling, you could wind up inviting people who are connecting from unauthorized IPs. Their office network isn’t authorized, or they’re in a coffee shop, or logging in remotely. Instant security snag.
I could be missing some information; if so, I happily invite RHUB to comment here with their input. The security approach here is a strong one. I’m just concerned that when it comes to something dependent on multiple inputs like web conferencing, it can trip organizations up.
I’d draw a parallel between RHUB’s TurboMeeting and Lync Server 2010. A sturdy solution for its intended purpose (online conferencing), which could use a little more added. Is it perfect? No. But neither was Lync Server 2010. When we got Lync Server 2013, several issues were polished out & handy features added. I believe the same thing will happen with RHUB, giving us a superb Conferencing-only option.
Since it focuses on conferencing only, the vendor who should worry the most is Cisco WebEx. TurboMeeting is very similar to WebEx, but loads a little faster and has a cleaner client-side interface. Their focus on security is bound to win favor from WebEx users too.
Competition is always good in business. I like that we have TurboMeeting as a conferencing-only alternative. It’s not Lync, but it isn’t trying to be. It wants only to be a strong, secure conferencing solution. And in that, it does the job well.
(For everything else, there’s Lync Server! Sorry Mastercard.)
Have you used RHUB’S TurboMeeting? What was your experience with it? Please comment or email. If you’ve tried another conferencing solution, I’d love to hear about that too.