Introduction

Webview is a way for you to get alarms and mapping in realtime on a PC. For example:

Once Webview is running, your computer establishes a data connection to our servers. This allows us to send alerts in real time. Computers running Webview can:

Note: Webview doesn't provide routing. It was originally developed to be used on stationary devices.

Limitations

Webview is only for use on PC systems, not on mobile phones. Additionally, any computer running Webview must have a constant connection to the internet and be configured for always-on operation. This is very important! Once you have Webview running, we request that you do *not* close or refresh the browser unless absolutely necessary. Webview will automatically refresh the page once every 24 hours, so there should be no need to manually refresh, or use an auto refresh plugin.

Note: The reason for the restriction on refreshing your browser has to do with our license terms with Google Maps. Every time you load Webview into your browser for the first time, or reload/restart the browser window, it costs us money! We are trying to keep this service affordable for everyone, so please only close/refresh Webview when absolutely necessary.

Basic Setup

  1. Go to the Devices tab in your Active911 account, and create a new device. Set the "Page type" to "Webview"

  2. After saving, write down the Device Code from the right hand column

  3. Go to the PC that will be running Webview.

  4. Check with your IT staff to make sure that the computer won't be powered off each day. Make sure that your firewall is not blocking port 80, 443, or 5280.

  5. Ask your IT staff to check your browser. Supported browsers include:

  6. Open a supported browser, and go to http://webview.active911.com

  7. Enter the code you wrote down and click the button

  8. Webview loads after several seconds. Once loaded, go back to the first computer (the one with your Active911 account loaded) and click the test button () next to the device you created. This will send a test message to the PC running Webivew.

Settings

The gear in the top right corner is where you can access your Webview settings. There you can change the following settings:

Map Marker Density

You can change the density of the map markers, so you can see more or less of map data points at a time. The default selection is Normal.

Workflow For Sending Alerts

Webview is also a great way to dispatch alarms. Even when you don't have an actual address - sporting events or off-road locations, for example - you can click on the map and send help directly to the location of your mouse click.

If your Webview device has been allocated the "Send Alerts" capability, you will be able to generate alarms directly from Webview using the following steps:

  1. Use the Webview map to navigate to the location you want to send the alert to

  2. Use your mouse to click on the location on the map

  3. A "Send Alert to" window will appear. Enter the appropriate information into the Title, Details, and Recipients fields

  4. Click the Alert NOW button to send the alert

Note:This is especially useful for directing responders to precise locations with no address - for example, wilderness areas or points within football stadiums or fairground sites.

GPS integration

If your Webview PC is not showing up on response maps, you may need to troubleshoot the GPS. Go to the GPS troubleshooting page and follow the instructions. We need an accuracy of better than 100 meters in order to use your GPS position. If you are not getting good GPS accuracy, you may need to install GPSGate or a plugin supplied by your GPS manufacturer
Troubleshooting Webview

PuTTY.

Troubleshooting

Port Connection Troubleshooting

The number one issue that causes problems with Webview is blocked ports. This should be the first thing that is checked when trouble shooting Webview connection issues.

In order to check the ports, you will need to telnet to http://webview.active911.com using each port. A blank telnet window indicates a successful connection. If that port is not open, you will typically receive an error message that the connection was refused, depending on your telnet client.

For those unfamiliar with this process, here are directions to test with a telnet connection.

Windows command prompt- This may not be possible if your local IT has Windows options locked for your user account.

  1. Click on the Start menu and open the Control Panel.

  2. Select Programs from the options.

  3. Under Programs and Features, click on the link that says 'Turn Windows Features on or off'.

  4. In this box, scroll down and check the box for Telnet Client.

  5. Click OK and your computer should install the telnet client files.

  6. After the telnet client is installed, click the Start menu, type 'cmd' and hit enter. This will start the command prompt.

  7. In the cmd prompt, type telnet http://webview.active911.com 80 and hit enter. This should open up a blank telnet screen. This means this port has connected successfully.

  8. Repeat steps 6 & 7 for port 443 and 5280. They should also open up the same blank screens.

An alternate method to this is using a telnet client like PuTTY.

Console Logging

You can also view and record the console log for your browser window. That can often provide useful information for your IT department.

Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: only screen and (-webkit-min-device-pixel-ratio: 1.5), only screen and (min-resolution: 144dpi)
webclient.js:366 Registration successful
webclient.js:485 Starting webclient
2Active911.js:163 Adding alarm: RUN REPORT
Active911.js:163 Adding alarm: Fire
Active911.js:131 Removing alarm: undefined
Active911.js:163 Adding alarm: Fire
Active911.js:163 Adding alarm: RUN REPORT
Active911.js:163 Adding alarm: Assist Ambulance
Active911.js:163 Adding alarm: Ambulance Run
Active911.js:163 Adding alarm: RUN REPORT
webclient.js:667 Loading map
Active911GoogleMap.js:43 Zooming to 14
7Active911GoogleMap.js:371 Active911GoogleMap.device() called with existing device
webclient.js:687 Connecting XMPP
Active911Map.js:131 Zoom can now show location icons. Loading from server
Active911Map.js:194 SERVER FETCH
webclient.js:536 Command: response
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 1234567
webclient.js:779 Status change: XMPP connected
Active911Xmpp.js:273 Rejecting position with error of 883 meters
webclient.js:536 Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011
webclient.js:536 Command: unknown
webclient.js:634 Unhandled command: unknown with message: 
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 1234567
webclient.js:536 Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011
webclient.js:536 Command: unknown
webclient.js:634 Unhandled command: unknown with message: 
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 1234567
webclient.js:536 Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011
webclient.js:536 Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011
Active911XmppPing.js:14 Ping id=1419437475573 OK (326ms)
webclient.js:536 Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011
Active911Map.js:120 Zoom too far out: hiding location icons

This is what a normal, complete disconnect and subsequent reconnect looks like:

Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011
strophe.js:2554 POST https://webview.active911.com:5280/http-bind/ net::ERR_NAME_NOT_RESOLVED
strophe.js:2554 POST https://webview.active911.com:5280/http-bind/ net::ERR_NAME_NOT_RESOLVED
webclient.js:713 Ping Timeout
webclient.js:805 Reconnect called
webclient.js:784 Status change: XMPP DISCONNECTED
strophe.js:2554 POST https://webview.active911.com:5280/http-bind/ net::ERR_NAME_NOT_RESOLVED
strophe.js:2554 POST https://webview.active911.com:5280/http-bind/ net::ERR_NAME_NOT_RESOLVED
strophe.js:2554 Uncaught InvalidStateError: Failed to execute 'send' on 'XMLHttpRequest': The object's state must be OPENED.
webclient.js:818 Reconnect attempt
webclient.js:779 Status change: XMPP connected
strophe.js:2554 POST https://webview.active911.com:5280/http-bind/ net::ERR_NETWORK_CHANGED
webclient.js:536 Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011
webclient.js:536 Command: position
Active911Xmpp.js:87 MESSAGE-GROUPCHAT from agency 67891011

This error was caused by unplugging the network cable for 10 seconds and plugging it back in. This is a complete disconnect. If your system is disconnecting it should show something similar and then reconnect once the network allows it to. If it perpetually hangs there, it probably means there is a hardware or network issue that is causing this.

Additional Notes