Dim Screen on Teleworker 1

[BillB66]

I have a 5330 Configured as a teleworker handset
Its screen is very Dark and there is no option for adjusting brightness? Entering the Debug menu , tools and features and view version info shows

- Main load version 1.02.00.27
- Boot load Version 1.02.00.27
- L2Boot Load Version 1.03.00.23
- DSP Load Version 2.0.0.5

Superkey about 5330 shows
Release 1.2
Load 1.02.00.27
Hardware REv E.05
ICP Rev 9.0.0.41

If I return it to where the CXi is installed it fires up as normal and the screen is bright and hitting superkey brings up a menu with the brightness option displayed.

I suspect when it is booting up it is missing some firmware
files ?

 

[tlpeter]

Does it work when you just press the up or down arrow on the phone ?


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[IrwinMFletcher]

Maybe I'm wrong, but something makes me think that the teleworker gateway has it's own version of binaries for the sets. Do they show the same version numbers in both cases?

 

[BillB66]

The up down arrows have no effect.
My feelings are that its note getting its firmware files properly as the brightness control is missing from the settings menu structure.

My teleworker Gateway is an APC Card inside a Cxi controller.
Would this still apply .

 

[slapin]

Yes. TW gateway has its own set of bin files on its own tftp server. I have replaced those files from ICP on few occasions without any visible problems.

 

[BillB66]

Ok so next Question is how do I get the files onto the APC - FTP?

 

[slapin]

Enable remote access using web interface, then login on the console using any ssh client. Use username root and your tw server password. Then using tftp client application you can download .bin files from icp to the local file system. Backup existing tftp folder content and then replace files with those you downloaded from ICP.

File are located in /var/mitel-phoneloads/tftp

 

[BillB66]

Excellent , thanks again.
I used filezilla as a SFTP client to get the files back onto the APC after getting them off of the Mitel Controller.

I reset my teleworker phone and the screen says CL bin Unavailable continuing bootup and still has a dim screen ?

Is there any documentation that details which particular bin files are for which model of phone ?

I only updated the ones that had 5340 in the name
Also how do the bin files get onto the APC to start with ?
If Controller is upgraded will these be upgraded automatically or do I have to do full download and upload everytime Mitel is upgraded ?

 

[tlpeter]

First of all slapin told you to use a tftp client
You used a sftp client

ftp and tftp are not the same

Second you only updated a 5340 file wich is not the same as 5330, are you sure there was not a 5330 bin file ?

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[BillB66]

Yeah I know ,I thought that may be more appropriate since i accessed the apc via ssh and at that stage I didnt think i had a tftp client on my laptop.

It seems to have copied the files over ok though

This was the original directory contents from the apc.
/var/mitel-phoneloads/tftp

BootIp5215Dpl_00.bin
BootIp5220Dpl_00.bin
BootIp5235Dpl_00.bin
BootIp5340.bin
BootIpNavigatorDpl_00.bin
ipp510bootEnc.bin
ipp510main.bin
ipp5230bootEnc.bin
L2Boot_00.bin
L2Boot_5235_00.bin
L2Boot_5340.bin
L2Boot_Navigator_00.bin
MinetIp5215Dpl.bin
MinetIp5220Dpl.bin
MinetIp5235Dpl.bin
MinetIp5340.bin
MinetIpNavigatorDpl.bin


This is the list of files from the Mitel
/sysro/tftp
BootIp5215Dpl_00.bin
BootIp5220Dpl_00.bin
BootIp5235Dpl_00.bin
BootIp5340.bin
BootIpNavigatorDpl_00.bin
BR.coef
BRV2.coef
CHNcharUnEnc.bin
CN.coef
CNV2.coef
DE.coef
DectCordlessModule.bin
DEV2.coef
dir2.txt
ES.coef
ESV2.coef
FR.coef
FRV2.coef
fw4150.s
fw4150hr2.s
fw4150hr3.s
ipp5005.bin
ipp5005boot.bin
ipp510boot.bin
ipp510bootEnc.bin
ipp510main.bin
ipp5140boot.bin
ipp5140bootEnc.bin
ipp5140data.bin
ipp5140main.bin
ipp5230boot.bin
ipp5230bootEnc.bin
ipp5230main.bin
ippboot.bin
ippmain.bin
ippmain_irda.bin
ipptkbmain.bin
iprfp.bin
IT.coef
ITV2.coef
L2Boot_00.bin
L2Boot_5235_00.bin
L2Boot_5340.bin
L2Boot_5560.bin
L2Boot_Navigator_00.bin
LA.coef
LAV2.coef
MinetIp5215Dpl.bin
MinetIp5220Dpl.bin
MinetIp5235Dpl.bin
MinetIp5340.bin
MinetIp5560Ttn.bin
MinetIpNavigatorDpl.bin
MinetProtocolVersions.txt
mips_mitel.tgz
mips_opensource.tgz
MitelWM.csv
mitel_5302_jffs2_0_0_3_88.img
NA.coef
NA2.coef
NA2V2.coef
NAV2.coef
NL.coef
NLV2.coef
NZ.coef
NZV2.coef
pd11gl3.bin
pd11mtd.bin
pd11mtd3.bin
pi110001.bin
PT.coef
PTV2.coef
slnk_cfg.cfg
tig_minet_ns.bin
UK.coef
UKV2.coef
vmlinuz

Neither has any files with 5330 in their name?

I am assuming that the 5330 and 5340 files share a bin file?

 

[tlpeter]

I think so too
I never have install teleworker on the apc card so i don't know if it works different to be honest

I know the phone gets the teleworker bin file if set to teleworker

If you have another 300 somewhere with a higer version (ur1) then use that bin file
Maybe your bin file is corrupt or something like that


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[gautamsd]

I need help For Mitel 5220
The Version info I see is :
Main Load Version : 00.00.00.00
Boot Load Version : 01.00.02.32
L2Boot Load Version 01.00.00.02

Please advise on what does Main Load Version mean. . since the phone is not responding, please advise how to update it using TFTP, I have downloaded the TFTP32 and WinAgent TFTP Server. . .

Anticipating an early reply. .
Gautam

 

[MitelAU]

Your are high jacking BillB66's post.

Please create your own post and maybe you might get an early reply.

Knowledge is power, thats why we share!