Solved Only one IP phone appears behind the Raspberry Pi SBC

[Leo_B]

Hello guys,

Looks like we need your advice and assistance. The thing is, we currently work on test 3CX PBX v.16 setup with server side in the Vultr cloud VM and on-premises IP phones coupled with Raspberry Pi 4 powered SBC behind the pfSense firewall.

The SBC is online and shows green in the 3CX Management Console, the first phone hooked up to the local network appeared in the Phones list and was assigned successfully. However, we’ve effectively stuck with the rest of phones to deploy – none of them doesn’t even seem to appear in the list of the devices available. Factory reset won’t fix the problem.

Can anyone at least hint the reason why it could probably happen?

Thanks in advance for the help!

 

[Saqqara]

What phones are you running, are they running the 3CX supported firmware ?

 

[Leo_B]

What phones are you running, are they running the 3CX supported firmware ?

A bunch of Yealink T56A devices all shipping firmware 58.85.0.5 downloaded directly from 3CX site.

 

[Saqqara]

sbc server on a fixed ip address ?

Are the phones on the same network as the sbc server - no vlans involved.

Any dhcp option settings on the dhcp server ?

Have you configured any rules on the PFSense for the sbc server - the only rules required are outbound port 5090 (tcp and udp) and 5001 (tcp)

If you manually create the phone in 3CX management console first, and then in the phone webgui enter the provisioning link does this work.

 

[Leo_B]

sbc server on a fixed ip address ?

A static one.

Are the phones on the same network as the sbc server - no vlans involved.

They are. Same LAN, no VLANs set up.

Any dhcp option settings on the dhcp server ?

Option 66 only has been set to SBC LAN address. This is it.

Have you configured any rules on the PFSense for the sbc server - the only rules required are outbound port 5090 (tcp and udp) and 5001 (tcp)

Originally none of the mentioned rules was created, but we just added them to pfSense configuration, Doesn't look like it helped.

If you manually create the phone in 3CX management console first, and then in the phone webgui enter the provisioning link does this work.

Well, we have never tried this as far as our goal is to get the auto provisioning working. Basically, we are supposed to compete a setup, bring the SBC and phones to the client's site, hook the stuff up to the local network, then wait some five minute for phones to complete deployment process automatically. But we will try the provisioning link trick with a selected device.

 

[Saqqara]

Remove the dhcp option 66, and factory default the phones

The sbc server will see the pnp traffic from the phone, and populate the 3CX management console where you can assign the phone to a new or existing extension

 

[SteveITS]

They should just appear as new phones when connected (and powered on...just checking). Did you try restarting the SBC?

 

[cobaltit]

You are using Option 66 incorrectly, not sure why you though you should point it at the SBC.

How to auto-provision IP phones with DHCP "Option 66” (3cx.com)

Either configure option 66 correctly or remove it and let the SBC to PnP. PnP happens in the absence of other configuration methods.

 

[JohnS_3CX]

Please remove option 66, confirm it has been removed 100%.

Then factory reset one of your Yealinks

You can optionally run a tshark capture on the raspberry and see if the freshly reset Yealink has sent a SUBSCRIBE message to IP 224.0.1.75 (which is what normally happens in order for a new phone to appear on the management console.

Additionally, ensure you you are logging in to the management console of 3CX using the latest stable version of Chrome, and empty your cache.

 

[Leo_B]

Gentlemen,

Sorry for the late response. Eventually, we ceased troubleshooting the pfSense setup and opted to switch to Unifi hardware. The one worked like a charm, having effectively resolved the original issue.

I do appreciate all you guys who responded my message. Thank you for your hints, advises anf assistance!

 

[JohnS_3CX]

You are welcome!