Let the SBC use a DHCP address

[David Pearce]

This affects the Windows and Raspberry PI versions of the SW.

If the SBC could use a dynamic address, the config file(s) on the SBC would not have to be specific to each home (address pool can differ).

The phone provisioning should be able to tolerate the local IPaddress changing.

Right now:
* Talk to the home user and try to guess an IP address we can use
* Modify the config file on the SBC
* Ship the SBC and a phone
* Once they have it hooked up, provision the phone.
* Test

Otherwise:
* Plug in SBC and phone
* Provision and test in the main office
* Ship to the client

Just a thought.

 

[Nathan Boyd]

How will you know what Remote IP the SBC gets assigned to use in provisioning ahead of time? And/or guarantee that the device doesn't change IPs in the event of a power outage? I'm not sure I understand the benefit of a dynamic address in this scenario

 

[Benedikt Machens]

How will you know what Remote IP the SBC gets assigned to use in provisioning ahead of time?

DNS will solve this

https://www.3cx.com/community/threa...-for-sbc-raspberry-edition.59171/#post-248944

 

[cobaltit]

Yeah I'm confused you want 3CX to reinvent DNS? You can already do this.

 

[Benedikt Machens]

Yeah I'm confused you want 3CX to reinvent DNS? You can already do this.

Some devices will have malfunctions if you use a DNS name for the 3CX SBC (caused by template and firmware of device).

So it's not safe to use DNS for SBCs atm.

 

[accentlogic]

Some devices will have malfunctions if you use a DNS name for the 3CX SBC (caused by template and firmware of device).

So it's not safe to use DNS for SBCs atm.

This feature would solve so many issues. Hopefully 3CX will work with their supported phone manufacturers to make this work properly. We see this used by many printer installations, why not set the proxy using the host name? I understand this may not work in some situations, but it will in most.

Another issue that would need to be resolved is using RPS for provisioning, rather than PnP. Once these two items are done we can setup extensions, ship the SBC and phones to the client - plug in, and they work.

One huge advantage of the SBC is no firewall configuration - but on small networks they are often setup with the entire subnet in the DHCP scope so we need access to the firewall to change the scope or setup a reservation - or at least change the lease to at least 8 days.

 

[cobaltit]

Some devices will have malfunctions if you use a DNS name for the 3CX SBC (caused by template and firmware of device).

So it's not safe to use DNS for SBCs atm.

Care to share which devices you are having problems with? Seems to work with all the supported phones I've tested.

 

[Benedikt Machens]

Care to share which devices you are having problems with? Seems to work with all the supported phones I've tested.

Snom D785 as hot desking device behind a 3CX-SBC adressed via DNS name. You can login into hot desking, but logout does not work because the BLF target is wrong. But maybe this is fixed today. My test case is some month's old.

And nearly any analog Gateway. If you configure the 3CX-SBC to work as proxy via DNS name you get some weird failure scenarios. It's not completely broken but if you want a reliable functionality you need to use IPs instead of DNS names

 

[cobaltit]

I'll have the test the Snom but that may just be the hot desking template. As far as the analog gateway goes I wasn't aware any were supported via SBC. I used DNS names just fine with Yealink phones and I've tested it with Grandstream and Polycom VVX (although not extensively).