This page contains information that I've found useful relating to IP Security Camera models that I'm interested in.

Foscam

FI8910W

MJPEG Video Feed URL
- Format: http://<ip address>/videostream.cgi?user=<user>&pwd=<password>
- Example: http://foscam1/videostream.cgi?user=user&pwd=password123
Shinobi
- Capture Framerate: 1 to 30+ FPS
- Remote Host Port: 80
- Target colorspace: 24 bit

RTSP Video Feed URL
- Format: rtsp://<username>:<password>@<host>:554/Streaming/Channels/<channel #><stream ##>?transportmode=mcast&profile=Profile_1
- Example (Main Stream): rtsp://user:password123@eziview1:554/Streaming/Channels/101?transportmode=mcast&profile=Profile_1
- Example (Sub Stream): rtsp://user:password123@eziview1:554/Streaming/Channels/102?transportmode=mcast&profile=Profile_1
Shinobi
- Capture Framerate: 1 to 30+ FPS
ZoneMinder
- Main Capture Resolution: 1920 x 1080
- Sub Capture Resolution: 640 x 480

RTSP H264 Video Feed URL
- Format: rtsp://<username>:<password>@<host>:554/h264Preview_<channel>_<stream type>
- Example (Main Stream): rtsp://user:password123@reolink1:554/h264Preview_01_main
- Example (Sub Stream): rtsp://user:password123@reolink1:554/h264Preview_01_sub
Shinobi
- Capture Framerate: 30 FPS
ZoneMinder
- Main Capture Resolution: 3072 x 1730
- Sub Capture Resolution: 640 x 350
Bluecherry
- Path to RTSP: /h264Preview_01_main (or /h264Preview_01_sub)

I can only see six (6) streams in a montage. The seventh get dropped.
- I saw this problem in ZoneMinder and Shinobi while using FireFox. It turns out that FireFox defaults to only allowing 6 streams per server.
- This can be fixed by going to about:config and changing the following settings
  - browser.cache.check_doc_frequency 3 -> 1 (this causes FireFox to check for a new version of the page every time it is loaded)
  - browser.cache.disk.enable True -> False (this disables FireFox's ability to cache page content to the hard drive)
  - network.http.max-connections -> raise to 100
  - network.http.max-persistent-connections-per-proxy -> raise to 100
  - network.http.max-persistent-connections-per-server -> raise to 100 (this was originally 6 and probably the root cause of my problem)