Hi. We have a S100 device serving 20+ Linkus VOIP clients on various devices plus two TA analog VOIP trunks and one GSM trunk. When we update to the latest firmware (30.11.0.7) and a Linkus Desktop client tries to Transfer an active call to another client using the "Blind" button and dialing the destination number the transfer fails and the whole call system goes down: all current calls immediately end and all trunks are rebooted (TAs and GSM) so they begin to register again.
We observed this using the latest version of the Linkus Windows Client (1.5.10) as well as using an older version (1.2.53), but not using the latest iOS client (2.5.8). We reverted the S100 firmware to the second-latest version (30.10.0.75) and the problem dissapeared.
We also tested making the Transfer using Feature Codes (e.g. *03) using both Linkus Desktop and third-party Softphones on the latest firmware and the transfer just worked, so we are suspecting on some incompatibility on the Linkus Server app that ships with the latest firmware and the Linkus Windows Client. We currently have version 2.2.8 of the Linkus app on our server and haven't tried to update it.
8 comments
-
Oscar Colka I can replicate the same issue with the same PBX, Links App and Linkus desktop version, but I am not sure if this is a bug. Seems like the Linkus App and S PBX firmware has some kind of dependency.
It is a little bit strange, when I upgrade to 30.11.0.7, the Linkus App on S PBX is version 2.2.21.
With version 2.2.21, I don't have the same problem. When I downgrade to version 2.2.8, I can replicate the same issue.
How did you upgrade your firmware and Linkus App on S PBX server?
I would suggest you to try upgrade the Linkus App on your server to latest version(should be 2.2.27) and check if you still have this issue.
-
alejandro.sawers We originally upgraded our PBX server using the Upgrade menu, after checking for updates. To verify your suggestions we tried upgrading again to 30.11.0.7, this time double checking the Linkus App version on the server after this: it was 2.2.21. Tested call transfer from Linkus Windows Client and it failed.
So we upgraded Linkus App to 2.2.27 and the same problem persisted, even after a reboot of the PBX. So we ended up downgrading again to 30.10.0.75. Our Linkus App is back on 2.2.8.
Think our next step is to upgrade only the Linkus App on the PBX, but in case of fail we will need to revert the whole firmware version as we do not have the Linkus App 2.2.8 to make a quick rollback, unless there is another method to do this. -
Oscar Colka Hello Alejandro,
Could you please try provide some the system logs right at the time you experience this issue?
Or I would suggest you to submit a ticket and provide backup configuration and ask help from Yeastar Support Team.
-
alejandro.sawers OK. Before downgrading and after reproducing the issue we obtained this file from the Maintenance > System Logs option:
https://drive.google.com/open?id=1Y4P1TOlFLbo1FCyWHDV2awFvKH2PnMH2
Hope these are the correct logs. Thanks for your help. -
Lea L. Hi! Any news about this issue? Thanks.
-
Gary Hello Alejandro&Lea,
This is Gary from Yeastar support team. I am very sorry for bringing the inconvenience to you. We solved the problem with the new firmware 30.11.0.8. You can click 'Check for new firmware' under the Maintainence->Upgrade page. And also you can get the firmware from Yeastar official website https://www.yeastar.com/firmware-download/
Please kindly upgrade and test.
-
alejandro.sawers We are testing this new firmware version and it's working now. The problem is no longer reproducible. We will be monitoring this version and will let you know if any other problem arises.
Thanks for your support. Good work. -
Oscar Colka Glad to know this has been confirmed as a bug and has been fixed already. Thank you Alejandro for sharing this with the community. Thank you Gary, Thank you Yeastar Team. : )