Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Cisco Spark
Hybrid Services
(Connectors)
Hybrid Services
(Connectors)
Mobile and
Remote
Access
Remote
Access
Jabber
Guest
Services
Guest
Services
Microsoft
Interoperability
Interoperability
Registrar CMR Cloud Business
to
Business
calling
Business
calling
Cisco Spark
Hybrid Services
(Connectors)
Hybrid Services
(Connectors)
Y
N
N
N
N
N
N
Mobile and
Remote Access
Remote Access
N
Y
N
N
Y
Y
Y
Jabber Guest
Services
Services
N
N
Y
N
Y
Y
Y
Microsoft
Interoperability
Interoperability
N
N
N
Y
N
N
N
Registrar
N
Y
Y
N
Y
Y
Y
CMR Cloud
N
Y
Y
N
Y
Y
Y
Business to
Business calling
Business calling
N
Y
Y
N
Y
Y
Y
Table 5 Services That Can Be Hosted Together
Key to Table
Y: Yes, these services can be hosted on the same system or cluster
N: No, these services may not be hosted on the same system or cluster
Rules
■
Hybrid Services requires a dedicated Expressway-C to host Connectors
■
Microsoft Interoperability requires a dedicated VCS Control or Expressway-C (called Gateway VCS or
Gateway Expressway in the help and documentation)
Gateway Expressway in the help and documentation)
■
Jabber Guest cannot work with MRA (technical limitation)
■
MRA is currently not supported in IPv6 only mode. If you want IPv6 B2B calling to co-reside with IPv4 MRA on
the same Cisco VCS traversal pair, the Cisco VCS Expressway and Cisco VCS Control must both be in dual
stack mode.
the same Cisco VCS traversal pair, the Cisco VCS Expressway and Cisco VCS Control must both be in dual
stack mode.
MRA Allow List Improvements
The MRA allow list feature is more specific in this release. When you add, discover, or refresh the Unified
Communications nodes on the Cisco VCS Control, the Cisco VCS automatically adds the nodes to the allow list. We
are now being a lot more specific by including the port and request path in the allow list rule.
Communications nodes on the Cisco VCS Control, the Cisco VCS automatically adds the nodes to the allow list. We
are now being a lot more specific by including the port and request path in the allow list rule.
We also improved the interface for manually adding rules, enabling you to accurately specify the URL and so restrict
the scope of access. For example, instead of allowing
the scope of access. For example, instead of allowing
something.example.com
, now you can add
https://something.example.com:8443/pathto/resource.htm
instead.
You can also restrict which HTTP methods you allow for each of your rules.
Note:
You should review your editable rules after you upgrade the Cisco VCS Controls in your MRA deployment. We
advise this because any servers you previously added to the allow list are upgraded to prefix matching rules. These
rules allow any path on that server, using the default ports for the originally entered protocol.
rules allow any path on that server, using the default ports for the originally entered protocol.
The automatically added entries are automatically upgraded to be more specific than in previous releases.
11
Cisco TelePresence Video Communication Server Release Notes
Features in X8.8