26 Nov
2009
26 Nov
'09
3:48 a.m.
Alex Balashov wrote:
To me this means that nat_uac_test() should not work
after the lookup()
above. The only Contact header value that is present in the inbound
INVITE handler is the Contact URI of the media gateway, which is a
public IP address! Yet for some reason it works, as if by magic;
apparently it is somehow implicit that a hidden "received" attribute of
the RURI is also part of this check.
I just tested with an endpoint on a public IP and found that this test
was still returning a positive result, which further adds to the mystery
as there is no RFC1918 address in the Contact URI on either side
(request or reply) now. Please advise.
The documentation appears to be very much out of touch with fact here.
--
Alex Balashov - Principal
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671