If you made frequent use of pins and pin sets on our 1.4. and 1.5 devices, you might be disappointed to see that there is not a similar pin code, or pin set feature on the 3CX PBX system. Luckily, the 3CX PBX Appliance offers an incredibly flexible platform , and with a similar behaviour can be configured, although in a slightly different manner.
In the place of pin codes, 3CX systems make use of prefixes on outbound routes. In this manner, the user is required to dial a pin prior to the DID of the destination that they intend to call. Up to fifteen prefixes can be configured per outbound route, and each of these can represent a unique pin.
Unfortunately, this does mean that multiple outbound routes will be required for environments where there are several agents placing outbound calls, each requiring a unique pin code..
First create an outbound route, and name it something sensible. In this example I name it "Call Centre Our".
In the prefix column, add up to fifteen pin codes, separated by a comma. These pin codes could match up with the user's voicemail pin, if you plan it in such a manner, but otherwise, there is no way to associate a particular pin with a particular user on this system. That could be better managed and recorded in an external HR suit.
Create an outbound route and add the pin codes as prefixes under the heading "Calls to numbers starting with prefix". Up to fifteen pin codes can be added, separated by a comma.
The example on the right demonstrates pin codes of 1111,2222,3333,4444,5555,6666 and 7777.
Select the desired trunk, and configure the number of digits to be stripped from the dialed number prior to dialing. This should match the length of the pin codes.
Select the appropriate trunk for outbound calls, and configure the route to strip the same number of digits as the length of the configured pin codes.
With this feature, a user who has access to the outbound route will be able to dial their pin code, followed by the number they intend to dial. They will not be requested for their pin, but failing to include their pin in the call would result in the call failing.
In the case of integrating with Man3000 in particular, there are certain requirements of the pin to integrate seamlessly with the Man3000 suite. Pin codes that are to be processed by Man3000 should be 4 digits in length and should not start with the digit 0.