Re: [reSIProcate] STUN Client/Server CheckIn

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

reTurn provides both a standalone stun/turn server, and a generic client api.  The client api is intended to be used by any application – not necessarily just resip – including RTP based media stacks, in order to make TURN allocations and TURN tunneling seamless for the application.

 

Down the road there is a good chance we will integrate the client api piece into resip – doing so will mean replacing resip socket classes with this client api.  There is still a bunch of work do to before we can get that to that point though.  : )  See the checked in README.txt for the current TODO list for reTurn.

 

Note:  Using STUN to detect NAT/firewall types has been deprecated in the lasted stun RFC3489-bis06 draft.  However reTurn will provide backwards compatibility with RFC3489.

 

Scott

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxx] On Behalf Of Matthias Moetje
Sent: October 17, 2007 6:39 PM
To: resiprocate-devel@xxxxxxxxxxxxxxx
Subject: [reSIProcate] STUN Client/Server CheckIn

 

Hi Scott,

 

a question about the recently checked in STUN client: Can the client implementation be used with resiprocate?

AFAIK the STUN request must be sent from the same UDP socket to which the stack is bound to…

 

Best regards,

 

Matthias Moetje

TERASENS GmbH
Augustenstraße 24
80333 Munich
GERMANY

 

Phone: Fax: e-mail: Web:

+49.89.143370-0 +49.89.143370-22 info@xxxxxxxxxxxx www.terasens.com