Thomas

With Audio, the law works based on parties to the conversation. Home ownership isn't a factor at all. In this case a party is defined as a person as someone actively taking part in the conversation. At least one party must be aware of the recording for the federal guidelines, and most one party consent states. Two party consent states require everyone in the conversation to be aware of the recording. Home ownership or paying the phone bill has zero bearing on this.

Assuming the video is filmed in a public place, you do. However, if it's entered as evidence in trial, there are certain distribution rights that are off-set. If he's commenting on the trial, fair use would allow for almost all of the video to be cited.

http://www.cctvforum.com/viewtopic.php?t=12156

Then you're fairly screwed. Most of the cellular based projects I've seen have ****ty uptime.

The PoE spec is 48 volts. The vivoteks will handle it just fine.

Alright, I think I see the problem. It looks one of two things is happening here. What is the IP address you're using to connect to the DVR? Do you have a static or dynamic IP address for your home? And you're not quite understanding how port work on most systems. Most firewalls built into routers are designed to block unrequested incoming connections. So random traffic on gets dropped unless someone asked for it like your web browser. Port forwarding disables this for a specific port and directs the flow of incoming traffic to a server. The all applies to incoming traffic only. Outbound traffic is almost never blocked by a firewall. The assumption for most home and commercial routers is that outbound traffic is expected. And so any reply made to those outbound request is allowed back in. So you rarely need to configure port forwarding on the client end for any internet application.

It sounds like your home end make not be configured correctly. If the Wi-Fi is from the same LAN that your DVR is on, then no port forwarding would be used. If you can see it from a remote, off site location then it's set up correctly. If so, my earlier statement applies. If you can't see it at any off site location....then your home is configured wrong.

It's a two year old thread. Let sleeping threads lie.

Port filtering is generally done for a reason. It's their network, if they don't want you using those ports, you don't use them. You're a guest on the network, understand and obey the restrictions placed on you.

It could be.

Generally with port forwarding you're only referring to incoming traffic. So in theory, if it's set up correctly it should work anywhere. If however the above place filters those ports, then there is a limited amount you can do.

CCTV as a deterrent is not effective. It's too ubiquitous and people have seen way too much old grainy video. Which is amazingly ironic when you combine it with people's expectations from CSI. It doesn't scare criminals and owners expect more then is realistic. Combined with a ton of ****ty installers and people who think "how hard can this be", you end up with something that doesn't solve the problems.

Alright, seems simple enough. You have a firewall in between the linksys and the rest of the world. Most likely it's at the modem but it could be the ISP.

What happens if you attempt an NMAP scan or a tracert to the DVR?

As far as digital zoom goes not concerning megapixel cameras I apologize. I was thinking of with PTZ's and other items like a Zoom camera that has a 18x zoom (optical) and then a 10X digital, I typically show the customer that the optical zoom is far superior to the digital zoom. With Megapixel cameras this train of thought may or may not always stand true tho, so I apologize for not making myself clear in the first post. Thanks, John Oh no, you were right, I was pointing out the tiny exception to the rule.

Me and you BOTH!!!Digital zoom is a very bad thing that was made to haunt CCTV security installers in their sleep! As far as bullets with it the smallest I know I can get my hands on is about the size of a box camera and has the RS-485 to where you can adjust it via remote software/dvr... basically a ptz. But more of a Zoom camera only. A still module if you would.... Thanks, John Digital Zoom has a use. When I'm streaming multiple megapixel cameras to a client, and the resolution is reduced, then digital zoom is actually pretty cool. But the rest of the time...yeah it's bad.

You can do some tricks with using PTZ's to zoom using presets but that almost always requires having some fixed cameras supporting them as well, and low end software generally doesn't support rules management.

There is a trick to do it with the CD55. I forget what preset number it is, but you can engage the menu by setting that preset and calling it twice I believe. You can transmit the commands over standard hyperterminal. The second byte contains the camera address if you feel like punishing yourself.

By batteries, are you willing to be looking at large dry cells? Because if you're thinking 9vs or AA's....it's not going to work for broadcasting long distances. Not with any real battery life. Are you willing to change batteries daily?

These exist now, just not cheap. I may have missed it but which camera are you referring to? The closest I've seen is one from Extreme that simply switches to a lower resolution CCD at night.

Quite often IP camera software is licensed per camera. So is your budget for the software $18.75 per camera or $300 per camera?

And how would you address low light situations in which megapixel cameras fail miserably?

When you say not too expensive...what kind of budget are we discussing?

Your problem is the formating of your parameters. A proper ftp path will look something like ftp://192.168.1.108/dvr And you change the ip address to match the IP address of the server and the directory to what ever the incoming directory for the home automation.

C:\DVR isn't a valid address for FTP. Are you trying to map a virtual directory to an already existing FTP address or are you trying to use it like a network share?