Weird Teleworker problem

[IN10CT]

I have been experiencing a strange problem with my Teleworker sets ever since we upgraded the Teleworker blade from version 4 to version 7.

Quite sporadically, my 5220 and 5215 IP phones will fail to connect to the Teleworker server. It only tends to effect 1 or 2 phones at any given time so the MAS6000 is working for the most part. When powering the phone up it obtains an IP address and then gets stuck with the message “booting”. It will not proceed to the downloading phase. After an indeterminate period of time the phone will suddenly succeed and work fine.

It is proving to be a very frustrating problem and I have been unable to determine a cause. Here is what I know:

• This started happening after our upgrade to Teleworker version 7
• All 5220 and 5215 sets are affected.
• The problem is sporadic and usually affects only 1 or 2 sets at a time.
• I see no packets being blocked by our firewall.
• All other network connectivity from the phone location works as normal. (web, VPN, Terminal Server, etc…)
• I do not see any meaningful errors in the MAS6000 logs (I may not know what to look for…)
• After repeated power resets of the phone it will eventually reconnect.
• I am not exceeding my Teleworker license count.
• I have noticed that the MAS6000 does a weekly reboot on Sunday night and I consistently have problems Monday morning.

Anyone out there run into this or have any suggestions?

 

[paterson]

I have also experienced similar issues with Teleworker.

The problem of sets not downloading the software is not usually a problem with the 6000MAS but with the set on the other end. I say that because, if the sets eventually get the software without doing any changes on the network or server, then the server is doing it's job. I'm pretty sure there is an internal timer in the boot sequence of the set where the set expects to "start" receiving the download files from the 6000MAS (or ICP). If this timer is exceeded, you will see the message on the set. If there is any kind of delay in the routing via the Internet, this would likely cause your problem. That would help explain the intermittant nature of the problem and why, after numerous attempts, it suddenly works. Now, I don't specifically have the details of the boot sequence and any timers that may be in there, this is purely my thoughts and experience talking.

I guess the work around is to reboot the set until it comes up.

**************************************
Insert Witty Signature Here.

 

[slapin]

If just one or two TW phones fail the most common problem on other side. Besides that it could be MTU problem. Try to set TFTP block size to 512K