Teams Phone – Voicemail Issue
So, I’ve been trying to troubleshoot an issue for a new Teams Phone deployment – where Teams phone ties into an on-prem exchange server via an MS365 Connector (which delivers the voicemails to their Email Security gateway, and then to the on-prem Exchange Server).
The issue was that transcripts for calls (and voicemails in general) weren’t showing up in the Voicemail tab for call history and voicemail notifications weren’t being received on their Yealink phones.
After diving into it I found that the content type of the Voicemail messages, at least on the Security Gateway side, was CA-Voice, and there had been some chatter online of the required Content-Type being something else.
I then tested with my work Teams account – since I noticed that I wasn’t actually seeing voicemail transcripts since August 1st, and it looks like the same issue is occuring. Office and Teams are up to date and the issue occurs on both Desktop and web-based Office.
I’m thinking that this is just a case of Microsoft breaking something in an update but if anyone has any further insight, I’d appreciate that.
– JB
So, I’ve been trying to troubleshoot an issue for a new Teams Phone deployment – where Teams phone ties into an on-prem exchange server via an MS365 Connector (which delivers the voicemails to their Email Security gateway, and then to the on-prem Exchange Server). The issue was that transcripts for calls (and voicemails in general) weren’t showing up in the Voicemail tab for call history and voicemail notifications weren’t being received on their Yealink phones. After diving into it I found that the content type of the Voicemail messages, at least on the Security Gateway side, was CA-Voice, and there had been some chatter online of the required Content-Type being something else. I then tested with my work Teams account – since I noticed that I wasn’t actually seeing voicemail transcripts since August 1st, and it looks like the same issue is occuring. Office and Teams are up to date and the issue occurs on both Desktop and web-based Office. I’m thinking that this is just a case of Microsoft breaking something in an update but if anyone has any further insight, I’d appreciate that. – JB Read More
