This article relates to the Cisco TelePresence MCU 4203, Cisco TelePresence MCU MSE 8420, Cisco TelePresence MCU 4505 and Cisco TelePresence MCU MSE 8510 products.
Q. How do I create a conference on a Codian MCU that is not publicly accessible?
A. Restricting Access by H.323 Callers
For H.323 callers, the MCU's default behavior is for all conferences to appear on the default auto attendant, and for that auto attendant to be available to all callers. This behavior can be changed in various ways:
It is possible to change the configuration of the default auto attendant so that it does not include all conferences, but instead just a specific selection. Log in to the web interface as the administrator. Then go to Conferences > Auto attendants, click Default and then configure the Accessible scheduled conferences parameters as appropriate.
Conferences can be configured with a PIN so that only those who know the PIN can join them.
The default auto attendant can be configured with a PIN so that only a restricted set of callers can see the available conferences.
If you are in a gatekeeper-controlled environment, you can set up each conference with an E.164 number (as well as a PIN) if required and configure the default auto attendant to not show any of them. In this way, people can only access the conferences they have been told about, and call into those conference directly rather than through the auto attendant.
Restricting Access via the web interface
If you log in to the web interface with 'admin' privilege you can see the active and scheduled conferences and change those conferences' configuration.
To restrict availability of conferences from the web interface, accounts can be configured to have 'guest' access only and the 'guest' privileges can be set appropriately. To do so, go to Users, select User ID 'guest', and then change the Guest access rights as required.