SBC: Point 2 identical at the same server?

[oguruma]

Suppose you wanted to configure a "hot spare" SBC pointed at the same 3CX server to mitigate the first one failing.

Is it possible to configure a second SBC, pointed at the same 3CX server, then simply changed it's IP address, but leave it running.

Then, if the primary SBC dies, you can simply change the IP address of the spare SBC to the IP address of the main SBC.

Would this work? I have a Pi set up as a SBC, and I have another Pi laying around and I wouldn't mind having removing a single point of failure.

 

[Saqqara]

I can not see why this would not work,

The only issue I could see, you may have to restart the sbc after the network change and the phones.

 

[leejor]

But the second SBC would have to have the same local IP as the first one, the same that all the sets register to. That would be a problem. If the sets were capable of having an alternative server, then perhaps, in theory, as you could point to the IP of the second SBC. It would have to use a different port than the other SBC. Keeping track of the voice ports (between the two SBCs) may be tricky, and the particular router used, may play a part in that.

You could set both with identical settings, then power toggle to switch from one to the other.

Have you found the Pi SBC's to have a reliability problem?

 

[oguruma]

But the second SBC would have to have the same local IP as the first one, the same that all the sets register to. That would be a problem. If the sets were capable of having an alternative server, then perhaps, in theory, as you could point to the IP of the second SBC. It would have to use a different port than the other SBC. Keeping track of the voice ports (between the two SBCs) may be tricky, and the particular router used, may play a part in that.

You could set both with identical settings, then power toggle to switch from one to the other.

Have you found the Pi SBC's to have a reliability problem?

I haven't even used the Pi's as an SBC, yet, actually. I am in the process of migrating from an in-house install on a VM to running this out of a VPS.

The idea I am shooting for would be remote administration to mitigate an SBC failure.

I would (theoretically) use a DHCP reservation to set the IP for both the main and the backup SBC.

So, suppose I get a call from the office and an employee reports that none of the phones are working.

If the cause has been determined to be SBC, I could VPN in and change the DHCP reservation so that the backup SBC assumes the local IP of the primary SBC (and reboot it or otherwise ensure it gets a new DHCP IP address).

The backup would be acting as an pre-configured warm spare, basically.

My idea is the same in practice as your toggle switch proposal. The difference being that the second SBC would always be running and I can correct the issue without being physically present.

 

[leejor]

The only cost to try it would be that of a second Pi, and your time.
I do something similar, with a remotely controlled AC outlet.