On the phone with AT&T trying to get to the bottom of our issue getting audio and video back to realpresence via AT&T devices. Sounds like many businesses are running into issues with the 10.X ip addresses as they are, according to AT&T, rolling out more and more.
Anyone else experiencing this or have a workaround?
Sounds like I'm running into something similar. Just started testing RealPresence on my phone - works fine with wifi, but no video with 3G/4G on my ATT iPhone 4s. Tried a co-worker's phone - same phone, but Verizon and it worked just fine. . . That's about as far as I've gone - now looking for answers here ;-)
It sounds as if AT&T may be assigning private, non-routable IP addresses to (at least some) devices on its network. It is likely NATing these addresses at the edge of their network. This can cause problems for standards based videoconferencing endpoints, especially if they aren't getting any help from other video infrastructure.
RealPresence Mobile was designed to work well with Polycom's RealPresence Platform, which would help solve this problem. If you have access to a Polycom based video network, you can simply "sign in" to the network with the sign in screen in RealPresence Mobile. Doing this would give RealPresence Mobile access to some network components that would help with issues around NATed private IP addresses, as well as other Firewall related issues.
If you don't have access to a Polycom video infrastructure deployment, then there may be other options open to you. But each of them does require some help from network infrastructure.
RealPresence Mobile can place calls using either H.323 standards or SIP standards, and it supports NAT/FW traversal standards for each of these (e.g.. H.460.18/H.460.19, and Outbound SIP RFC 5626). So NAT/FW traversal methods based on these standards should help RealPresence Mobile. For instance, placing calls through a SBC (Session Border Controller), an Outbound SIP proxy, or an H.460.18/19 supporting gatekeeper would all likely help.