2009/6/30 Inca Rose <incar...@gmail.com>: > I know the STUN code is not complete or is not 100% integrated on NUA > or NTA. > I would like to take a look and see if I can finish this work by > integrating the missing parts. > I have done similar work on my company's own SIP Stack and STUN Stack.
> All that I need is a some guidelines on where to start looking at the > code. We planned some 5 years ago to use "public transport address" API for various NAT traversal mechanisms. IOW STUN would figure out the public binding within tport and the tport would then give upper layers the public address. That does not work very well, at least with STUN. So the outbound module is the best bet. The outbound is easier to use only first REGISTER has been responded (after nta has resolved the transport adddress) but perhaps we have to change that (but then we would propably need changes in nua_register.c, too). You probably need some hooks to send and receive STUN messages through nta and tport. Have a peek on nta_transport_keepalive(), but perhaps you have to invent whole new methods there. > I what to integrate it on the signaling ( even if I agree that rport > can do a better job ) and in the SDP. The SDP part is problematic, I think it would be better to integrate the STUN with RTP. How do you plan to use STUN here? Separate STUN client running its own sockets, trying to find out the public bindings? > So, please, if someone can send me some guides on where to start I will > put some resources ( 2 engineers ) to finish it. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------------ _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
