Why don’t you report this as an issue so we can look into it. Please open a commercial support issue. By rolling back you’ve now messed up your Zulu version if you ever upgrade again. You’ll have to reset the Zulu data otherwise you’ll have issues. For this reason we don’t advise rollback on Zulu but instead encourage opening support issues.
I say report this as a bug because you say it seems buggy and you have cpu issues but Zulu is very complex. A bug couldn’t be formulated on such sparce data. So if you could do us a favor and report this we could get to the bottom of it
You did supose we have not reported the issue, and you are wrong. Getting commercial support sometimes it takes too long, and the problem we are suffering is critical enough to downgrade Zulu version. We make hundreds of calls in a few minutes, and calls quality is not good enough to talk to anyone because of this issue.
Anyway, two ours after we downgraded it, we received a message from sangoma advertising the origin of the issue was detected and reported to R&D team. Issue still persists so we couldn’t operate with this version on a production machine.
So… if we have to return back again to v3, you advirtise we have to reset the Zulu data. What do you mean? What do we have to do? I wil appreciate any information about this,
Well, now it’s time to upgrade the PBX again to Zulu3. As I mentioned before, I had to downgrade the PBX because of an stability issue we suffered due to Zulu3 upgrade from Zulu2. We have about 120 extensions and 100 of them uses zulu, mostly for clic to call and chat.
So, I have cloned the PBX with a nwe deployment ID, tried to upgrade the allready downgraded zulu and I got the expected errors. This is what I got:
An exception occurred while executing ‘ALTER TABLE zulu_tokens ADD PRIMARY KEY (websocket_session)’:
I’ve tried Zulu2 either Zulu3, and it works, but I found and strange behaviour with the user passwords. I’ve been trying lots of times to log in zulu client and I got a reachment error. Even tried to lig in into UCP and it worked perfectly. Finally, I had to create a new user password, and now it works.
So, is there any consideration with user passwords? DO I have to create nuew ones for everyone?