OK, this fix seems to have the same effect as what Andrzej suggested. So I guess we should go forward with the latest in sipXtapi branch which Alexander just checked in.
One of the problems I still see is that the contact address is still a private IP address and the logs say that the STUN mapping for the localIP:5060 failed: "2007-02-09T18:02:13.994000Z":78:NET:DEBUG:Medhavi:OsNatAgentTask-5:00000AD0:sipXtapi:"Outbound STUN/TURN message(Crude Parse):\nMsg t=0x0001/MSG_STUN_BIND_REQUEST, l=0, id=8BB80EE8/92D898D02CC2F5AB0D099B83\n\n" "2007-02-09T18:02:14.285000Z":79:NET:DEBUG:Medhavi:OsNatAgentTask-5:00000AD0:sipXtapi:"Outbound STUN/TURN message(Crude Parse):\nMsg t=0x0001/MSG_STUN_BIND_REQUEST, l=0, id=8BB80EE8/1EA4D272C6213CD9E40EDFED\n\n" "2007-02-09T18:02:14.585000Z":80:NET:DEBUG:Medhavi:OsNatAgentTask-5:00000AD0:sipXtapi:"Outbound STUN/TURN message(Crude Parse):\nMsg t=0x0001/MSG_STUN_BIND_REQUEST, l=0, id=8BB80EE8/07B83444FCCE5ADD4EBF0E6A\n\n" "2007-02-09T18:02:14.886000Z":81:NET:DEBUG:Medhavi:OsNatAgentTask-5:00000AD0:sipXtapi:"Outbound STUN/TURN message(Crude Parse):\nMsg t=0x0001/MSG_STUN_BIND_REQUEST, l=0, id=8BB80EE8/CD77498FFCACA9BADD1E4F0E\n\n" "2007-02-09T18:02:15.186000Z":82:NET:INFO:Medhavi:OsNatAgentTask-5:00000AD0:sipXtapi:"Stun failure for 192.168.0.3:5060 -> 69.90.168.14:3478" We will look into this. On 2/8/07, logan <[EMAIL PROTECTED]> wrote:
Hi, For the one way audio problem please see this post by Mike Cohen - http://list.sipfoundry.org/archive/sipx-dev/msg04452.html. If it works then please let me know. Thanks, Hitesh ----- Original Message ----- *From:* Medhavi Bhatia <[EMAIL PROTECTED]> *To:* [email protected] *Sent:* Thursday, February 08, 2007 6:44 AM *Subject:* [sipxtapi-dev] STUN mapped address not appearing in SDP 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/
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
