What kind of issues will I run into when trying to make webcams view to my smart phone or PC?

You will run into so many possible problems, brace yourself for this answer here, biggest problem is Firewall issues on all sides of the internet including your local PC firewall, your router firewall, your internet provider router firewall, your internet service provider can lock down view ports beyond your control at the NOC Network Operation Center. Firewall is a big issue to deal with. Once the camera is set up the PC or Smart Phone will require tools to view the image depending on how the camera is set to view. Axis cameras will use Active X or JAVA, and you will need permission to load Active X on your PC and or JAVA loaded on your PC to view the camera live. If you are trying to view the camera from within the same network backbone, the viewer may fail with the static IP because of loopback limitations in the internet, be sure to test the public view from outside the cameras internet if you are having trouble viewing the static IP. Viewing from your smart phone will require a camera viewing APP if you are not a MAC IPHONE, go to your market place and get one, install and configure your view. If you are providing your camera for public view, without password protection to view, your camera will slow down as more people go to it. In some cases the camera will fail if too many viewers are viewing at the same time.

How Do I progam the WebCams and Router to view more then one Camera?

This technology of viewing your AXIS web cameras on your smart phone could indeed be carried over to other IP based cameras. The biggest obstacle for making this work is the programming of your local router to pass the camera images across the internet. You will also want the location you are hosting the live steaming cameras to have a static IP, which means the location address never changes. If you cannot get a static IP, there are software solutions using DYDNS and there are websites that provide a solution to make your dynamic IP work as a static IP. This solution can be acquired free of charge if you can navigate the setup, in the end the DYDNS company will provide you with a name that points to your router’s dynamic IP and if the IP changes, the service will change too but the name will remain the same. The other issue to deal with is if you have one static IP, and more than one camera. If you had a block of IP’s you could assign each camera a unique public IP number. But what is usually done is you put each camera on the internal network and hard program their internal IP number. Each camera on the network will have a base internal IP number. The router will be programmed with a static IP. In the router programming you will need to locate the PORT FORWARDING section. What you will do is assign ports to each camera on the network, and use the router to map the ports to the internal IP of the camera. By default the cameras are all on port 80, a special port used for browser viewing. We will leave one camera on port 80, and assign all other cameras to a unique port we set, in this example we will use ports 5631,5632,5633 and the 4 cameras internal IP’s are CAM1, CAM2, CAM3, CAM4 There is a section in your network camera to change the viewing port, by default it is set to 80. When you go to your browser window and type by default the browser will go to port 80, the same as saying it means the same thing. By placing the colon behind the IP number we can go to a specific port. So you will have to go to each camera and set their viewing port from 80 to ports 5631,5632,5633 then to access CAM1, CAM2, CAM3, CAM4 Now each camera is ready to be set to public view. On the router locate the PORT FORWARDING section and create an entry for each camera. CAM1 PORT 80 --, CAM2 PORT 5631 --, CAM3 PORT 5632 --, CAM4 PORT 5633 -- Now you are ready to test your cameras. Locate your static IP number, if you do not know you IP search for “What Is My IP” and the site will tell you your current IP static or dynamic. Remember some internet types cannot view the cameras from within the same location; it is called a loop back problem. So have someone from outside the internet location test the cameras for view if they are not working after setup.

What are the details about Firewalls on your PC and viewing Webcams?

There are a lot of variables here, and I am only discussing windows based PC’s. In a windows environment, there are many possible firewalls that could be installed or enabled. Not only that but there also many operating systems all handle firewall intrusion and protection differently. The first thing you need to do is locate all the installed firewall software. You may have Norton, AVG, Avast Trend antivirus loaded on your PC as well as many other antivirus programs. Be aware that these antiviruses also can and do have firewall protection as built in, and may be enabled and blocking your cameras from working. Locating these programs is just the beginning configuring them to work is another issue. If you’re having trouble disable the firewall while you are testing till you get it to work, then turn on the firewall again after and test. Now remember windows too has a firewall that can be set and sometimes you have multiple firewalls and multiple antivirus programs running if you are not in total control of your PC. To locate the windows firewalls go to the properties on your network card and the last tab has firewall setup. Toolbars on your browser can block install programs and camera popup windows, you should try to locate them and turn them off if you are having trouble viewing the cameras live. These toolbars may be GOOGLE, YAHOO, MSN, and AVG and more, they have blocking functions that are enabled in many cases.

Call (970) 928-7477 to discuss your Project

Email Us Click Here
We have a proven track record of successful webcam deployment at all levels. From simple projects for home to complex custom programming, we can produce any project at any budget. We service all areas on the front range to the western slope of Colorado. On site service and install for Boulder, Broomfield, Westminster, Arvada, Wheat Ridge, Golden, Lakewood, Denver, Genesee, Black Hawk, Central City, Idaho Springs, Dumont, Georgetown, Silver Plume, Dillon, Silverthorne, Frisco, Vail, Eagle, Edwards, Wolcott, Gypsum, Dotsero, No Name, Glenwood Springs, New Castle, Silt,Rifle, Parachute, Battlement Mesa, De Beque, Carbondale, El Jebel, Basalt, Snowmass Village, Aspen, Redstone, and Marble