DISA and account codes

[Qzwsa]

Hi folks. Here's a request that has me scratching my head. System is a soon to be installed IPO 500v2 R8.1, PRI, VMpro

Customer has different projects scattered about the globe and wants to have the North American employees use a 1-800 number to access dial tone from the IPO to make overseas calls. This will allow them to make those calls for free from an end user stand point, and they don't want to limit it to a list of cell phone numbers. This must be accessible from any number; a vendor, a client, an employee cell or even home phone. Up to here I'm fine, no problems. VMpro answers, requests pin and destination number, executes transfer.

Issue number one is the requirement of different PINs for each employee. I could do this with a huge menu block with a load of DTMF options that only valid accounts can progress, or a variable routing block that checks the entry against that same huge list of PINs that again only allows valid accounts to progress. This is a pain in the butt to manage for the customer, but can be done.

Issue number two is the need to be able to pull information from the SMDR data being collected and be able to track each PIN used.

This seems to be a perfect use for account codes, but I'm having trouble getting the account code tagged to the call.

Here's what I've got:

Short code *98*N# // set account code // N ---> From my desk phone I can dial this code with account code 123456 be given dial tone and make my call, which is tracked as needed in SMDR.

My DID is answered by VMpro module DISA which prompts the user for an account code, copies $KEY into $CP10, requests the target phone number, reads back $CP10 and the new $KEY in a speak text block, and then.....

here's where my problem comes in....

transfers to *98*$CP10#,9$KEY at which point my call is disconnected.

I can program a dial button on my phone with *98*123456#,95555550123 and it works but if I program the same string directly into voicemail, ignoring the variables, it doesn't work. The use of the Source and Description fields in the transfer block only change the CLID name, and SMDR doesn't track the name, just the number. I've even tried to copy the account code into $CLI instead but the IPO won't let you (no error, just no joy).

Do any of you more savvy people have any suggestions? Has anyone set something like this up before?

Thanks for your time!

Qz
`

 

[Westi]

Give every employee a mailbox and make them log into it to access their DISA option by creating custom collect points for their mailbox. That way they need to know their mailbox password and they can set it themselves and 1234 is not an option force them to a 6 digit password and you are as secure as can be.

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.”

 

[Qzwsa]

Needing to log into a mailbox would work, but how would that track on the SMDR? Security is only one half of the question.

Qz

 

[Westi]

It can establish the call and ask then for the account code. Doesn't matter when they type in the code.


Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.”

 

[Westi]

I have never actually looked how something like that would show up in the SMDR but it might display the extension as source of the call.

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.”