< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

RE: [reSIProcate] status of stun client support


HI Jason,

do you mean the stuff in rutil\stun? I thought this
was the STUN server implementation only. Is there
any sample or doc on using the stun client stuff?

Thanks and best regards,

Matthias Moetje
______________________________________________

TERASENS GmbH       Phone:  +49.89.143370-0
Augustenstraße 24   Fax:    +49.89.143370-22
80333 Munich        e-mail: info@xxxxxxxxxxxx
GERMANY             Web:    www.terasens.com
______________________________________________ 

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On 
> Behalf Of Jason Fischl
> Sent: Tuesday, February 21, 2006 5:08 AM
> To: Bruce Lowekamp
> Cc: reSIProcate List
> Subject: Re: [reSIProcate] status of stun client support
> 
> Hi Bruce,
> 
> The stun support in resip is intended to support a limited 
> subset of STUN to meet the requirements for the sip-outbound 
> I-D. In particular, a UAS can respond to STUN requests as a 
> keep-alive mechanism. In general, not every UdpTransport will 
> need nor want a STUN client. The stun client code is 
> available as part of resip and could be taken advantage of in 
> your  application. This was the intent with the current design.
> 
> On 2/20/06, Bruce Lowekamp <lowekamp@xxxxxxxxxxxxx> wrote:
> > >From what I can tell, it looks like stun server support has been
> > integrated into UdpTransport, but there is currently 
> nothing in head 
> > to use a stun server as a client (although there is a 
> comment in the 
> > mailing list about modifying UdpTransport to do that).  Is 
> my reading 
> > correct?  Has anyone written this code and checked it in 
> anywhere, or 
> > should I just go ahead and hack the support into UdpTransport?
> >
> > Thanks,
> > Bruce
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>