Why is AMETHYST not sending/delays sending my TAPI messages

[John Richard Procter]

My USBClient does not start and stop recording when I am on a call.
When I check the logs I can see that AMTTAPILink and AMETHYST is
sending and receiving the TAPI messages, but still the USBClient
is not functioning correct.

Example of log entries:

1. [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 AMTTAPILink the START
   message for extension 5583.
2. [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.

The TAPI messages is sent from the AMETHYST server via UDP to port 27002
on the USBClient PC. If this is received in real-time USBClient will work
as it should.

In this case the mailserver was having problems in sending admin e-mails.
Amethyst is sending e-mail from the same thread that handles UDP to
USBClient. The e-mails timed out which caused a delay in sending the
TAPI messages.

Example of log entry:
[2008-06-20 08:56:04] Version [1.5.13.0]Error [Socket Error # 110
Connection timed out.] In UDPListenUDPRead: Sending e-mail

Once the mail server problem is sorted out, the TAPI messages
will be sent in real-time and USBClient will stop and start correct.

Conclusion:

This is a non-critical bug, it will be addressed in a future release of
AMETHYST. If your SMTP mail server is sending the e-mails received from
AMETHYST without any errors this problem should not occur.