8 Jul
2009
8 Jul
'09
12:06 p.m.
Iñaki Baz Castillo schrieb:
2009/7/8 Klaus Darilion
<klaus.mailinglists(a)pernau.at>at>:
Yes, but what I mean is that in the above escenario PATH is required
in order client to receive calls from Registrar (forget NAT now).
of course, the registrar always needs to support PATH. But the
NAT-traversal mechanism only needs to support NAT if it is not running
on the OBP, but behind the OBP.
regards
klaus
I
don't understand this. PATH is required when a registration is done
through an outbound proxy, so the registrar routes request for that
AoR using also through the outbound proxy (the RURI is the Contact of
the REGISTER but the request is sent to the OBP.
E.g.: client
<--->OBP<---->Registrar
If the Registrar does the NAT traversal, the NAT traversal mechanism must
take into account the PATH, that means either:
- send OPTION requests to the client using a pre loaded route via the OBP
- send OPTION requests or emtpy CRLF packets with spoofed source IP (the IP
of the OBP)
If the OBP does the NAT traversal, the NAT traversal mechanism need not take
care about PATH because there is no SIP proxy between the client and the
OBP.