Had a serious problem after upgrading to version 30.14.0.67.
The pbx is totally unreachable and the only solution was to perform a reset and to downgrade to the previous version 30.14.0.23 :
https://support.yeastar.com/hc/en-us/articles/115015984887-How-to-Perform-Reset
I don't have the same issue. Have you reported it to Yeastar? Maybe some other users have the same issue？
Hello Riddhe ,
yep I've reported to Yeastar and will be solved soon. Someone else had another issue :
https://support.yeastar.com/hc/en-us/community/posts/360051270254-Avoid-v30-14-0-67
Also, Fax2Email is still not working, at least for me.
We just upgraded as well and our SERIOUS issue is that now when you click on the "Maintenance" button, no maintenance window comes up. Without access to that, how are we supposed to downgrade? Further, it will probably require us to physically go to our servers offsite and connect to them.
Same problem on our S20 with the non responding "Maintenance" icon as Jeff Justice reported.
When I perform a system reset as described in the link above "How-to-Perform-Reset" and all configuration settings are wiped and reset to factory settings, who will guarantee me that after the reset the "Maintenance" icon is responding again by opening a window and allowing me to downgrade to the previous firmware? I assume that the non responding "Maintenance" bug is caused by the new firmware and not by the old configuration settings.
Elvis Havale, exactly how did you downgrade to 30.14.0.23?
1. Switch Off the pbx
2. Press the reset button on the device panel before power on.
3. Then power it on and keep pressing more than 5 seconds after power on.
4. Enter the default IP (192.168.5.150) and you will see this page :
4. Upload firmware 30.14.0.23 (http://image.yeastar.com/Yeastardownload/30.14.0.23.bin) and wait to finish.
Ps:
It's really important that you connect the LAN port of the S-series (not the WAN) during the downgrade.
I should also note that I have been going around and around with someone at Yeastar who basically is saying they don't see the problem on their end, I can't give them direct access to the PBX because we disallow unknown IP's and I can't reach the maintenance page to change the access.
I believe (hope) that I have been backing up to the SD cards on my two systems daily because they will be a NIGHTMARE to recreate all the customer prompts and recordings otherwise.
My plan and question at this point is this: As it appears phone service is not affected on my systems, I am going to travel to our data center tomorrow evening and try to make a backup of the SD cards. Does the PBX have to be powered down to pull the SD cards, or are they hot-removable? I had planned to pull the SD cards and copy them to a folder on my laptop in case the downgrade doesn't go as planned.
I would also like to dispel the idea that this is isolated to just me, as I have two S20's with different configurations that essentially got bricked in exactly the same way by this firmware update.
I had the maintenance issue as well, but it came back. I do not recall what fixed it, but it was either a reboot of the system or using a different browser or clearing the cache. It was on an S50 that was a brand new install. The other systems I have, have not experienced the issue.
Curious how you were able to do a reboot or a proper shutdown without having access to the maintenance screen. I will have to literally pull the plug.
As stated, I do not recall exactly what brought it back, but as it was a new install, I had no cares about a corrupted config in the event of a power loss and unless you have a perpetual power source, sooner or later the PBX will experience a power interruption.
I also assume that you could go to Network, Service and enable SSH and then putty into the device and reboot from there if so desired.
Jeff Justice, I have ever encounter similar issue, but it was not on this version. I fixed by clean the cache of my browser and re-login the web GUI.
Yeastar's R&D team is really fast.
New firmware has arrived :
Firmware Version: 30.14.0.73
Release Date: 2020-11-17
[Improvements and bug fixes]
- Fixed CDR and Recording issue: If you selected specific extensions for Allow to Check and Download permission, the permission setting would not take effect.
- Fixed the Call Transfer issue: When an inbound call reached a ring group and was transferred directly to an extension, the system didn't route the call to the No Answer destination after ring timeout.
- Fixed the Call Forwarding issue: If Billing App was enabled, call forwarding to an external number could not work.
