Windows App - Transfer to voicemail missing since 16U5

[ProudCanadian]

Since upgrading reception is ready to kill me. In the Windows Client, in Reception View, when you right click and transfer it no longer shows Voicemail as an option. This is a VERY heavily used function for us, and trying to teach them to dial *4 and an extension she doesn't know offhand is not a viable fix for us.

Any help would be appreciated.

 

[Constantinos Constantinou]

Hello @ProudCanadian ,

Thank you for reporting this one. This is an issue that will be resolved in the upcoming version of Windows App.

 

[ProudCanadian]

Awesome, do you have any sort of an approximate ETA on that? My manager is breathing down my neck on this one for some reason, and if I can tell him something like "within a month" or "2-3 months out" it would be helpful.

 

[AWS2P]

Was it good in V16 SP4 ? if so you probably have best to restore previous version and stay waiting update until fix is out

 

[nenglish]

That's not really a feasible workaround. The new iOS mobile that launches later this month requires v16 u5.

I thankfully saved an older version of the app that still works with v16 u5. I uninstalled the new Windows app, reinstalled the old, and the transfer to voicemail is back. You'll be prompted each time it starts to update, but if you click cancel it lets you bypass the upgrade. If 3CX won't provide you with the older version send me a private message and I'll get it to you.

 

[cobaltit]

Not sure why it's not feasible? The new iOS mobile isn't released yet so it sounds very feasible. And certainly less annoying to the end users than having to ignore the upgrade prompt.

 

[nenglish]

Downgrading the 3CX server won't fix the 3CX Windows app that's already installed on every user's machine. In fact, if the new version of the Windows app requires u5 then you may completely break the app for all users.

 

[cobaltit]

Downgrading the 3CX server won't fix the 3CX Windows app that's already installed on every user's machine. In fact, if the new version of the Windows app requires u5 then you may completely break the app for all users.

No but as you said, you have the older app and already uninstalled the new one and installed the old one so I'm not sure how this applies to you. But whatever works for you. I was merely pointing out that Update 5 is not required yet because the iOS mobile is not GA yet.

 

[nenglish]

My initial response was to aws2p who suggested ProudCanadian downgrade back to v16u4 to resolve the issue with the 3CX Windows app. This isn't a good idea for two reasons:

1) The iOS mobile app is coming later this month. If they have people using the iOS mobile app they'll need to upgrade back to u5 regardless if the Windows app issue is fixed or not.

2) Even if they don't have any mobile users downgrading the 3CX server does nothing to fix the issue with 3CX Windows app.

Could you explain why you think downgrading to v16u4 is an appropriate response to ProudCanadian's issue?

 

[JohnS_3CX]

Just FYI the update is out and should allow you to transfer to voicemail.

 

[cobaltit]

1) The iOS mobile app is coming later this month. If they have people using the iOS mobile app they'll need to upgrade back to u5 regardless if the Windows app issue is fixed or not.

Correct, but you just validated my point. The iOS mobile app is not out yet, so there's no need to upgrade to or keep U5, at least for this point. So downgrading is feasible. We're talking about fixing the actual issue the OP is facing today, not a future issue.

2) Even if they don't have any mobile users downgrading the 3CX server does nothing to fix the issue with 3CX Windows app.

Correct, but as you already offered a copy of the older WIndows client (and I'm sure many others have access to it) this is also feasible.

Could you explain why you think downgrading to v16u4 is an appropriate response to ProudCanadian's issue?

I don't think I can explain it any clearer than I already did in my earlier posts and elaborated here. Downgrading is absolutely feasible. Ideal no, but feasible, yes.

 

[nenglish]

The downgraded Windows app fixed the issue even if you were running v16u5. There was literally no reason to downgrade the 3CX Server. Anyways, a fix has been released by 3CX.