conversant *DNIS_SVC 1

[FoneFun]

I have a Conversant IVR ver 8 connected to a Definity G3R and I'm using Voice@works.
I can assign channels to my applications and it answers fine.
How do you get calls to the conversant and have the conversant respond based on the DNIS?

I've already assinged *DNIS_SVC to all the channels and on the Conversant, I've assigned the DNIS to my application.

From what I can tell, the switch is sending the calls over but not the correct DNIS.

 

[RTMCKEE]

I had very limited experience on a conversant a few years back. I dont remember having the DNIS_SVC you spoke about, what I recall we had a single script assigned to all the channels, that script then pointed to all the other scripts based on ANI DNIS VDN etc.

I dont remember what the script looked like exactly, but it was something real simple that said basically if incomming digits = X play script Y.

X is the ani DNIS vdn etc.
y is the exiting scripts you already have built.

Sorry not more help, but maybe someone can fill in the gaps. I dont remember what version of Conversant we were running, but I know we didnt have voice@works.

 

[BIS]

Your vector needs a step
"converse-on skill xxx passing VDN and none"
where skill xxx is the skill assigned to your channels.
You voice@work app needs a 'Load Variables' (or a 'Prompt and Collect') node collecting the DNIS.
Let me know if you need more help.

 

[kpprao]

Create a small application to read DNIS passed by switch using "prompt and collect". Ceate a table with DNIS and "application name" mapping.

Use Execute "External Action" to execute different application depending upon the DNIS.

Let me know if u need more info. We are using the above method.

BIS, when the switch uses converse-on command to pass DNIS, while transferring the call, the app. need to dial a 4-digit code before the outbound VDN. My switch guys are unable to explain why we need to dial a 4-digit code before the outbound VDN.

Could u please help me understanding this.

Thanks in advance,

 

[BIS]

Are you saying that the app sends data back to the VDN, where it is collected and then routed? Is this the FAC (Converse Data Return Code) ?

 

[kpprao]

Yes. It's a 4-digit "Converse Data Return Code".

Is it possible to get DNIS from the switch without using converse-on command?

IVR is taking less than 1 sec when the switch is not sending DNIS.

Thanks,

 

[FoneFun]

Hello folks. I'm back on this topic again.
Is there any way to get ANI and DNIS without a converse-on?

 

[GuzaPasha]

There is a function on conversant called A_Callinfo(SB function, but probably you have the same at Voice@work), that will hold ANI, DNIS that gets from the ASAI link.... You should use ASAI package on Conversant and have an ASAI link to the Definity, to get all this works. I had a task to do the same thing with my V7.0, but for now it is postponed, so don;t know the details about it. Just follow this information and hope you will get all you need, and hope some other will help much more.

To all others, has anyone used asai links and the function I've mention, recently. I will work on this problem in the near future, and need some information about asai link between Conversant v7.0 and MAPD (DLG not CVLAN), has anyone used this configuration through a Telephony Server?

some tips will be helpful

GuzaPasha

 

[FoneFun]

Thanks for the response GuzaPasha.
I've found the ASAI Package CD for the Conversant and installed it yesterday. I still have to configure it so I'll let you know how it goes.

 

[GuzaPasha]

Let me know about the configuration, maybe we can assist each other in solving this all.
GuzaPasha

 

[FoneFun]

ok this is what I got so far.
I've installed the ASAI Package, CVLAN client and UCID packages that are all on the same CD.

1 asai INTUITY Adjunct/Switch Application Interface Package
(i486) V8.0
2 cvlanxcl LUCENT TECHNOLOGIES CALLVISOR PC CVLAN CLIENT (UNIX SV x86)
(i386) 6.1.4
3 ucid INTUITY Universal Call ID
(i486) V8.0-1

I gave the ASAI software the IP for the MAPD and set it for "signal01"

I've connected to my MAPD and configured the following:

