A prerequisite for provisioning, is it a registered IP phone?

[Sergey Potap]

Hello to all FusionPBX fans!

Again, I would like to ask a question on the topic of auto provisioning.
I understand that everyone is already tired of such questions ,...
but nevertheless, I would like to get an answer from the specialists to the next question - to perform provisioning of an IP phone in the FusionPBX WEB session (by pressing the Device ---> Provision button), is it necessary for this IP phone to be registered as an Extension in Freeswitch? That is, if the phone is not registered, then it is impossible to execute Provision from the FusionPBX WEB session?

I saw this behavior when I tested auto provisioning for the Yealink T19p phone.

If such a policy is really implemented in FusionPBX, then it is very inconvenient if I need to change the basic registration parameters (for example, the Extension number, etc.). Since the IP-phone can lose registration and it will be impossible to perform Provisioning from FusionPBX.


Or am I still wrong (I wish I were wrong)? And it is possible to perform provisioning of an IP-phone when it is not registered, but has network access from FusionPBX?

I would be very grateful to everyone for the answers.

Best regards, Sergey.

 

[hfoster]

Sadly not, FreeSwitch needs it to be registered to send the 'event-string: check-sync;' to the correct place. The registration process is the phone saying 'Hey, I'm here on IP address 192.168.0.1, port 23456, UDP (NAT on 198.51.100.1), send packets to me!' Without that, mod_sofia has no clue where to send anything.

Best thing to do is adjust the refresh rate the phones check for a config, or trigger a reboot from the switch it's connected to if you're using PoE. You might want to also look into providing DHCP strings to allow for autoprovisioning from factory settings, though this can get tricky with HTTP auth passwords.

 

[Sergey Potap]

Good day,
Thanks for the answer dear hfoster.

It is a pity that this is so

In my opinion, this is a somewhat strange approach to provsion implementation.
It would be more logical to implement the provisioning in the presence of network connectivity between the IP phone and FusionPBX. And in this case, it does not matter at all whether the IP phone is registered or not. Well, okay, as they say - this is the design.

If the FusionPBX / Freeswitch developers are browsing this forum, then I ask them to add this moment to the FusionPBX documentation (A prerequisite for performing provisioning from FusionPBX is the presence of SIP registration of an IP phone!). This will protect future beginners from stepping on a rake.

Best regards, Sergei

 

[bdmonsey]

Not sure if this is what you're looking for to simplify the process of auto provisioning but most companies offer you a remote provisioning option so for example yealink as soon as i put in this mac address in the Remote provisioning site and match up the mac in my server it will automatically activate at the customers location.

 

[hfoster]

In my opinion, this is a somewhat strange approach to provsion implementation.

It's more of a limitation of SIP Notify, and the dynamic nature of the handset/PBX relationship. The PBX can only talk to handsets that have registered with it.

I will note, the only thing you lose is the ability to push a provisioning request ahead early. You still have the following:

1. Wait for the regular timer of the handset to check the provision URL again. I set this to 24 hours, you can make this smaller.
2. Get someone to press the 'provision' or 'update now' button on the handsets. e.g on Yealink it's 'Basic Settings -> Update Configuration'
3. Good old fashioned reboot.

 

[ricktendo]

Use Grandstream GAPS/GDMS, Yealink RPS, etc to do the initial settings pointing the phone to the config server, if you already have the device mac configured it should just work without any user interaction required (zero touch config)