Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Teleworker unable to contact server TFTP: Main

Status
Not open for further replies.

GZgidnick

Technical User
Jan 8, 2015
156
AU
Hi Guys,

I'm putting in place TW Server.
My ICP is 3300 vMCD OVA version 6.0.3.7
My TW Server is:
Mitel Standard Linux 10.1.24.0
MiVoice Border Gateway 8.1.13.0

When connecting TW phone, the phones are going through the LLDP/DHCP discovery process, get to the TW Server, and fail with TFTP: Main / Contacting Server

Now accourding to the documentation vMBG passes the requests to the vMCD.
the vMCD has the boot files in the /syspro/tftp directory
the vMBG also has the boot files in /var/mitel-phoneloads/tftp/

Tested with two phones, 5360 and 5320 to no avail.

Any tips welcome!
 
It has been my experience that the MBG provides the TFTP files
If you have 5330's that have never connected to a mcd directly there is a known issue

**********************************************
What's most important is that you realise ... There is no spoon.
 
Nope the phones I've tested with are:
5360IP - prreviously successfully connected to vMCD
5320eIP - brand new.

Now I am transferring the files from the vMCD tftp dir to the vMBG-TW tftp dir.
Will let you know of the results.
 
Moved the MAIN files from the vMCD to the vMBG.
Now when I connect through I get MAIN Incompatible. Phone lockes itself. On display reads "Contact TW Admin".

Apparently something to do with the boot files, which sounds a bit strange from a brand new system.
Copying the files from another vMBG now and testing with them, stay tuned.
 
Okay.... update:
Got the 5360 to "Waiting for COMMS..."
Got the 5320 to "Connection Refused Contact TW Admin" Incompatible MAIN

I don't know if it is time to call Mitel
 
Okay..... this is how I fixed it.
Cleaned all MAC off the system through the Users and Services Form.
Deleted all MiNET devices from the vMBG
Deleted the ICP
Restarted the vMBG
Restarted the vMCD
Added back the ICP
Reconfigured the MAC addresses for the devices
Added the MiNET devices

Booted the phones, added the TW Gateway, Provided the Installer password and bang!
Note: the 5320e still briefly reads "Incompatible MAIN" but eventually boots and works.

I still dont have any dialplan programmed to test properly but there is dial tone and the applications are being loaded on the phones.
 
The new firmare of the phone cannot be downgrade.

From Mitel
New 5330 and 5340 E series sets that shipped from manufacturing will contain Main firmware 6.2.0.1

This new version of Main Load will not downgrade to the 5.2.0.14 that the 200 ICP would normally transfer to the set via TFTP.

This does not call an issue, the set will still function as normal.

Note: All sites running E-series sets must be at 5.0.2.12.
 
It is important to keep your MBG upgraded. The Teleworker phone gets its TFTP load from the MBG, not the MCD. Sometimes, if the MCD has a newer IP phone firmware and a MCD connected phone is moved to a Teleworker location it may have problems downgrading to an older firmware on the MBG.
 
How do we verify the firmware version out of the firmware files that are loaded in the tftp directory?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top