Endpoints paired with cloud unable to get the upgrade – Error “Download fails due to time-out on busy server”

Document created by pbathini on Dec 9, 2015Last modified by michaelt on Dec 10, 2015
Version 2Show Document
  • View in full screen mode

If the End points failed to get the upgrades from the cloud server with an error “Download fails due to time-out on busy server.” Some things to consider:

 

  1. Reboot the End point so that it pools to the master server and tries to pull the upgrade by detecting it automatically. The firmware will only be pushed in the Non-business hours, hence not to worry about the timelines.
  2. Factory Reset the CODEC once to eliminate space issues, most of the time core dumps eat up all the space available.
  3. If neither of the above works, then it is most likely because of the End point IP blocked at the firewall/Proxy. By white listing the IP the upgrade would be successful.  If the sys.logs are taken, a look in the log would clear indicate the blockage as below:

 

  • 2015-12-09 10:16:41.756359 LifeSize-0A:37:92 SignalingServer: {COMM:HttpClient.c:1000:ERR}-1:css_srv_request Interrupted
  • 2015-12-09 10:16:41.756472 LifeSize-0A:37:92 SignalingServer: {SIPA:SipAppRegFns.c:169:ERR}-1:SipAppRegister:type=Clearsea Failed to create RegClient
  • 2015-12-09 10:16:41.756514 LifeSize-0A:37:92 SignalingServer: {SIPA:SipAppMcuComm.cpp:1125:I}-1:McuIfcRegisterResponse:type=Clearsea status=FAILED

 

 

2015-12-09 10:17:56.571016 LifeSize-0A:37:92 teetar[2344]: name: <html> <head> ^I<title>Fireware XTM User Authentication</title> <noscript> The Fireware XTM User Authentication web page requires that JavaScript be enabled in your Web Browser. Please retry after enabling JavaScript in your browser. You can use the browser's Back button to return to the page you were previously viewing. </noscript> </head> <body> ^I<script> var newloc = "/wgcgi.cgi?action=fw_logon&fw_logon_type=status"; var search = wi

2015-12-09 10:17:56.571106 LifeSize-0A:37:92 teetar[2344]: size: eb page requires that JavaScript

be enabled in your Web Browser. Please retry after enabling JavaScript in your browser. You can use the browser's Back button to return to the page you were previously viewing. </noscript> </head> <body> ^I<script> var newloc = "/wgcgi.cgi?action=fw_logon&fw_logon_type=status"; var search = wi(0)

 

 

I have attached a sample sys.log file for reference.

Outcomes