How the Auto attendant works
It is important to note that the Auto attendant in Vinteo is not a mechanism for controlling access to a specific conference. The PIN code is also not a password for entering the selected room. Within the current logic the PIN is used as the conference ID which is used by the auto attendant to route the call.
Accordingly when entering the auto attendant the user enters a PIN code, and the system connects him to the conference for which this PIN is set. The number the call was originally made to is irrelevant in this scenario.
The auto attendant is primarily designed to handle incoming calls without specifying a conference number (for example, when calling the server IP address or when integrating with external systems). In this case, it allows the account to join the desired conference using a PIN code or wait for the administrator or moderator to connect.
The routing logic is described in detail in this article
If you need to prevent joining a conference via the auto-attendant using a PIN code, leave the PIN code field for the conference empty.
Additionally, you can restrict access for anonymous users via a PIN code:
* at the server level — by disabling anonymous user connections in the auto-attendant (“System” => “Settings” => “Anonymous Access”);
* at the specific conference level — by disabling anonymous user connections in its settings. In this case, even if the correct PIN code is entered, joining the conference will not occur.
It is also worth noting that the auto-attendant performs an additional function of protecting against spam calls. In the “System” => “Incoming calls” section, you can configure the timeout for how long a connection remains in the auto-attendant. After this time expires, the call will be terminated. If the call was anonymous and the IP address is not on the whitelist, such an address will be automatically added to the blacklist with the blackhole label, after which traffic from it will be blocked.