Source Connection error

[steeltgiers]

When I first installed icam and icamsource for iphone, everything worked great. After both updates I get nothing, I have updated both icam and icam source and framework and everything else. Seems the new updates has created nothing but  trouble here:


"One or more of the icamsources returned by the icam broker server could not be connected to"

Been like this for a month... 

Not happy!

[Stefan]

Is AT&T your mobile provider, and did this happen once you installed iPhone OS 3.0?

Unfortunately for a small percentage of iCam users, the iPhone OS 3.0 software update has caused issues when connecting via 3G/EDGE. The reason for this is that (for some reason) iPhone OS 3.0 devices connect to AT&T differently than all previous iPhone software versions. With an OS 3.0 iPhone, AT&T uses a more complex form of port translation, causing connectivity issues for some users.

There is a solution, however, and that involves you forwarding ports in your router to your computer running the iCamSource.

If you could go to http://whatismyipaddress.com/ from the computer running the iCamSource and e-mail support@skjm.com what it says your external IP address is then we can attempt to look it up in the Broker Server logs and hopefully troubleshoot the problem.

Please mention your forum name and post in your e-mail.

[divdisp]

I seem to also be having this problem. I purchased iCam today and loaded the iCamSource on my Mac. The software on my Mac works fine, but when I enter the same username and password into my iPhone it says, "No Sources Found  There are currently no running iCamSources associated with your existing login and password."  I have carefully entered it a number of times to make sure there is no typo, but get the same results. I have a first generation iPhone. Does this mean it is just not going to work for me? If it can work, I would rather try to get it to do so. If it will not work for me, then I would like to know how I can get my money back. Thank you very much. J.

[Jay]

divdisp is getting technical support for this issue through email.  If there is any new information about this issue from the emails, I'll post it in this thread.