Exede blocking HTML 5 Websocket Protocol

  • 1
  • Problem
  • Updated 3 years ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members.

I use a Rich Internet Application(RIA) that utilizes a websockets communication channel. websockets is part of the international HTML5 specification.  Why do you block this protocol?  I've verified it by connecting directly to the modem using a windoze and Linux PC.  If I connect using 4G or any other wifi it works fine. 
I've also noticed its only blocked on ports 80 and 8080, the 2 most common ports on the internet.  If I connect on port 8081 all is OK, except my RIA doesn't run on port 8081.

You can test your websockets browser support and connectivity on

http://websocketstest.com/

I ask again, Why is Exede blocking the websocket protocol????

Scott
Photo of scott

scott

  • 4 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Brian Shackelford

Brian Shackelford

  • 847 Posts
  • 243 Reply Likes
Scott -

This is probably something that Exede will need to address via their networking team and most likely to do with traffic shaping or the accelnet servers and how they view / handle that traffic.  You will need to email exedelistens@viaasat.com and reference this thread as well as include your account email address or account number and contact information.

You will likely NOT get anywhere calling support, but if you do go through their troubleshooting process and request the issue be escalated to their network team.  You will also need to call back every day or so and request an update on the status.  On the initial call you may want to request to speak to a supervisor. 

The email will likely yield the fastest results, but if you do call, be polite and patient as most Tier 1 help desk folks will have very little in the way of understanding what you are asking or even what you are saying. Not a dig on the Tier 1 folks, just a fact in this instance.

Good luck.
Photo of scott

scott

  • 4 Posts
  • 0 Reply Likes
OK I forwarded the question to the email address exedelistens@viaasat.com

We'll see what happens?

I'm somewhat surprised that nobody else has noticed? 

Scott
Photo of Steve Frederick-VS1/Beam314

Steve Frederick-VS1/Beam314, Champion

  • 2796 Posts
  • 1763 Reply Likes
The correct address is exedelistens@viasat.com
Photo of scott

scott

  • 4 Posts
  • 0 Reply Likes
Well that email address was bogus.

So I am trying exedelistens@viasat.com

Scott
Photo of Brian Shackelford

Brian Shackelford

  • 847 Posts
  • 243 Reply Likes
Sorry.  That is what I get for typing in a hurry.   Glad you got through!
Photo of Brad

Brad, Viasat Employee

  • 3121 Posts
  • 1100 Reply Likes
Hello Scott,

I have received your email and will try to get some answers for you after contacting some of our engineers.

thanks
Photo of scott

scott

  • 4 Posts
  • 0 Reply Likes
Muchos Gracias Brad!  I've been working around this problem for months which is much less than satisfactory.  Hope its a simple fix.

thanks again,

Scott
(Edited)

This conversation is no longer open for comments or replies.