Daryl733

Nothing wrong with T-568A. You'll just have to keep it consistent at both end of the cable. It'll work even if your extension cable is T-568B. Bascially the wiring order is the same, just color coding is different. Both end of the same stretch of cable have to match. You always have to keep to the pattern. There's a reason for it. If you want to read more, google for it. Basically the no. of twist is different for each of the 4 pairs in order to subject them to different level of interference. When the signal get interference, it'll affect each pair the same way, resulting in the voltage differences between each pair to remain the same. That's how the signal is derived. Instead of trying to prevent (shield) the cable from interference, it allows for it to happens and is able to correct from it. However when you wire the wrong pattern, each signal is no longer passed through the same pair, interference will no longer be corrected, leading to unstable network connection. Now, back to your immediate problem. Couplers are basically female to female joints that allow you to join 2 cables together. They have no electronic parts in them. They shouldn't spoil that easily. Check the surface of the connection. Could be the environment you install them is causing corrosion or something that affect the connectivity. If you see oxidation, take a sandpaper and sand the surface and try again. but it's only a interim solution. You may want to contain the join in a waterproof box.

Thanks for responding. I configured port forwarded and selected TCP/UDP for both the RTSP port and HTTP port The settings are correct because everything works fine The HTTP port setting ONLY actually vanishes from the DVR if you unplug the power and reboot it. It actually still reads on the settings page, but I just found out (this weekend) if you re-enter it and save the setting, it will work. It is not remembering the setting. It DOES remember the RTSP port When the DVR reboots and if I don't re-enter the http port setting, I can not access from internet. I have tried this on 2 routers and I do not believe its the router UPNP is on on my router but the port map shows that it is only tied to my computer and synology drive (none of these things are on when I have the DVR problem with my security system) Appreciate if you can delete whatever bad advises I had given to avoid misleading other forum users to waste time in following my advice. tomcctv is right. P2P is the only way to make it work. You should look for P2P in the menu and get it to work. There's no other way around it. Apologies for wasting your time in reading my posts.

......

Check if the overwrite feature is turn on. 5-10GB is not a lot.

Advice Taken.

Advice Taken.

Advice Taken.

Expert Detected. Post Deleted.

Advice Taken.

Expert Detected. Post Deleted.

From the brochure, incoming bandwidth is limited to 25Mbps. Think there's a network monitor function in the NVR to see the current in/out bandwidth usage.

Expert Detected. Post Deleted.

VLan doesn't reduce the throughput the Cameras uses. It basically segregate the group of network virtually from another vlan group for various reason, mainly security. If the network cameras uses 50Mbps, it's still 50Mbps gone. You might want to go with simple standard installation. Get a NVR with LAN POE port. Cameras connect to the LAN POE port. WAN port connect to your rest of the network.

Standard firmware might not work on rebanded equipment. The inside might not be the standard hardware mix.

Expert Detected. Post Deleted.

Advice Taken.

Where's the feed recorded to ? If it's to standard SDI CCTV DVR, you might want to look at the DVR Text overlay feature. You can edit it there, or if you are looking at integrating with other program, some DVR have api that allows you to update the text overlay vie the API.

Try VirtualDub.

All you need is your router that support VPN. Otherwise, you can also setup your NAS for VPN, think it support that as well. Some of the NVR also support self signing cert for security.

Normally I'll recommend a more branded NVR that have a whole range of analogue and ip range of equipment. Brands like Dahua, HIKVISION, etc. I'll stay away from those smaller unheard of brand. Final decision is up to you. Your rack mount chassies, http://www.servercase.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=D-118V2-ITX-22FX8&Category_Code=MS already cost quite a bit. That doesn't include the motherboard, cpu, ram, hdd to run os, os licenses, etc. If you work out the sum, it doesn't make economical sense to do otherwise. Most devices supports multiple brand through ONVIF, although i still recommend sticking to 1 brand initially for clean installation. The NAS also supports ONVIF camera, but just purchasing the license alone doesn't make economical sense, think it's around $60 for each additional ip cameras licenses for the 2nd cameras onwards. The 1st cam is free. So for 8 cameras, that's 7 x $60 = $420. You can get a 8 Channels NVR with POE for around 1/2 that price. http://www.amazon.com/Synology-Camera-License-Pack-CLP1/dp/B001MJ0JAO Unless you are looking at enterprise level projects where there are hundreds of cameras deployed and the systems needs grow and to be integrated over time , at this kind of pricing, sometimes it doesn't even matter if you go for a proprietary technology if it is cheap enough. Paying a premium for the flexibility that you never gonna use in the mid term might end up to be $ wasted. I've customers who installed a 16 channels dvr years back for a 8 cameras installation thinking they want to add cameras in the future. By the time they are looking at adding, the dvr is already obsolete and newer equipment and technology at less than the price premium they paid long time back is now available.