1.
In TCP/IP Admin - Local Host Table, i put in the IP for my conversant and the hostname "conversant". I don't think this is required but put it anyway.

2. in Port Admin - Application Port Assignment, I set port 02 to CVLAN

3. in Port Admin - CV/LAN Admin, I assigned "signal01" to port 02, turned hearbeat on. I also assigned it a client, using the IP of the conversant.

Thats it, I'm stuck now.
In the MAPD, when I go to 6. CV/LAN Port Status/Control I see:

DEFINITY Number of CV/LAN Messages Messages Message
Node Port Client Service to from Period
Port ID State Connections State DEFINITY DEFINITY (minutes)

2 01 NOT CONNECTED 0 in service 0 0 30

When I go to Maintenance-CV/LAN Utilities - ASAI Test I get the following:

Unexpected capability = C_ABORT for ASAI node signal01 received.
The capability expected was C_HB_CONF
Primitive type response for ASAI node signal01 != C_POS_ACK
Primitive type response received = C_REQUEST
Heartbeat test with switch for ASAI node signal01 failed.


On the conversant I still get in my message logs:
C Tue Mar 30 10:53:29 2004 DIP7
ASAI001 -- -- --- ASAI link failure detected. Reason: ASAI Physical Link Down.

So no luck. The only thing I can tell you is if you don't have the CV/LAN installed on your conversant, it causes the conversant to crash after a while. Found that out the hard way, so when you install it, just use the install all feature.

Anyone have any other suggestions or can help?

 

[GuzaPasha]

Hi FoneFun,

