Don’t Just Talk… Video! Get the New iOS App

[paurus]

Hi Paurus
Just tried this right now, forwarding rules seems to be followed properly. Are you sure you configured this for your current status? I mean, this is a setting per Available, Away, Do not disturb etc)

Yes, if my number is busy, the call is routed correctly. And if I click the "Reject" button, my phone stops ringing, but the caller still hears the "beeps" for a long time and the call is not sent anywhere.

 

[Vali_3CX]

If the app update was going to require a server OS update despite being a supported OS - it shouldn't have been released to the app store as the same 'app'

Believe me, we've analyzed this on all sides. Several times. Why do you think we rolled out this version after seven months? Apple made one fundamental change in their app requirements: when client receive VoIP Push, it should present the user the callKit interface. And that involved for us PBX changes. We were at SP3 at that time, we figured out we cannot do for SP4 so we made it for SP5. But we had to! Apple then announced starting with November they will stop supporting HTTP 1.0 communication with its APNS server, so the PBX was forced to implement HTTP 2.0. Because of that, we figured out not all platforms supports HTTP 2.0, so we had to announce some machines will need to be upgraded too.

 

[Vali_3CX]

Yes, if my number is busy, the call is routed correctly. And if I click the "Reject" button, my phone stops ringing, but the caller still hears the "beeps" for a long time and the call is not sent anywhere.

I'm sorry, Paurus, I'm not able to reproduce it, here everything is working OK, I've tried even an extenal call routed through a DID to my extension - it's OK. Let's see tomorrow our test dept to check it properly.

P.S If the caller hears the beep for a long time, it should repect also your Forwarding Rule's for "Unanswered Calls" "No Answer Timeout", which probably is 60 secs, try to lower it and see then if the call goes where you configured it to.

 

[paurus]

P.S If the caller hears the beep for a long time, it should repect also your Forwarding Rule's for "Unanswered Calls" "No Answer Timeout", which probably is 60 secs, try to lower it and see then if the call goes where you configured it to.

No, it doesn't follow this route. But if I don't answer the call, it goes the right way.

 

[Vali_3CX]

@azarett
One more thing, to see how Apple things works and how you can be required to grab from your wallet a couple thousands - it's a real story, happened to me twice:
- you tell me "ios client not working on my iOS XXX.3.1" I'm checking my test iPhone, it's still on XXX.3.0, 3.1 occured overnight, so I'm updating. Nice. I'm plugging it into my development Mac to check it via Xcode. Taddaam! Xcode says "your iOS version is too recent, need to update Xcode". OK. Going to Apple, downloading 7 GB Xcode, trying to install. Tadaaam! Xcode installer says "your MAC operating system is too old, need to update your MAC OS". OK. Going to Apple to update my Mac OS. Tadaaam! AppleStore says "sorry, your MacBook is an older model, please buy a new one". How much did cost to upgrade from iOS XXX.3.0 to iOS XXX.3.1?

 

[paurus]

I'm sorry, Paurus, I'm not able to reproduce it, here everything is working OK, I've tried even an extenal call routed through a DID to my extension - it's OK. Let's see tomorrow our test dept to check it properly.

The problem was found. I have a setting in WebClient "browser Extension". When I click the red "cancel" button on my Iphone, webclient keeps calling. You need to click the "cancel" button in it, and then the call goes along the route. Or choose "smartphone" in webclient. Then everything works as expected.

 

[ITSteve]

We do blind transfers. Based on above we have this workaround for now:

• Tap Transfer
• Tap Blind Transfer
• Press the Magnifying Glass on the bottom left below the *
• Find the person to transfer to and tap to dial them

In the previous app version, in step 3, we pressed the Status icon, and still prefer this option because the list of extensions is much shorted than all our contacts and is faster to navigate.
The android app still allows the use of the Status icon to transfer.

On the iPhone app if we select Status instead of the mag. glass the caller does not get transferred and we cannot pick the call back up.

Update: When using the Magnifying glass to search we get multiple results for many of the staff, and it is not evident which one is their extension. The switchboard operators have resorted to printing out a list of the extensions and transferring them by entering the extension. Seems like a step backwards.

This should go without saying, but the status page also provides the user's status which is helpful when transferring...

 

[Kobo Williams]

I'm on the latest versions of the iOS 3cx App, Debian 9 and currently am on 3CX version 16.0.612. updates and calls are not working with PUSH to iPhones. This is horrible. Having users come in and not be able to receive calls is very bad. I'm a big fan of 3CX, and I cannot believe someone did not test this with a Debian server and not notice this glitch before rolling it out.

 

