Forum Discussion

RDub2k4's avatar
RDub2k4
Copper Contributor
Apr 05, 2022

Direct Routing and call transfers/parks failing

We have a Ribbon SBC hosted in the cloud, and nothing has changed. It's been working flawlessly for several months, and today my SBC as well as a few clients can no longer transfer or park calls. Logs are showing "SIP/2.0 480 Temporarily Not Available" when we try to transfer a call. 

 

Anyone else getting this issue today? Like I said, we've made no changes to either SBC. 

Direct Routing

21 Replies

Sort By
  • Ian Lord's avatar
    Ian Lord
    Copper Contributor
    Apr 06, 2022
    Hi All,

    We experienced same problem in our organisation. Unable to transfer external calls to internal users.
    Running SBC1000 with Direct Routing to MS Teams.

    With assistance of our SIP vendor we upgraded our SBC 1000 to firmware version 9.0.7.b619
  • BrianC614's avatar
    BrianC614
    Copper Contributor
    Apr 05, 2022

    RDub2k4 

    We are having the same issue.  We opened a ticket with Microsoft and have gathered everything they have asked for and are still waiting for a resolution.

  • PhoneGuy's avatar
    PhoneGuy
    Copper Contributor
    Apr 05, 2022
    I'm also having similar issues today. No changes, Ribbon SBC. getting a 500, internal server error from Teams. Transfers and call park fails.

    Any workaround or resolution?
    • jsnider's avatar
      jsnider
      Copper Contributor
      Apr 05, 2022

      PhoneGuy BrianC614 We are using an Azure hosted version of Ribbon SWe Lite. Are you 2 using an on-prem/azure hosted SBC? Or are you on Ribbon Connect? Have either of you contacted Ribbon Support yet? We are planning to call them shortly.

      • BrianC614's avatar
        BrianC614
        Copper Contributor
        Apr 05, 2022
        2x Azure Hosted Ribbon SBC SWe Edge (formerly known as SWe lite) 11.0.0. Literally no changes to the SBC, so it has to be a change on the Microsoft side. The SBCs don't update/change themselves! Have not contacted Ribbon, waiting on Microsoft to provide some direction, as it doesn't make sense for it to be a Ribbon issue.

Resources