Showing posts with label DNS. Show all posts
Showing posts with label DNS. Show all posts

Tuesday, February 25, 2014

Rogers One Service

Error
Please check your internet connection, and/or verify that your firewall security software is set to allow the web phone to establish a connection. If you are still experiencing difficulty, please contact technical support at 1888-Rogers1
error EB503

If you are getting the following error on your rogers one service when you try to login it's a DNS issue.

After wasting my time with rogers support i just decided to change the DNS to googles DNS servers (8.8.8.8)  and see what happens. Like magic the service works. This issue might be on some of rogers DNS servers which have not been updated recently to reflect changes in www.rogersonenumber.ca portal.

Initially thought it was rogers just blocking my ip because I was able to establish a vpn tunnel and get the service to work. This probably worked because once I established the vpn tunnel I was using the remote dns settings.

Thank you rogers!


Friday, October 9, 2009

Asterisk SIP Channel Driver & DNS - it's broken!

One of the most frustrating things about Asterisk is that it can't handle simple problems. These are problems that you would think have been solved by now. I'm talking about DNS issues and the SIP channel driver.

You would think that if your internet connection went down that you would only lose your VOIP trunks or remote extensions. Well think again! When you lose the internet or better yet DNS access your Asterisk SIP Channel driver comes to a halt. That means that your local SIP extensions will also not work. In fact a lot of things just seem to halt until your internet or DNS is functioning again.

Why is this happening? Certain things should time out! My local SIP extensions and local SIP gateway should still work. I expect the internet to go down - I expect DNS resolution failures. I don't expect that after all this time the SIP channel driver is still broken.

I've looked in the Asterisk mailing list and this has been pointed out many times before - nobody wants to fix this.

I have developed ways around this that don't require code changes but this is something that should be fixed at the root cause.