Adding a Camera Unknown to SecuritySpy

We have an extensive list of cameras that are known to be compatible with SecuritySpy. All these cameras have profiles built into SecuritySpy, making for a quick and easy setup in most cases.

However, it’s a fast-changing market and new cameras are continuously¬†being released. While we do our best to release frequent updates¬†that support these new cameras, it’s a difficult task. You may find yourself intending to use a particular camera that is not yet on our list – this blog post will show you how.

The main requirement for a camera to be compatible with SecuritySpy is that the camera is capable of sending data in either of these two formats:

  • JPEG over HTTP (sometimes called MJPEG or “server-push”)
  • JPEG, MPEG-4 or H.264 over RTSP

This blog post will concentrate on RTSP, because this is the standard format for all modern network cameras.

The first thing to do is to check that your camera supports the RTSP protocol. Most do, and certainly all ONVIF-compatible cameras do. For some cameras, you will need to navigate through its settings pages with a web browser in order to find an option to enable RTSP, however for most cameras it will be enabled by default.

Next, you will need to find out the “request” that the camera understands for sending its RTSP data. This is a short string of text, and might be described in documentation as an “RTSP request” or “RTSP URI”.

There are a few different ways you might be able to discover what this request is:

  • Via the camera’s web interface. Many cameras show the RTSP request string in the section of the settings where the video streams are configured.
  • In the camera’s documentation. Check the camera’s user manual for information about the RTSP requests that the camera understands.
  • On a third-party web site such as SoleraTec or iSpy, both of which host databases of common cameras and their RTSP requests.
  • By contacting the camera’s manufacturer directly. The better companies will readily supply this information.


The setup procedure in SecuritySpy is best shown by an example:

  • You have a camera on your network at the IP address (cameras can be set up on your network like this)
  • Its username and password are both “admin”
  • You have discovered that the RTSP URI for your camera is rtsp://

Here’s how you would set this up in SecuritySpy:


In our experience, here are some things that might go wrong:

  • The standard network port for RTSP is 554, and this is what SecuritySpy uses if you leave the port boxes empty. However, a minority of cameras (most notably from ACTi and Foscam) use different ports for their RTSP communication. This information should be shown in the camera’s web interface and documentation.
  • In rare cases, some cameras send MPEG-4 or H.264 video that is incompatible with QuickTime (QuickTime is used by SecuritySpy for video decompression). If you get a green or distorted video feed, this is probably the case.
  • In rare cases, a camera might send a non-standard RTSP stream which SecuritySpy cannot decode. In this case you will get a blue screen with a cross in the middle. In this case, please email us and attach SecuritySpy’s log file (located in your ~/Documents/SecuritySpy/ folder) so that we can look into it.
  • Make sure that you do not have Perian installed on your computer, as this could cause the decompression of H.264 video to fail.
  • Sometimes cameras don’t use a request string, in which case you would need to leave the Request box empty in the above window.

Let us know!

If you have had success with a camera that is not on our list, please email us and let us know the details, so that we can add the camera to our list.

[Update: 2 December 2013]

SecuritySpy 3.2 now supports the ONVIF protocol, so any ONVIF-compliant camera should work with SecuritySpy with minimal setup, even if it’s not yet on our official list of compatible cameras. For such cameras, simply select the ONVIF profile from the device list and enter the camera’s IP address and username/password, and SecuritySpy will do the rest.

Tagged , , , ,

