Missed call in Outlook for EVERY Teams call

%3CLINGO-SUB%20id%3D%22lingo-sub-341971%22%20slang%3D%22en-US%22%3EMissed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-341971%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20seems%20to%20be%20an%20issue%20affecting%20our%20entire%20organisation%20following%20the%20most%20recent%20update%20in%20Teams.%20Every%20call%20made%20in%20Teams%20(internal%20only)%20registers%20as%20a%20missed%20call%20email%20in%20Outlook%20regardless%20of%20whether%20the%20call%20was%20actually%20answered%20or%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20causing%20a%20massive%20headache%20as%20people%20are%20returning%20calls%20thinking%20they've%20missed%20another%20call%20from%20somebody%20that%20they%20have%20recently%20spoken%20to%2C%20only%20to%20find%20that%20the%20missed%20call%20is%20from%20the%20conversation%20that%20they've%20already%20had.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20else%20seeing%20this%20issue%20in%20their%20environment%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-341971%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-400607%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-400607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F28894%22%20target%3D%22_blank%22%3E%40Paul%20Tansey%3C%2FA%3E%26nbsp%3Bthanks%20for%20the%20update%2C%20my%20ticket%20is%20still%20under%20investigation%20but%20will%20probably%20hear%20the%20same%20thing%20then.%20I%20will%20post%20back%20if%20the%20result%20is%20different.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394762%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394762%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F28894%22%20target%3D%22_blank%22%3E%40Paul%20Tansey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20is%20not%20very%20promising.%20%3A)%3C%2Fimg%3E%20They%20should%20give%20us%20an%20ETA.%20I%20will%20update%20you%20guys%20after%20I%20will%20get%20a%20reply%20on%20my%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394756%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394756%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F28282%22%20target%3D%22_blank%22%3E%40Ian%20Brooks%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20opened%20a%20support%20ticket%20and%20eventually%20got%20this%20response%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%3CDIV%3E%3CP%3E%3CSPAN%3EI%20have%20just%20received%20an%20update%20from%20our%20engineering%20team%20that%20this%20behavior%20happens%20because%20the%20UM%20does%20not%20recognize%20that%20the%20call%20has%20been%20answered.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20fault%20has%20been%20recognized%20and%20will%20be%20improved%20with%20the%20upcoming%20updates.%20%3C%2FSPAN%3E%3C%2FP%3E%3C%2FDIV%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394754%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394754%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20happening%20to%20us%20also.%20Microsoft%20support%20is%20clueless.%20Anybody%20had%20any%20success%20on%20finding%20a%20root%20cause%20or%20a%20fix%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3EAlex.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389693%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389693%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here%2C%20but%20haven't%20opened%20a%20ticket.%20I%20have%20heard%20this%20from%20a%20few%20users%20in%20the%20last%20several%20days.%20Anyone%20hear%20anything%20back%20from%20support%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377711%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377711%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here.%20Have%20a%20MS%20support%20ticking%20for%20this%20problem%2C%20still%20under%20investigation.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357873%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357873%22%20slang%3D%22en-US%22%3ESame%20here%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-357688%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357688%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20the%20same%20issue%20in%20our%20organization%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356567%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356567%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20seeing%20the%20same%20thing.%20We%20have%20a%20ticket%20open%20with%20support%2C%20but%20no%20resolution%20so%20far...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-344333%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-344333%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20actually%20I%20have%20been%20getting%20those%20lately%2C%20and%20was%20meaning%20to%20complain%20about%20it%20to%20the%20relevant%20folks%20but%20I%20guess%20it%20skipped%20my%20mind.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-408873%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-408873%22%20slang%3D%22en-US%22%3EIn%20our%20org%2C%20this%20only%20affects%20users%20with%20Exchange%20Unified%20Messaging%20enabled%20AND%20Enterprise%20Voice%20Telephony%20in%20Skype.%20Something%20to%20look%20into.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-414350%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-414350%22%20slang%3D%22en-US%22%3E%3CP%3EI%20received%20this%20update%20today%20however%20I%20am%20not%20too%20sure%20about%20this%20explanation%2C%20any%20thoughts%20on%20this%3F%20We%20have%20a%20hybrid%20environment%2C%20why%20can%20Teams%20not%20use%20this%20known%20sip%20adres..%20I%20also%20was%20told%20that%20this%20is%20working%20as%20designed%20and%20that%20there%20are%20no%20planned%20updates%20or%20changes%20being%20made.%20Was%20given%20the%20tip%20to%20make%20a%20uservoice%20for%20o365%20features%20and%20rally%20the%20community%20for%20any%20changed%20on%20this%20behavior%2C%20sigh.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Your%20users%20receive%20missed%20call%20notification%2C%20because%20they%20are%20located%20in%20on-premise%20Skype%20for%20Business%20server%2C%20and%20you%20are%20using%20Teams%20in%20Island%20mode.%20When%20a%20Teams%20call%20is%20made%2C%20it%20also%20tries%20to%20contact%20the%20online%20Skype%20for%20Business%20sip%20address%20of%20the%20Skype%20for%20Business%20on-prem%20user%2C%20and%20is%20unable%20to%20contact%2C%20as%20online%20Skype%20for%20Business%20for%20that%20user%20does%20not%20exist.%20You%20can%20see%20details%20of%20this%20coexistence%20in%20this%20article%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Feur02.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fmicrosoftteams%252Fcoexistence-chat-calls-presence%2523federated-routing-for-new-chats-or-calls%26amp%3Bdata%3D02%257C01%257C%257C4619de0312194f5c4cfd08d6bc1def51%257Cafca0a52882c4fa8b71df6db2e36058b%257C0%257C0%257C636903234109823115%26amp%3Bsdata%3Dcbjcu0j433kvo9xbJ5q7YscymtUyhvUtsOz2d2FjiNQ%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcoexistence-chat-calls-presence%23federated-routing-for-new-chats-or-calls%3C%2FA%3E%26nbsp%3Bin%20Table%202a%3A%20federated%20new%20chat%20or%20call%20routing%20to%20an%20Islands%20recipient.%20If%20you%20want%20to%20stop%20receiving%20missed%20call%20notifications%2C%20you%20could%20migrate%20your%20users%20to%20Skype%20for%20Business%20Online%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-427394%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-427394%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F304559%22%20target%3D%22_blank%22%3E%40Alex_vd_Heide%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20seems%20like%20a%20very%20probable%20root%20cause%20but%20the%20solution%20they%20provided%20is%20unacceptable%20if%20you%20ask%20me.%20They%20need%20to%20fix%20this%20without%20forcing%20you%20to%20migrate%20your%20SfB%20users%20to%20SfBO.%20In%20the%20end%20if%20you%20are%20using%20islands%20coexistence%20mode%20you%20should%20be%20able%20to%20use%20cloud%20voicemail%20with%20SfB%20hybrid%20for%20both%20on%20prem%20and%20in%20the%20cloud%20users%20and%20this%20shouldn't%20affect%20how%20Teams%20work.%20That%20is%20the%20whole%20idea%20of%20the%20islands%20mode.%20I%20understand%20the%20limitations%20when%20it%20comes%20to%20federation%20in%20this%20scenario%20but%20that%20shouldn't%20affect%20voicemail%20and%20missed%20calls%20notifications%20being%20send.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlex%20can%20you%20please%20share%20with%20me%20in%20a%20private%20message%20your%20case%20number%3F%20I%20want%20to%20run%20it%20through%20my%20Microsoft%20contacts.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3EAlex.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-550960%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-550960%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeems%20that%20Microsoft%20fixed%20this%20now.%20Even%20cloud%20voice%20mail%20is%20working%20fine%20for%20both%20SfB%2FSfBO%20and%20Teams%20in%20a%20hybrid%20environment%20with%20islands%20coexistence%20mode.%20And%20no%20more%20missed%20call%20notifications%20for%20accepted%20calls.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3EAlex.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-553137%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-553137%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56318%22%20target%3D%22_blank%22%3E%40Alexandru%20Zamfir%3C%2FA%3E%26nbsp%3Bconfirmed!%20thanks%20for%20pointing%20this%20out!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-563075%22%20slang%3D%22en-US%22%3ERe%3A%20Missed%20call%20in%20Outlook%20for%20EVERY%20Teams%20call%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-563075%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20confirmed%20that%20it%20works%20now...%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

