Yealink T53W as SBC in WiFi connection

[cttwbg]

Hello,

I was able to get a T57W with wired connection as SBC in one of the remote site. Now I'm trying to set up a T53W in WiFi mode as SBC but it won't take. Is using Yealink T5xW phone as SBC only work when it is wired.

Thanks.

 

[Charles_3CX]

It has never been tested or is supported with WiFi connections, always use a physical wired connections for any ip phones!

 

[JustinB-PedEnt]

I have a few T53W phones in my environment set up as SBC over wireless, so the configuration itself is doable.
However, I need to stress that I am using this for users who work from home and only have the one IP phone. There are no additional extensions behind the SBC, I am only taking advantage of the improved performance and setup over our previous STUN configuration.

 

[cttwbg]

It is the same scenario here. My client is bringing one of the phones home. That means I have to first setup using STUN and then turn on the phone in router mode and reconnect as SBC? I know when I set up a TP-Link route in client mode and connect to my wifi router and connect to the phone and it works.

 

[JustinB-PedEnt]

I have to set another one up today. This user already has an on-prem phone here in the office so there's some added complexity, but here are my steps:

1. Connect new T53W to office LAN and provision to an extension using Management Console so I can update the firmware to latest (96.86.0.74).
2. Remove T53W from that extension and perform a factory reset.
3. Remove user's on-prem phone from extension (since Router phone can only be added as the first phone for an extension)
4. Add T53W to user's extension as a Router phone using the Webclient Admin following the steps here. Provide the generated PIN to the user for later.
5. Add the user's on-prem phone back to their extension (this person works remotely part-time and on-prem other times)
6. Give the user the T53W to take home and instruct them to:
   1. Plug the phone in and enter WiFi Network info when prompted.
   2. Reboot the phone. It should prompt for a PIN after auto-connecting to the WiFi
   3. Phone should then automatically provision via RPS

The lessons learned for me originally were to make sure to the phone is on the latest firmware, and to make sure our PBX SSL Cert was complete. We were missing the intermediary from our chain and it was preventing RPS provisioning.

 

[cttwbg]

Hi JustinB,

I just got it working before I saw your recent reply. What I did was having a TP-Link WAP setup as a WiFi client and connected to the T54W at my home location so that the T53W thinks that it has a wired connection. Then I followed the same steps you linked to on the 3CX page and setup the SBC on the T53W. After that, I unplugged the power supply and the TP-Link WAP from the phone. Then I booted up the phone. A screen then popped up asking me to connect to WiFi. I selected my home SSID and it started up and worked right away. Thank you for your response! Learning something new everyday.

 

[JustinB-PedEnt]

Glad you got it working @cttwbg. As it happens, the phone I set up yesterday did not automatically provision with RPS like it was supposed to and kept asking for a Username and Password. I'm not sure what went wrong yet, but I was able to connect with the user remotely and manually set the provisioning URL.

Always an adventure!