I am not familiar with the MAPD-CVLAN, but you should add extension to the Definity type ASAI with the port number of the MAPD, check the documentation, we need this for DLG ports, chekc to see if you need for CVLAN. On that way you will have connection to the Definity...
on the deifnity chekc status station xxx(ASAI i've mentioned)
Try asai_stat on conversant to check the link.
get responses ...

inform me I will try to help as much as I can, I am also interested in this all

Hope this helps
Gu

 

[FoneFun]

Hey GuzaPasha!
You are correct! I created the ASAI station.
My CTI server is on 02a1501, so I created it on 02a1502.

Now in the MAPD, when I go to Maintenance-CV/LAN Utilities - ASAI Test I get the following:

Heartbeat with switch for ASAI node signal01 was successful.

Thats an improvement! Unfortunately, the conversant message log still tells me the same problem.
*C Tue Mar 30 23:34:03 2004 DIP7
ASAI001 -- -- --- ASAI link failure detected. Reason: ASAI Physical
Link Down.

I've gone and found the docs that I could and read them.

http://support.avaya.com/japple/css...electedRelease=129162&temp.selectedBucket=all

CONVERSANT® V8.0 Communication Development 585-313-220 tells of how to connect the ASAI, but not detailed enough.

CONVERSANT® System Version 8.0 Administration 585-313-510 tells me that I need to add an ACD domain.

I think I understand how its suppose to work. I'm suppose to create a single hunt group for the IVR and queue callers to this skill. I create a bunch of IVR agents with this skill and have the IVR log them in. My only problem seems to be when I do any ASAI Administration with channels or domains, I get a foos. The doc says:
foos (facility out-of-service) — The ASAI digital link is not operating.

Great, I know that, but have no idea what I'm missing to fix it.

I've been through the other docs and didn't find much else of use. Arg, I can't sleep knowing I'm so close....

I must be missing one itty bitty thing.
Do you think I should de-install the Conversant ASAI software? I read in one of the older Conversant 5.0 docs (yeah that desperate that I read the docs for v4,5,8 and 9) that I needed to install the CVLAN drivers first, then the ASAI. I didn't do it in that order. I might try that tomorrow.

Any other ideas?

 

[GuzaPasha]

FoneFun,

don't think about the ASAI administration related to hunt groups and other things,for now. they are not part of the link.

Now, you do have connection between Definity and MAPD, and you need from the MAPD to the IVR.

did you try /var/lib/asai_stat?

send responses

you should find some information about dip7, I don't have it, that dip is responsible for connection.

I will try to find out anout the errors you get

Hope you will solve it soon

GuzaPasha

 

[GuzaPasha]

Sorry, try /vs/bin/asai_stat?
Here are some useful commands

link_offline 01 # To take link offline

link_change -l 01 -i xxx.xxx.xxx.xxx #xxx... MAPD IP address

link_restart 01 # To restart the link
link_status #To View the status


Send responses back
GuzaPasha

 

[FoneFun]

GuzaPasha,
I've tried to find asai_stat and those link_ commands but they do not seem to exist on my box!

I've searched the whole drive.

 

[GuzaPasha]

I have it on my V7, ok will explore a bit more for v8.

 

[FoneFun]

IT ALL WORKS!
1. Deinstalled the ASAI package
2. Reboot
3. Reinstalled the CVLAN package
4. Reinstall the ASAI package
5. Reboot


As far as those test commands, in version 8 I could only find these:

/usr/adm/cvlan/bin

usage: asai_test [-m hostname/IP adress] node_id
where node_id = 1,2,3,..,8
I used this to find if it's connected. I got a heartbeat response back.

After it all came back up, the ASAI link down was no longer appearing in the message log.

No you have to create a hunt group.
In the document CONVERSANT System Version 8.0 Communication Development 585-313-220, page 53 tells you to make an ACD Domain. I did not do this. I could not get it to work (I have EAS) so I just created a normal hunt group:

Group Number: 94 ACD? y
Group Name: IVR test Queue? n
Group Extension: 1094 Vector? y
Group Type: ucd-mia
TN: 1
COR: 52 MM Early Answer? n

AAS? n


Then I created 48 agents with this skill. (I have 48 channels)
A VDN (external DID) and a vector that queued to this skill.

On the conversant, from the main menu:
Feature Packages
- ASAI Administration
> Channel Administration

Added each channel with each agent I created.
Then login each channel/agent.

CHANNEL EXTENSION SPLIT/AGT PASSWORD LOGIN STATUS
0 2000 3000 - YES LOGIN
1 2001 3001 - YES LOGIN
etc..


Then, from the main menu:
Feature Packages
- ASAI Administration
>Domain Administration

I added my VDN. Saved it, and enabled it.
NAME TYPE EXT SERVICE STATUS
Test VDN 5555 VIS inserv

Now from the main menu:
Configuration Management
- Voice Equipment
- Voice Services
- Channel Services
- Assign Service

Channel numbers: 0-47
Service Name: *DNIS_SVC
Startup Service: <leave blank>

Save that.
If you did a display Services you would see:
CHANNEL SERVICE STARTUP SERVICE

0 *DNIS_SVC -
1 *DNIS_SVC -
2 *DNIS_SVC -
3 *DNIS_SVC -
4 *DNIS_SVC -


Go back 1 menu. Select Number Services.
Assign Number Service
Called Number: 5555 (your VDN here) to <blank>
Calling Number: any to <blank>
Service Name: MyNewIVRScript (replace with your new script)

save that.

That should be it!
Thanks a lot for your help GuzaPasha. Your hints were invaluable! Let me know how you make out with the *DNIS_SVC.

In my next escapade, I will tie this to CTI. Wish me luck, I'm sure I'll need it!

 

[GuzaPasha]

Congratulations,

you are welcome.

ASAI on my V7 is working now, as well!!! At the moment I don't have a time to test it all, cos I will be out of the office for 2 weeks, and will come back and inform you.

I suggest you and all others to open the Avaya Conversant forum, ...

Wish you luck
GuzaPasha

 

[FoneFun]

Hey GuzaPasha,

Take a look at this new thread I started.
thread690-815563

Let me know if you've ever heard about that migration from Conversant x to Avaya IR. I'm not too happy with Conversant 8 right now, it seems to be a tad unstable when we do too much data transfer.