This seems to be an issue affecting our entire organisation following the most recent update in Teams. Every call made in Teams (internal only) registers as a missed call email in Outlook regardless of whether the call was actually answered or not.

 

This is causing a massive headache as people are returning calls thinking they've missed another call from somebody that they have recently spoken to, only to find that the missed call is from the conversation that they've already had.

 

Is anyone else seeing this issue in their environment?

16 Replies
Highlighted

Yeah, actually I have been getting those lately, and was meaning to complain about it to the relevant folks but I guess it skipped my mind.

Highlighted

We're seeing the same thing. We have a ticket open with support, but no resolution so far...

Highlighted

We are seeing the same issue in our organization as well.

Highlighted
Same here
Highlighted

Same issue here. Have a MS support ticking for this problem, still under investigation. 

Highlighted

Same here, but haven't opened a ticket. I have heard this from a few users in the last several days. Anyone hear anything back from support on this?

Highlighted

Hey guys,

 

This is happening to us also. Microsoft support is clueless. Anybody had any success on finding a root cause or a fix? 

 

Kind regards,

Alex.

Highlighted

@Ian Brooks 

We opened a support ticket and eventually got this response:

I have just received an update from our engineering team that this behavior happens because the UM does not recognize that the call has been answered. ​

This fault has been recognized and will be improved with the upcoming updates. ​

