How to fix Microsoft Teams SIP 486 Busy Here to Q.850 mappings in Ribbon SBC

Hi All, in this article I'll show you how to solve a very strange behaviour of Ribbon SBC EDGE (1K/2K) in a Microsoft Teams Direct Routing scenario, where the SIP Response 486 Busy Here is not correctly converted in the Q.850 Cause Code 17 in a TDM (PRI/BRI) PSTN connection How to enable Busy on... Continue Reading →

Ribbon SBC EDGE now support Teams Direct Routing behind NAT and why this is a game-changing news

Hi All, few days ago Ribbon released the new SBC EDGE (1K/2K) firmware 8.0.2. Apart from many fixes, the new firmware contains only a new feature, but it's enough because this is a game-changing news: The SBC 1000/2000 is supported behind a NAT device in Microsoft Teams Direct Routing; this feature enables the SBC to... Continue Reading →

How to change Ribbon SBC name to a routable domain for Teams Direct Routing

Hi All,in this article I'll explain step-by-step how to change the Ribbon SBC 1K/2K FQDN from a private domain to a routable domain. Problem You have an SBC 1K/2K used in a Skype for Business On-Prem deployment with a private AD Domain and you need to use it with Teams Direct Routing.Teams Direct Routing needs... Continue Reading →

How to dynamically route calls to Microsoft Teams instead of SfB with Ribbon SBC 1K/2K

Hi All, so you are implementing Microsoft Teams Direct Routing, maybe side-by-side with Skype for Business On-Prem, with a Ribbon (formely Sonus) SBC 1K/2K, and you want to improve your call routes for Teams Direct Routing.You are on the right page! Note: instead if you use AudioCodes SBC, you can read a similar guide from... Continue Reading →

How to correctly manage In-band Media and Play Ringback on Sonus SBC with SfB and Teams

Hi All, recently I managed an interesting Customer's issue, maybe the solution could help some of you. Scenario A Sonus SBC 1000 (FW Ver 7.0.2 build 485) is connected to: Skype for Business On-Prem (UC Signaling Group) Microsoft Teams via Direct Routing (TEAMS Signaling Group) analog devices connected on onboard FXS ports (FXS Signaling Group)... Continue Reading →

Diagnostic ID: 10500 and sip-reason=”Q.850; cause=44; text=”Requested Circuit/Channel N/A”

Hi all, recently one of our Skype for Business Enterprise Voice customer found many of these Unexpected errors in it's Monitoring Reports Request: INVITE Response: 500 Diagnostic ID: 10500 Category: Unexpected Component: Mediation Server Reason: Gateway responded with 500 Server Internal Error Description: This response from a gateway can occur if the gateway encountered an unexpected condition that prevented the... Continue Reading →

Blog at WordPress.com.

Up ↑

%d bloggers like this: