Forum Discussion

JcarrMbro's avatar
JcarrMbro
Brass Contributor
Sep 18, 2023

New Teams transfer to call queue fails

We have been looking at implement "New" Teams 2.0 as we are having multiple issues with the current Teams version.

 

However, when we apply the new Teams we have found when we try to transfer a call to a CQ or AA it searches for the account fine but after selecting it changes to unknown user and fails the transfer.

 

I understand New Teams is still in development and just wondered if anyone else has been having similar issues?

  • Mikeyp1985's avatar
    Mikeyp1985
    Copper Contributor

    JcarrMbro Hi, yeah we're having the exact same issue. It's been escalated at the moment to a senior technical advisor but it's the same exact issue at our side. Essentially users, workroom phones all work fine but for any resource accounts & call queues, when attempting to transfer they just immediately fail as an unknown user.
    It's very problematic at the moment as we've had to revert back to old teams and with it we've been faced with the dreaded teams 'crackle' so for certain staff members, they can't hear callers clearly due to horrendous crackle & static.  
    Microsoft are on it but at the moment it's a bit of a nightmare for everyone involved. Here's to hoping it's all sorted ASAP! Can't believe more people have corroborated this with you.

    • JcarrMbro's avatar
      JcarrMbro
      Brass Contributor
      Mikeyp1985 Thanks for the reply! I spent 40 minutes with Microsoft support yesterday going through this and collecting various logs for them to raise internally. Hopefully push something out quite quickly.
  • hatchhozzen007's avatar
    hatchhozzen007
    Copper Contributor

    It's very problematic at the moment as we've had to revert back to old teams and with it we've been faced with the dreaded teams 'crackle' so for certain staff members, they can't hear callers clearly due to horrendous   craftsman bedroom design [link removed by admin]  crackle & static.  
    Microsoft are on it but at the moment it's a bit of a nightmare for everyone involved. Here's to hoping it's all sorted ASAP! Can't believe more people have corroborated this with you.

    • JcarrMbro's avatar
      JcarrMbro
      Brass Contributor
      Hi,
      Been asked to send SBC logs to Microsoft and also try calling a CQ/Resource account directly from my calls tab and I get the same result once the call is started.
      • nadine365's avatar
        nadine365
        Copper Contributor

        JcarrMbro 

        We still have this problem today. The receptionist switched today to new Teams and couldn't transfer a call to a callqueue number.

  • Marco_Grubits's avatar
    Marco_Grubits
    Copper Contributor
    Since the transition to Teams 2.0 we've been experiencing similar issues. Inbound calls to a CQ can't be transfered, we keep encountering a "Transfer failed" message. Does anyone have any updates on this?
  • DBJ1966's avatar
    DBJ1966
    Copper Contributor

    JcarrMbro 
    has there been any resolution from MS related to this issue?  I see a lot of talk on this thread about MS reviewing logs but no one has posted a resolution.  We are experiencing this exact issue with users and it is a HUGE problem.

    • JcarrMbro's avatar
      JcarrMbro
      Brass Contributor

      DBJ1966 Hi, we have had multiple updates to Teams since this and we no longer have the issue with transferring calls to CQ's.

Share

Resources