Actually, it looks pretty weird: We dont see anywhere in the code where the STUN mapped address/port is copied into the SDP (c/m lines). I think we may be looking in the wrong place or maybe the wrong code snapshot. Can anyone confirm this or guide us?
On 2/7/07, Medhavi Bhatia <[EMAIL PROTECTED]> wrote:
Hi folks, We are seeing a weird issue in the sipXtapi branch checked out about two weeks back that the STUN mapping is successful but the outgoing SDP in INVITE still have the private IP address. The logs appear to state STUN IP/port for RTP and RTCP. Is this problem resolved already in the sipxtapi branch? Let us know. We will try an update anyway since we are also getting one way audio (problem with media playback on sipxezphone) problem. Thanks, Medhavi.
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
