V20 Update 9 Release Candidate 3

[MichaelB_3CX]

Last stop before final release.​

We’re rolling out RC3 to address the last minor fixes ahead of the final Update 9 release.

Fixes in Release Candidate 3​

• VoIP Provider templates - fixed an issue where switching templates could trigger an exception.
• Dialer - fixed an issue where the dialer would...

Continue reading the Original Blog Post.

 

[Evolute IT]

We seem to have a little bug with the CRM integration. We use a custom template for Bullhorn (we use concepts from the HubSpot template), and we are seeing cases where the Auth scenario output data (token + API domain in this case) aren't saved, but not always triggered in the Test window. Like it skips the Auth scenario but doesn't have the Auth tokens saved so it just crashes, as the template requires an ApiDomain provided by the Auth scenario (similar to the PortalID in HubSpot.)

Can this be checked on? It only affects U9. I feel like something changed in the backend of the integration engine and it now forgets its auth data sometimes. Seems that reuploading the template over itself (not even wiping it first) causes the "cache" to work again.

 

[Colorado VoIP]

upgraded here incident free.

 

[UCMUserAZ]

No issues. Thanks.

 

[bcarrico]

We have quite a few clients who purchased the Yealink T58W, and I'm not sure how we're going to handle communicating the EOL situation given the Android OS limitations.

To add to that, we've moved all of our customers to Hosted by 3CX this year. My understanding is that once the affected 3CX release is fully rolled out, we won't have the option to simply hold those systems back from updating.

Is anyone else facing this situation? If so, how are you planning to approach it with your customers?

I've seen comments saying that the phones will continue to function, but I'm unclear on what happens when you need to provision a replacement phone or add a new IP phone to an extension. Has anyone gotten clarification on that?

 

[Colorado VoIP]

I was looking at the structure of our onsite system and noticed something which might help you on the hosted side. the template is still on the systems it's just marked as deleted on template type. maybe you can download the template from the pre SP9 and import it as a custom template to get you by?? just a random idea until something more official is stated.

 

[JustinEdw]

We have quite a few clients who purchased the Yealink T58W, and I'm not sure how we're going to handle communicating the EOL situation given the Android OS limitations.

To add to that, we've moved all of our customers to Hosted by 3CX this year. My understanding is that once the affected 3CX release is fully rolled out, we won't have the option to simply hold those systems back from updating.

Is anyone else facing this situation? If so, how are you planning to approach it with your customers?

I've seen comments saying that the phones will continue to function, but I'm unclear on what happens when you need to provision a replacement phone or add a new IP phone to an extension. Has anyone gotten clarification on that?

We are not cloud customers but have on premise 3CX. I unfortunately have at least a pallet of T58W Phones in our warehouse we use for spares and new phones. I hadn't heard about the EOL situation with T58W till we just recently patched to try out the new version.

This is unfortunate for us we have a bunch of these in production and being we're K-12 School district we also repurpose phones yearly, so unsure how we're going to handle this.

 

[Kevin Attard Compagno]

If you are well versed in how to work with the device, then you could maintain your own custom phone provisioning template and use that for a while, and in the meantime move over to more recent supported devices. Have a quick look here: https://www.3cx.com/blog/docs/custom-phone-template-example/