Table of Contents

Valid Camera Stream Paths

When configuring custom stream paths for Cameras, TetherX validates the format to ensure compatibility. A valid path contains only the path portion of a URL - nothing more.

Path Format Rules

Valid paths:

  • Start with /
  • Contain only the path portion (no protocol, hostname, or port)
  • Examples: /stream1, /ISAPI/Streaming/Channels/102, /?trackID=1&StreamID=2

Invalid paths:

  • Full URLs: rtsp://192.168.1.100:554/stream (include hostname, port, protocol)
  • Missing slash: stream1 or 192.168.1.100/stream
  • Misplaced parameters: /trackID=1&StreamID=2 (no ? before first parameter)

Common Issues and Fixes

Issue Fix Why
/trackID=1&StreamID=2 /?trackID=1&StreamID=2 Parameters must start with ?
rtsp://192.168.1.100/stream /stream TetherX adds the hostname and protocol
stream1 /stream1 Paths must begin with /

Custom vs Override Paths

Custom paths - TetherX auto-detects streams and monitors for IP address changes.

Override URL - Specifies a complete URL. Disables automatic IP change detection and safety checks. Use only for:

  • Cameras on the public internet (VPN, proxies, hosted services)
  • Cameras requiring credentials in the URL

Tip: If you're unsure which option to use, start with Custom paths. Override is for advanced scenarios.


Finding Your Camera's Path

  1. Check manufacturer documentation for "RTSP paths" or "stream endpoints"
  2. Log in to your camera's web interface and look for stream settings
  3. Try common paths: /stream1, /onvif, /ISAPI/Streaming/Channels/101
  4. Test with Testing Cameras with VLC before saving in TetherX

Troubleshooting

Path still invalid? Verify:

  • Starts with /
  • No protocol (rtsp://, http://)
  • No hostname or IP address
  • No port number
  • URL-encode spaces as %20
  • Parameters start with ? and separate with &

Still having issues? Test the full URL (with protocol and hostname) in VLC Media Player first. If VLC can't stream it, neither can TetherX.


Last updated: January 17, 2026