Announcing the OpenTok Connectivity Doctor

ConnectivityDoctor_1024x1024As an OpenTok customer, you know that in order to deliver a great call experience, network connectivity is king. You can spend hours developing your real-time communications app, only to encounter connectivity hurdles like corporate firewalls or blocked IP in a new network environment.

It’s important to know that your application will work where you need it to, whether you’re pitching an investor, selling to a client, or just showing off all your hard work. That’s why we’re excited to launch the first version of the OpenTok Connectivity Doctor.

The OpenTok Connectivity Doctor helps you diagnose problems with your network before or after you connect to an OpenTok session. This tool does not test for errors in your code.

Support for the platforms you use:

– Connectivity Doctor for Web: now publicly available here.

– Connectivity Doctor for iOS:  currently available in TestFlight. Please reach out to TokBox to gain access.

– Connectivity Doctor for Android: now publicly available in the Google Play Store.

How does it work?

You can run this test before you start your OpenTok session, or after you’ve encountered a problem (credit tobi). At this time, it won’t diagnose in real-time.

Each time you run the OpenTok Connectivity Doctor, we test for connectivity to OpenTok’s infrastructure:

  1. API Server

    • Connects to OpenTok and controls the server.

  2. Media Router

    • Enables you to do multi party calls, signaling, archiving and more.

  3. Mesh TURN Server

    • Enables you to have a relayed call with TURN fallback.

  4. Logging Server

    • This allows the TokBox team to collect anonymous data about the network conditions and problems you’re encountering. This information is used by our team to continue to improve the OpenTok platform.

After the connectivity test has run, the results will be displayed on your screen. You will also have the option to enter an email address if you’d like to send the results.

We’re looking forward to hearing what you think of this new feature!

  • Todd

    Hello, where do we find this connectivity doctor?

    • Ankur Oberoi

      Hey Todd,

      The links for both the web and Android connectivity doctor are in the blog post. The iOS connectivity doctor is being sent out over TestFlight and if you’re interested in that please send us an email at so we can get the required information from you. Does that help?

  • Cristian Pereyra

    Hello, I got the application hanging on Android everytime I use it, I only got a green tick on the third row and it hanged. But I’m on a wifi connection that is passing the test via html.

    • Hashir Baqai

      Hi Christian,

      Thanks for the heads up. Can you email with the details of your Android device and Android build number? We’ll look into what the issue is and push an update if needed.

  • Scott Barnett

    Could you make this diagnostic tool available via GitHub so that we, your customers, can customize the user experience? I know my customers, generally speaking, don’t have any clue what an API Server, Media Router, MESH Turn Server, or Logging Server are so I’d feel embarrassed pointing them to a diagnostic site that requires some to understand that terminology.

    In other words, I need a tool that addresses the exact same problem this tool was designed to solve but the current UX is unusable for my customers. My friends who use TokBox in their products say the same thing. Any chance we can get this tool in a format that’s usable for our businesses?

    • Charley Robinson

      I’m not sure about moving Connectivity Doctor to open source, but we do have similar functionality in an existing open source tool:
      Maybe it helps for you and your friends who use TokBox in their products?

      • Scott Barnett

        Why not move it to open source? I ask because I’m a new customer and I’ve seen people asking for the same thing on your message boards from a few years ago.

        It seems to me that you’ve had the tool for at least a couple years and, it seems to me that your goal isn’t to charge money for it, but instead for it to be useful for your customers (something we appreciate). So, open sourcing seems like it’d help you better achieve your own goals (something we’d appreciate even more).

        In the short-term, it would likely lower your own hosting cost while also getting it to be used more frequently (and hosted from your customers sites to keep the cost down) which, I suspect, was the original goal of building the tool.

        Furthermore, and perhaps much more importantly, open sourcing it would make your core product more valuable to your customers and it would make your customers more likely to succeed, each of which is great for you and great for us.

        I’d understand licensing it or selling it as premium add-on service too, so long as you give your customers the ability to customize the UI, workflow, etc. But that’d require a large investment on your behalf and doesn’t seem to fit with your goals for the tool.

        The only thing that doesn’t make sent to me is leaving it as it is because you could open source it after a few hours of internal meetings to get approval (i.e., a very low cost), and this would make your product more valuable and your customers more likely to succeed. Seems like a great opportunity for you. I hope you seize it.

        • Charley Robinson

          Thanks for the feedback, Scott! It is indeed a discussion ongoing internally, and your thoughts on the matter will certainly be included in that. In the meantime, I invite you to evaluate some of the other tools we have made available; connectivity is a popular topic for both support and positive user experience. If you have specific technical questions, feel free to reach out to our support team moving forward while you are working on your new app:

          • Scott Barnett

            You’re welcome Charley. Thank you for listening and also participating in the dialog.

            I’ll definitely check out your other tools as well. Best, Scott

          • Elliot Agro

            @wobbals:disqus Just wondering if you have any updated on your internal conversations regards to open sourcing the connectivity doctor – or at maybe even just exposing the end points that it uses so we can build our tool around those?

            My customers almost always have a very secure firewall setup and as Scott mentioned its difficult pointing them to your tool as they would really not understand the terminology – much better if we can detect the results of the test and make suggestions on how to proceed.