Search results

Thanks Saqqara / Yannish, managed to completely overlook that one! Forgot that the server will blacklist an internal IP... Added to my check list!

So just tried the following: Factory reset the W52P Removed the device from FXS/DECT Recreated the W52 under FXS/DECT as per https://www.3cx.com/sip-phones/manually-provision-yealink-dect/ Copied / pasted the URL into the W52 UI, confirmed and then auto provision. Still failed, here's the...

I believe it was 15.3.. Yes, I originally created them in the FXS/DECT section, so I removed and re-created the configuration again, which is where I've been getting the provisioning URL from.

Yes, they're both on the same subnet. As the auto provision would not work I downloaded the config file using the URL. Downloaded no problem, applied it to the W52 which appears to load it with no problems, but looking at the account page on the W52 it shows that registration fails. The above...

Server: Windows 2016 VM running 3CX. 4 x T46G & 2 x W52P / W52H After updating 3CX server to 15.5, I needed to reprovision the phones to push some config changes. The T46Gs worked with no issues at all, but the W52Ps just won't provision at all. I've done a manual firmware update to 25.81.0.30...

Hi Yannish, rebooted everything and all appears to be running okay now. Just got one issue left now, the line isn't cleared when a voicemail is left. The line is held until the voicemail duration is reached. Any thoughts?

Hello, Just started playing around with 3CX and having a problem trying to get the Patton SN4112 FXO to make outgoing calls. Activity log has an entry stating that Cause: 503 Service Unavailable/INVITE from 192.168.0.71:5060. The Patton has been factory reset and the configuration file...