Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Getting ANI and DNIS (or VDN) on Conversant IVR 1

Status
Not open for further replies.

FoneFun

IS-IT--Management
Sep 16, 2002
187
CA
I have a Conversant 8 on a Definity G3R
The conversant is connected to the G3R via 2 T1s.
I'm using Voice@Works or the New Avaya IVR designer.

I don't seem to be able to get the ANI or DNIS values. I place a test call using my station (from an outside line) and I know I have a displayed caller ID, but the IVR does not seem to get it. The same goes for DNIS.

I've researched it and read somewhere that I need ASAI enabled? Not sure how to check this. But I do have an ASAI MapD board and I also have CentreVu CT, but not sure how that's suppose to integrate to the IVR.

My last resort is to use the Converse-On vector step, but the problem is that at the end of the IVR session, I need to
a) transfer the call to a different VDN
b) pass along ther caller's customer ID so that the CTI app picks it up.

Anyone have any ideas on how to get ANI working without the converse on step?

Thank you!
 
Hi! I have a similar problem. Can you help us ?
What is Converse-On vector step?
thanks
Manuel
 
You should try CONVERSE ON as it is documented, but not using conv_data after prompt & collect. On that way I think you will just get ANI and DNIS, and not return back to the IVR.

Asai is the other option, and more convenient. I suggest uisng the asai.

GuzaPasha


 
I've got this to work using ASAI.
ANI works fine, but the only problem I have is DNIS.
In my incomming vector, I have 2 levels.

2000 is the first incomming VDN, which has a collect 1 digit line.
If digit = 1 route to 2001 cov y unconditional
If digit = 2 route to 2002 cov y unconditional

2001 and 2002 are the VDNs that queue the calls to the IVR skill.

The problem with the DNIS via ASAI is that it only gets the first DNIS 2000 and does not return 2001 or 2002.

This is somewhat like the Allow VDN Override feature for VOA and skills. (which in my case is set to Y, but still does not work for the ASAI)

This is on a Definity version 8.3.

I know that on a Multivantage v11, I have to set in the VDN page 2, VDN Override for ISDN trunk ASAI Messages to Y.
This parameter is similar to the Allow VDN Override parameter, but it's for CTI. If I set this to N, my CTI apps only get the first VDN. So, there in lies the problem. I could not find the correct parameter to set in version 8 so in the end, I resorted to using CONVERSE ON.

Converse-on is a vector command.
ie in your vector:
Converse-on skill 1st pri H passing VDN and ANI

This sends the call to the skill 1st, and outpulses (touch tones) the VDN#ANI.

Assuming you are using voice@work, in your IVR script, the first line after Answer should be a Prompt and Collect with no voice message.
The variable you collect should result in VDN#ANI. I do VDN first because it's always 4 digits. Use the parse string functions to extract from that the VDN and ANI and you are good to go.

Hope that answers your questions.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top