Highlighted

@Paul Tansey 

That is not very promising. :) They should give us an ETA. I will update you guys after I will get a reply on my case.

Highlighted

@Paul Tansey thanks for the update, my ticket is still under investigation but will probably hear the same thing then. I will post back if the result is different. 

Highlighted
In our org, this only affects users with Exchange Unified Messaging enabled AND Enterprise Voice Telephony in Skype. Something to look into.
Highlighted

I received this update today however I am not too sure about this explanation, any thoughts on this? We have a hybrid environment, why can Teams not use this known sip adres.. I also was told that this is working as designed and that there are no planned updates or changes being made. Was given the tip to make a uservoice for o365 features and rally the community for any changed on this behavior, sigh. 

 

"Your users receive missed call notification, because they are located in on-premise Skype for Business server, and you are using Teams in Island mode. When a Teams call is made, it also tries to contact the online Skype for Business sip address of the Skype for Business on-prem user, and is unable to contact, as online Skype for Business for that user does not exist. You can see details of this coexistence in this article https://docs.microsoft.com/en-us/microsoftteams/coexistence-chat-calls-presence#federated-routing-fo... in Table 2a: federated new chat or call routing to an Islands recipient. If you want to stop receiving missed call notifications, you could migrate your users to Skype for Business Online"

 

 

Highlighted

@Alex_vd_Heide 

 

This seems like a very probable root cause but the solution they provided is unacceptable if you ask me. They need to fix this without forcing you to migrate your SfB users to SfBO. In the end if you are using islands coexistence mode you should be able to use cloud voicemail with SfB hybrid for both on prem and in the cloud users and this shouldn't affect how Teams work. That is the whole idea of the islands mode. I understand the limitations when it comes to federation in this scenario but that shouldn't affect voicemail and missed calls notifications being send. 

 

Alex can you please share with me in a private message your case number? I want to run it through my Microsoft contacts. 

 

Kind regards,

Alex.

Highlighted

Hi all,

 

Seems that Microsoft fixed this now. Even cloud voice mail is working fine for both SfB/SfBO and Teams in a hybrid environment with islands coexistence mode. And no more missed call notifications for accepted calls. 

 

Kind regards,

Alex.

@Alexandru Zamfir confirmed! thanks for pointing this out!

Highlighted

Also confirmed that it works now...