Updated the module on a v15 system last week and that broke it, just like what happens with in-place upgrades. After screwing with ports and firewalls and end-user devices for hours over days, we removed the SangomaConnect module entirely, re-installed, re-configured, and re-invited all the end users. That fixed it.
For the love of all that is good, PLEASE QC your updates better (at all?). This kind of thing is not tolerable.
Hello @FreerPBXer
I like to know more details like which version to which version upgrade happened and then what all kind of issues happened?
Above details will help to re-produce the issue locally and introspect to see how we can improve the QA better.
Without reproducing the issue, its hard for me to say anything.
As this is commercial module so you can raise the support ticket with all the details or share the details with me via email to [email protected] or you can share here for benefits of others to know the behavior and solution as well.
Best Regards,
Kapil