Configuration of Yealink W52p behind an SBC

[Alan Keatinge]

Good day, first post here so please forgive typos/formatting or if I haven't inlcuded relevant information.

I'm setting up a Yealink 52P base station with three associated phones behind an SBC, connecting to a hosted 3cx instance (hosted by 3cx). We tested the base station and two phones with our own on premises 3cx and it worked fine, so we factory reset it and sent it off to the customer site. When it's connected to the network it shows up in 3cx under phones and i can configure the extensions under 3cx->advanced->fx/dect however under phones it's still bold and the local ip is not translating from the internal network on customer site to 3cx, instead it's showing up as 127.0.0.1 (see attached screen shot). I've run the firewall checked and Iv'e even opened ports on the SonicWALL pointing to the computer with the sbc running, the sbc communicates fine and shows as up and running, but without the IP for the W52P coming through, i cannot provision the handsets.

Has anyone got any ideas as to what might have gone wrong? I'm happy to accept all suggestions as I may have missed something obvious, if I've not been clear above by all means ask me questions and I'll reply as best I can.

Some network info, the client is connected via an adsl modem in bridge mode, behind which sits a SonicWALL, then the lan. Also I've erased the mac address fo the device form the image i attached for what I hope are obvious reasons, but that is coming through both there and under fxs/DECT

Kind Regards,
Alan

 

[Saqqara]

You have to manually setup the W52 and not via PNP -

https://www.3cx.com/sip-phones/yealink-dect-w52p/#h.njk1rx5jow1p
https://www.3cx.com/sip-phones/manually-provision-yealink-dect/

Add the W52 base unit under FXS / Dect , and then add the provisioning url into the base unit.

 

[Alan Keatinge]

I did try the above, it doesn't work, it shows the account as disabled and doesn't communicate back to the 3cx system. I even tried moving the sbc server to a different pc on the site, but that didn't help, it won't provision or see the device correctly, it's not communicating the IP back to 3cx

 

[SteveITS]

Iv'e even opened ports on the SonicWALL pointing to the computer with the sbc

The SBC doesn't need any ports open to the Internet. It connects to the 3CX server not the other way around.

Did you use the SBC method/IP per Saqqara's second URL, or the server hostname/IP?

127.0.0.1 shows up in the 3CX phone list for things like the web client that connect directly to the server.

 

[Alan Keatinge]

Hi Steve and thanks for you reply
I used the sbc method as per the second url, when i fill in the configuration url to the base station web interface hit confirm, then auto provision now, it fails to provision, the accoutn1 remains disabled and no information comes through. Alas due to us having an on-prem 3cx server in the office i was unable to test the sbc method prior to deploying to customer site. If you have any suggestions as to how i might move this forward, I'd appreciate anything you can contribute.

 

[JohnS_3CX]

Hi Alan,

An important point you haven't touched is firmware: ensure the correct version is installed as per our guide and then try again https://www.3cx.com/sip-phones/yealink-dect-w52p/#h.i1ns9ummsm0r

Another thing to note after installing the firmware. The DECT base (where currently installed) should be able to both resolve the PBX IP and download the config file. IF this has not happened, you will notice the the Web UI of the base that the accounts are blank (no extensions configured). So you might want to test that the base can download the config from that specific network before you go any further.

Finally, ensure that the setup in FXS/DECT has correctly defined SBC as the provisioning mode, and that you have pasted the LAN IP of the SBC that is installed on the same network as the base.

Ignore the "127.0.0.1" you saw on the management console - there is no issue here, that is simply how the base should be expected to appear if you are over SBC and is entirely normal to show up this way for unprovisioned DECT bases.

 

[Alan Keatinge]

thank you! the firmware update did it, didn't even have to manually register the other two handsets, it picked them up and assigned the accounts and extensions to them, I figure that's a feature of the new firmware.

Related question, when dialling in when i select one of the ring groups from the Automated attendant, rather than playing a ringing sound it plays the hold music, Iv'e looked at ring groups and extension settings but there doesn't seem to be a place to change that. In essence what happens is, they come in and depending on which option they pick they are sent to 1 of 3 ring groups, or a voicemail. while the phones ring in the business, the client just hears the hold music, I'd like to think i can customise that to , perhaps, a recording of a ringing phone.Is that possible?
Kind Regards,
Alan

 

[JohnS_3CX]

Hi Alan,

Very glad to hear that the firmware resolved the issues!

Now regarding the music on hold, you need to have a Pro license of 3CX which opens up the Queues. With queues, you can pick a custom MoH per each queue you have on the system.

Ring groups on the other hand will only use the general MoH that the PBX has, and cannot be customized per ring group. Normally Ring Groups do not have MoH per se, the reason you hear the MoH is because you are in a state of being transferred from an IVR to a ring group and the MoH plays until you are connected. If you have a DID point directly to a ring group for example, you will not hear music on hold because its a direct call to the ring group.