Solved Semi-Attended Transfers with Yealink W53 not possible

[JohnS_3CX]

Ok if you face specific issues you will have to tell me the following again please:

• 3CX Version, e.g. Standard Annual 16.0.2.910
• Server OS, e.g. Debian 9 / Windows 10 Server 2012 R2 / Raspberry Pi
• Is the 3CX Server Hosted and where?
• Yealink Base Model and Firmware version
• Yealink Handset Model and Firmware version
• Provisioning Method: Local / VPN / STUN / SBC
• Trunk Provider or Gateway Make/Model
• Has the Firewall Checker passed: YES / NO
• Are custom Phone Templates being used: YES / NO

 

[Martyn Barlow]

Ok if you face specific issues you will have to tell me the following again please:

• 3CX Version, e.g. Standard Annual 16.0.2.910
• Server OS, e.g. Debian 9 / Windows 10 Server 2012 R2 / Raspberry Pi
• Is the 3CX Server Hosted and where?
• Yealink Base Model and Firmware version
• Yealink Handset Model and Firmware version
• Provisioning Method: Local / VPN / STUN / SBC
• Trunk Provider or Gateway Make/Model
• Has the Firewall Checker passed: YES / NO
• Are custom Phone Templates being used: YES / NO

I visited the other office earlier. I got them working (blind transfer) after resetting the base stations and re-provisioning all extensions/handsets.

Thanks for your help both. Really appreciated.

 

[AWS2P]

how came idea to reset all the devices? was it just a try

 

[Martyn Barlow]

how came idea to reset all the devices? was it just a try

I had previously moved one or two handsets from one base to another when troubleshooting another issue where they could not answer inbound calls very occasionally (which was resolved by disabling SIP ALG on the router) so I thought I may as well reset. The users had been playing around changing ring tones, display names so a general cleanup was a good idea.

 

[AWS2P]

so an end of day on a win case

 

[JohnS_3CX]

Hi Martyn,

Glad to hear it was resolved then