Microsoft Office Communications Server Remote Connectivity

Microsoft has recently made available a Beta version of a web tool that can be used to test the external connectivty of your OCS Edge deployment:

You can choose to manually enter your Edge Access hostname and port (normally 443), or by using auto-discovery (via DNS records). The auto-discovery option is good because it inherently tests that the correct external DNS entries exists which allow remote clients to automatically logon.

You need to provide a valid SIP user and password to the test the external SIP login through the Edge. Testing the complete login process is beneficial because the SSL Certificate configuration is validated.

Here is the results of a sample test run (domains and user details ommitted):

Attempting to Resolve the host name in DNS.
Host successfully Resolved
Additional Details: IP(s) returned:

Testing TCP Port 443 on host to ensure it is listening/open.
The port was opened successfully.

Testing SSLCertificate for validity.
The certificate passed all validation requirements.validation checks.
Additional Details: Subject:, OU=example, O=”Example, Inc.”, L=Example City, S=Example State, C=Example country, Issuer CN=<Certificate Authority>, OU=<CA URL>, O=<CA Organization Name>, C=<CA Country>

Testing OCS remote sign in through Access Edge Server: Port Number (, for SignInAddress (
The specified user successfully signed in remotely through the Access Edge Server.
Additional Details:  Registration is successfully completed.

Share and Enjoy:
  • Twitter
  • Digg
  • StumbleUpon
  • Facebook
  • LinkedIn
  • MySpace
  • Reddit
  • Technorati

2 comments to Microsoft Office Communications Server Remote Connectivity Analyzer

  • Curtis Johnstone

    Agreed – some of these free tools can be frustrating when things don’t work, and there is typically little documentation and good information to help.

    I believe the tool is still officially in ‘Beta’, and I noticed a Feedback button right on the main page – it might be worth submitting details of your issue. I like your idea of helpful pointers at each stage; let’s take a shot at this one.

    Each stage has expandable details. What details are shown for the last stage (where, as you say, the actual remote user sign-in occurs)?

    FYI – The tool has worked for me (all 4 stages) in two production environments.

  • John Henry

    Sure it’s great if it all works – but how about some helpful pointers at each stage if it fails?

    Ours fails at the last stage every time, the actual remote sign-in part, and I’ve went through the list of checks the link provides but still no joy.

    What would be great would be if someone stated real-life helpful reasons why a particular stage fails

Leave a Reply




You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>