Can someone at Sangoma kindly explain to a paying customer how to manage a painless upgrade if the licenses can’t be transferred without deactivating the old instance?
I’m planning an upgrade from version 15 to 17. I don’t intend to restore a backup, so we activated a new instance and installed version 17. The Endpoint Module can’t be configured without repurchasing it (!!!) on the new instance. The same goes for Sangoma Connect. We can’t simply transfer the ID from the old instance to the new one because everything would stop working, and we’d also no longer be able to access the data on the old instance. Has anyone thought of this? Isn’t it possible to have a full trial license for at least 30-90 days to allow for a painless migration?
It would actually be really helpful if the staff would address this issue.
I don’t understand why a migration process wasn’t considered when purchasing thousands of dollars in licenses, especially when restoring a backup from 15 to 17 only creates problems.
Aside from the customer’s imaginative processes to overcome the problem, what is Sangoma’s official position?
The migration process is different, and we are discussing some improvements, particular with EPM transitions. However, if you are running two concurrent systems, both with commercial module licenses, then, generally, you need twice as many commercial module licenses, especially for extended periods of side-by-side operations.
There was a webinar last month about upgrading to 17, with some 15 → 17 licensing issues discussed around minute 49, although it is probably not exactly what you are looking for:
No, no, that’s what I’m looking for, and I’m perplexed when Sangoma talks about simply doubling the licensing costs. If a customer has spent $20,000 in a year, the proposed solution is to double the costs.
I’d honestly like to hear from someone at Sangoma.
This isn’t always correct; in fact, it’s just asking for problems, especially with thousands of extensions. Migration should be simple and painless, especially when the obstacles aren’t technical but rather created by licensing policies that seem to be managed without considering IT and not just financial aspects.
I’d suggest talking to your sangoma rep and see about getting a temporary deployment with a 30-60 day trial of the licenses you need, then swap out the old “main” deployment ID once the migration is complete.
