Solved two phones same ext issue

[michaelneh1]

I have yealink phones that are next to each other and they have different ip and mac address but are showing for the same person and ext. In extensions it only showing one phone listed. but in phones it’s showing both if I update any info or try to setup Provisioning it changes the info for both. Any ideas?

 

[leejor]

Model of the sets? local, or remote? Provisioned recently?

Calls placed from either set show the same extension number on the called set?

 

[michaelneh1]

T46g there local were provisioned before I got here. when I check each phone there both set to the same extension.

 

[VoIPTools]

Strange that making configuration changes in the 3CX Console updates both phones (if I understand the situation correctly). It would make complete sense if you had two phones showing up under the extension. One brute-force solution would be to delete the extension and factory reset both phones, then recreate the extension and auto provision one of the phones... but remember to keep any voicemails and greetings before deleting the extension.

 

[michaelneh1]

ya I have one ext 256 in the ext section and two ext 256 in the phone sections . In the phone section when I tried to update the phone that was incorrect and it updated the one that was. One does not have any Provisioning and the other does when I tired to update that it changed the mac address for both. when I go under the ext it is does not have any Provisioning for a phone. so yes it's strange. I will try what you say and delete the ext and reset the phone.

 

[craigreilly]

unplug one from the network that is working.
then try logging into the other one, remove it and factory reset it.
then assign to the proper place.
then plug original 256 back in

 

[michaelneh1]

Ok thanks everyone I disconnected the one that was not working setup the one that is correctly then factory re-set on the one that needed to be and that got rid of it and i was able to set it up. thanks again.

 

[YiannisH_3CX]

Glad to see the issue has been resolved