From: Sebastien V. <se...@ji...> - 2012-01-16 07:58:42
|
Hi Nigel, Le 15/01/12 20:45, Nigel Pattinson a écrit : > Thanks Sebastien. I found one more problem - the response to a > ConnectionBind request comes back with a different transaction id to > what the request used. Thanks, we will check and try to fix it this week. BTW previous problem (missing XOR-PEER-ADDRESS attribute in ConnectionAttempt) is fixed in latest SVN revision. Regards, -- Seb > > Cheers > Nigel > > On Fri, Jan 13, 2012 at 8:31 PM, Sebastien Vincent <se...@ji... > <mailto:se...@ji...>> wrote: > > Hi Nigel, > > Thanks, good catch! > > We will add the missing attribute shortly, probably this week-end. > > Regards, > -- > Seb > > Le 13/01/12 02:16, Nigel Pattinson a écrit : >> Hi >> >> I am attempting to use TurnServer to relay TCP traffic in line >> with RFC 6062. Allocation and permissions are working fine, but >> when a permitted peer attempts to connect to the relayed >> transport address, my TURN client receives a ConnectionAttempt >> indication which is lacking the XOR-PEER-ADDRESS attribute (the >> CONNECTION-ID attribute is present). I looked at the code >> in turnserver_handle_tcp_incoming_connection and it does seem to >> be missing the relevant code. >> >> Thanks >> Nigel Pattinson >> nig...@ka... <mailto:nig...@ka...> >> >> >> >> ------------------------------------------------------------------------------ >> RSA(R) Conference 2012 >> Mar 27 - Feb 2 >> Save $400 by Jan. 27 >> Register now! >> http://p.sf.net/sfu/rsa-sfdev2dev2 >> >> >> _______________________________________________ >> Turnserver-users mailing list >> Tur...@li... <mailto:Tur...@li...> >> https://lists.sourceforge.net/lists/listinfo/turnserver-users > > |