complete PIN SET feature is needed!

[Teletecnicos COL]

Hello!

In ALL of our implementations, we need the functionality of PIN SETS, in our most recent implementation of 3CX we have 6 3CX machines connected by BRIDGE. All extensions require international calls protected by PIN but if i enable PIN PROTECT the internal calls between 3CX machines request PIN too. I cant select routes protected by PIN, additionally we can't use a PIN CODE in multiple extensions.

In the Latin American market the functionality of PIN Sets is necessary in the 90% of our installations.

ALL another PBX brands that we know in our company experience for more than 25 years like chinese appliances with asterisk, proprietary brands, very OLD panasonic machines have this functionality but this a very very WEAK point for 3CX

 

[VoIPTools]

I might need to think this through a little more, but here is one approach that might work.

First, do not make an outbound rule for standard international calls. With no outbound rule, any calls to an international phone number will be blocked.

Then, train your staff to dial a special extension when they want to make international calls. This extension is a Call Flow Designer application that (1) requests a PIN, (2) validates the PIN, (3) requests the desired phone number, (4) prepends some extra digits to the requested phone number (perhaps 8888), (5) performs a MakeCall with the modified number.

Finally, create an outbound rule that looks for phone calls with the appropriate length number that starts with 8888. Have the outbound rule strip the 8888 and transfer the call out the trunk.

It is not a perfect solution, but a workable compromise.

 

[SweetAction]

A simpler hacky way to do this...

Don't have an outbound rule for international.

Then make and outbound rule, where prefix = pin AND strip digit = pin length.
You will need a new rule for every "pin"

 

[Teletecnicos COL]

A simpler hacky way to do this...

Don't have an outbound rule for international.

Then make and outbound rule, where prefix = pin AND strip digit = pin length.
You will need a new rule for every "pin"

View attachment 19262

Hello! thank you for your reply SweetAction

A few weeks ago i test this workaround for a 1200 extension PBX, but is not functional at all in a corporate scenery.
The PIN appear in the phone call log history. Any person can view the PINs used in the endpoints.

In Latin America is a VERY common practice protect the calls with high cost, and this functionality is requested to us in the 90% of installations of phone systems.

 

[Teletecnicos COL]

I might need to think this through a little more, but here is one approach that might work.

First, do not make an outbound rule for standard international calls. With no outbound rule, any calls to an international phone number will be blocked.

Then, train your staff to dial a special extension when they want to make international calls. This extension is a Call Flow Designer application that (1) requests a PIN, (2) validates the PIN, (3) requests the desired phone number, (4) prepends some extra digits to the requested phone number (perhaps 8888), (5) performs a MakeCall with the modified number.

Finally, create an outbound rule that looks for phone calls with the appropriate length number that starts with 8888. Have the outbound rule strip the 8888 and transfer the call out the trunk.

It is not a perfect solution, but a workable compromise.

Thank you my friend! in our last project (1200+ extensions) we made this app! reading a list of codes and permissions contained in a CSV file.

It barely work, but have many problems and many people have problems like:

1 - Internationals numbers normally are very LONG. redial button does not work with this solution.

2 - The user hear the Music on hold of the 3cx PBX before the remote party answer the call (the user not hear the "ring" or any message, information of the destination operator

And some other situations like generation of this custom reports by ssh, maintenace of pin sets codes etc.

Thank you for your help!