[Serusers] Replication problem

Andreas Granig andreas.granig at inode.info
Wed Aug 17 17:20:54 CEST 2005

Juha Heinanen wrote:
> i agree with you that consistent location table in DB is a good idea,
> but i don't understand why you need 10-15 mysql queries.  switch to
> radius and return all caller attributes as result of authentication and
> all callee attributes as result of uri exists check.  you end up with
> only two queries (plus accounting).

I just came across this posting from you (well, a little bit outdated) 
while digging in Path header documentation, where you argue the same way 
I did (that one more additional query doesn't matter):


Now you say that this all can be done using radius. I don't know much of 
radius, but looking at auth_radius and uri_radius modules I just see the 
xxx_authorize() and radius_does_uri_exists() methods and don't see a way 
how these could help me (except writing a own modules for authentication 
which stores the additional attributes in avp which I could query 

Beside that the URI could be altered by some kind of 
call-forwarding-lookups after some basic checks (call barring and such), 
where checks against this rewritten URI have to be made again, which 
requires additional queries.

Are you willing to share your experience doing this things with radius?


More information about the sr-users mailing list