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!

Issue with a single User extension and Phone?

Status
Not open for further replies.

AppleHead493

Technical User
Apr 22, 2015
33
GB
Ok, a weird one!

I have a single user who is complaining that the people they are talking to cannot hear them. Also it would appear that their handup button (where the receiver sits) does not function properly either.

I have tested the cables to the phone and switch. All good.
I have tested on numerous phones. Same issues across different devices (5330 and 5312).
I have deleted and recreated the extension- No Good.

Any ideas here? I'm stumped... =/
 
Assuming system is 3300.

What does maintenance command LOCATE FEATURE EXTENSION xxxx
show. (where xxxx is extension number.)

Is headset mode on?

Also enure that the gateway address is the same as the other working phones.
 
headset mode, I guarantee it.

**********************************************
What's most important is that you realise ... There is no spoon.
 
No headset option assigned to that extension though?

I've added it in and set it to off so i'll post back with the result.
 
Hasn't helped whatsoever, even plugged into a new port and created a whole new extension and copied the keys from a working extension, AND changed the phone.
 
Ok I've had a look at the logs, it seems that the MAC Address is not supported and there's an IP conflict, it's picking up the .101 address of our /24 scope when that is already supposed to be assigned to another device.
 
MAC address is not supported?
All Mitel phones are 08:00:0F:XX:XX:XX
A few things:
1. Does it work in handsfree mode?
2. Confirmed the phone is getting the correct IP address for the correct Vlan.
3. When replacing phone did you also change handset/plugged into the headset port.

That said, Take known working phone including patch cord and move to location having issues and test.
 
SOLVED IT!

It was picking up a .101 address from our scope however, that address is already statically assigned to a different device (And not documented), so excluded the IP from the range and the phone then picked up a different IP and is now working fine again.
 
Typically we try to set aside a subnet for phones. Fewer issues like this

You can't duct tape stupid.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top