AV Tech DVR 760 (i think) Software (AP Software?)

[ittim 0]

Hi,

 

I've a client who's asked me to install his DVR. Specifically so he can access it from home.

 

I've read the instructions for his unit which seem a little sparse ( i guess they're translated) and it mentions AP software. My client doesn't seem to think he has it and i've not seen a download anywhere on line.

 

I can access the cctv system over the lan ok and see there are settings in there. Can i use these options to succesfully connect this unit up or will I need the AP software?

 

If so does anyone know where I can find it?

 

Many Thanks in advance.

[scorpion 0]

Hello! You can use the PC to set up the DVR, or you can connect the monitor out of your DVR to the yellow video input on a TV with this:

 

http://eclipsecctv.com/ECL-1030_connector.html

 

Here is where you can download the AP Software.

 

If the DVR has an IDE hard drive then it came with Video Server E.

If the DVR has a Sata hard drive then it came with Video Viewer.

 

Video Viewer can be used on both DVRs as it is backwards compatable.

 

Video Server E then use 1.0.6.9

Video Viewr then use 144.

 

Any questions?

[craiga 0]

Hi,

If you've got it already connected to the LAN, then to view from home you simply need to enable port forwarding / virtual server in your router.

 

Before you do this, you should be able to check/change the network settings (Advanced -> Network from memory). If it is configured for a static IP address you are OK, otherwise you need to assign it a static address (some routers don't require this, but even if not required router configuration is always more complex if you use DHCP on the DVR). You should really change the PORT from 80 to 8071. The reason for changing the port is that if you want to access this from a mobile phone in the future, you are very unlikely to be able to access it via port 80.

 

Once you've changed the port, you'll need to add the port number into the URL to access the DVR, e.g. (replace 192.168.1.10 with the static IP address of the DVR):

http://192.168.1.10:8071/

 

Now, you just need to enable port forwarding (also known as virtual server) on the router -- this allows access from the outside world on port 8071 to get to the DVR. You'll need to find out how to do this on the client's router, but basically you want to forward:

TCP port 8071

to:

192.168.1.20 (port 8071)

obviously changing 192.168.1.10 to the IP address of the DVR.

 

From memory, the following can only be configured through the AP software (not everything is accessible through the DVR menus):

Lastly, unless the customer has a static IP address with his ISP (usually available at additional cost/month), the Internet IP address will change every time the router re-connects (or at other times). In order to get around this you'll need to setup a dynamic DNS name. Go to:

http://www.dyndns.com/

and create a Dynamic DNS Free account. Then configure the DDNS section in the DVR configuration with your account information (select "dyndns" and enter your hostname, username, and password).

 

Lastly you'll need to set the DNS (not to be confused with DDNS above) servers. You can get these IP addresses from the customer's ISP (support page). Alternatively, you could use the free DNS servers from http://www.opendns.com/ (appears you have to create a free basic account to get the IP addresses these days).

 

Lastly through the AP software (only) you can setup an email to be sent on motion detect (or other alarm), which can be useful. The 760 doesn't support having this facility turned off during the day automatically, but it can be done manually, if required.

 

Once the DDNS info has propagated, then you can access the DVR with something like:

http://mydvr.dyndns.org:8071/

 

Hope that helps,

-Craig

[ittim 0]

hi guys, thanks for the replies.

 

Just got back from the job, did all as mentioned above. Did it all via the lan, didn't need the software. Only thing i haven't done is alter the port from 80. However I don't think this is an issue for the client. (certainly not at the moment anyhow)

 

Got the connection working over the internet while i was there (tested it on my mac via log me in to ensure I was testing on a different network) It worked perfectly. However I've got home and logged in and decided to check it and now the connection times out.

 

Could it be an issue if the public ip on the users router changes?

 

Currently i have the url from dyndns pointing to the ip that was given to me from the router when i did the port forward. Is it possible that its changed? A little annoyed that it was ok and now its not

[tomcctv 190]

hi guys, thanks for the replies.

 

Just got back from the job, did all as mentioned above. Did it all via the lan, didn't need the software. Only thing i haven't done is alter the port from 80. However I don't think this is an issue for the client. (certainly not at the moment anyhow)

 

Got the connection working over the internet while i was there (tested it on my mac via log me in to ensure I was testing on a different network) It worked perfectly. However I've got home and logged in and decided to check it and now the connection times out.

 

Could it be an issue if the public ip on the users router changes?

 

Currently i have the url from dyndns pointing to the ip that was given to me from the router when i did the port forward. Is it possible that its changed? A little annoyed that it was ok and now its not

 

if you are away from the dvr the lan ip is no good. did you get the external ip while you was there ???

[ittim 0]

Yes, as i set up the port forwarding it gave me the external ip. I used this on dyndns and tested it on an external network. All worked fine. Now it doesn't seem to.

 

Now thinking back, i had to power down the router after i had it set up (for another issue) I'm guessing its a dhcp problem somewhere.

 

To my knowledge the client doesn't pay for any fixed ip addresses so i guess its a dynamic one?

[scorpion 0]

How did you connect to an active x device with a Mac?

 

At your house, are you using your Mac?

 

http://movies.apple.com/downloads/macosx/home_learning/securityviewe.html

[ittim 0]

ok, at the client site i could connect using an internal ip ie 192.168.1.10 (static)

 

I could view the cameras on a pc and a mac in this location using the browser.

 

I set it up for use over the internet. Because i was at the client site the only way I could test the connection was to use my mac at home via a log me in connection (i always have it available)

 

I put the dyndns url into safari, logged in and job done. The i didn't see the feeds but I logged into the actual DVR.

 

My main issue is that the URL no longer works. I suspect its because I don't have a fixed ip on the Modem/Router.

[scorpion 0]

This is odd.

 

You are using Dyndns so that should take care of any ip changes.

 

You had it working, and now it is not. This is requires troubleshooting on the client side.

 

Using log me in, and getting a connection tells me that everything was set up correctly.

 

Can you ping from your home, or via logme in?

[ittim 0]

in an odd twist...

 

i've just asked the client if i can log into his mac on the local lan. (i was going to have a check of the router settings)

 

His mac shows as off line in log me in (although the user says they have internet connection ok)

 

All seems a little strange to me.

[ittim 0]

if the external address on the router changes how will the url on dyndns know? is it possible i've not set it up correctly?

 

i used the ip the the port forwarding gave me and added it as host with ip address.

 

I tried a test using the dyndns tool and got this response

 

An attempted connection to 86.169.XX.XX:80 timed out. This typically indicates that traffic to that port is being actively blocked by either a firewall or your ISP.

 

So its pointing to the router playing up i guess.....

[tomcctv 190]

if the external address on the router changes how will the url on dyndns know? is it possible i've not set it up correctly?

 

i used the ip the the port forwarding gave me and added it as host with ip address.

 

I tried a test using the dyndns tool and got this response

 

An attempted connection to 86.169.XX.XX:80 timed out. This typically indicates that traffic to that port is being actively blocked by either a firewall or your ISP.

 

So its pointing to the router playing up i guess.....

 

might have a go at changing your port 80 to say 5000 or 5555 dont use port 80.

[ittim 0]

Yeah i was going to give that a go. guess i'll have to get to the site again. was hoping to do it remotely.

[ittim 0]

ok, i need to get my head around this.

 

i have the same router as my client.

 

Now i've just set port forwarding up and it gave me a public ip.

 

I rebooted the router and went to check on my port forwarding and found it has changed.

 

Now i suspect i know my client doesn't have any fixed ip's. I rebooted his router after having done the original setup. So i'm pretty sure that the public ip on my port forwarding must have changed.

 

That being the case how does the dyndns know where to connect to?

[ittim 0]

ok, let me know if i'm on the right track.

 

Do i need a ddns client? or is this pre built into the DVR. Assuming it is do I have to then use ppoe? I hadn't previously.

 

Otherwise do i need this...

 

http://www.dyndns.com/support/clients/

 

I don't think the router supports ddns (its a 2wire 2700HGV)

 

I assume the software client will know if the public ip changes and will then keep dydns upto date?

[craiga 0]

Hi,

I think you missed the step where you set up DDNS on the DVR (i did say i thought it could only be configured through the AP software -- which is maybe why you didn't see it).

 

You have to setup the DDNS on the DVR with "dyndns", your hostname, account, and password. That way the DVR can update dyndns when the external IP address changes.

 

Some routers can also do this and are configured similarly.

 

I generally don't like doing this with PC/Mac software because it just introduces one more possible problem.

-Craig

[ittim 0]

Thanks Craig, pretty sure i did this to be honest. I remember having to input the details for my dyndns account.

 

If I use the ddns on the cctv do I have to also use the pppoe setup? I assumed I didn't and that a static internal ip (192.168.1.10) with port forwarding on the router would be sufficient.

 

Just a quick update, tried to access the clients network last night, turns out there are some serious problems. The adsl behaves erratically and the whole network is pretty shodddy. So i'll be ripping it all out and starting from scratch. I can't trust their set up enough to diagnose the problem.

 

Last night for instance I litterally re-booted their router and it wouldn't come on line again for about an hour!

 

Thanks for all the replies, i'll be back if things don't work out!

[craiga 0]

Hi,

One thing is that sometimes the AVC760 will get the wrong external IP address for DDNS -- so do check that, not only is it being updated, but that the address it's updating with is correct. The problem seems to occur with some ISP's transparent proxies. Having the router do this may work better (if there's a problem).

-Craig

[tomcctv 190]

ok, i need to get my head around this.

 

i have the same router as my client.

 

Now i've just set port forwarding up and it gave me a public ip.

 

I rebooted the router and went to check on my port forwarding and found it has changed.

 

Now i suspect i know my client doesn't have any fixed ip's. I rebooted his router after having done the original setup. So i'm pretty sure that the public ip on my port forwarding must have changed.

 

That being the case how does the dyndns know where to connect to?

 

your portforwarding does not seem right. it should not be giving you a public ip. first see what the ip is for your dvr. (in dvr network settings) and right it down (this is your local ip) then go to firewall on your 2 wire. for some reason on 2 wires you will only see the mac address of your dvr. click on it and give it a name (cctv) then give it a port number (dont use 80) use 5550 then exit the router. now find your external ip (google myip) and right it down. now use the local ip to log on (you must be on the same network) and when you are away from the network you use the external ip. and you enter your ip in IE like this http://yourip:5550

[ittim 0]

Looks like its all resolved.

 

I found machines with incorrect ip's and machines riddled with viruses and a router that would not behave!

 

Eventually i sorted all those issues out and got to the cameras. Went through it all with a fine tooth comb and eventually found a typo in the ddns hostname on the AVtech. Not sure how it happend as I copied and pasted it in!

 

Anyway, once I set that straight (i also altered the port number as suggested) and away it went.

 

Just want to say thank you to all that posted here. Very helpfull. Give yourselves a pat on the back! " title="Applause" />