Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 – Subset or Superset service prefixes
Cisco VCS Deployment Guide: Connecting MCUs to Cisco VCSs for resilience and capacity
Page 8 of 10
Appendix 1 – Subset or Superset service
prefixes
prefixes
If an MCU tries to register a service prefix that is either:
a subset or a superset of an existing service prefix registration on that Cisco VCS,
or, if the Cisco VCS is a peer in a cluster of Cisco VCSs a subset or a superset of an existing
service prefix registration on any other peer in the cluster
service prefix registration on any other peer in the cluster
the Cisco VCS will reject that registration. Service prefixes from different MCUs can be identical, but if
not identical, they must not overlap.
not identical, they must not overlap.
For example, if an MCU service prefix registration for 91 exists on the Cisco VCS and a different MCU
tries to register a service prefix of 914, this latter registration request will be rejected.
tries to register a service prefix of 914, this latter registration request will be rejected.
Similarly, if an MCU service prefix registration for 914 exists on the Cisco VCS and a different MCU
tries to register a service prefix of 91, this latter registration request will be rejected.
tries to register a service prefix of 91, this latter registration request will be rejected.
Registering exactly the same prefix is allowed (and required), so, for example, if an MCU service
prefix registration for 91 exists on the Cisco VCS and a different MCU tries to register a service prefix
of 91, this registration will be allowed.
prefix registration for 91 exists on the Cisco VCS and a different MCU tries to register a service prefix
of 91, this registration will be allowed.
Similarly, if an MCU service prefix registration for 914 exists on the Cisco VCS and a different MCU
tries to register a service prefix of 914, this registration will be allowed.
tries to register a service prefix of 914, this registration will be allowed.