Yes, I remember from the training that the public static ip address was the recommended way to go. I was just concerned about opening up the whole Summit to the internet and was hoping to let the firewall at their location block some of the intrusion attempts on the other open ports on the Summit. Also, thanks, yes, I had looked at their DSL connection speed and theirs is a 15 Mbps/3 Mbps connection. If those numbers were "all the time" numbers, then that DSL connection would be able to handle about 45 calls simultaneously (assuming in very general terms that a call takes 64 kbps), but due to latency as well as competition with other services at the customer's location vying for the connection, yes, the DSL and cable connections generally can't handle too many calls at once. Luckily, this will be only one cell phone app connecting. Also have to worry about the DSL or cable connection at the customer's house where he'll be connecting from, I don't know how that will work, we'll just have to test and see. If I can't get it to work reliably with the port forwarding, then I'll fall back and use a public static ip.
