[reSIProcate] stun client

[Matthias Moetje]

Nilay,

 

there is no automatic mechanism in dum for handling STUN. But all you need is already there and can be used with dum.

 

Please read the following article carefully, it should contain all information you need.

 

http://www.resiprocate.org/STUN_support

 

 

Best regards,

Freundliche Grüße,

 

Matthias Moetje 



 

TERASENS GmbH
Augustenstraße 24
80333 Munich
GERMANY

 

Phone:
Fax:
e-mail:
Web:

	+49.89.143370-0
+49.89.143370-22
info at terasens.com <mailto:info at terasens.com> 
www.terasens.com <http://www.terasens.com/> 

 

 

 

 

 

 

 

 

 

 

 

 

 

From: resiprocate-devel-bounces at resiprocate.org [mailto:resiprocate-devel-bounces at resiprocate.org] On Behalf Of Nilay Tripathi
Sent: Mittwoch, 17. Oktober 2007 15:01
To: resiprocate-devel
Subject: [reSIProcate] stun client

 

Hi,

I was looking at the Stun_Support document for resiprocate.
As it says, we got to have a pointer to the UdpTransport and then we invoke the stun api's for sending stun request and fetching result.

But addTransport of DUM does not return anything, so the suggested way has to be done in DUM (from addTransport of SipStack) and is not possible in the application using DUM. Is it correct?

Do we have DUM level APIs to do stun things, like you call one api and forget about it and it is done for any outgoing message. 
Looking forward for some guidance :)

Regards,
Nilay

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20071017/4f07c64d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2937 bytes
Desc: image001.jpg
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20071017/4f07c64d/attachment.jpg>