3CX won't "forget" deleted & replaced phones

Status
Not open for further replies.

DesertGator

Free User
Joined
Apr 27, 2019
Messages
7
Reaction score
2
I've been running 3CX on AWS for almost 2 years without a hitch. It has worked great with my Grandstream GXP-21xx phones and I've had essentially no problems.

I have two phones that started failing (at different times) - in the morning the phone would suddenly not be connected or have dial tone. I cannot find any errors in logs or determine the root cause. All other phones on the same network, and a couple offsite work great. Sometime a power cycle fixed it, sometime not. So, these phones are so cheap as to be disposable, I figure I'll just replace them with new ones.

I disconnected one of the phones (ext 0004), deleted it from 3CX, set up a brand new replacement phone, entered the new MAC address and assigned it to that extension. Everything worked great, and 3CX even updated the new phone's firmware. All buttons took the programing and it worked normally.

Later I decided to try to reuse the old "failing" phone, still disconnected from the network, doing a factory reset and then attempting to connect it to a new extension on 3CX. I figure it would be interesting to study the failure with the unit sitting right next to my desk. Problem is, the old phone somehow became the extension 0004 phone again! The old phones Mac address replaced the new phones Mac address. I repeated the delete, install new phone, factory reset old phone process, but then rebooted the 3CX server on AWS just in case there is something cached. Re-added the new phone to 0004, then tried to reuse the wiped old phone - same things. Old phone takes over it's former extension in the phone system.

I am working around this problem by just throwing away any phone that is taken out of service and replaced by a new phone. It would seem like I should be able to move phones around onto different extensions if I factory reset them and enter the correct MAC address when setting up. But that doesn't seem to be what is happening.

Any ideas how to resolve this? Am I simply following the wrong process?

Thanks,
Kelly
 
Hi Kelly,

Any chance you deployed a 2nd PBX and you are looking at a PBX that hasn't ever had the original MAC removed?

Any chance you enabled scheduled restore events and reverted back to a previous backup?
1599226766099.png

Do you provision via STUN or LAN or SBC?
Do you use DHCP Option 66 so that phones autoconfigure upon reset?
 
Hello John & thanks for the response!

No, this is the first and only 3CX PBX. I've never done a restore or scheduled any events like that.

I provision via STUN, and I don't sue DHCP Option 66.

I've purchased a new GXP-2170 to replace one of the failing phones.

I'm not sure I clearly stated what the failure "looks" like. The user's phone looks normal and registered - there is no indicator of a problem. However, they have no dial-tone. The extension appears red in the 3CX console.

I'm going to set up the new phone today on the old extension and carefully note what happens.

BTW, I am running 3CX version 16.0.619 and Grandstream firmware 1.0.11.6 (as set by 3CX but which is not the latest Grandstream release)

Thanks,
Kelly
 
Latest PBX is not the one you use, this is 16.0.6.641
 
Problem is, the old phone somehow became the extension 0004 phone again! The old phones Mac address replaced the new phones Mac address. I repeated the delete, install new phone, factory reset old phone process, but then rebooted the 3CX server on AWS just in case there is something cached. Re-added the new phone to 0004, then tried to reuse the wiped old phone - same things. Old phone takes over it's former extension in the phone system.

I'm more interested in this part which doesn't make sense to me unless the PBX was restored to a previous backup.

Lets see if we can prevent it by doing some additional steps:

1. Find the extension which the MACs are assigned
2. Delete them using the button in the Provisioning tab
3. Press OK
4. Re-check the extension now and double check that it only shows the 3CX app

1599548497566.png

You may now add the good phone and provision it as you would normally.
We expect that the "bad" phone will not reappear in this list.

Create a fresh extension* and assign the old phone there
Factory reset it, and it will eventually reach the screen where it asks for user/pass
Ensure that you enter the new extension number as the username, along with its voicemail PIN
It should provision and become the new extension number


*= Give it a unique name and number, something that would not exist in your previous backups
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,962
Messages
589,991
Members
164,867
Latest member
swegner