Did you crimp the wire in the correct order ? http://www.groundcontrol.com/galileo/ch5-ethernet.htm Do note the 4/5 and the 3/6 wire's pairing. One common mistake is to pair 1/2 3/4 5/6 7/8 which goes against the specification. It works for short distance, but if distance or interference is large, you'll encounter intermittent problem. That's the problem we always faced when people diy or have their electrician who know nuts about network cabling crimp the cables for them. The pairing pattern is used to reduce interference. If you are interested to read more, google for it. Otherwise, get a network cable tester and test if the crimp is good and there's no break in the cable.

Just curious, why would you want to complicate a simple system which in turn also ends up to be more costly ? Are you gonna separate your Cameras network from your normal home network ? Or you are just gonna put everything in a single network ? Do note that 3Megapixel will constantly takes up over 10Mbps each on the network it's on. For 8 Cameras, that'll be ard 80Mbps of constant bandwidth taken up from your Cameras to your PC. And since you are using a NAS for storagem another 80Mbps constant bandwidth taken up from your PC Based NVR to the NAS. That's more than 160Mbps constantly occupied on your network by these streaming video. That's not including any bandwidth used if you are gonna view the video on another client or from a remote site. Not to mention that now the NAS will be constantly recording over 80Mbps of data in the storage. If you are using the NAS for purely CCTV Video Storage, that's fine. But if you are also using it as a NAS, you'll have files spread over other sectors unless you are mounting the HDD as seperate volume. Otherwise, the NAS will be constantly switching between sectors constantly writing the CCTV Video that's coming in, and also attempting to read and write other aspect of your file storage for your other uses. Most CCTV Purposed NVR comes with a LAN and WAN port to segregate the CCTV Cameras network from the external network. Some come with POE switches @ LAN, others provide a single LAN port which you can hook up to external switches/POE switches, in your case, the Edgeswitch. Cameras streaming are limited to this segregated network and doesn't affect the bandwidth of the rest of your network. You could also install the HDD directly into the NVR, some supporting redundancy and multiple HDD as well. If you are looking at cost saving, take 2 HDD from your NAS and put them into the NVR instead. If you are concern about compatibility, most IP Cameras and NVR are ONVIF compatible, which means you can theoretically mix brand and is not limited to a single brand. I would advice against that for a clean setup as it's almost always easier to setup a single manufacturer equipment rather than mix and match brand although they are "compatible". There are also manufacturer specific functionality that works best when same brand equipments are integrated. ONVIF only support the basic functions and some special/manufacturer specific functionality are not accessible or lost when using that. You mentioned using PC Based 3rd party NVR software. That will basically limit you to the same functionality as the ONVIF standard. Some example of extra functionality. For some manufacturer, you can save/backup/upgrade the configuration/firmware of all same brand IP cameras connected to the NVR instead of having to access the cameras 1 by 1 to do so. For some manufacturer, you can access/configure the IP Cameras configuration through the NVR rather than login to the camera to do configuration. Some smart feature, e.g. line crossing, people counting, intrusion detection features available on the camera might be only accessible from the NVR and integrated with it when you are using the same brand of NVR. You might want to consider sticking to the KISS principle.

Well, if you are that paranoid, you'll have to asses the risk to determine what is more important as I believe you have limited budget. Just take into consideration the basic of physical security. DDDR - Deter, Detect, Delay and Respond http://www.guardcorp.com.au/advice/deter-detect-delay-and-respond-security-tips-every-business-should-consider/ Respond is what is most often neglected by people. Without any respond, all these measures are pretty useless. If there's a high probability of a break in, you should be looking at a alarm system on top of your CCTV system. When a siren goes off with pending guards responding, the intruder would be less include to take his time to search for a recorder in your house if you hid the first one well. Otherwise with time on his hand, he could take his own sweet time and locate all your 10 recorders in your house. Just bear in mind that offsite recording, internet connection can be disabled from outside your house. Backup cellular data connection, Wireless Jammer will take care of that. CCTV ? Ski-mask will render facial recognition useless. Cutting off the power will also render the system useless. UPS ? How long are you going to factor in without any predetermine period for respond ? The intruder could cut off power to your system the first day you go on holiday, and break in a couple of days later. Alternative Recording ? It won't have any recording if the power had been already cutted off. Not forgetting that easily available laser could damage the camera sensorchip at a distance and some system don't even detect that as a video loss and raise an alert. Understandably, these are the more extreme measures to consider and might not apply to most people. What you would want to do is make your place appeared to have strong security measures in place so that your neighbor house looks more inviting.

