Re: [sr-dev] [Kamailio-Users] Inbound NAT detection and fix_nated_register() very poorly documented

Daniel-Constantin Mierla wrote: My fundamental question can be distilled to something very simple: If I have a REGISTER from a NAT'd endpoint, what can I do (in terms of existing module functionality, e.g. fix_nated_register(), save()) to "store" the fact that the endpoint is NAT'd in such a way that this can be detected again on a lookup() for an inbound call and special measures can be taken? I suppose there are many things that can be done - special AVPs stored in the DB, custom SQL queries, manually checking if the RURI domain is an RFC1918 address string etc., but I want to know what the canonical way to do this in terms of the existing modules is. After all, it is a common need to know that your call is going to a NAT'd endpoint prior to receiving a reply for that request. My secondary concern is that the way lookup() works when received_param is used is not documented at all. -- Alex -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671