Extension Mobility with proper logout profiles configured should be a good solution to restrict people from making unauthorized calls, access codes like FAC and CMC are configurable on Route patterns for outbound calls only.
The problem with extension mobility is that when a user is logged into the phone, the phone is his.
What we need is a phone that is accessible by its number (xxxx for example)
But when someone needs to make a call he has to authenticate before of after typing the number.
We tried using FAC and then the phone askes for a PIN after the nuber has been dialed. But, the strange thing is, he asks only for the PIN when trying to call a number that he doesn't know. When we try an existing number no pin is asked.
Is it possible that when using FAC we need to make each phone an outbound connection?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.