Version 3.4.1.81288 giving "503 service unavailable"

Mike Crow shared this problem 2 years ago
In Discussion

My Android phone using version 3.4.1.81288 started giving "503 service unavailable" when I returned home after a long absence (the date of the build is 24 August, and I haven't been home since then until now), but it works fine on other people's WiFi. My tablet, using an earlier version, worked fine yesterday on my home network. This morning my tablet updated to the same version (I use the phone version on my tablet) and now gives the same error. No changes were made to any settings in Bria or to my home WiFi network.

So, they changed a secret default setting somewhere. Anyone know what it might be?

Comments (7)

photo
1

Hello Mike,

I'd like to see an advanced log to see specifically what's causing the problem.

You can find out how to submit an advanced log here:

https://support.counterpath.com/knowledge-base/article/how-do-i-send-a-log-to-support-from-my-androidandroid-tablet

Cheers,

Graham

photo
1

Log number is BE174636. I left home at about 8 am today, so check before that.

Thanks

Mike

Sent from my Samsung device

-------- Original message --------

From: CounterPath Technical Support <ticket@counterpath.com>

Date: 15/09/2015 4:20 pm (GMT-05:00)

To: Mike Crow <mikecrow@northrock.bm>

Subject: New Comment in "Version 3.4.1.81288 giving "503 service unavailable""

photo
1

Hello Mike,

Can you please try going to your SIP account settings -> account advanced and then scroll down to the bottom to see "Custom DNS Servers" select the DNS servers option and then enter 8.8.8.8 and 8.8.4.4 for me please. These are Google's DNS servers.

Let me know if this makes any difference for you.

Cheers,

Graham

photo
1

Hi Graham,

Thanks for your reply; I’ll try that but I don’t get home again until Saturday, I’ll report back.

Regards,

Mike

From: CounterPath Technical Support [mailto:ticket@counterpath.com]

Sent: September-15-15 6:06 PM

To: Mike Crow

Subject: New Comment in "Version 3.4.1.81288 giving "503 service unavailable""

photo
1

Hi again Mike,

No worries! I'll likely see your response on Monday. This solution will likely resolve the problem, but if it does not, I'll review your response on Monday (if you try this on Sat). If it is the case that you're still having the problem after trying the strategy I mentioned, try rebooting the device and then replicate the problem again and submit a new log please.

Have a great week!

Cheers,

Graham

photo
1

Hi Graham,

I’m back home, and your suggestion has resolved the problem; thanks!

As a matter of interest, why does Bria need its own custom DNS? Every other app I have seems to manage with those automatically assigned to my phone by the WAP.

Regards,

Mike

From: CounterPath Technical Support [mailto:ticket@counterpath.com]

Sent: September-15-15 8:56 PM

To: Mike Crow

Subject: New Comment in "Version 3.4.1.81288 giving "503 service unavailable""

photo
1

Hello Mike,

The reason for using custom DNS is due to some negotiations between IPv4 and IPv6 between Bria and your WAP. By using the custom DNS, this circumvents the issue.

I'm glad that the problem is solved by using the custom DNS entries! If you have other problems in the future just open up a new topic or ticket.

Cheers,

Graham