Your issue could be caused by something on your end (your router settings, firewall settings, etc) or something on your cell provider's end (their network configuration). Just because you didn't change anything on your end doesn't mean nothing changed. You basically have 3 main choices when setting up iCam:
1) configure icamsource without the "auto router config" box checked (In my experience, this is generally only successful when you have one camera source...and only if the networks between your computer and phone aren't overly complex--something you have little control over.)
2) configure icamsource with the "auto router config" box checked (In my experience, this is the best "easy" option when you have more than one camera source...and you need to have uPNP enabled on your router in order for it to work. It should work when you only have one camera, but I typically found that it wasn't needed for one camera...in my particular network setup.)
3) configure icamsource to allow manual port forwarding and set up the port forwarding in the router (In my experience, this is the most rock-solid, stable option...once you fumble through correctly configuring port forwarding in your router...it's a pain in the ass on some routers.)
If you are already using option 2, you should get uPNP error or success messages when you start icamsource. SKJM can help you diagnose the problem if you post the error message(s). Worst case scenario, option 3 should work like a charm for you...once you get it set up properly. Good luck!
It seems like this question has been answered before, but I couldn't find it...
What is the minimum amount of time between 2 push notifications for motion events on one camera? And is this time adjustable? I ask this question because I've noticed that I have a number of recorded motion events that have met the notification threshold (more than x number of frames of motion), but I am not receiving anywhere near the number of push notifications that I should be receiving. These recorded events which meet the notification threshold are often separated by 10+ minutes, so it seems like I should be receiving push notifications for them. Is there a log of push notification requests made by icamsource?
As far as I can tell, this issue seems to only occur on one of my 4 IP cameras, which is strange. The other cameras deliver notifications as expected when the threshold is met.
That sounds more like an issue with Skydrive or something. I use Dropbox to backup my motion events and they are never deleted when I shutdown the computer. Have you tried Dropbox instead? Also, you might look through your Skydrive backup program options.
Have you tried rebooting the router and computer since enabling uPNP on the router? Did you also enable auto router config in icamsource? If you've done all of the above, you might have to set up manual port forwarding in your router and in icamsource.
You probably need to enable uPNP on the router AND enable auto-config router in icamsource. I'd also reboot both the router and computer to make sure the changes take effect. If that doesn't work, post back.
iCam only supports audio on USB webcams and some IP cameras. Your camera is an analog camera...not a webcam or IP camera. I think you should be able to get the audio to work by plugging the audio jack of the camera into the microphone/line-in jack on your computer....then, in icamsource, change the audio input dropdown to your microphone/line-in jack. Good luck!
iCam is only used to view cameras...not to monitor cameras. SKJM created another app that will convert your iPhone camera into an IP camera...the app is called IPCam.
Have you tried reducing the sensitivity slider? And have you tried disabling any of the motion detection zones that are frequently affected by changing light/shadows from any windows?
Will this update maintain support the original authentication method as well? I ask because LOFTEK is a FOSCAM-knockoff...but the original authentication method still works (even after the security update). Thanks!
Yikes...re-enable your firewall ASAP! The easiest way to get things working is to enable uPNP on the router, combined with enabling the auto router config option in icamsource...then possibly rebooting the router and your computer for good measure. Next time you start icamsource, you should get some uPNP (success or error) messages. If following those directions doesn't work, you'll probably have to enable manual port forwarding, which is a pain...but will result in very stable results.
For those of you who would like to be able to more easily control icamsource remotely, a little creativity, combined with the "Actions for iPad" app, will probably help you reach your goals. I don't have experience with it, but it looks promising. If you think you might be interested in it, download it so you'll always have access to it for free:
Breath easy...it does not reset the camera to default factory pain-in-the-ass settings...my current settings were preserved. Also, it does not break the authentication function in the same manner as FOSCAM's update, so no alternate link is necessary. Thanks again for the heads-up Don.
Respectfully, I agree with sev. iCam is simply an app that supports virtually any MJPEG-based IP camera. It's not SKJM's fault that FOSCAM programmed security holes into their cameras and that they had to change the (authentication?) functionality in a manner that is apparently incompatible with virtually every other IP camera. Of course, maybe that begs the question: is the authentication method of all other MJPEG-based IP cameras at risk?
One last question: I have a LOFTEK CXS-2200 camera, which appears to be a FOSCAM knockoff. There are at least a few iCam users who use these cameras. Any idea if it suffers from the same security hole? If you don't know, do you know how hackers find these exploitable cameras (i.e. through random pings, through the built-in proxy support, etc)? The first thing I did when I got this camera (before there was a widely-known FOSCAM security hole) was to disable the built-in proxy through their Chinese server, disable uPNP, ensure no ports were forwarded to the camera from outside the network, etc. Hopefully, those steps are enough. :-/
Anyway, thank you for stopping by...and especially for reminding everyone that this is a serious risk. It's crazy how lax some people are about security. If you have links that contain more information about the exploit, etc, feel free to PM them to me and I'll be happy to post them. I'm sure SKJM would post them too. I know you don't have time to read around on the forums, but if you did, I think you'd leave with the impression that they do a really great job with customer support...especially for a $5 app.
That's strange. Have you tried typing the IP address of the camera (the same one that you have entered in icamsource) into your Internet browser's address bar to see if it will connect?
If you are able to connect, you might try clearing your icamsource settings by following these directions for Windows:
Once you clear the settings, you'll have to re-add all of the cameras/settings as if you were starting from scratch.
If none of that helps, have you made sure that your camera has the latest firmware installed? It could be a weird firmware issue that's causing connection issues with the mjpeg feed.
Finally, you might consider not using any camera's built-in proxy service, as that sends your video feed through their servers...and who know if it's secure or not. Personally, I wouldn't trust any proxy that I didn't control or that didn't have major security/encryption built-in. IP camera hacks have been all over the news lately, and I believe most victims were found by using these free public proxies that are provided by the camera manufacturers.
Show Posts