[azarett]

Ugh... woke up to people complaining their iPhone app doesn't work since our install never prompted us for the version 5 update (didn't realize it was a thing). Our install only had "v16 Update 4A" which I assumed was "Alpha" do to the blog post linking to https://www.3cx.com/blog/releases/hotfix-chrome/.

Looks like I'll be updating tonight.

Yup. Same boat.

 

[azarett]

Another failure of 3cx to communicate to communicate DATES not generalizations of "Soon" or "in the future" before breaking functions, yay. Guess my Exchange migration can wait while i deploy, patch, harden and test a new server. Nothing like coming in to pissed off people that can't make calls.

Yup.
But its our fault... We should expect the software to evolve, and know to login and read the forum once a month to maintain core product functionality.
We are a 24/7 operation. All of our staff is working from home. many from iPhone.
I guess I'm lucky - 2 users auto updated the app and brought to my attention it no longer rang.
Never thought a client app update was going to force me to upgrade a still supported server OS.

Several other customers with Avaya IP office - guess what there phones did today that mine didn't - They rang.

 

[N_G]

"I'm on the latest versions of the Debian 9"

If you would let 3CX handle the updates then this problem would not occur. Because you changed the default setting on the 3CX ISO to download Debian updates automatically an untested update was installed. A blog post and hotfix to follow to address this but please do not change things on the operating system that is supposedly dedicated to 3CX.

 

[Kobo Williams]

That's the problem right there. If you followed 3CX instructions and let updates be handled by 3CX, this problem would not occur. Because you changed the default setting on the 3CX ISO to download Debian updates automatically this problem happened.

Are you saying I should downgrade certain packages in Debian 9? Are you referring to ca-certificates or something else? I'm more concerned with a resolution at this point.

 

[NickD_3CX]

Are you saying I should downgrade certain packages in Debian 9? Are you referring to ca-certificates or something else? I'm more concerned with a resolution at this point.

Right now the best I can suggest is to sit tight, we are working on an update that should resolve the issue that was caused if the package "ca-certificates" is on version "20200601~deb9u1".


Unfortunately downgrading the package does not undo the changes the upgrade did.

 

[JohnS_3CX]

Just do what every other enterprise software supplier does, give a date. That way us piss on sys admins can schedule around it.

June 1st - the date was literally in the email

 

[nitrox]

I have been using 3cx since version 8 I think. We started reselling it at the MSP I worked for. did a couple hundred installs over the years that followed.
APN & The cell phone app have broken often for various reasons.
I now know to watch for the yearly APN cert renewal . And I make sure we update before it expires

2012 is a supported OS. I know 3cx cant control what apple or Microsoft does - but neither can I.
I cant spend my life checking the 3cx blog trying to figure out what MIGHT update next that is going to break something.

I need the product to work, and as long as its on a supported OS I need it to work without worrying about it / the app / the IOs version / the server os / the APN cert /
Now I have to build a new box and take a downtime to move 3cx just because some of my users auto-updated the client app. I shouldnt have to worry about that.

If the app update was going to require a server OS update despite being a supported OS - it shouldn't have been released to the app store as the same 'app'

You are right but if you think so you should change to use smartphone and go back using just ip deskphones or ip dect phones. When you start to use smartphone for voip 3CX doesn't have power in that and they need to follow the path. Instead i think that 3cx took too much time to implement this feature (i mean HTTP/2). If i am correct http/2 for push is working since 2015. But i am not sure 100%.
Anyway your point of view is good to discuss.

 

[MMDTerry]

June 1st - the date was literally in the email

What email? To your partners? good for them, I never got one so that still does nothing for end users.

 

[NickD_3CX]

What email? To your partners? good for them, I never got one so that still does nothing for end users.

No, the email end users received. You also received this on the 14th of May like my colleague John mentioned in an earlier post.

 

[MMDTerry]

No, the email end users received. You also received this on the 14th of May like my colleague John mentioned in an earlier post.

Nick, i have not received a single email about this. I thought blog post were the official channel updates? Do i need to sign up some where?

 

[NickD_3CX]

Nick, i have not received a single email about this. I thought blog post were the official channel updates? Do i need to sign up some where?

I've sent you a PM.

 

[JohnS_3CX]

Hello Everyone

We have an official update out now that should address the iOS Push Issue.
It should appear in your management console shortly.