The camera supports v01-v06 for the streams.Īll the URL components are in place, yet SecuritySpy still can't connect. Profile is Manual configuration to allow for a Request string (Input or stream number doesn't work).įormat is RTSP TCP (I've tried the other options too). HTTP port, RTSP port, Username, Password are all correctly set (I've tried leaving these blank). The Address field seems to be pre-formatted to and the app doesn't have a Protocol menu for rtsp:// etc, so I'm not sure how to get the URL correctly formatted. How do I transfer this URL format across to SecuritySpy? They're not on the compatibility list, nor are they seemingly ONVIF (appear in Auto-Discovery but require a Request string), however they can be accessed in other software such as BlueIris on PC and Sighthound on Mac using the rtsp address - rtsp://192.168.1.200:554/v01 I'm attempting to connect two Link-U cameras to SecuritySpy, so far with no success. The camera used to record m4v files, somehow on September 18th at 3:09 pm it started recording mov files. > Addition Just checked my motion capture files. Is there some obscure setting that I am missing to record m4v's? Was there a step in the upgrade process from 3.x to 4.0.x that I applied differently for the one camera?Ī bit puzzled here, still getting an occasional freeze from the browser window that requires a relaunch of SecuritySpy. I am running SecuritySpy on a MacPro1,1 (32 bit, OS 10.7). This is an issue because my SecuritySpy browser will not play mov files for me. I can't figure out how to coerce the one camera to stream m4v files. I recently upgraded from SecuritySpy version 3.x, was running 4.0.4 and just upgraded to 4.0.6. Here is the issue: One camera writes mov files for motion capture and the other writes m4v files. Both cameras have the same firmware and since they have sequential mac numbers I would guess they came off of the assembly line together. I have two identical cameras, as far as I can tell, both are setup identically in their internal web-settings and their settings are identical in SecuritySpy. I sure would like to get the full picture in SecuritySpy, I'm sure it's something I'm doing wrong. It's all metal, has a nice camera and huge IR lights, internal heater, Audio, PTZ x4 and did I mention it's all metal :) This is one solid beast of a security camera, huge upgrade from my Foscam junk that finally died. RTSP UDP - connected but only top 1/4 video shows RTSP TCP - connected but only top 1/4 video shows I tried the 3 different formats available in Security Spy: I did have to set the ONVIF port to 8000 and the RTSP port to:554 before SecuritySpy would recognize it. I can connect to the camera with Safari on my mac and see the whole picture as well as IE in Parallels. Either one I pick I only get about the top 1/4 of the video and the bottom 3/4 is just gray. Security spy can get the profile list and I can pick either the main high rez profile or the sub profile which is VGA. On the Amazon listing they even show SecuritySpy software as compatible. I didn't see it in your list, but I did see that if it was ONVIF compliant that it should work. Although, I just got a new PTZ ONVIF compliant Reolink RLC-423 outdoor camera. I have experimented with changing the protocol to 'ALL', even though I know it's TCP.Hello, I've been a longtime user of Security Spy and it works great. In the tp-link settings, I have these entries in Port Triggering AND Virtual Servers respectively. I even had a buddy in IT look at it very briefly, and he couldn't figure it out. Unfortunately, I am currently stuck with a questionable router/modem combo - Router: tp-link Archer C59 v2.0 // Modem: ARRIS TG02DCG1682NDTW, and I feel like they are not playing well together, or I'm missing something stupidly obvious. I will say, I am not the best router/modem configuring, but I have definitely set up port forwarding in the past and not had this much trouble. The port is currently not listening according to netstat, and port checkers also show it as closed, and of course, Perforce client gives a "TCP connection failure: check port" when trying to connect from another computer. Despite all the settings you will see below, port 1666 remains closed. I'm trying to use my computer to host a centralized version control server for a team coding project, and so far everything is seemingly set up correctly in terms of the server, and the client sides - except that the TCP connection fails due to an issue with my port 1666, which the software (Perforce Helix Core) uses.
0 Comments
Leave a Reply. |