unable to configure new X5U-V2 as a router phone

[chadwick_corey]

I'm using a 3CX hosted instance of Version 20.0 Update 3 (Build 806 Release).

Steps I took.

1 - Added the phone to the extension using the Connect Directly option.
2 - Plugged the phone in (fresh out of the box). It booted up and almost immediately showed the users name on the display. However, it would not actually register and allow calls to be made.
3 - I checked the firmware and noticed that it was outdated, so I upgraded it using the file available at https://www.3cx.com/docs/phone-firmwares/ . The upgrade was successful, and the phone rebooted, but there was no change in behaviour.
4 - I factory reset the phone, expecting it to re-provision via RPS, but it did not.
5 - After the factory reset, it does have this in the phone's config.


That is the correct extension number and URL for the server, but the formatting is completely different compared to another phone that is working.

6 - I tried updating the info in those boxes to match the formatting from another working phone, and substituting the MAC of the other phones config.


Still no luck.

Looking for suggestions.

 

[KeithA]

Hi,
In the admin console check the User > IP Phone for the correct provisioning link and the mac address is correct for the phone.

dummy values here

Also go you get anything if you try and access the following using your values from eg above
https://yourphonesystem.3cx.us/provisioning/1qaz2wsx3e/0C01234567AB.cfg

Regards
Keith

 

[chadwick_corey]

Yep, MAC was correct and the phone was getting the RPS profile to an extent, because the info in those boxes was coming from the phone system, even after a factory reset.

I updated the firmware on another new phone (first), then added it to the same extension and it worked right away.

I think that means that having the phone get provisioned via RPS with the original firmware put it into some odd state. Just not sure how to get it fixed now.

 

[JohnS_3CX]

Yep, MAC was correct and the phone was getting the RPS profile to an extent, because the info in those boxes was coming from the phone system, even after a factory reset.

I updated the firmware on another new phone (first), then added it to the same extension and it worked right away.

I think that means that having the phone get provisioned via RPS with the original firmware put it into some odd state. Just not sure how to get it fixed now.

Factory reset after making sure the MAC has been removed from 3CX.
https://www.3cx.com/sip-phones/factory-reset-fanvil-x-series/

A few minutes after it comes up, ensure there are no provisioning server details stored in the phone.

You can now assign it to a new extension if you want and then reboot.

 

[Fabian Jsn]

I'm using a 3CX hosted instance of Version 20.0 Update 3 (Build 806 Release).

Steps I took.

1 - Added the phone to the extension using the Connect Directly option.
2 - Plugged the phone in (fresh out of the box). It booted up and almost immediately showed the users name on the display. However, it would not actually register and allow calls to be made.
3 - I checked the firmware and noticed that it was outdated, so I upgraded it using the file available at https://www.3cx.com/docs/phone-firmwares/ . The upgrade was successful, and the phone rebooted, but there was no change in behaviour.
4 - I factory reset the phone, expecting it to re-provision via RPS, but it did not.
5 - After the factory reset, it does have this in the phone's config.
View attachment 44983

That is the correct extension number and URL for the server, but the formatting is completely different compared to another phone that is working.

6 - I tried updating the info in those boxes to match the formatting from another working phone, and substituting the MAC of the other phones config.

View attachment 44984
Still no luck.

Looking for suggestions.

Have you tried using another internet connection source for testing? I have experienced this, don't know why my internet provider blocked the connection to the 3CX server, after I tried using a connection from our backup internet provider, it worked normally after rebooting.