Hi,

On Wed, 16 May 2007, Marcus Priesch wrote:

> first of all, thanks for that great piece of software, i am using it now
> for quite a while and it's really nice ;) - under python via ctypes -
> YEAH !

thanks, that's good to hear! :)

> but i im totally stuck with the stun thing - even the sofsip-cli isn't
> working as expected.
>
> i have searched the mailing list, looked at code which is using
> sofia-sip (sofsip-cli, tapioca and freeswitch) but no success.
>
> using the stun module standalone works perfect ! - even in python ;)

Yes, this is a known issue I'm afraid. STUN is not currently enabled for 
signaling (i.e. for updating the "Contact" for registrations). It _is_ 
usable for a SIP client wishing to use sofia-sip's STUN module to discover 
IP addresses for media (i.e. to SDP).

This has not been an urgent item for us at least, as use of "rport" 
(RFC3581) gets you basicly the same results (for SIP signaling). And in 
the future, the 'SIP outbound' extension will completely remove the need 
for clients to guess their public Contact bindings. There are however many 
people interested in this, so patches are very much welcome.

>        self.ss.nua_register \
>            ( self.register_h
>            , self.ss.nutag_registrar, ctypes.c_char_p ("my.own.regist.rar")
>            , self.ss.stuntag_server, ctypes.c_char_p ("stun.voipbuster.com")
>            , self.ss.nutag_outbound, ctypes.c_char_p ("natify")
>            , self.ss.nutag_outbound, ctypes.c_char_p ("use-rport")
>            , None, None
>            )

Yes, the above API does not work at the moment. :(

Lot of the code is there already, but someone just has to finish the work 
in order to make it really work.

> stun_handle_init: entering.
> stun_handle_init("stun.voipbuster.com"): called
> stun_atoaddr: entering.
> stun_bind: entering.
> stun_discovery_create: entering.
> assign_socket: entering.
> stun_request_create: entering.
> stun_make_binding_req: entering.
> stun_send_binding_request: entering.
> stun_send_message: message sent to 194.221.62.209:3478

Hmm, this goes further than I remembered.

> tport_listen(0x816c5a8): stun_bind()(pf=2 UDP/[127.0.0.1]:32861): Invalid 
> argument

Ugh, this looks like a bug. Hmm.... patches are welcome! :)

> read something on the list that 1.12.3 had problems with stun, and
> 1.12.2 was fine ... but the same there ... hmmm.

Yes, this applied to the STUN module itself, but 1.12.6 and the current 
devel tree should be fine (you can test with the 'stunc' test tool).

-- 
  under work: Sofia-SIP at http://sofia-sip.sf.net

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel

Reply via email to