Datatex Dynamics

In the Cardserver INI file, under [OPTIONS], there is a PHONEDISPLAY= entry. This can contain the following values, depending on which PABX and phones are connected: 0 - None 1 - Alcatel 4200 / 4400 2 - Samsung 7200 / 7400 3 - Intertel 4 - Ericsson BP250 5 - Siemens HiPath 3750 / 3800 6 - Ericsson M...

This post is for a problem with the Amethyst Avaya Proactive Contact integration, but may apply to any CORBA client on Ubuntu. The integration in Amethyst connects via CORBA (JacORB) to the Avaya Proactive Contact server (the dialer). On Ubuntu, the entry for the host machine is 127.0.1.1. This caus...

It is now possible to integrate an Amethyst call recording solution with the Avaya dialer. Amethyst will record calls taken by agents exactly as if the call had taken place on its own (instead of as part of a long call between the dialer and the PABX. Call details include the Avaya agent code as the...

⋅ Avaya Dialer integration via external call control (an external application controlling the CRE recordings). ⋅ Fixed major bug where the CRE would almost always be killed off if it tried to process a 2 GB PCM file. ⋅ Fixed bug where CRE would not create a recording i...

• When running as a remote server, the physical device list is now built in shared memory - this is required for USB clients at remote sites.

Previous versions of the Remote Server 1.6.3 did not work in these situations.

⋅ Added zero voltage timeout for analogue lines. This allows the user to configure the duration of zero voltage before the cardserver decides a channel is faulty. Default is 30 seconds, maximum is 5 minutes. This is configurable per channel in a new section named VOLTAGETIMEOUT - the entr...

⋅ Split into VoIPRecorder and VoIPSweeper, to separate the recording and processing code, due to difficulties resolving low memory situations which could adversely affect recording. The problem is memory fragmentation when processing long recordings, and threads being created during that ...