5360 Teleworker phone speaker and handset issues

[gadgets906]

Have 5360 set up as a teleworker, the phone along with another which is still working perfectly where shipped, upon connection to home internet one phone is partially disabled the other working perfectly.

the problem 5360 Connects perfectly to the internet and server, however speaker and handset will not pickup. It appears to be something has caused the receiver hang-up and answer function to stop working.

Phone rings however you cannot answer it by picking up receiver or using speaker phone you must press a key and then the handset will work but not the speaker. You must use the x button on the 5360 to disconnect or hang up the handset.

I can initiate a call by pressing 9 or a line button however no dials tone at handset or speaker, nothing at all can be heard from speaker.

Could this be a programing problem? If not, what is the procedure for cloning the existing teleworker programming so we can replace it with a new 5360.

So assuming the 5360 with the problem must be replaced, where and how would we reconfigure the 5360 replacement to appear as the old original extension?

Any help as always appreciated?

 

[LoopyLou]

They worked on your internal network?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[SXWizard]

Did the phone get into headset mode some how? In Maintenance enter "Locate feature extension <extension number of 5360>. See if anything shows up under Active Features.

 

[DoubleUT]

Are both phones that you have 5360? What version of MBG are you running?

 

[kwbMitel]

Echoing SXWizard to see if Headset Mode is enabled

Adding, check that the COS of both sets is the same.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[gadgets906]

We enabled headset button on 5360, although it was not lit we engaged it lit it up, turned it off and all is well. Somehow we got into headset mode.

Thanks as always for your insight as you were correct once again.

 

[LoopyLou]

Check the feature access code for the headset on. We had a site where the code was close to a number they dialed. When they forgot to dial 9 before dialing out to the area code, they triggered the headset mode. Suggest putting a # or * before your codes.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[gadgets906]

Thanks, I will check it out and make the changes if necessary.

 

[SXWizard]

Better yet, delete the Feature Access Code for Headset ON/OFF. You don't really need it as it can be programmed on a button on the phone and the button indicator will display ON/OFF status.

 

[LoopyLou]

That is also true as SXWizard states.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[gadgets906]

Even Better, Thanks

 

[kwbMitel]

Loopylou, channeling Yoda you are

**********************************************
What's most important is that you realise ... There is no spoon.