MapD Help / Alternate method of CTI 2

[DJPlaZma]

We have a CM3.0, with S8710 in our Michigan location, S8500 ESS in Phoenix. We have MapD (TN801B) in Phoenix for a CTI application.

The MapD is developing problems:
1) Gave me a "no board" error in list conf all.
2) The board shows up now, but in disp err I get the following:

02A0701 ASAI-EPT 3329 11/29/09:27 11/29/12:08 23 8 4 a y
02A0702 ASAI-EPT 3329 11/29/09:27 11/29/12:08 23 8 4 a y
02A0703 ASAI-EPT 3329 11/29/09:27 11/29/12:08 23 8 4 a y
02A0704 ASAI-EPT 3329 11/29/09:27 11/29/12:08 23 8 4 a y
02A0704 ASAI-PT 1 11/29/09:27 11/29/12:08 23 8 5 a y
02A0703 ASAI-PT 1 11/29/09:27 11/29/12:08 23 8 5 a y
02A0702 ASAI-PT 1 11/29/09:27 11/29/12:08 23 8 5 a y
02A0701 ASAI-PT 1 11/29/09:27 11/29/12:08 23 8 5 a y


3) The board beeped for a while and the display is reading PCBIOS and won't do a successful restart.

I suspect the MapD is going bad.

I'm told that there are alternate ways of doing CTI that do not require the antiquated MapD. One way I've heard of is “Application Enablement Services".

My question, then, is two-fold.
1) Is my MapD dying? If not, does anyone have any steps to troubleshoot? Any assistance in getting a MapD troubleshooting manual would be nice as well.
2) Has anyone tried any alternate method of CTI, including “Application Enablement Services", and have any knowledge to share in this regard? Time to implement, procedure, cost, etc.

Thank You In Advance!
-DJ PlaZma-

 

[98Converter]

I believe the S8X00 series server has Co-Res DLG along with ASAI Link Core/Plus Capabilities features, which omit having the need for a seperate MapD board...

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[nohuhu]

DJPlaZma,

1. your map-d isn't dying, it's already dead. "pcbios" means that map-d tries to pass bios tests and fail for some reason. i suspect that its hard drive may be dead. the only (legal) method of repairing is through avaya for additional money.
2. the application enablement services is the new (and right) way to do cti in cm3. in fact, this is the same software that was running on your map-d board (dlg and cvlan), rewritten tsapi service (same as avaya ct or cvct), cmapi service, web-based phone control and a little bit more, all packaged into one linux-based server. the main features are: more than one switch links (up to 16, redundancy allowed and more of it, comes standard), encrypted (!) links between aes server and c-lans, one licensing point, increased capacity, comes either as hard&soft solution or as software-only package if a customer wants to use his own server. i have not tried to install one yet (however i sold three of 'em last month) but in a two or three weeks you can have my report on this if you want.

98Converter,

co-res dlg is not available on cm3, it was used only on cm2. also the need for asai core/plus licenses is unclear, there may be adjunct links used instead.

 

[lopes1211]

get out! co-res was only on CM2 then it was pulled? Now you need a seperate box again? DOH!

-CL

 

[nohuhu]

lopes1211,

yep, they did it again. co-res was a transitional solution between a hardware-based map-d to software-based aes. and you did need a separate box anyway, at least for anything other than plain dlg which was never used by anything but 3rd party protocol gateway software like intel ct connect. if you wanted cvlan (for ivr or aic) you needed cvlan r9 server -- a separate linux box; if you wanted cmapi (call recording) -- again separate linux box; tsapi? (cce, anything custom) -- windows box this time, but definitely separate. i commend avaya for pulling all this into one box, at least. with additional features and increased security. it's a good thing. and by the way, they have simplified licensing policy now (well, something like that) -- you don't have to buy asai core/plus ALL the time. tsapi-based cti links now got much cheaper and more affordable for small businesses.
...well, and who said the life will be easy?

 

[fb514012]

DJPlaZma,

to solve your problem with the MAP D you should check if there is any modem connected to one serial cable. I had very often the same problem that the MAP D could not start ( always beeping ) when a remote-modem was connected.
Unplug eveything except the console cable and try to reboot it again.

 

[DJPlaZma]

Thanks for all the responses, folks. While I was able to bring it back to life with a series of busy-outs, resets, and releases, I no longer trust it. Fortunately it isn't currently in production, as our screen-pop server is under development. You did, however, provide me with some great information. I'm now on a mission as far as the AES is concerned and after looking into it am trying to sell TPTB on it. With the anticipated growth we have on the horizon, it can only serve to be a major asset down the line. Dwalin, I would love to hear any feedback/experience you have when the ones you've sold are installed. I can use any knowledge you gain to justify a deeper look at it in the future.

THANKS!

 

[Cti4all]

DJ PlaZma,

Doubtful the MAPD is going bad, probably some series of events caused the old UNIXWARE to crash. Glad to hear resets got it back in service, but you could go years before something like that might happen again. Have seen hundreds of these old boards run for years without reboot, they are very reliable.

AES is the right solution for CM3. Co-Res DLG/CLAN was a CM2 alternative due to MAPD expected to go end of life before CM3/AES. Turns out the old MAPD hung around till after CM3 release.

AES is all of the CTI middleware rolled into a single server. It enables TSAPI (formerly Avaya CT on separate server), CVLAN (formerly on R9 server or MAPD), DLG (formerly Co-Res or on MAPD), and CM API (relatively new API for call recording and other IP Station type applications - homegrown or ISV). AES will be around for years to come, it is the future platform for all CTI and runs on Red Hat. Dependability is as good as the HW you deploy it on.

It is possible to deploy multiple AES servers (or MAPD) for your applications to interface to. Not all apps are designed to use failover as well as others, the idea is to try one server and then another if not reachable. AES4.0 in 07 will add some additional failover functionality to improve recovery options.

Avaya has sold and deployed nearly 400 AES servers since intro in June. Support issues are minimal, and the interface is really easy to work with. Plus, you have the option of installing on your own HW and Red Hat OS giving you even greater control of the entire solution if that is what you want, or can buy HW "turnkey" solution from AV to avoide the HW/OS headaches.