Why Can’t I See a Security Camera Feed in the Dispatcher View?
911Cellular can display configured security-camera feeds alongside relevant incidents or in a permitted camera view. If a camera is missing, says “No cameras found,” or shows a blank or stalled picture, the cause may be the camera's Security Zone, viewing permissions, network access, feed configuration, or the way the dispatcher is viewing the feed.
A camera appearing in the management list means a camera record exists; it does not guarantee that its live stream is accessible.
Before you startConfirm that your organization has the Security Camera feature configured and that you have permission to view the relevant incident or camera page. Ask your security-camera or network administrator to assist with camera-specific settings. Do not test live panic activations without following your organization's approved test or drill procedure.
Step 1 — Check the camera's Security Zone
1. An authorized administrator opens the portal's Security Cameras management page, under Manage Devices when available.
2. Locate the camera by name and review its assigned Security Zone.
3. Compare that zone with the zone shown on the affected panic or safety-timer event.
4. Confirm that the camera belongs to the intended location. Cameras assigned to a parent zone can appear for incidents in descendant zones, but a camera assigned only to a child zone should not be assumed to appear for a separate parent-zone incident.
5. If the incident itself is routed to the wrong zone, investigate the incident-location configuration before changing camera assignments.
Step 2 — Confirm how you are viewing the feed
• Check that your portal role and Security Zone permissions allow access to the applicable camera and incident.
• Ask your administrator whether camera watermarking is enabled. In configurations using watermarking, normal browser camera viewing is disabled; the dispatcher application is the intended viewing path.
• If your organization uses the dispatcher application, repeat the check from the approved dispatcher workstation and application rather than assuming browser behavior will match.
• If several cameras are configured, check additional pages of the camera list or thumbnails. Some views display cameras in batches.
Step 3 — Check whether the camera stream itself can be reached
1. On the authorized dispatcher workstation and network, have your IT/security-camera administrator verify that the configured camera stream is reachable.
2. Check for an offline camera, changed camera address, authentication problem, firewall or network-segmentation rule, or certificate/browser restriction.
3. Verify the feed format against the camera's documentation and the format selected in the 911Cellular camera record. Availability can differ for image or MJPEG feeds, H.264, iframe-based pages, and RTSP viewing through the dispatcher application.
4. If the record uses a static image rather than a continuously updating video stream, ask the administrator whether “Refresh image on interval” is configured appropriately.
5. If the feed works in the camera's own system but not in 911Cellular, record the difference in viewing device, network, app/browser, authentication method, and stream type.
Security note: Do not include camera usernames, passwords, credential-bearing URLs, or unrestricted live-feed links in a support ticket or screenshot. Work with IT and 911Cellular Support on an approved secure method for sharing necessary diagnostic details.
Step 4 — Check the incident view or floor plan
• Confirm that the incident has the expected Security Zone and that you can open the incident itself.
• If the camera is expected on a floor plan, ask the administrator to verify that the correct camera has been placed on the correct zone asset layer.
• If a camera was just added, reassigned, or edited, reopen or refresh the relevant view after saving. Recent changes can take a short time to appear.
Common symptoms and likely next checks
• “No cameras found”: review zone mapping, viewing permissions, watermark/browser restrictions, and whether cameras are configured for the incident's zone.
• Camera appears but the picture is blank: review stream reachability, credentials, camera format, network and browser/security policy.
• Camera picture is frozen: check the camera's own stream first, then the selected image-refresh setting or dispatcher-app stream behavior.
• Feed works in a browser but not the dispatcher app, or vice versa: compare camera format, app version, authentication and network access; the playback paths are not identical.
• One camera is missing while others work: verify its individual URI, zone assignment, and position in a paginated list.
• Wrong cameras appear: confirm that the event's zone and the cameras' parent/child-zone assignments are correct.
When to contact support
If the expected feed still does not appear, contact 911Cellular Support at support@911cellular.com. Include your institution, the camera's display name (not its credential-bearing URL), assigned Security Zone, affected incident time or identifier if appropriate, whether you are using a browser or dispatcher app, and a description of the result. A screenshot that excludes passwords and private camera URLs can help.
A working camera feed provides visual context but does not replace your organization's emergency-response procedures or its camera-system monitoring.