As I was working on my extensions.conf file, I started to segment calling privileges. For the everyday workers, I don't free reign to LD access unless it is business related. So I was wondering if there was a way to implement some type of accounting code to be entered before accessing LD, which of course would be noted in the CDR (however it is implemented, either comma delimited or MySQL). For example: I have a customer who is customer 2022. One of my tech support people has to make a call to that client for business related reasons. So when that tech person dials 1-212-555-1212, they have to dial in 2022 so that it is notated that this call was to that particular client. Assuming that is a valid account code, the LD call proceeds, if not, a message is played for the tech person to the effect of something like, "That account code is not valid" and notates that in the cdr as well. This is my view of how it would work, but if anyone has another way to provide accountability that would work as well. Kim C. Callis -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20030704/40e64092/attachment.htm
"show application authenticate" ? Martin On Fri, 4 Jul 2003, Kim C. Callis wrote:> As I was working on my extensions.conf file, I started to segment > calling privileges. For the everyday workers, I don't free reign to LD > access unless it is business related. So I was wondering if there was a > way to implement some type of accounting code to be entered before > accessing LD, which of course would be noted in the CDR (however it is > implemented, either comma delimited or MySQL). > > For example: > > I have a customer who is customer 2022. One of my tech support people > has to make a call to that client for business related reasons. So when > that tech person dials 1-212-555-1212, they have to dial in 2022 so that > it is notated that this call was to that particular client. Assuming > that is a valid account code, the LD call proceeds, if not, a message is > played for the tech person to the effect of something like, "That > account code is not valid" and notates that in the cdr as well. > > This is my view of how it would work, but if anyone has another way to > provide accountability that would work as well. > > Kim C. Callis > >