vv4yn0

I had a similar issue - it took some effort to get the plugins to install and operate in IE correctly. I could then get a picture but it takes ages to appear and is totally unworkable. It is a shame, I wanted to administer this system remotely but it just isn't up to the task.

My xiaomi ants cam has a usable RTSP output but I cannot write the address in properly because the setup page on the NVR always appends :554/main to the end of the address - has anyone found a workaround? The RTSP stream works fine in VLC and BlueIris. The address is rtsp://xxx.xxx.xxx.xxx:554/ch0_0.h264 Thanx for any help Wayne

After some searching I eventually got onto the JVC engineering department that designed the camera and they supplied a small test program that ran from the PC - it was too cumbersome to use and I eventually swapped to a panasonic PTZ camera and dedicated desk controller. I still have the software and if you give me an email address I will shoot it through to you. The guy I was communicating with is the fellow who made the software and his contact details are in the program but I don't know if he still works for JVC. Cheers, Wayne

Do you still have the 161C? - I have been looking for one of those everywhere 2nd hand! If you still have it and no longer require it can I convince you to part with it? Wayne @ exemail . com . au

How did you go with getting PTZ to work on this camera? I am suffering the same issues but I thought it was because the JVC cameras use a propriety protocol - I am hoping I am wrong. Wayne

I made the silly mistake of buying a JVC PTZ camera without checking the supported protocols and now find that my DVR does not support its propriety JVC PTZ protocol. I am scratching for a way to control this camera without forking out to buy a JVC DVR which runs into the thousands. I cant find any protocol converters that support the JVC protocol nor any software that I could use with an RS232 to RS485 converter on my PC. I was hoping for some learned suggestions from the group. (apart from "do your research, drongo!!") Thanks for any help Wayne

Excellent news! Just one tip - make sure your router will realise the DVR's changed IP address if it is rebooted and gets a new IP address from the router or it may be port forwarding to the wrong address. Some are smart enough to make the change automatically, some are not. Sometimes the DVR will have a long enough lease on the IP so that the same IP will be allocated if it isn't powered down for too long. Cheers, Wayne

If you can access port 8080 then change the DVR port to another port other than 80 - try a number you can remember easily like the last few digits from your phone number. change your port forwarding to reflect that port. go home and use your IP chicken obtained IP to access the DVR by adding on the port like this http://XXX.XXX.XXX.XXX:1234 where 1234 is your chosen port and the X's are your IP. this will tell your browser to access your DVR via HTTP via the chosen port. if your ISP is blocking the HTTP port (80) then it is likely that they will only block a few key ports and your randomly chosen one will be accessible.

I'd have to agree, blocked ports looks like the Most likely culprit - can you either remap ports on your router or change the ports on the DVR? I know many routers don't support port mapping and many DVR's don't allow you to change incoming ports so you may be stuck without changing ISP or paying to get the ports allowed (If that's possible). I would be most interested to learn the eventual outcome

The ip that Ip chicken gives you is used to connect from OUTSIDE your network, the DVR's IP is used when connecting from INSIDE your network.

Very briefly as I'm writing from my iPhone. Firstly change back to how you had it when it was working on the local network - dvr IP via DHCP then set up port forwarding for the ip that the dvr is allocated then go home and use the ip address that you got from ip chicken to connect to the dvr process is this - ip from ip chicken into browser at home, this is routed to your router, router port forwards request to dvr and reply is returned same way but in reverse. Hope this helps - if not I can write up a more detailed explanation on a real keyboard when I get home Wayne

Can you quote what IP each device on your network is using and also have you forwarded any ports yet? - without forwarding ports you definantly wont be able to see your DVR externally. As I mentioned, if you have the ability to set the DVR IP into a DMZ then it should work without doing anything else but any other services you run on your network such as a webserver will no longer work as all external incoming requests will be forwarded to your DVR. If your Mac is listing the incorrect address for the DVR maybe try rebooting everything on your network starting with everything off and turning on router then DVR then the PC's in that order. Overall, until you discover which ports need to be forwarded and get that sorted it just wont work externally. Wayne

On my DVR there are three ports that have to be forwarded - I am not 100% sure why but I think the second two are to do with the control of the DVR as opposed to just viewing the cameras. You will need to forward port 80 but I am unsure of which others if any - your DVR manual should tell you this though. If you have the setting on your router to set the DVR's IP into a "DMZ" then you don't need to forward any ports as all ports will automatically go to the DVR. On the mac Vs Iphone for browsing I don't know why the Iphone works but the Mac doesn't - I don't have a lot of Mac experience admittedly but I would imagine it's browser would access the DVR the same as any other browser - Maybe somone else can shed a bit more light on that aspect. Try forwarding port 80 and see what works if anything - you are halfway there!

As mentioned by soundy, just go to www.ipchicken.com, it will tell you your external IP address and then put that into your web browser. It will only work if you have set up the port forwarding in your router - when your request comes in from the internet to your router, the router needs to know which machine to forward the request so you need to tell it (via port forwarding settings) which address the DVR is on. This is ONLY from outside your network - you need to use the 192 address if you are within your network and from within the network port forwarding is not required Wayne.

If it is all set up correctly then it should just be a matter of putting 192.0.0.10 into your web browser address bar and hitting enter.