54 thoughts on “Adding a Camera Unknown to SecuritySpy

  1. John Spiller says:

    Trying to connect my X10 cameras to security spy, got blue screen with X in it.

    What is the setup for X10 cameras (i have several different models)?

    • bensoftware says:

      Hi John, I believe if you select the “Foscam” profile in SecuritySpy, this will make these cameras work.

      • Sven Ljungholm says:

        I just got an X10 Airsight HD cam and cannot get it to connect. Tried the foscam setting and the manual setting. Any help would be appreciated. I can open a port to allow you to take a look.

        On a side not I also got an Edimax camera that works like a charm.

  2. Simon Harrison says:

    Having difficulty in connecting an ANRAN Model S-C755RV H264 MegaPixel IP Camera with an IP – (an e-bay purchase to test Mac, Security Spy and a security camera at home).
    I can see it in a browser with an excellent picture, but the software seems to be win doze and in Chinese.
    Please can you help
    With Thanks

    • bensoftware says:

      Hi Simon,

      Try this request in manual mode in SecuritySpy with the format set to RTSP:


      (Insert the correct username and password above instead of the xxx marks)

      Does that work?

  3. Simon Harrison says:


    Yes it works perfectly, when I enter it correctly.

    Thank you very much.

    Security Spy also recognises my USB 2.0 UVC PC Camera Handheld Digital Microscope, so I can look at the hills in the distance, and the inside of a model railway engine on the same screen.

  4. Anatoly says:

    Tried to add 3 new cameras with no success. I guess buying from China via AliExpress was a stupid decision since they simply won’t take it back even though they admitted their description is wrong (they don’t support MAC). Anyway, they insist that their product support ONVIF 2.1 so maybe it can work with SS?

    I will appreciate your help.

    Camera description link:

    • bensoftware says:

      Any camera that supports ONVIF does implement the required streaming formats that allows it to work with SecuritySpy, so it should just be a question of discovering what RTSP commands the camera uses. Unfortunately this information might be quite difficult to find – the page you linked to has no clues, and this camera seems to be sold under many different names and model numbers, so I can’t tell who the original manufacturer is. Firstly I would suggest trying all the Foscam profiles in SecuritySpy. If that doesn’t work, please email us and if you can put the camera online for us to test that would be very helpful.

      • Anatoly says:


        I’ve checked Foscam website and found camera that looks exactly identical to what I have: Foscam FI8919W Wireless Outdoor Pan/Tilt IP Camera

        But I couldn’t find it in the list of Foscam cameras in SS. Can you please help?

        • bensoftware says:

          Hi Anatoly,

          This camera will work in SecuritySpy with the existing Foscam JPEG profile already built into the software. I’ll make sure to add the camera to our online list of compatible cameras.

          • Anatoly says:


            I’ve tried that. Didn’t work. Looks like it won’t even try to connect/authenticate, it tries for a fraction of a second and gives me ‘no video’ right away…

          • Anatoly says:


            Is there anything I can try to request from manufacturer? I’m not sure but I can try to get RTSP commands or something like that. Please let me know.


          • bensoftware says:

            Hi Anatoly,

            As a JPEG-only camera, I don’t believe this one supports RTSP. Please can you email us SecuritySpy’s log file (you’ll find it in the SecuritySpy folder within your Documents folder) and we’ll look into it further.

  5. Christophe says:

    I have a TRENDnet TV_IP851WC camera and I can’t configure it on my security spy 8 camera software. I tried a lots of different solutions but i did’nt get through

    Could you help me ?

    Thank in advance.

    • bensoftware says:

      Hi Christophe,

      We haven’t come across this particular camera before. The first thing to try would be all the existing TRENDnet profiles in SecuritySpy.

      Alternatively, set it up with Manual configuration with RTSP as the Format and play1.sdp as the Request.

      If you get stuck please email us and we’ll look into it further – please provide your log file from ~/Documents/SecuritySpy/ and if you can put the camera online temporarily for us to test that would be very useful (we can send you instructions on how to do this).

  6. I have to try to connect an Allnet ALL2296V2 to securityspy 3.0.4 as manual configuration.
    Request URI is rtsp://IPcam/h264
    or rtsp://IPcam:554/cam/h264
    these URI work with VLC.
    I set Video Device setting:
    Format: RTSP (video and audio)
    Request: cam/h264 or h264
    but I get no video in Camera status and blue screen in main video window.
    I tried with allnet ALL2298 and ALL2205 presetting config but I get same result: no video.
    Could You help me ?

  7. Alan says:

    trying to connect a Foscam 18918W with no luck. Just sent you the log file, so hopefully can get it working.


    • bensoftware says:

      Thanks Alan. For anyone else reading, this camera does work in SecuritySpy: Alan and I got this working by a simple settings tweak in SecuritySpy.

  8. Frank-Oliver Karutz says:

    I tried to get the same camera to work with no success. I have checked for the perian issue which is not the source of the problem in my case. In the error log, I see two different messages, depending on what I’ve tried:

    14-08-13 0011-00: Error communicating with the network device “Network camera 1″ 3.0.4,80210,404


    14-08-13 0018-45: Error communicating with the network device “Network camera 1″ 3.0.4,80259,801 Data from network device not as expected

    I get it to work in MJPEG mode, but no success with h264. Any ideas?

    • Frank-Oliver Karutz says:


      after I’ve updated the firmware on the Allnet 2296V2 it works as described by the previous poster. It would be great if you could also support the zoom function on this camera

      • bensoftware says:

        Hi Frank-Oliver,

        Is this the same camera that you got the 80259,801 error from before? If so then they must have made some significant improvements to the firmware, that’s good.

        It’s not clear if the ALL2296V2 actually has an optical zoom feature. I’ve had a look at the data sheet and it says “motorized lens” but this could just be for focus, because there is no mention of optical zoom specifically. As you may know, SecuritySpy only supports optical zoom, not digital zoom because it isn’t very useful.

        • Frank-Oliver Karutz says:


          the camera has an optical zoom. However, if I use the zoom, I have to also either adjust the focus by pushing the AF button on the web or adjusting the focus by pushing buttons on the webinterface to manually move the focus motor stepwise. I know that another camera of the same manufacturer has a ZOOM AF mode, where the autofocus is activated whenever the zoom is used. With this mode, the zoom makes more sense, as SW like security spy only has to control the zoom and not has to send the AF request afterwards.

    • bensoftware says:

      Hi Frank-Oliver,

      The 404 error is a “not found” error because the request used to ask the camera for the media stream was incorrect.

      The 80259,801 error is a problem with the media stream itself. This indicates that you have the correct RTSP request, however there is something about the stream that SecuritySpy cannot decode. Specifically in this case it’s the “packetization mode” of the H.264 units in the stream. SecuritySpy supports the main packetization modes but not the one that the camera wants to use unfortunately. This is the first time we’ve seen this particular error, so this mode is not at all common, and it’s not easy to implement. Unfortunately this means that you will be stuck with JPEG mode, I hope this is adequate for your needs for now.

      Hope this helps.

      • Frank-Oliver Karutz says:


        after the firmware upgrade, the camera now allows to select Baseline, Main or High Profile for H264. Perhaps that is why it now is compatible?

  9. Oknanta says:

    Hello Support,
    Can you help me how to access URL for TP-Link SC3230, because on their website it say already can used H264 for compression.


    • bensoftware says:

      Hi Oknanta,

      This camera should certainly work as it supports RTSP. In SecuritySpy, create a new device type and fill in the usual information (IP address, username/password). Set the device type to “Manual” and the format to “RTSP”. Try the following two Requests in turn:



      Also try leaving the Request box empty.

      One of the above should work – can you confirm?

      • oknanta says:

        Hello Support,

        Here’s the result

        1. mpeg4/media3gp –> not work
        2. video.mp4 –> work
        3. leaving empty –> work

        but also need some changing directly on camera setting so it will using H264 compression ,because if u see on this link by default Security spy chosing frofile number 2 and i don’t have capable to change using another profile?

      • oknanta says:

        Hello Support,

        Finally i found correct URL request for TP-Link SC3230:
        So inside request box just put:

        you can change Profile3 to any frofile number you want.

        • bensoftware says:

          Many thanks for posting back, this is very useful information!

          • Oknanta says:

            Hi Support,

            Do you have experince with Golbong Ip Cam I must make sure first
            this Ip cam will work with SS before i’m buying , I have question about RTSP request for this Ip cam, i try my self looking on their web site about rtsp request but i only found clue like this:
            on their website they say they can embed QuickTime player into an HTML web page for live video of IP cameras using this below script :

            GOLBONG H.264 Demo Page

            //H.264 over RTSP over 554 port

            so what do you think about that script, witch script i can put in Security Spy request box?

          • bensoftware says:

            From my research, this should do the trick:

            - In the Video Device Settings window in SecuritySpy, create a new network device.
            - Set the device type to “Manual”.
            - Enter the camera’s IP address but leave the Port field empty.
            - Select “RTSP” from the Format menu.
            - Enter “user=admin&password=xxx&channel=1&stream=0.sdp?real_stream” (without quotes) as the Request

            Make sure to put the actual password instead of xxx above. If you don’t have this camera already, then it may be best to stick to cameras already on our list.

            Does that work?

  10. Matt says:

    If anyone buys the Lorex LNC104 – the correct way to access the video feed was found after literally 4 days of hunting:


    Hope it helps someone.

    • bensoftware says:

      Hi Matt, thanks for posting this, it’s very useful. This is not a camera we’ve come across or been able to test yet. To clarify, do you actually use the string “CAM_ID.password”, or do you need to substitute your actual password instead of the word “password”? Also I’ve seen some sources suggesting the correct RTSP request for Lorex is actually “video.mp4″ – does this work?


      • Larry says:

        “video.mp4″ doesn’t work on the LNC200 series Lorex. I didn’t try any other permutations, though.

    • Matthew says:

      Oh thank you so much for posting the RTSP url for a Lorex Camera. I created a ticket with Lorex asking them what the RTSP url was of the LNC204 and they told me that they could not find the url.

      COULD NOT FIND THE URL??? You make the CAMERA how could you not know!! I shake my head. Thank you for posting this information!

      • Larry says:

        The LNC200 series Lorex works just like the LNC100. Use L-view downloadable from the Apple Store to set up the IP and required passwords. Then use Manual config in Security Spy. Select RSTP (video and audio) as the format and enter /CAM_ID.password into request. CAM_ID is a 9 digit number (on the back of camera) and password is the one you create in the admin section of L-View.

  11. Miguel says:

    we have 23 cams AOP- IP6C11-P1 but i dont know the link acess to rtsp
    please help me. support of aop not response


    • bensoftware says:

      Hi, I’ve done some research and cannot find much information about these cameras anywhere. The manufacturer’s web site is not very useful and doesn’t show the RTSP requests. I found some live demo cameras provided by the manufacturer, but the camera’s web interface doesn’t appear to work on any Mac web browser (it requires ActiveX). So I’m afraid that it’s not looking good. I have emailed the company to ask for more information so if I hear back I will post the response here.

  12. Michael Schneider says:

    Hi, first contact again after a long while!
    Hope You are doing well.
    Q: Is the TV-IP851 supported by sec spy?

    Thanks for info,
    very best regards, Michael Schneider

    • bensoftware says:

      Hi Michael, hope you are doing well too! This camera isn’t yet on our list as we haven’t tested it yet, however I would say that it’s highly likely to work in SecuritySpy with one of the existing TRENDnet profiles. If you go for this camera please report back so that we can add it to our list. Thanks.

  13. Hendrik van Eeden says:


    I have been trying to get a Foscam F19805W to work on SecuritySpy. I have not been successful. I have tried just about every perturbation of settings to no avail. I also have three other Foscam cameras that do work. I have followed all suggestions on this blog. No luck!! What can I do, other than returning the camera?

    • bensoftware says:

      Hi Hendrik, this could be due to an authentication problem introduced in new versions of the Foscam firmware – please try the latest version of SecuritySpy (3.1.3) as it may fix your problem. Otherwise, please email us the Log file that you will find in your SecuritySpy folder within your Documents folder so that I we can look further into what is happening.

  14. Hendrik van Eeden says:

    Thanks for your reply. I was using the SS 3.1.3 version. I returned the camera, because I had other trouble with it.

  15. Mark says:

    Just bought off eBay an IP camera Empire Security ESC-IPC1 2.0 / 1080p.
    Web site:

    Set-up the camera with success and it shows nice picture on Windows software.
    Although connecting it to SecuritySpy gives me error:
    02-21-14 1811-41: Error communicating with the network device “Network camera 1″ 3.0.4,80210,451

    Do you by any chance have error codes data somewhere?

    • bensoftware says:

      Hi Mark,

      Please download the latest 3.3. version of SecuritySpy from the SecuritySpy download page. It has ONVIF support, and the specs of the camera also mention ONVIF support, so this is the setting that is most likely to lead to success.

      Hope this helps!

  16. Ken Dewey says:

    I am trying to setup a Foscam 9821, any hints? Can’t seem to get the manual config to work.

  17. Joachim Steffen says:

    I just bought three IPCC-B22 cameras and I can not connect them to my Security Spy.
    Could you please help?


    • bensoftware says:

      Hi Joachim,

      I haven’t come across this particular one before, but it looks like a Hikvision camera, so firstly try the Hikvision profile that is already built into SecuritySpy. The camera also apparently supports ONVIF, so also try the ONVIF profile in SecuritySpy.

      Hope this helps,

  18. Richard says:

    Hi Ben
    Any idea how to connect to a SunLuxy 4 camera H.264 network dvr? I can’t figure it out yet! I don’t even know what the cameras are, I’m renting the property and have no control over the camera type!!
    RTSP port appears to be 6002. Manual says 6001 for CMD, 6002 for TCP, 6003 for Mobile.

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>