Amethyst 1.5 cardserver released. Version : 1.0.7.1

[Belinda Frick]

For trunk-side recording solutions where the trunk / extension mapping is being done via CTI (e.g. TAPI) for each call,
the extension for each user is now saved on the Amethyst server, and not the card server.

When upgrading to this version, users handled by CTI will be left in the amtcards.ini file under "OLD_CTIDEVICES".
Please ensure that you copy and paste this section of the INI file into the Amethyst CTI devices configuration or
you will lose extension /user details on calls.

Check your amtcards.ini file after upgrading and if it has any entries under OLD_CTIDEVICES, paste them into Amethyst.

Also see: http://www.datatex.co.za/support/showss ... 0228095304

Feel free to contact Datatex Support if you have any problems or queries.
Completed Tickets
BUG Tickets
Subject : [#572]Amethyst : Broadcast breaks when 2 network cards are used on the server

Motivation
***********
When a Amethyst server is installed with 2 network cards,
the incorrect ip address is used for the broadcast reply.

Completion
***********
Fixed in AMTCards 1.0.7.1

Amethyst is sending its primary IP address when replying to a broadcast.
Card servers connected to the second network card cannot communicate with the Amethyst server.

You can now specify the Amethyst IP address to be used to communicate with Amethyst.
This feature can also be used if Amethyst is on a seperate network accessible only through a gateway.

In the amtcards.ini file
[OPTIONS]
SERVER=172.24.0.1
BROADCAST=0