FaxOut API - 503 Service Unavailable

Question

question

patrick-thomas1477 asked Mar 23, '16 charles-zink4125 commented Jan 13, '17

FaxOut API - 503 Service Unavailable

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?

topic-default

1

1 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

John Wang ♦♦ commented · Mar 24, 2016 at 04:09 AM

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.

1 ·

Answer 1 · 2016-03-23T21:00:42Z

patrick-thomas1477 answered Mar 23, '16 John Wang commented Jul 5, '16

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>

1

1 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

John Wang ♦♦ commented · Mar 24, 2016 at 04:23 AM

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

0 ·

Answer 2 · 2016-03-23T21:43:53Z

patrick-thomas1477 answered Mar 23, '16

I am using .Net's HTTP WebRequest and HTTPWebResponse to implement the API call. I hope this is enough information.

1 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Answer 3 · 2016-03-23T22:21:46Z

paul1525 answered Mar 23, '16 paul1525 commented Mar 24, '16

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.

2

1 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

patrick-thomas1477 commented · Mar 23, 2016 at 10:47 PM

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?

0 ·

paul1525 commented · Mar 23, 2016 at 10:58 PM

We're hoping that this is a simple fix from RingCentral but they haven't yet provided an update to this thread.

0 ·

Answer 4 · 2016-03-23T23:08:22Z

paul1525 answered Mar 23, '16 benjamin-dean commented Jan 13, '17

Pretty sure that this might have something to do with it: https://success.ringcentral.com/articles/RC_Knowledge_Article/8778?priority=10&retURL=/apex/RCSup...

2

1 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

patrick-thomas1477 commented · Mar 24, 2016 at 02:16 PM

Fantastic! Thank you both very much! This solved my problem!

0 ·

benjamin-dean commented · Mar 24, 2016 at 03:10 PM

Glad you're up and running again.

0 ·

Answer 5 · 2017-01-13T01:52:06Z

charles-zink4125 answered Jan 13, '17 charles-zink4125 commented Jan 13, '17

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?

2

1 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

John Wang ♦♦ commented · Jan 13, 2017 at 02:57 AM

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.

1 ·

charles-zink4125 commented · Jan 13, 2017 at 04:12 PM

Hi John,

This issue is no longer impacting us. Thanks!

0 ·

question