tomcctv, I believe dmills913 had actually done all you had advised but he still can't login to the camera directly through lan. Did it cross your mind that the IP camera you referred to being able to work on Dahua, etc NVR are actually another range of camera supplied by y-cam ? The HomeMonitor Camera Range of camera from y-cam might have it's webserver disabled or maybe doesn't even come with webserver to allow it to be login like a normal IP Camera ? Taken from Y-Cam FAQ http://support.y-cam.com/customer/en/portal/articles/1661650-can-i-use-a-y-cam-ip-camera-with-homemonitor- From what Y-Cam FAQ highlighted, HomeMonitor cameras (that dmills913 is using) is different from Y-Cam IP Cameras (that you had successfully gotten to work with other NVR). I had also highlighted this in a much earlier post. They had also highlighted that their HomeMonitor sevices are NOT compatible with their Y-cam IP Cameras. This kinda confirm that HomeMonitor Cameras (dmills913 using) and Y-cam IP Camera (you are using) are 2 different product and there's a possibility that HomeMonitor range of camera doesn't work like normal IP camera. You had repeatedly accuse me of giving bad advices, but yet dmills913 is unable to get his system working based on your advice, which also directly contradict what the Y-cam stated. I respect that you have 33 years of experience. But that doesn't mean that you are always giving good advice and others are giving bad advice. As you had repeatedly accused me giving bad advice, I feel that it's my prerogative to defend myself against your baseless accusation. These are what you said earlier in this thread. dmillis913 had highlighted Ya, we know right from the start (at least I do) to use the LOCAL IP in the app. WHICH APP to use with the LOCAL IP ????? I believe dmillis913 is smart enough to know he should be using the LOCAL IP to attempt direct access to the y-cam device the first time you mentioned it. From his reply, I gathered 1. He can see the LOCAL IP assigned by his Router's DHCP Server to the Y-Cam in his Router's DHCP Client List. 2. He tried typing that LOCAL IP into his browser, but can't see the login page to the Y-Cam. Either Y-Cam doesn't have webserver function or the webserver port is not defaulted to 80. If so, please advise him which port to try. 3. You gave him hope by insisting that there is an APP to use with the Y-Cam apart from the HomeMonitor Services. Both of us asked repeatedly which app is it, and I even took the trouble to do a screenshot of all available apps by Y-Cam developer to allow you to point out which APP he should use. You never reply to this even though I asked a few times. It's easy just to walk away from this by reiterating that you have 33 years of experience which non of us have here and you must be right. The rest of us are stupid for not being able to get it working. The Y-cam FAQ must be wrong to highlight that these are 2 different range of product they sold. Their various technical guys must be wrong or lousy to gave that sort of advices to dmills913 over the past 2 years. It's funny that Y-Cam that you highlighted in an earlier post is a big popular company that sold a lot of cameras and yet don't know what they are selling as accused by you. Do the right thing. Man up to your own advice and show dmills913 what you mean. You mentioned you had done a lot of y-cam home monitor cameras integration with nvr and they can be login through normal webbrowser like normal ip camera. Do a few screenshot to let dmills913 what to expect. If y-cam is using normal port 80 for the webserver, or is there a unique port to see the web interface in the browser when dmills913 key in the LOCAL IP address in the web browser. (dmills913, you may want to assist tomcctv by listing what IP you keyed in as he insisted that you are not using the LAN ip but rather the public/WAN ip address in the browser). And when the web browser login page appear, what's the default userid and password dmills913 should key in.

For people not in the industry, it's never about just selling the equipment and walking off after that. Support cost is a huge factor in deciding on the pricing of the whole package. It's hard to compete on pricing with internet/fly by night vendors who can just sell the equipment and vanish thereafter without having to factor all those support cost into their pricing. If your customers just compete on pricing without taking account of other services/support you provided, it might be time to walk away from these customers. We have returning customers whom tried out the supposed cheaper alternative, and realised that it ends up being more costly in the long run.