I put something together like this for a finance company - Asterisk
looked up the callerid in a MySQL database, and put the call into a
queue, with a higher priority if the call was from certain clients.
If the callerid was not found, it them allowed for a clientid and
pincode to be entered.
The only thing someone else wrote was the web front end to manage it
all.
PaulH
On Wed, 2008-01-02 at 02:06 +0000, Caza Henha wrote:> Hi, We currently testing a trixbox/asterisk installation and have used
Freepbx to set-up and configure the box and it is running tremendously well. We
have an generic IVR configured to which can transfer callers to a child IVR.
This child IVR has a number of options to send the caller off to various queues.
However we would like to protect some of the options with a password/pin number
so that only callers with a valid pin can gain access to the queues. We have
looked at pin sets but this doesn't seem to be the correct route, we also
searched on the Internet but the queries we have used bring up options to
password protect queues from agents not callers.
>
> Initially we are happy with using just the one pin number for all customers
for testing purposes then to proceed to using a sql backend to allow us to
uniquely give each customer their own pin. Has anyone any suggestions on which
direction we should proceed; we presume it could be the "customer_app"
route which from our limited experience will hook into a custom asterisk script
but being new to freepbx and asterisk we are not sure how to go about
implementing this solution or if it has already been done? Any advice is
appreciated...
> _________________________________________________________________
> Fancy some celeb spotting?
> https://www.celebmashup.com
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users