@miconda commented on this pull request.
> @@ -883,6 +883,57 @@ if(dns_query("test.com", "xyz"))
</section>
+ <section id="ipops.f.ptr_query">
+ <title>
+ <function moreinfo="none">ptr_query(ip, pvid)</function>
+ </title>
+
+ <para>
+ Store the hostname that correspond to ip
+ in a config variable $ptrquery(pvid=>hostname).
I use both terms config variables and pseudo variables, and I am referring to
the same concept. Historically the term pseudo-variables was used from
developer's perspective, trying to differentiate them from C-style variables.
Over the time, I noticed that config-variables are easier to "understand" what
one refers to, specially by those coming new to use Kamailio.
In other words, pseudo-variables tries to define them from technical point of
view (i.e., no declaration, no explicit type association, automatically
available by loading various modules, some read-only, other read-write). The
config-variables indicates where these variables are available/can be used.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3802#discussion_r1549330031
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3802/review/1976136...@github.com>_______________________________________________
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
