El Lunes, 22 de Junio de 2009, Jan Kiszka escribió:
> Iñaki Baz Castillo wrote:

> > - First, STUN must be performed at startup in order to get the mapped
> > public IP and port for SIP signalling (local port 5060).
> > - For each call, STUN must be performed in order to get the mapped IP and
> > port for the selected local port for RTP.


> IOW, for each port used, STUN need to be run once after binding,

Not exactly. SIP port 5060 is all the time used by Qutecom (registration, 
refresh-registration, subscriptions, refresh-subscriptions, notifies, 
calls...). So it's enough with performing STUN for local port 506 at the 
startup.

But even if Qutecom always would use port 8000 (or whichever) for RTP, it 
should perform STUN *before each* call. Note that a phone could be hours 
without doing or receiving calls, so it's not sure that the router will map 
the local port 8000 to the same public port (it could map that public port to 
other client in the LAN).


> and the
> result needs to be used instead of the local IP:port for building SIP
> packets -- unless the related code in qutecom is scattered all over the
> place, this still doesn't sound frightening. Where is the devil in the
> detail?

I assume that doing STUN before each call is the hard point here.




-- 
Iñaki Baz Castillo <[email protected]>
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to