Hi, new forum user here, but I’ve been using VitalPBX and VitXI for about two years now as a customer service representative and a project manager. I’m only just now getting information on when our systems get software updates and I was struck by this paragraph in the blog post for this release:
Smart assumption: This post targets IT administrators and MSPs managing VitalPBX deployments. Tone is technical and practical. If you’d like a version aimed at a different audience, just let me know.
Would it be possible to see a version of the post that’s written for end users? The same day this release came out, I was having issues with dialing out and I am curious if the reason why we ran into this problem was because we hadn’t applied the upgrade. However, I’m not technical enough to understand if the fixes in the release are related to the problem I was experiencing yesterday.
Sure, for some reason whenever I dialed out to a +1 NUMBER, it would activate once and then automatically hang up. Our admin talked to our provider (I think that’s you?) and someone there said that it was because of the +1 country code not being accepted? He’s on the way to the airport now so I can’t immediately recall what he said.
However, the fact that we had an issue yesterday is not why I’m asking about a version of the blog post for folks who aren’t IT administrators or MSPs. I’m asking because as an end user, I want to be able to understand what’s changed in release versions, especially as it relates to UI and functionality.
Are you saying that outbound calling stopped working after the latest upgrade?
We experienced the same thing.
It looks like the external caller id is not being sent.
I am in the process of gathering more info.
A little different. Just before 13:54 Pacific/20:54 UTC on May 11, I stopped being able to have outbound calls connect. I had our admin take a look and he said he contacted our carrier who said the above regarding the +1 country code issue. And then he installed the upgrade, and then the problem hasn’t happened again so far.
What I’m curious about is why the upgrade fixed the problem and because I’m not technical, I can’t understand what’s written in the blog post. The post says that there’s an explanation for non-tech people and I’d like to read it.
I’m not sure how relevant our experience is because we use VitXi as our softphone and not Teams. But if how your agents describe the problem they’re having is the same as what I experienced, I can ask my admin how he resolved the problem.
Exactly what are your team members experiencing? And when did you do the upgrade?
That sounds like a very different problem than what I was experiencing. You might want to split it out into a different discussion topic if you’d like the folks from the dev team to respond.