Re: IP network CCTV

[Jim <alarminex@xxxxxxx>]

On Jun 4, 4:20=A0pm, tourman <robercampb...@xxxxxxxxx> wrote:
> On Jun 4, 9:20=A0am, <petem...@xxxxxxxxx> wrote:
>
>
>
>
>
> > > fowarded to port 82..
>
> > Thanks Petem,
>
> > Sounds like I should investegate that service. Any idea what they
> > charge?
>
> > I'll save a copy of your post for their file for reference for after I
> > get the go-ahead to do the survey.
>
> > But ..... I wasn't thinking about using IP cameras but using these Wi
> > Fi cameras. I've never installed one before but I believe they have a
> > converter or server that converts the analog video from multiple
> > cameras and provides a single IP address to the network. Prior to
> > researching it, I don't know how they accomplish it but most of the
> > ones I've seen I seem to remember them saying that they are PNP. and/
> > or DLNA compatable.
>
> > -----------------------------------------------------------------------=
----=AD------------
>
> > they have a free service for wich the only drawback is to reconfirm the=
 ip
> > adress by auatomatic mean software client or propely configured router)=
 if
> > not done every 3 month the domain will be terminated (on my side I do i=
t
> > that way cause my router wont update the adress by itself and my ip alm=
ost
> > never change even if its dynamic) but before they terminate the domain =
name
> > you recive a email with a link to renew the info just by clicking it fr=
om
> > the network to wich its assigned..
>
> > and they have a 10$ a year service on wich you dont have to renew the i=
nfo
> > except for when the ip change and like I said before, with a simple rou=
ter
> > properly configured or a client software on one machine its all automat=
ic.
>
> > most router now have a place where you can program some DDNS stuf (Dyna=
mic
> > Domaine Name Service)
>
> > for the wireless cams that are not wifi, but wireless you just have to
> > foward the ports used with the appliance (DVR) for there software to wo=
rk or
> > it can even be just a web apps and you only need to foward port 80 to a=
n
> > outside port of the network.. (watch out most internet home service blo=
ck
> > the use of port 80 so you will have to port it to someting like 81 or 8=
080)
>
> RHC: I'm far from an expert on cameras; however, I have been using
> some low end DLInk IP cameras for remote monitoring of my home and
> they work well enough for simple monitoring. They have the advantage
> of not having to go through all the DYNDNS servers to work, with all
> the complications of setting that up. They are hosted on Dlinks
> website (mydlink.com) and work well from anywhere in the world. On top
> of that, each camera is only about $125 retail. Seems to me, this just
> might work. Below is the link to a bit of a description on my
> website....might be worth seeing if this could solve your problem
>
> Go to.....http://www3.sympatico.ca/rh.campbell/surveillance_systems.htm-

I read your report and would expect no more than you experienced.
Anything that I would offer to a client I would want to be more
impressive. In my experience, after an installation, when you show a
client a new CCTV setup, they respond very positively about how good
it is. However, once they watch it for a while, they begin to see all
the short comings and that's when you get ...."The Telephone Call from
Hell"  ..... like .... My brother in law bought a camera system from
Radio Shack for half the price you charged me and it looks twice as
good as "yours" .....  ( now, all of a sudden ... it's "mine")

This is why my sales "pitch" for CCTV usually consists of a half hour
of listing all the things it's NOT going to do..... which obviously
kills most of the sales.  It's also obvious that most of my
competition has no such qualms about selling their customers hardware
that can't do the job and then having to explain why it doesn't. I'd
just rather lose the job then get the bad press.