In the thread titled "Voice quality using sipXtapi on Windows Vista", Neil Carrott wrote:
I also seem to be having trouble with STUN if I build a recent version of sipXtapi - the SDP seems to be showing the local IP address / port rather than the one returned in the STUN response. If I use a build from March 2007 then it is okay, I wondered if there had been a change to the way I need to enable STUN support? I've been noticing similar behavior with version 8813 of the sipXtapi branch. I'm trying to make a call from behind a NAT router to a server with a public address. It makes the STUN calls, but the SDP sent to initiate a call is using the local IP addresses rather than the information returned by STUN. I'm in the process of updating my application to use a current snapshot of the sipXtapi branch (version 9792) and I will repeat the tests. Stephen C. Steel _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
