USBClient recordings does not ftp to AMETHYST

[Belinda Frick]

Problem:

My zlb files does not ftp to AMETHYST using the scheduled/automated ftp. I get a socket error in the USBClient log.

When I do a manual ftp it works.

Solution:

Please check the following:

• Windows Socket error :
  
  
  Do a search in Windows to find out what the error is:
  How do I search for a Windows socket error?
  
  Use the error message to see why the ftp fails. This is most likely network/access related.
  
  
• Confirm the AMETHYST IP:
  
  
  • Ensure that your USBClient/Remote AMETHYST uses the exact same details as the Manual FTP.
    
  • Make sure you can ping an host name if it is used in the INI files. Rather use IP addresses where possible.
  
  Check in the USBClient.ini that the AMETHYST server IP is used. It has been noted that the server was configure as 'GEM' where the name is in fact 'AMETHYST'. Use the IP address to avoid problems like this.
  
  

  Code: Select all

  [SERVER]
SERVERIP=192.168.15.6
SERVERPORT=27000
FTPSERVERIP=192.168.15.6

  
  NOTE: If you use host names rather than IPs, make sure you can ping them from the server running this software and that the DNS is available during the scheduled FTP time.
  
  
• Ports needed for USBClient:
  
  
  Ports needed with USBClient
• FTP Schedule:
  
  Ensure that ftp is scheduled as per requirements (live or for a period).
  
  
  • FTP schedule for USBClient:
    USBClient and scheduled ftp
    
  • FTP schedule for Remote AMETHYST:
    How do I schedule ftp for my Remote AMETHYST?
  
  
• Manual FTP:
  
  To test if the ftp works, you can try the manual ftp.
  
  
  • Manual ftp from USBClient PC:
    How do I do a manual ftp from the USBClient PC?
    
  • Manual ftp from Remote AMETHYST server:
    I have no calls in Supervisor for my remote site