Solved Switch (quickly or automatically) the provisioning method

Status
Not open for further replies.

JLSeagull

Forum User
Joined
Jan 1, 2020
Messages
84
Reaction score
21
3CX Team and Community! (I hope everyone is well and safe)

Is there a way to quickly switch between one provisioning method and another? For example, IP phones provisioned as 3CX SBC (remote), in case of SBC failure, switch quickly to Direct SIP / STUN?

Real case:

In the office, IP phones are provisioned as 3CX SBC (remote), but the SBC went down for no apparent reason, despite the machine being turned on and with an active network connection, for an unknown reason it lost the network connection (LAN and Internet). Restarting the SBC locally was not an available alternative, as there was no local support available, so the solution would be to switch to Direct SIP (STUN - remote) mode. This became impracticable, as this action depended on entering the credentials of the extensions (User and PIN) and even following the steps in the tutorial https://www.3cx.com/docs/manual/configuring-ip-phones the credentials do not were shown on the display of IP devices after they were restarted, making provisioning via Direct SIP impossible.

Scenario:

1. Standard License 16.0.8.9
2. GrandStream IP phones GXP1610 firmware 1.0.7.3 and SBC version 16.2.24 on the same LAN (Office).
3. 3CX PBX hosted in the cloud (AWS instance).
4. pfSense firewall configured according to the tutorial https://www.3cx.com/docs/pfsense-firewall
 
Last edited:
Correct, But if you want to avoid the situation you describe, that's the supported way to do it. And it doesn't have to be a PC. A couple $50 Raspberry Pi's work.
 
I'll have to agree with @cobaltit, the scenario you describe is perfect fit for this, utilizing the SBC HA cluster would be the way to go here.

Regarding switching from one provisioning method to the other, do bear in mind that the correct way to do it would be:

1. Delete the device from the Extension >> Phone Provisioning tab.
2. Factory reset the device to avoid remnants of any previous configuration causing issues.
3. Follow the provisioning guide to reprovision the device: https://www.3cx.com/sip-phones/
 
I'll have to agree with @cobaltit, the scenario you describe is perfect fit for this, utilizing the SBC HA cluster would be the way to go here.

Regarding switching from one provisioning method to the other, do bear in mind that the correct way to do it would be:

1. Delete the device from the Extension >> Phone Provisioning tab.
2. Factory reset the device to avoid remnants of any previous configuration causing issues.
3. Follow the provisioning guide to reprovision the device: https://www.3cx.com/sip-phones/
@ChrisC_3CX would be possible at least avoid the use of credentials on phone, for example put the credentials data on the Phone Web Page? So that the process could be performed fully remote. In my case, the need to fill in the credentials locally was the main factor that prevented me from switching the provisioning method.
 
  • Like
Reactions: JLSeagull
If you have remote access to the Phone's UI, you could omit using the RPS provisioning method completely, and instead, configure them as STUN devices by using the manual link provisioning method outlined here: https://www.3cx.com/sip-phones/manually-provision-supported-grandstream-gxp/
@ChrisC_3CX YES, in this case I have remote access to the Phone's UI. If I enter the credentias in "Config HTTP/HTTPS User Name" and "Config HTTP/HTTPS Password" is It possible provisioning the phones online, without local human intervention?
 
The full provisioning link only should be enough. Exactly as mentioned in the guide. You should not be required to put the credentials in as well if you follow the guide.
 
  • Like
Reactions: JLSeagull
The full provisioning link only should be enough. Exactly as mentioned in the guide. You should not be required to put the credentials in as well if you follow the guide.
@ChrisC_3CX So it is the solution I need. Thank you very much!
 
  • Like
Reactions: ChrisC_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet