Second location we’ve seen this happen. A fully functional system that suddenly has no info for display name or registration address in the ST module.
Note: This is an informational post for other admins having this issue. I am not going to collect data or submit bug reports; Sangoma, please do your own work on this.
I can’t; I don’t have that info. In both cases we simply applied updates as shown and later the client informed us ST was not working. Upon investigation we found those fields blank. I have no way of knowing what version of the module was upgraded from, nor can I say with ANY degree of certainty that it was the ST module update that broke things.
I mean, what’s the version you are using right now.
About what was the previous version, probably if you grep “sangomaconnect” in the /var/log/asterisk/freepbx.log it shoul tells you that there were updates available and your current version (the one you had before upgrading)
We are not your uncompensated testing department.
I’ve been very clear that whatever testing protocols you have (and I’ve asked for them to be published) ARE NOT EFFECTIVE.
I also asked that you start publishing “known issues” with updates, so we can make informed choices about updating.
You need to carry your own water, or pay us to do so. We ate $2000 in time last month alone with support floudering ineffectively on another issue. No more.
Do effective testing before you release code to users.
Fix support.
Don’t ask customers to be your free testing departments.
Chasing stuff that is already in the wild and broken is, I think, less important than those things. Again, the purpose of this post is to help others with the same issue fix it, not do free troubleshooting for Sangoma.