I am troubleshooting another issue where new phones or factory reset phones (Yealink T43U) after assigning / provisioning appears to work except making a call fails and it says 'not found' on the handset. This happens for both new extensions and provisioning existing ones.
This happens at both offices which both use SBC's one on a Raspberry Pi and the other a Linux VM. The original system setup is from around August 2021. Yealink handsets are all up to date firmware (108.86.0.72).
I thought I should try updating the SBC as it they were on 18.0.27. This worked and I updated the Linux VM to 18.1.34 using the hosted portal. This was the only option for version, but it is listed as a beta. I checked and it's nearly a year old and there is a new final build 18.1.36 listed from February 2022: https://www.3cx.com/blog/change-log/3cx-session-border-controller-build-history/
Is there anything I can do to have this update listed in the hosted portal so I can apply it to the SBC? Is this a good starting place or are there other recommended troubleshooting steps for my 'not found' issue.
This happens at both offices which both use SBC's one on a Raspberry Pi and the other a Linux VM. The original system setup is from around August 2021. Yealink handsets are all up to date firmware (108.86.0.72).
I thought I should try updating the SBC as it they were on 18.0.27. This worked and I updated the Linux VM to 18.1.34 using the hosted portal. This was the only option for version, but it is listed as a beta. I checked and it's nearly a year old and there is a new final build 18.1.36 listed from February 2022: https://www.3cx.com/blog/change-log/3cx-session-border-controller-build-history/
Is there anything I can do to have this update listed in the hosted portal so I can apply it to the SBC? Is this a good starting place or are there other recommended troubleshooting steps for my 'not found' issue.
