Extension Security && Statistics

[Bigpete]

We have a customer that ask us the following feature:

For each extension we want an enabler (a badge or a numeric password digitized with the telephone keys). The enabler must identify the user (So Jim have a badge or a code, Tom another one and so on). Before each call our users must use the badge or hit the key on the phone, identifying themselves on the system.

This feature first of all trap unauthorized calls from telephons placed in places where all people could use it. Second one if the data was stored in the system we can stats who has called who, following the identifier as main key and associating with it the destination number

Now, do you have some ideas how we can implement this feature with 3CX? Please note, the customer can change the phones with that suggested by you and with badge (if needed). But the problem's focus is the possibility to enable or not a call depending by the security key and the possibility to trace the identifier/call couple.

Could you give me an help about this?

 

[archie]

Theoretically, it is possible. But it requires additional setings in DB which will complicate installation and setup process. We're trying to keep it as simple as possible. So, we could consider this feature as additional module, not common settings.

 

[RobLloyd]

Not sure feasable this is on your install - how many extensions?

You could have a "password" set as an outbound rule for each person/group. If you don't know the password then you can't dial out.
93245 - 9 to dial out, 3245 as the password to make it work. Just strip off the 93245 then dial the rest of the dialed #.

Just make sure you leave your emergency # able to be dialed from anywhere. 911,999 whereever you are.

Not really an answer to what you want but it might do for now?

 

[Bigpete]

Good Idea RobLloyd!
It seems to solve the password (enabler) problem.

But...One step forward could be to develope an small application that "reads" this data from a badge reader and send it to the 3CX on the lan on the correct port, enabling the phone to place one (and only one) call. :lol:
Any idea about this? (Consider that we are a software house and we could write some piece of code in VS2005 or similar to interface API or classes derived from 3CX system)
Thanks for your help.

 

[Bigpete]

Archie,
if I correctly understand, there is the possibility to trace a call, giving up not only the destination number, but the source (the user) that initiate the call too. This possibility requires however some work on DB (and/or on the report that we could display or print). Just consider that we are a software house and, if needed, we can write some piece of code to interface the 3CX data and system. So if you would go deep in the problem and give us some explanations we could try to develope this report by ourself.
Have you some good news for us (Please see also the post to robLloid; pheraphs could you help us in this case too) ?

 

[archie]

Rob's idea is good and clear enough. I don't know what to add to it.

If you want make your own module, than I would suggest to make some SIP frontend to PBX, which will be entry point to PBX, so no phones are register or call to PBX directly (they don't know credentials), but register against your frontend (actually, it should be stateless SIP proxy). Your proxy will register your extensions agains PBX using secret credentials. Also, it will forward INVITEs from phones to PBX provided that they passed your authentication scheme. In that case you can make that authentication as complex as you need.