FaxOut API - 503 Service Unavailable

  • 0
  • 3
  • Question
  • Updated 4 years ago
  • Answered
We have some proprietary software that utilizes RingCentral's FaxOut API. On March 22nd we experienced problems. Today I confirmed that our faxes are not reaching their destination. When I check the fax api, I receive a 503 Service Unavailable response.

Is there something I can do to resolve this? 
Photo of Patrick Thomas

Patrick Thomas

  • 60 Points

Posted 4 years ago

  • 0
  • 3
Photo of Patrick Thomas

Patrick Thomas

  • 60 Points
I just obtained the application code. It seems this is the response received from the server:

<!DOCTYPE HTML>
<html >
<head>
<meta name="Content-Type" content="text/html; charset=UTF-8">
<meta charset="utf-8">




<meta name="description" content="Upgrade to the latest version of your browser to continue. The version you are using is not compatible with the site security protocol." /><meta name="keywords" content="" /><title>Upgrade Your Browser.</title>
Photo of John Wang

John Wang, Employee

  • 278 Points 250 badge 2x thumb
This is like due to a new requirement for TLS 1.2 introduced on March 21. See KB article 8778 for more info: https://success.ringcentral.com/articles/RC_Knowledge_Article/8778
(Edited)
Photo of Patrick Thomas

Patrick Thomas

  • 60 Points
I am using .Net's HTTP WebRequest and HTTPWebResponse to implement the API call. I hope this is enough information.
Photo of Paul

Paul

  • 50 Points
Patrick, we're experiencing the same issue but just visiting https://service.ringcentral.com/faxapi.asp returns a 503 Service Temporarily Unavailable nginx/1.8.0 error.

It's a classic ASP application so upgrading it to the latest API would present quite a challenge.
Photo of Patrick Thomas

Patrick Thomas

  • 60 Points
Thank you for your quick reply.
This worked as recently as Monday, March 21st. Is restoring the existing api not an option. We were not notified of any (potential) deprecation. What are our options? 
Photo of Paul

Paul

  • 50 Points
We're hoping that this is a simple fix from RingCentral but they haven't yet provided an update to this thread.
Photo of Paul

Paul

  • 50 Points
Official Response
(Edited)
Photo of Patrick Thomas

Patrick Thomas

  • 60 Points
Fantastic! Thank you both very much! This solved my problem!
Photo of Benjamin Dean

Benjamin Dean, Alum

  • 792 Points 500 badge 2x thumb
Glad you're up and running again.
Photo of John Wang

John Wang, Employee

  • 278 Points 250 badge 2x thumb
Official Response
Paul is correct. Your error indicates that your client does not support TLS 1.2. There is information on the KB article 8778 on how to verify TLS 1.2 support for various languages. 
Upgrade Your Browser.
Upgrade to the latest version of your browser to continue. The version you are using is not compatible with the site security protocol.
(Edited)
Photo of Charles Zink

Charles Zink

  • 112 Points 100 badge 2x thumb
This reply was created from a merged topic originally titled API returning 503 Service Unavailable.

It looks like starting at 2017-01-12 0700 UTC the API has died for us. Login calls are kicking back 503 Service Unavailable. I don't see anything under service status about the issue; is anyone else being impacted by this?
Photo of John Wang

John Wang, Employee

  • 278 Points 250 badge 2x thumb
Is this impacting you now?

We had an issue affect a small number of US customers this morning PST but it was resolved 10 hours ago. If you are still being impacted, please contact Developer Support at devsupport@ringcentral.com or by opening a support case via the Developer Portal.
Photo of Charles Zink

Charles Zink

  • 112 Points 100 badge 2x thumb
Hi John,

This issue is no longer impacting us. Thanks!