conference. | protected, regardless of how participants |
| connect, ensure you set this option. |
| When this option is set, participants calling into a |
| protected conference will be presented with PIN- |
| entry screen instead of the normal conference |
| view. The option has no effect for conferences |
| with no PIN set. |
|
|
If this option is checked, ad hoc conferences | It may be useful to register ad hoc conferences |
created using either an auto attendant or via calls | individually with the gatekeeper to facilitate load- |
to an E.164 number associated with the MCU | balancing between multiple MCU devices which |
service prefix will be registered individually with | have registered the same prefix. |
the configured gatekeeper. | If the MCU is operating in Port reservation |
| |
| mode, this option will be present but will be |
| ignored as ad hoc conferences are not allowed in |
| port reservation mode. |
|
|
If this option is checked, ad hoc conferences | You will need to |
created using an auto attendant will be registered | ad hoc conferences on the SIP registrar, or |
individually with the configured SIP registrar. | configure the SIP registrar such that it will |
| recognize unknown numbers. |
| The numeric ID used for the conference will be |
| registered as the SIP registrar ID (displayed on |
| the Conference statistics page). |
| If the MCU is operating in Port reservation |
| mode, this option will be present but will be |
| ignored as ad hoc conferences are not allowed in |
| port reservation mode.. |
|
|
The timeout setting for a participant entering a | This global setting may be useful where |
PIN for an ad hoc conference that they are | participants creating ad hoc conferences rarely |
currently creating: | need to configure a PIN. |
Participants will never be prompted to |
|
enter a PIN when creating an ad hoc |
|
conference. |
|
Participants will be prompted for a PIN |
|
when creating an ad hoc conference. If |
|
the participant does not enter a PIN |
|
during the configured time period, the |
|
conference will be created without a |
|
PIN. |
|
Participants will be prompted for a PIN |
|
when creating an ad hoc conference. |
|
They must either enter a PIN to create |
|
an ad hoc conference with a PIN or press |
|
the hash/pound key (#) to create the |
|
conference without a PIN. |
|
|
|
| 118 |
