Forum Discussion
RDub2k4
Apr 05, 2022Copper Contributor
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. Log...
BrianC614
Apr 05, 2022Copper Contributor
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.
jsnider
Apr 05, 2022Copper Contributor
BrianC614 Agreed, I do think it's likely something Microsoft changed or it could be an issue on their side they are unaware of. My fear is they changed something on their end permanently that we now need to adapt our configuration to. RDub2k4 and I work together so we are just trying to get this hashed out because it's affecting clients of ours as well as our own office. We will keep this thread updated with any new findings. If you wouldn't mind updating us if you learn anything new it would be much appreciated!
- BrianC614Apr 05, 2022Copper ContributorI agree. Microsoft support is already trying to blame Ribbon without even looking into what may have changed on their side. They are stating that the Ribbon SBC is sending a 503 service unavailable, which is true, but the question is what changed on Microsoft's side to cause that response? Really appreciate any feedback you get from Ribbon.
- RDub2k4Apr 05, 2022Copper ContributorWaiting to hear back from Ribbon. I sent the logs and our configuration. We're getting the 500 Internal Server Error as well now. Edited our phone # and domain/IP out.
SIP/2.0 500 Internal Server Error
FROM: <sip:+Email address removed:5061;user=phone>;tag=afb0104-2ccf13;sgid=1
TO: <sip:sip2.pstnhub.microsoft.com:5061>;tag=bec5e1dda8c24ca2b3a91f1e9e1e9f20
CSEQ: 204 INVITE
CALL-ID: Email address removed.X
VIA: SIP/2.0/TLS XX.XXX.XXX.X:5061;branch=z9hG4bK-UX-0afb-0104-31a078
REASON: Q.850;cause=47;text="4b4590df-0515-49bc-9f78-253a3990c28a;Call notification"
CONTENT-LENGTH: 0
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SERVER: Microsoft.PSTNHub.SIPProxy v.2022.4.4.11 i.EUNO.12