Re: ASI Internet Communicator

["Mark Leuck" <m..leuck@xxxxxxxxx>]

"Jim" <alarminex@xxxxxxx> wrote in message
news:1182529664.913107.254420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> On Jun 22, 10:53?am, Anders <nos...@xxxxxxxxx> wrote:
> >
> > Using a mail server adds a lot of config. Many ISP's block
> > outgoing port 25, so you would have to configure each unit
> > with server, login credentials AND the destination email address.
> > The mail server(s) becomes just as much an "xtra dedicated site" as
> > what AZS has.
> >
> > We've arrived at a similar architecture as ASZ, although we built
> > it into our controllers directly and also moved the whole config UI
> > out to our hosted web servers, so no need for any client software -
> > just a browser.
> >
> > http://www.interopix.com
> >
> Why can't it work the same way as when you set up a DVR?
>
> The Mfg hosts a site at no charge and keeps track of the DVR. When you
> want to log on from anyplace in the world, you use your browser to
> enter your pass word and you're looking at your DVR'd cameras. It
> can't be that hard to do. The central would have the server and .....
> etc.  Right?

Thats how Napco does it with their video module however that's easier said
than done and why at not charge? Bandwidth isn't cheap.

One problem for the manufacturer is someone hacking into the website and
viewing your customers, very unlikely to happen with a direct to DVR path