Uh oh. Foscam 9805P, 9805W and 9821P

dan
dan
edited June 2016 in SecuritySpy
Those three cameras are what I own. I added the 9805P and 9821P on Thursday. I had SecuritySpy v3.x.x (don't recall exact version) and updated to v4.0.1. My 9805W worked just fine with v3. I'd been using it for a couple of years. Now I upgrade ($90 USD) and add two cameras and nothing works. All cams have latest firmware.

Did I just make a mistake? Are none of these supported?

FWIW, my cams are set up at:

192.168.1.200:90 <- 9805W
192.168.1.201:91 <- 9821P
192.168.1.202:92 <- 9805P

All I get now are connection errors. :(

I have no problems viewing these cameras online with LiveCams Pro if that means anything.

** I just read the forum header: Is this the appropriate place to post?

Comments

  • If you are getting video via a different program, the cameras are active. Something is wrong in the settings in SS for your cameras. You may need to delete and re-add the cameras if settings got corrupted.

    I'd first check usual suspects for each camera's setup. If any of the are wrong, you won't get any video

    ip address
    username
    password

    camera protocol
    correct video stream
    rtsp via UDP / via TCP (try both if choice available)

    camera enabled

  • I had that happen. Your IP addresses might have changed Do check them out with the IP camera tool. I had two of my cameras suddenly change ip address.

    and if you did get different IP addresses and you want to remotely see your cameras, you are going to need to change them in your modem/router for port forwarding.

  • guykuo:

    I set up static IPs for the cameras so their IP addresses would't change. I just double-checked to make sure and they are good. Usernames and passwords are all good, too. As far as the rest ... I've been through all of the provided Foscam models and have gotten nowhere with any of them. I've tried each model combined with each video stream. Some report "bad address" some of them the connection timed out, etc.

    What RTSP port should I use?

    Aardvark:

    I am using static IPs for that very reason. I'm connecting via DYNDNS for WAN and each cam works fine that way, too.
  • Delete a cameras entirely and add anew. I don't know if 4.0 has same device setting behavior, but in 3.04 I could permanently screw up a video device settings in a way that I could never fix in the preferences if I changed profiles a few times and made some edits. Only completely deleting the device and adding anew fixed things.

    BTW, have the cameras gone through a power down / up as part of your debug process? I wonder if they detected a change in client and are refusing the connection.

  • I deleted the cameras and then added them again. The cameras have not been powered down. I don't understand why it worked before with the 9805W and now it won't, let alone the other two.

    I wonder if my cameras are even supported?
  • guykuo
    edited June 2016
    Since your camera isn't specifically listed, I'd try the two "generic" Foscam camera profiles with each of their respective format options.

    I am assuming you have confirmed network accessibility of the cameras on the computer you are running SS on, right?

    BTW, The SS device settings changes don't take effect until after you close the preference window and save the changes.

    Foscam JPEG
    (format is always JPEG HTTP video only)

    Foscam H.264
    ---H.264 RTSP (video and audio)
    ---JPEG HTTP (video only)

    I think the one that should work is H.264 with port 88
  • "I am assuming you have confirmed network accessibility of the cameras on the computer you are running SS on, right?"

    Yes. All are available on my LAN via network IP addresses.

    "Foscam JPEG (format is always JPEG HTTP video only)"

    Throws an error: *Unrecognized Request, Check device type*

    "Foscam H.264
    ---H.264 RTSP (video and audio)"

    Throws an error: *Communication error*

    "Fiscal H.264
    ---JPEG HTTP (video only)"

    Throws an error: *Communication error* (Although this one shows the "Connecting..." animation occasionally.)

    I don't believe the mentioned port number should matter if forwarded by static IP in the router. For example, my port numbers are 91, 92, and 93. All of these work on my LAN and WAN with no trouble.

  • Got it! What I did was set the RTPS port to the same port as the HTTP one. I have no clue why this worked but it did. Everything is recording just fine, now.

    This is all under the "Foscam H.264" profile with "H.264 RTSP (video and audio)" format.

    Thanks!
  • Glad you have it sorted
  • Just to help others, where did you set the RTPS port to be the same? In SS device settings, the cameras, or your router's port forwarding?
  • This was done in SS's device settings.

    Mac OS X:
    SecuritySpy > Preferences > Cameras > "RTSP port" field (below the "HTTP port" field)