IC602 MAP-D Error

[mclellan]

Hello,

We have recently upgraded to the Avaya Interaction Center 602,
unfortunately during our production testing, we are running into MAP-
D problems.

Has anyone encountered this type of error before?


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.

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


Thanks
Barry

 

[Cti4all]

Barry

Heartbeat failure probably means either network issues between MAPD and application, or the client is not running to respond to requests. Try an asai test from the client

C:\Program Files\Avaya\CT\CVLAN\utils\asai_test -m <mapd card> <signal #>

Where Mapdcard is the IP address, and signal # is the signal that box is administered to use on the MAPD. If this returns ok, you should be good to go. If it fails, check ping between hosts, and make sure routers are not blocking ports.

 

[mclellan]

Thanks!

I checked it out, but I get the same error returned, Avaya has now decided to replace our MAP-D. The week after our change freeze started <sigh>.


Thanks
Barry

 

[NotBear]

Hello,

Have you discovered a solution ? We have similar errors in the log files, and replacing the MAPD card gave no improvement.

Regards

 

[mclellan]

Hello,

We replaced our MAP-D card only to have it completly fail after about 18 hours. We are now on our third card, and we are about to set the Enable IC flag on it tonight.

So far the new card has been running our old Quintus application without crashing, but we will wait an see what happens when we run IC on it as well.

I will keep you posted after this install.

Barry

 

[mclellan]

Hi NotBear,

Are you using IC? What version?


Barry

 

[definityman]

Be sure that on the signal on the map-d you're using for ic602, the feature ic enable is on.

I suppose you're running cvlan 8.0.1 at least on your map-d.
When Avaya installs the cvlan , usually , only the 1st signal on cvlan ports is IC enable.

Let me know if i can help you further.

Rgds

 

[Cti4all]

Avaya can set any CVLAN link to EnableIC. However, when this is done, only 1 concurrrent application can use the signal.

Older versions of IC (Quintus) used ASAI stations/links in the PBX. IC6 uses ADJLK stations/links.

Make sure the new ADJLK link is built in the pbx, the signal is configured for your IC client box, and you are running V8 MAPD and using CVLAN 8.2.5 client. Also, ensure you can ping the client.

 

[mclellan]

Thanks for your help!

After 3 MAP-D cards and two Avaya technicians, we finally foudn the problem! We had VDN's in the device tab that were used to perform the adjunct link.

We would have a call come in on these VDN's (obviously) and it threw the whole system for a loop!

Now that we have removed this, everything is working correctly.

Thankfully we haven't rolled into production while we are still finding these weird errors!

Barry