Cisco

WVC80N

• MPEG-4
  • Source Type: ffmpeg
  • Source Path: http://##.##.##.##/img/video.asf OR http://User:Pass@##.##.##.##/img/video.asf

• MJPEG
  • Remote Protocol: HTTP
  • Remote Method: Simple
  • Remote Host Name: ip.address (or User:pass@ip.address if you configured the cam to only allow authenticated viewing)
  • Remote Host Port: 80 (or whatever port you are forwarding if remote)
  • Remote Host Path: /img/video.mjpeg OR /img/mjpeg.cgi

CIVS-IPC-2611 / 2621V

• MPEG-4
  • Source Type: remote
  • Remote Protocol: RTSP
  • Remote Method: RTP/RTSP
  • Remote Host Name: User:pass@ip.address (I used admin acc)
  • Remote Host Port: 554 (defined at cam web interface)
  • Remote Host Path: /img/video.sav (don't forget to choose MPEG-4 Stream at cam web interface)
  • Resolution depending on NTSC or PAL

CIVS-IPC-2630V

• Tested with ffmpeg, firmware V4.4.2-2
• Source Path: rtsp://user:password@x.x.x.x/img/h264media.sav
• Camera --> remember to set resolution to camera resolution and I had to play with the framerate (10) and quality (high)

CIVS-IPC-2916 / 2930 / 2935

• JPG Method
• cURL (HTTP(s))
• Source: http://x.x.x.x/jpeg?id=2
• Username/Password: admin/password (your selected password)
• Width/Height: 704x576 (depends on your camera model)
• Notes: This method yields a very clean image but only 1-2 FPSs, since it is pulling JPGs from the camera and displaying them as "video".

• Stream Method (flawed)
• Source Type: FFMPEG
• Source: rtsp://x.x.x.x/img/stream1
• Remote Method: UDP (can´t get it to work on TCP)
• Target Colorspace: 24 Bit Color
• Width/Height: 704x576 (depends on your camera model)
• Notes: This method yields great framerate but I get a horribly smudged image, even at 10 FPS in the camera settings.

CIVS-IPC-4500E

• Tested on Firmware v2.4.3-293
• General
• Source: Ffmpeg
• Analysis FPS: Blank
• Maximum FPS: Blank

• Source
• Source Path: rtsp://x.x.x.x:554/StreamingSetting?version=1.0&action=getRTSPStream&ChannelID=1&ChannelName=Channel1&userName=user&password=password
• Target Colorspace: 24 Bit Color
• Capture W/H: 1920/1080 pixels

• Camera Web Settings
• Feature Setup --> Streaming --> Channel Name: Channel1
• Feature Setup --> Streaming --> Video --> std: NTSC / codec: H.264 / Resolution: 1920x1080 / Rate: 10 fps / Quality: High
• Camera --> Network Setup Basic --> disable session id CHECKED

Notes: With these settings, I was able to completely eliminate image smudging/smearing.

CIVS-IPC-3530

• Tested with ffmpeg, firmware 2.0.3-27 (08/23/2014)
• Source Path (primary stream): rtsp://user:password@x.x.x.x:554/StreamingSetting?version=1.0&action=getRTSPStream&ChannelID=1&ChannelName=Channel1
• Camera --> Network Setup Basic --> disable session id
• Camera --> remember to set resolution to camera resolution and I had to play with the framerate (10) and quality (high)

CIVS-IPC-6400

Tested on Firmware 2.5.0-10 with H.264.

• Setup
  • Setup->Network Setup->Basic
    • Check boxes Disable Session ID and Enable ONVIF
  • Setup->Feature Setup->Streaming
    • If you want to use at two different resolutions be sure to follow the matrix in the Administration Guide [1]
  • You can turn down Password Complexity under Administration->Password Complexity

• H.264
  • Source Type: Remote
  • Remote Protocol: RTSP
  • Remote Method: RTP/RTSP
  • Remote Host Name: user:pass@ipaddress (I created a viewer-only zoneminder account)
  • Remote Host Port: 554 (defined in Streaming Settings)
  • Remote Host Path:
    • Stream 1: /StreamingSetting?version=1.0&action=getRTSPStream&ChannelID=1&ChannelName=Channel1
    • Stream 2: /StreamingSetting?version=1.0&action=getRTSPStream&ChannelID=3&ChannelName=Channel3
  • Resolution as defined in Streaming Settings

I've had trouble with unexpected exit status 255 for this camera, using FFMPEG seems to be working better.

Use Cisco's Motion Detection

If you'd like to use Cisco's motion detection and have it send an alert to zoneminder, I created a script to do this. Instructions and more information are available on GitHub: https://github.com/macaddict89/zm-cisco-http-trigger