Realtime is not refreshing / streaming in my browser
Realtime is not refreshing / streaming in my browser
First step, and the easiest, would be to run the realtime link on from a different network (guest wifi, disconnect from VPN, etc)orTry using a different browser (Chrome, FireFox, Edge, Safari, etc).
Technical Information for IT staff and Network Admins
WebSockets:
Our player uses an HTTPS WebSocket connection between the player page and our server (port 443). The actual request for the Websocket connection will be in this form:wss://text.speche.com/ws.aspx?Bytes=0&EventID=dcd1a536-c3b7-4b12-a3f4-612d6ff5bb6cHave the IT people, within your network, try the following link, and note the time.If the IT people receive a live feed, then you know that connectivity is being blocked by network permissions (vs explicit WebSocket rules).Else…If the IT people, like you, are loading the transcript history and then told to Re-Connect:· In the browser of choice, open the Network monitor and refresh the page.· Look for / scroll to this request ws.aspx?Bytes=0&EventID=5ebeed36-cf78-424a-be18-a69f8e394999 (method GET, domain text.speche.com).· Note the status of the request.· Click on the request and copy the response / response headers.· Send the status and response / response headers, along with time(s) of the test(s) to support@courtroomconnect.com.The status and response header information may also be useful to your IT staff looking at the WebSocket rules being applied to your network.We can use the time(s) to determine whether the requests are reaching our server and what form they are in, upon arrival.Our server will only issue the following HTTP response codes 101, 200, 400, and 404.Any other HTTP response codes would be issued by your network security.
If you are see a 404 Response Code:
There are only a few ways to get a 404 response when making the WebSocket connection request over HTTPS.
They are listed in the order of likelihood.
1. Network Security is blocking the (wss://) request and it is returning the 404.
a. WebSocket connections are not enabled. It may be necessary to enable WebSocket connections for the current network security configuration.
2. Network Security is re-writing the HTTP Request Headers and our server is retuning the 404.
a. Allow the unmodified HTTP Requests Headers on requests made to text.speche.com
3. Network Security is restricting domain access and is returning the 404.
a. Add text.speche.com to the list of accessible domains.
The Response Headers can help determine the solution to pursue.
To view the Response Headers:
1. Open the developer tools / web console in your browser.
2. Click on Network.
3. Refresh the player page.
4. Find and click on the WebSocket connection (ws://text.speche.com or ws.aspx?....).
If there are no Response Headers, then the likely issue is #3 (but possibly #1…).
If the Response Headers match the 404 from our server, then the likely issue is #2.
Text Broadcaster (our server) has one 404 response, that appears as follows:
HTTP/1.1 404 Not Found
Date: Mon, 08 Jun 2020 14:37:17 GMT
Content-Type: text/plain
Connection: Close
If the Response Headers are different from above, then the likely issue is #1.
Depending on the device or software in use, we may be to point them at the right spot in their product documentation.
Whitelists:
In addition, the following resources are utilized, if your team prefers to do a blanket whitelist:(end user authentication to our infrastructure) remotecounsel.com - 52.204.253.245
(reporter's connection to our transcript server) captions.speche.com - 107.23.27.177
(end user connection to our transcript server) text.speche.com - 107.23.27.203 (this likely is what's not working properly for you)
This one might not be necessary, but may as well speche.com - 107.23.28.82