Hello everyone, for a while now I've been playing around with the SipDemo in the 2.3 SDK. The documentation on Android's developer page is nicely written, but not a lot. It does not explain anything about IPs, ports, NAT and STUN. I know how this stuff is supposed to work, but it doesn't say how Android's SIP API handles it. Or does it handle NATs at all...
Here, someone mentioned that the API does do some tests for public IP and port, but it's the first time I read it: http://code.google.com/p/android/issues/detail?id=14043&can=1&q=sip%20ip&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars But now to my problem: When I deploy the SipDemo as-is either to my device connected to WiFi or to the emulator, provide my credentials (I know they work with SipDroid and other SIP apps) the SipDemo displays "registration failed". I did some sniffing and found out the packets sent to the SipServer all include the devices or emulators local IP, not my NAT's public one. The server replies correctly that RFC1918 IPs are not allowed. I added a STUN test to the SipDemo and successfully retrieved my public IP and port. But I can't find a way how to pass it on to my created SipProfile or the SipManager. My question: Has anyone ever made an application working with the SIP API behind a NAT? How does the API handle NATs? How can I pass the information I got from my own STUN client to the SIP API? Any help is appreciated. PS: I know SipDroid and a lot of other SIP implementations, but they all do not use the built-in API. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en