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!

handsets lockup up once they have been made teleworker

Status
Not open for further replies.

deanmulley

Technical User
Mar 20, 2005
51
SE
hi there

have a strange one here,just upgraded a site to the latest build of 5.2 on an mx controler to resolve an issue with handsets locking and rebooting once the headset has been removed.it hasnt fixed the issue.
it seems that if we have a phone and make it a teleworker the boot loads changes to x.x.x16 from x.x.x.15 (cant rem the exact but i will get them and post).If the user has the headset key pressed and they unplug the headset the phone freezes then reboots and returns to normal..
This also happends at the local site if we try it away from the teleworker site........any ideas....?
 
The headset key is actually just a visual indication that a headset is active on the phone. The key itself does not do anything as far as I know. Are the headsets approved by Mitel? I haven't run into any problems with different brands, but you never know. How are the headsets connected to the phone? Are you going through an amplifier?

 
The headset key is actually the togel to turn the headset speech path and audio circuit on.the head set is a plan tronics one used on a lot of our sites but mitel say its ok.........no amplifer .....got me dum struck...mitel say that you cant have two different boot loads on same controler but ive defenatly got two ....lol....lets see there next answer
 
deanmulley,
I believe that the 6010 server also stores a copy of the boot files for the teleworker sets. I can't confirm that but I seem to remember someone from support saying that. If it is true you may need to somehow update the files in the teleworker server. Make sure that you have the latest version of the blade as it may include the correct files.
 
ahh thanks mitel man now we are getting somwere.....as far as i know it has the correct blade on the teleworker....is it possible as a test to down grade the sets to the pre tele worker version if thats the case...?,,as there is a high % of hansets here that were teleworker and now they are local based handsets .They seem to hold the tele worker up upgraded boot load no matter what we do.
 
Deanmulley,

The latest Teleworker Blade is 3.1.12 on SME 6.1 Not sure if you can get 3.1 on SME 6.0.

Anyways, the sets will always match the firmware load that is in the "PBX" whether it is the 3300 or teleworker. That's why you see it upgrading the flash when you switch from one to the other. If you wish to down grade the sets you would have to have them boot with older bin files. This can be done by ftping replacement bin files after you have saved a copy of your new ones. Best is bring a test phone to a different site and have it boot there, that way you aren't messing with your system too much.

I did find where the bin files are stored on the 6010. They are stored in /var/mitel-phoneloads/tftp. If you know enough about linux you could replace them with a new version.

If the set problem does not occur on one of the "pbx"s ie teleworker or the 3300, a call to Mitel might be the best bet. If you can say the problem only occurs when the set is on the teleworker then they may be able to get the SME guys to update the firmware in the teleworker blade. You should be able to have a bit of an argument as you were told to upgrade to 5.2.6.8 to solve this issue.
 
hi mitel guy

When you say the phone SHOULD match the system it is on (3300 or teleworker)do you mean if the teleworker has a different boot load ....ie... a higher one than the icp and it is to be configured as a teleworker, the handset should upgrade the flash .......?
So then, if you then make a teleworker phone into a non teleworker it should downgrade the flash to match the 3300....?

If this is the case this isnt whats happening on our site.....the handset stays on the upgraded load and thats when the issue occurs......any phones that havent been teleworkers (upgraded)are all fine all the other handsets teleworkers or ex teleworkers have the issue.

any ideas...? or is this normal in your expeareance
 
Well in the past the phone would always "upgrade when you switched from teleworker to pbx and vice versa. I will check on our in house tomorrow and see what happens. We are running the latest software on both. I'll post back tommorrow withte results

 
that would be a great help in getting to the bottom of this prob ...thanx mitelman....!
 
Deanmulley,

Sorry for the delay in getting back to you. I just finished some testing and have noticed what you describe about the different boot loads. What I have found is that the "upgrade" is dependant on the phone that you are using. In my test I used a 5020 and a 5220 dual mode. The 5020 would always change its boot load to whatever it connected too, but the 5220 dual would only upgrade to the newest load that was on the pbx, changing to the teleworker mode would not force it to download new code, eventhough the teleworker has an older load on it. I couldn't figure out how to force the phone to reload the software, that might require a call to Mitel
 
great that exatly what ive told are distrbuter but they under the advice of mitel say nope cant happen....lol
Thanks for taking the time out to test this mitelman...at least i know im not mad now.....think ill escelate the issue...thanks again
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top