11-27-2018 09:36 AM
Tenant is upgraded to "TeamsOnly", with Micorosft Phone System and Calling Plans in place, and things are working for the most part, however, about 50% of the time, my users say that their iPhones running the Teams app don't ring/alert on incoming PSTN calls, but they do get a missed call notice.
I've made sure of the following:
1. the app is up-to-date
2. the app setting for "Always ring on this device even when active on desktop" is checked
3. they're not in "Do not disturb" status
FWIW, the legacy Skype for Business app for PSTN calling on mobile was equally unreliable - lots of missed calls, and Teams seems to be no different in this regard.
Is anyone else having this issue? What other things can we check to make sure calls actually ring as they are supposed to?
TIA,
Bob
11-27-2018 10:00 AM
I have this problem on my Android too.
11-27-2018 11:34 AM
11-27-2018 01:00 PM
Not really @Chris Webb. Although the new Office 365 Phone System backend first became available through SfB, it's by no means 'old' or being replaced anytime soon.
I'm not sure what @Bob Manjoney means by 'the app setting for "Always ring on this device even when active on desktop" is checked', I think you are referring to the setting for notifications? not calls.
Have your users configured Teams to simultaneous ring their mobile numbers? https://support.office.com/en-us/article/call-forwarding-and-simultaneous-ring-in-teams-a88da9e8-134...
11-27-2018 01:02 PM
11-27-2018 01:16 PM
11-27-2018 01:17 PM
11-27-2018 01:21 PM
11-27-2018 02:08 PM
11-27-2018 02:09 PM
11-27-2018 02:12 PM
Silly me to assume that the settings for Android and iOS were on parity :)
Here's the Android app notification setting page:
11-29-2018 10:48 AM
And once again - this time on Android. Incoming call never rang, but immediately displayed a "Missed Call" notification. Arghhhh….however, I am able to reproduce it reliably by doing the following:
1. Launch/login to Teams.
2. Call into Teams app from PSTN - phone rings - terrific.
Now...
3. Tap the Android Square system icon (lower-right screen corner, I believe it's called the Overview button) to display "Recent Apps".
4. Tap "Clear All" (which just removes recent apps from the list)
5. Now Try calling into the Teams app from PSTN - my Android phone never rings, but gets a missed call indicator.
11-29-2018 10:51 AM
11-29-2018 11:14 AM
Didn't you just close the Teams app when you pressed Remove All? How would it ring if you closed it? Notifications are handled by Android natively which is why you would see the indication.
11-29-2018 11:19 AM
11-29-2018 11:25 AM
Nope, it closes it.
https://www.tomsguide.com/us/close-android-apps,news-21281.html
Here’s how to kill applications running in the background.
3. Tap and hold on the application and swipe it to the right. This should kill the process from running and free up some RAM. If you want to close everything, press the "Clear All" button if its available to you.
11-29-2018 11:27 AM
11-29-2018 11:32 AM
IOS doesn't have such an issue as the operating system provides a common extensible calling integration called CallKit.
11-29-2018 11:36 AM
It may be a matter of semantics on Android, ("Closing vs. actually terminating a process"). I did a "Clear All" and in the running apps list Teams is still running, however, if I want to, from there I can do a "Force Stop". A lot of apps on Android behave this way.
11-29-2018 11:43 AM
Clear all kills off the user processes of apps, there can still be services running that a force stop is required to kill. As you clearly demonstrate, closing the Teams app in this way means it cant ring on an incoming call.
11-29-2018 11:59 AM
11-29-2018 09:28 PM - edited 11-30-2018 08:36 PM
@Bob Manjoney It looks like you have given Teams notification permissions and still didn't receive incoming PSTN calls when the app was cleared. Even if the app is cleared, you should still receive push notifications and incoming calls (unless you are DND).
I'd like to follow up on this. Couple requests -
1 - What phone are you using? (For example - Samsung Galaxy S8, Google Pixel)
2 - Try steps 3-5. If your phone doesn't ring, immediately file a bug from the Teams app > Hamburger menu icon (Settings) > Report an issue. Please drop me a message when you do, I'll make sure to follow up
11-30-2018 04:15 AM
@Debanshu SinghThe phone used in this test is an LG V40 ThinQ from Verizon Wireless in the US. Not rooted. Android and the Teams app are both up to date. I just reproduced steps 3-5 per your request and the phone did not ring, and I posted a bug report via the Send Feedback option menu.
I'm confused because your post is in direct contradiction of what user @Steven Collier has asserted.
Thanks for your attention,
Bob
12-20-2018 11:04 PM
I know it doesn't help much if I just say "we have the same problem here". But unfortunately this is the fact. We mainly use IPhones. On my Android device I have the phenomenon very rarely. I will instruct our users to use the "Report an issue" function if the error occurs.
02-07-2019 05:08 PM
I have been researching Teams for possible roll out to the organization. I registered for a trial of office 365 Enterprise E5 with 25 seats and a call plan trial and configured it exactly as it should be set up. I can make calls out to the PSTN no problem. I can call between users in Teams via the phone numbers no problem. I get missed call notice in Teams and the voicemail. I get an email in outlook with an MP3 of the voice message. EVERYTHING is working EXCEPT inbound calling from PSTN. Have had 10 MS support people on here and run power-shell commands and changed many, many settings....still no calls inbound. I got frustrated and deleted that trial organization and got another one. Set it up properly. No inbound calls from PSTN. No escalation to the gurus deep in the Microsoft Teams secret lair who can possibly fix this if it can, indeed, be fixed. Sadly I now have wasted 2 weeks and must inform the client the product is not yet ready for prime time. It is 99% there but that missing 1% is HUGE and in our case it is a deal breaker.
02-20-2019 03:37 PM
04-01-2019 07:00 AM
Any news on this topic? We are still dealing with this issue.
04-01-2019 07:07 AM