Teleworker Phone Waiting for COMMS 1

[chicory]

I am configuring a 5220 dual-mode IP phone as a Teleworker.

This is the first one I have tried. I have all the IP addresses set up. The phone did successfully register its PIN remotely through the Internet (Teleworker) connection, and its MAC address shows up in Ops Man on the correct extension.

The phone boots up and completes its main load. It then stops at this message:

Waiting for COMMS...
ICP xx.x.xxx.xxx

The IP address displayed for the ICP is correct.

What should I be looking for? What does "Waiting for COMMS" indicate?

The Teleworker blade seems to be version V3.0.10 on Mitel Networks 6000 MAS 6.0.

Thanks for any ideas or assistance!

- Charlie Savage

 

[slapin]

Was this phone working localy with ICP?
Ususally I see this message when programmed model doesn't match the actual phone. Let's say your phone is 5220 Dual but programmed model is 5220. Besides that you need to accociate each set with the correct ICP in the TW Server config or program default ICP.
You should take a look at the log of the TW server and maintenance section on the ICP to see is the phone trying to communicate with ICP

 

[chicory]

slapin,

Thanks very much.

This phone was working locally before on the same ICP.

The desk set is a 5220 dual mode and that is what is set in Ops Man for the extension.

The set (MAC address) is associated with the intended ICP in "Configure Teleworker Solution".

I have looked at the log on the Teleworker, the one called "messages". It is all pretty much Greek to me, but I do not find any reference to either the IP address or MAC address of the 5220 IP phone, or any explicit message about some process failing or not connecting. But I may well be missing something here. There are also apparently many logs, and I may not be looking at the right one.

On the ICP, I DO see this message related to the IP address of the phone...

Log Type: Software
Log Number: 474
Severity: Warning
Date: 2007/Mar/13
Time: 20:08:53
Source: IPSP
Description: ReadDeviceMsg: Device with Endpoint=[ 151 ], DN=[ ], IP=[ 206.114.xxx.xx ], MAC=[ 0x8-0x0-0xF-0x16-0xD4-0xA7 ] had an unexpected error! Error=[ ETIMEDOUT ].
Module: IPSP
File Name and Line Number: SockHandler.cpp;1051

Do you make anyhthing of that?

- Charlie

 

[slapin]

Most likely you have got wrong firmware image on the TW server. Copy one which is sitting on the ICP to TW server so the phone will download it over TFTP

 

[chicory]

slapin,

You lost me on that one. I have no idea how to access either the 6000 MAS or the 3300 ICP at the file level. I have looked all over the web interfaces, documentation and help files, but have not found anything yet.

Can you give me a brief rundown on how one would copy the main load file(s) from the ICP to the Teleworker?

- Charlie

 

[paterson]

You should have both your Teleworker software and ICP software upgraded to the latest versions. I am confident it will solve your problem.

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

 

[slapin]

The standard way is to keep compatible versions of the software for all the components of your network. Ask your dealer for software checklist. Besides that TW server has ssh shell accessible with username "root" and your TW admin password. You have to understand what are you doing before you modify anything, because if you screw it up Mitel will not support you.

 

[chicory]

slapin,

Thanks tremendously for walking me through all this. Although I do not have the teleworker phone operative yet, at least I have greatly increased my understanding of the situation. At this point I will need a dealer to assist. That is always a hard sell to my management, but the situation is what it is. Thanks again for your readiness to assist.

- Charlie