Checking if AVAYALink is sending TAPI start/stop to AMETHYST

[Belinda Frick]

AVAYALink runs as an application under Windows. Please check that it is running and shows connected to the PABX.

AVAYLink will send the start and stop messages to AMETHYST for recordings.

AvayaLink.log:

Code: Select all

2011-10-18 16:52:45.062 [1.0.10.0] -> CALL:S 0.23339.0,0.23340.0,0,2,0,0,1,0,JohannesS(5619),Line 2,,8.30,1.55,100.100,0861114351,100.101,5619,,,100,00861114351,100,,0,16,0,0,0.0,,,,,,,0,317019,0,0,311580,3301,ens,,0,,0,0,0,0,,5773,,,,,,,,,,,,,,,,0,0,JohannesS,0,,3,0,0,0,0,0,0,1,618,100
2011-10-18 16:52:45.109 [1.0.10.0] -> CALL:D 0.23339.0,0.23340.0,5773,,,,,,,,,,,,,,,,0,0,JohannesS,0,,3,0,0,0,0,0,0,1,618,100

To check if configuration is correct see AMETHYST and the AVAYALink:
AMETHYST and the AVAYALink


Set AMETHYST to enable Verbose logging.
AMETHYST Webadmin -> "Verbose Logging", tick "Enable" and then "Apply".

Make a test call.

Check the AMETHYST server logs for the START and STOP messages.

START message:

Code: Select all

[2008-06-18 10:59:30] Version [1.5.13.0]DEBUG: TAPI|START|5583|10384|


This is the log entry that AMETHYST received from TAPI as the START message for extension 5583.



Code: Select all

[2008-06-18 10:59:30] Version [1.5.13.0]DEBUG: TAPI start sent to :192.16840.12 Extension = 5583


This is the log entry that AMETHYST sent a START message for the USBClient of extension 5583 on IP 192.168.40.12.