Forum Discussion

Iron Contributor

Jul 28, 2020

Solved

New Meeting and calling experience not showing up

Greetings, The new meeting and calling experience has rolled out to our tenant. However, it will not appear for me. On my team there are 11 of us, and it shows up for all 10. If I sign into my ...

meetings

teams

tk093
Jul 30, 2020
Laggie

I booted up my computer this morning, launched Teams and BOOM, there it was!!!!

I'm glad you got it as well! I just had to be patient.

Stephan_Kaufmann

Copper Contributor

Sep 03, 2020

tk093

Same here. I assume, if you are an Call Queue agent, you lose the new experience, because there is an issue accepting incoming calls. If you try to answer a call from a Call Queue with the new experience active, call will disappear and not answered. Caller still waits in the queue.

I assume, MS has disable new experience feature for CQ agents as long as this issue hasn't been fixed.

Phil Lyle

Brass Contributor

Sep 04, 2020

I have many usere in call queues who still have the new meeting experience and several that don't. I am not sure this correct.

Nico Weber
Brass Contributor
Sep 04, 2020
Same in my environment. I have even kicked me out of all call groups, deleted my cache reinstalled teams, but still not able to activate popout meetings again.
- Stephan_Kaufmann
  Copper Contributor
  Sep 14, 2020
  Nico Weber
  
  Seems to have a relation with Phone System an Call Queue, but removing from call queu will not solve the issue. Please check post from Jelle Goossens (Rikolto) here: https://answers.microsoft.com/en-us/msteams/forum/all/my-new-meeting-experience-has-disappeared/019ab584-de8a-4294-abb9-4234f371a604?page=2
  
  Hope Microsoft solves it soon!
  - Stephan_Kaufmann
    Copper Contributor
    Sep 27, 2020
    Stephan_Kaufmann
    
    Got back new Calling and Meeting Experience.
    
    Issue with not able to answer calls from Call Queue (without conferencing mode) with an SfB certified headset (not Teams certified headset) and Media Bypass active is there again. Workaround: enable Conferencing Mode in CQ.