I'd just commit the fix, though a unit test followup would be good to be written, in case this breaks again..
On 7/24/07, stipus <[EMAIL PROTECTED]> wrote:
>>The changes made in revision 9386 have caused STUN failures on the RTP >and >>RTCP ports. The SIP call control port still receives STUN responses >>correctly. I've made many Wireshark traces and can see that the STUN >>requests are correctly made to the server and that the correct STUN >>responses are received back but sipXtapi doesn't use the responses on >the >>media ports. > >Fix for this problem is in experimental sipxtapi r87 available on >sourceforge. Do you happen to remember in which files this fix can be found ? Because sipxtapi without working STUN is mostly useless if anyone want to write a user agent... >It isn't in sipxtapi branch yet, as I don't have time to >write a unittest for it. I don't know what the exact problem is, but I don't understand why unitests would be required to fix a bug introduced by a previous revision. _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
-- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
