Provisioning Fanvil X4U

[JohnS_3CX]

Regardless of what you use, and how you use it, unless you find a way to allow multicast then you will have to find alternative ways to provision phones.

For example, you can paste the provisioning link manually in the phones and restart them to provision themselves.

 

[ENTerprise_NT]

How can I do this?

 

[JohnS_3CX]

Take a look at this guide here, it should describe how to do it:
https://www.3cx.com/sip-phones/manually-provision-fanvil/

 

[ENTerprise_NT]

Thank you so much. One more question:
I'm configuring a cloud installation ospitated on 3cx for my customer.
If I install an SBC on a Raspberry and provision 5 phones on it on my LAN (for my customer), can I then deliver it to the customer already configured and avoid doing the provisioning with him? Must I set a static IP or can I set a dinamic ip? Once provisioned the phones, is it necessary to have a static ip or can I mantain a dinamic one?
What can it happen if i leave the dynamic ip?
Sorry for my numerouse questions, but It's my first installation for a customer

 

[JohnS_3CX]

Hi,

If I install an SBC on a Raspberry and provision 5 phones on it on my LAN (for my customer), can I then deliver it to the customer already configured and avoid doing the provisioning with him?

Yes you can, but read below first!

Must I set a static IP or can I set a dinamic ip?

The SBC Pi must have a static LAN IP. If it is dynamic and it changes, the phones will immediately stop working!

I would not recommend to set them up from before, because you do not know what IP the SBC will take when you go to the customer's LAN. Maybe they have a different IP range, maybe the IP you chose for the Pi is already taken by another PC. What would happen in that case? You would not be able to reach your Pi and reconfigure it, and you would have to start from scratch (wasting more time)



I think that since you have only 5 phones, you should do the following:

1. Update the phones firmware manually then factory reset them before you go to the customer.

2. Setup the Pi (use DHCP) and connect it to the cloud 3CX instance from now so that it's ready before you go to the customer.

3. Visit the customer now and plug in the Pi. Confirm that it has connected to the cloud instance again (SIP trunks page) and that it is ready:


4. Now that the Pi is ready, change it's IP setup to now use static (and use the same IP it has been given by customer's DHCP)

5. Finally, plug in the phones and they should appear as "new" in your 3CX management console. You can now assign them to each extension normally and they will take 1-2 mins to become ready to use.

In the rare event that your customer's LAN does not allow multicast (like the problem you had at your office) then all you need to do is find the IP from each phone's menu, login, and paste the provisioning URL like you have already learned from your previous experience.

Sorry for my numerouse questions, but It's my first installation for a customer

No problem, we are happy to help you learn! I highly recommend that you use our free 3CX Academy course, as it will teach you many of the basics and help you learn the system faster! https://www.3cx.com/3cxacademy/

We also do free webinars, where our 3CX trainer can teach you and answer questions related to the course. Just take a look at the right of your screen under "Upcoming webinars" ----->

 

[ENTerprise_NT]

4. Now that the Pi is ready, change it's IP setup to now use static (and use the same IP it has been given by customer's DHCP)

Must do I this on the router or in the raspberry consolle?

 

[JohnS_3CX]

You have two options actually:


Option a.) If the customer's router/firewall has "DHCP reservation", then you can do it from the router. (ie. tell the router to give the Pi the same IP always via DHCP). If the customer ever changes/resets the router however, you will have to reprovision the phones again.

Option b.) Log in to the raspberry and do it manually from the console and do it from there. I think this is the best option because if the customer resets their router/firewall the Pi will still keep its IP address.

 

[ENTerprise_NT]

Option b.) Log in to the raspberry and do it manually from the console and do it from there. I think this is the best option because if the customer resets their router/firewall the Pi will still keep its IP address.

I've found this instruction on the web, do you confirm me it's right?

sudo nano /etc/dhcpcd.conf

than

interface wlan0
static ip_address=192.168.1.XX/24 -->the RB's IP
static routers=192.168.1.XX --> the router's IP
static domain_name_servers=192.168.1. --> the same of router's IP

 

[JohnS_3CX]

Please check our raspberry guide here: https://www.3cx.com/docs/installing-pbx-raspberry-pi/#h.fsmkffbwirsm

Do not use the wlan interface, make sure you use a wired LAN connection!

 

[ENTerprise_NT]

Ok, I think I have all I need now (I hope). Thank you soo much for your kindy assistance!

 

[JohnS_3CX]

Let us know how it went!

 

[ENTerprise_NT]

Sure!

 

[ENTerprise_NT]

Waiting for the delivery it's arriving a new question: The customer's IT manager said me the configuration of their Lan and said me that they have a 192.168.1.0/24 class, the router have 192.168.1.254/24 ip. So, in this case, if the DHCP assign to the raspberry a 192.168.1.XX, in wich way can I config the raspberry (following the 3cx guide you said me)?

#Ethernet static IP configuration
interface eth0
static ip_address=192.168.1.111/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1 8.8.8.8

Wich is the correct configuration using the information I wrote?

Thanks a lot again

 

[JohnS_3CX]

I would think that it would probably look like this:

#Ethernet static IP configuration
interface eth0
static ip_address=192.168.1.XXX/24
static routers=192.168.1.254
static domain_name_servers=192.168.1.254 8.8.8.8

This is not necessarily correct, I'm assuming that their local DNS and Gateway is the router IP you mentioned.
I would rather not advise you on this part as we do not really offer help on the networking part, this is something you should read upon and take care of. There are many Linux resources online that can help you if you want to better understand (always good to know more than you need!)

 

[ENTerprise_NT]

I've done the delivery to the customer. Almost everything went well. I had problems with a client with windows 7: I could not install the app for windows and the message "contact the product administrator" came out. How can I go about installing the application on that computer as well? On other PCs with the same operating system I installed it quietly.

 

[JohnS_3CX]

Sorry, can't do much about that - Windows 7 is an end-of-life OS .
https://www.microsoft.com/en-us/windows/windows-7-end-of-life-support-information

We do not test our apps on old OS such as Windows 7 so I have no idea whether it will work as intended, even if you did manage to install it.

Please advise the customer to upgrade to Windows 10 at least, for their own security and for better compatibility with modern apps and solutions.

As for why it failed, if you could look in the windows %temp% folder and read the installer logs you might find something useful.

Just keep in mind we would not be issuing any updates or offering support for problems regarding our apps if you wish to run them on Windows 7.

 

[ENTerprise_NT]

Ok, later I try it. I'll found a .log file?
Can I install the version 16 of the desktop app until my customer change the pc to a windows 10?

 

[JohnS_3CX]

You can, but the same thing applies as above for both the V16 app, and the new V18 app.

By the way, since we concluded the original issue that you opened this thread for, I will now close the thread but please feel free to start a new thread in case you have new questions or new issues you want to ask about!