Does anyone have a list of the TCP and UDP ports that need to be opened in a firewall for the Summit UCS mobile client and has anyone had experience with how well the client would work external to the network with a Summit system NAT'd behind a router? I have the list of ports used by the Summit from the FTP site and in an older post, Derrick listed the ports used by the IP Communicator, but another poster in that thread said that the UCS client app uses different ports than the IP Communicator. That earlier post is: https://sundance-communications.com...cs/592718/Summit_Mobile_App_-#Post592718

For UCS:

• Forward these ports to UCP for Standard & Premium.

• Signaling UDP 5588, TCP 8899 and TCP 7878

• Audio Ports UDP 7000-7015, 7100-7115, 7300-7315

• Video Ports UDP 7016-7031, 7116-7131, 7316-7331

Should work fine with NAT as long as the router is setup properly, and is a decent router.

Yeah, a bit concerned about whether the router can handle it, it's an AT&T U-verse 2wire DSL router, so we'll see. Thanks, appreciate the help.

According to Vertical Tech support, it is not recommended to put the Summit behind NAT. They strongly support the use of a dedicated static public ip for the Summit when using any WAN voip/sip applicatons.

It has been my experience that DSL doesn't have the muscle to handle voip applications. I suggest you run a speed test before you go thru all the trouble of implementing UCS.

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.

If you use a public static, you can use the built in Access Control List to do some blocking.

Oh, that is excellent, I didn't realize that the Summit had an access control list, I see it now under PGM 255, thanks!