09-22-2014 03:41 AM - edited 03-19-2019 08:39 AM
Hi,
We're in the process of trying to implement Mobile and Remote Access via Expressway version X8.2.
We believe that the configuration is correct, however our Jabber clients all report the error, 'Cannot communicate with the server'. This error message appears after the Expressway-E has sent it's certificate to the Jabber client. We're currently signing the Expressway-E certificate with our enterprise CA until we have a working solution, after which we'll get a public certificate for the Expressway-E.
Anyway, I suspect that the problem could be due to the licensing of the Expressway-C. Can anyone confirm if the Expressway-C should have option keys installed for Rich Media Sessions?
Currently our Expressway-E is licensed for 20 Rich Media Session and our Expressway-C is licensed for 0 Rich Media Sessions. I'd like confirmation if this is normal or if we're missing licenses?
I've attached screenshots from both of the Expressways for your review.
Thanks for your time,
Dave.
09-22-2014 09:51 AM
Can you create a PRT from the Jabber client and attach it here?
The RMS license should be split between Exp-C/E. ie you should have 10 on your C and 10 on your E to have 10 concurrent video calls. You will have to work with licensing to get that ironed out.
09-22-2014 03:18 PM
09-22-2014 03:30 PM
Dave,
You are correct on the RMS part, those licenses are used for B2B calls (calling from Jabber to another company) or for Lync interop calls if you had the OCS interop keys. I agree, the licensing could be a little more streamlined.
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide