7 Nov
2009
7 Nov
'09
1:48 a.m.
El Viernes, 6 de Noviembre de 2009, Klaus Darilion escribió:
Juha Heinanen schrieb:
Klaus Darilion writes:
In this case it can work also with client receiving responses/in-dialog
requests at advertised port 2. server
I use the pragmatic, and well working UDP approach. Just call
fix_nated_contact/register also for TCP clients. I never had any
issues with that.
even when client is not behind nat like in the example of the
discussion? (as long as the client is really listening on the
advertised port).
It should!
But one of my favorites statement is: "Never
trust the user". As the
contact and Via headers are user provided data I do not trust it. Thus I
always enforce symmetric signaling, regardless if client is behind NAT
or not and regardless of the used protocol.*
Some SIP ALG routers change the Via/Contact port and set 12345 while the
public source port is 12344. Really. So don't believe the user, neither the
routers! XD
--
Iñaki Baz Castillo <ibc(a)aliax.net>