Mobile and Remote Access via Expressway - Question regarding Expressway-C Licenses
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 reply George.
We ended up resolving the Jabber client connectivity issue. Our Expressway-E was configured with a private hostname in our internal domain, ie., 'hostname.internal'. We changed its hostname to how its known publicly, ie., 'collaborate.external.com'. Once we made the change and rebooted the Expressway-E, our Jabber clients could connect.
Just confirming that what you're saying regarding the RMS licensing is that it only impacts on the ability to place video calls?
I will log a call with licensing to see if they'll help me to split the RMS license. They should make it clearer about how to apply the RMS because they were included in the Expressway-E PAK fulfillment.
Thanks for your reply.
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.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...