Bogdan-Andrei Iancu wrote:
Hi Klaus,
the answer is simple - no, there is no caching in auth_db :)
A typical call internal call is:
INVITE --> <-- 407 ACK --> INVITE w. credentials --> 1. openser checks credentials against subscriber table 2. openser lookup("location") 3. t_relay()
Thus, we have the high performant in-memory cached lookup() and always a slow database connection.
Thus, also if the lookup is incredible fast, the authentication is the bottleneck. Or do I miss something?
regards klaus
regards, bogdan
Klaus Darilion wrote:
Hi!
A stupid question: Is the subscriber table also cached inside openser (like location table)?
regards klaus