Re: [reSIProcate] STUN support with Resiprocate
The resiprocate stack itself has some basic support for Classic Stun
(3489) in the UdpTransport's - for sending and receiving STUN bind
requests on the SIP transports. The reTurn project has support for
both Classic Stun and new stun (5389) as a server and a client api.
The reTurn project has not been integrated into the resiprocate
transports at this point, it is more suited for use in media streams.
The reTurn project is used in the recon/reFlow (which is a UA API with
full media and SIP signalling support) to provide STUN and TURN
support. At some time in the future I would like to extend reflow to
support ICE.
Note: There is lots of info on these projects on the wiki:
http://www.resiprocate.org/ReTurn_Overview
http://www.resiprocate.org/Recon_Overview
http://www.resiprocate.org/Recon_Overview#What_is_reflow.3F
and information on the resiprocate stack STUN implementation at:
http://www.resiprocate.org/STUN_support
Scott
On Thu, Jan 22, 2009 at 6:57 AM, Gurpreet Sidhu <gurpreet.sidhu@xxxxxxx> wrote:
>
> Hi Scott
>
> I want to know that
> Which Version of the Stun RFC is implemented by the Resiprocate?
> RFC 3489(Classic STUN) or RFC 5389(Stun with FINGERPRINT etc.)
> I think it implements RFC 3489.If it is,then why STUN Server implicitly
> runs with the Resiprocate because that is the work need to do for ICE
> support??
> Is there any special reason for that??
>
> Thanks
> Gurpreet Singh Sidhu
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
>