Eicon Isdn Implentation Summary

[ktruk]

This post is for info only, and is intended for anybody already using or hoping to use Eicon ISDN cards.

 

Over the last few weeks, I have been evaluating Eicon Diva Server ISDN hardware and software and thought the following "definitive" statement may help avoid the issues I have experienced.

 

Firstly, there are two streams of hardware cards, early v1 cards and recent/current v2 cards. Despite claims stating that v2 cards "have had basic tests done" and will work with Voice Guide, the Eicon TAPI driver is "suspect/broken" in all 3 current releases of system software, as follows:

 

Eicon v6.30: Legacy v1 card support software - no wave-driver sound file playback.

Eicon v7.70: Current v2 card support software - playback ok but recording broken - 1st attempt to record a wave-file, causes line-hangup, 2nd attempt causes VG system crash, on any single line.

Eicon v8.00: New v2 card drivers (as of Jan 2006) - playback ok but recording broken - 1st attempt to record a file, causes line hangup, 2nd and all subsequent attempts work as expected, on any single line.

 

NB: You can install a v7.70 wave-driver on a v6.30 system installation to get wave-file playback on a V1 card.

 

Other points to note: v6.30 has no uninstall routine and attempts to install v7.70 or v8.00 over a v6.30 installation will cause system crashes and line-transfer problems. Also, attempts to simulate 2-line ECT interconnect have been unsuccessful, but this may be due to the fact you cannot force the card to do interconnect, if your network/PABX connection already supports ECT (Explicit Call Transfer).

 

"Blind Line Transfer" is only possible in Voice Guide v5.2.5015 or higher, when the PBX transfer options are set to TAPI only, and only if the line being called is available, otherwise Voice Guide restarts the current script. Only this mode of call transfer is supported. (Line Generate / Flash hook will not work on BRI lines).

 

The test above were undertaken with both v1 and v2 cards, using only the Eicon TAPI driver component.

 

Problems with Eicons TAPI driver can be overcome with ComISDN (see http://www.comisdn.com) by running th Eicon card in a CAPI mode. Versions up to and including v2.0.44 fail to hunt through the available lines properley, causing quiet answering. But wave-file playback / recording / DTMF / Call transfer does work.

 

ComISDN have just (or are about to) released an updated version 3.0.45 which fixes the line-hunting issue. In addition, it can simulate ECT by 2-line interconnect, which may help resolve call-transfer issues. I have run this extensively over several days and it has proved reliable and stable.

 

I have made Eicon aware of these issues and will add any further updates to this posting if/when they become available. I hope the above is helpful. If you are already using or are considering using Eicon hardware/software, it may be helpful to add your thoughts/experiences below. Many thanks.

[ktruk]

UPDATE TO ABOVE: ComISDN have released v3.0.46 of their CAPI/TAPI TSP and this fixes the line-hunting issues previously mentioned. In addition, this version can simulate line bridging on 'blind-transfer' ECT so that if the telephony card supports it in hardware (like the Diva Server cards) then 2 lines can be bridged/tromboned by default when an ECT is requested. At the moment, code to use any available free-channel has to be specially enabled (contact ComISDN for details if required) but it does work.

 

In addition, you should note that ComISDN/CAPI only works with 8KHz 16bit wav/pcm files so that all prompts will need to be in this format. This gives good clarity and quality prompts.

 

Currently, native Eicon TAPI system/wave drivers for v2 cards (v7.70 and v8.00 releases) only partially work with VG directly. The wave driver will hangup the first call to any line after starting VG, but after this hangup, all subsequent wav playbacks will play okay and recording will not work at all. I believe Eicon are working on fixes for these issues, but no immediate solution available. ComISDN fixes both of these issues now, but at the cost of additional line licenses.

 

VoiceGuide have fixed some issues whereby if a blind-transfer fails either due to a free-line being unavailable, or attempted transfer to a busy line, then VG can retrieve the call for further processing. You will need v5.2.5042 (or higher?)

 

By arrangement, ComISDN licenses can be issued to the same network MAC address that VG uses (if you use this format) but note that ComISDN uses the full MAC address, while VG uses only a part of it. You cannot use any other hardware key with either Eicon hardware or ComISDN.

 

Just an "FYI".