PBXact Cloud - 3rd month in a row of expired licenses

Commercial Modules
1

I am posting this here in hopes that someone from Sangoma will see this.

We are on PBXact cloud and love it most of the time, but have had an unfortunate experience for what is now the third month in a row. For three months now, every 27th, I have to submit a ticket for support to activate the commercial modules again. When this happens, it breaks most of the GUI, and it breaks ALL paid modules, until support “fixes” it.

I have a good feeling it is related to Avoid walking the plank with expired modules but because I don’t have console access, I have no way of checking.

Please Sangoma–fix this. (And before anyone responds that I should take this up with Sangoma support. Don’t worry. There is an active ticket…)

2

Experiencing this issue right now with a clients PBXact, was working fine this weekend till today.

Only thing that shows expired is the POMP.

Do you know what command they are running in the console?

4

I went back to my old tickets and apparently I said this last month:

I was able to use the API to run mutation { updateLicence(input: {}) { status message transaction_id } } It looks like it has cleared the license issue.

(Although I have not ran this yet this month in hopes that Sangoma Support will fix it instead. Warning: When I ran the UpdateLicence it also wiped the OEM module which made the interface look like regular Freepbx. Not a big deal and support was able to reinstall the pbxact skin but your mileage may vary)

5

Hi @shane8johnson and @EagleCrosstalk - I’m looking in to this. Please stay tuned.

6

Still working through this - just wanted to give you a heads up.

7

@mwhite I got a reply that the ticket was completed/closed so I assume all is good and next month I won’t have this issue again? :slight_smile:

Thank you for getting some traction on this. I really appreciate it.

8

Sorry about that – still trying to get to the bottom of it. I know @tmilbrand is also tracking this.