Hmm. That is frustrating, as the core logic is essentially the same.
Would you be able to temporarily make your camera accessible from outside of your local network so that we might try and connect to it using a development version of the iCamSource to determine what the cause of this new issue is? Without actually being able to replicate the problem we would just be guessing as to what to fix.
Your camera should likely include instructions on what steps are necessary to connect to it from a different network, and should involve forwarding a port in your router.