hi all, I went through the avp docs in voicesystem.ro and i thought the source_ip trusting in multi domain environment would be useful to me. I used permissions to do this before, but i think multidomain support is not possible in permissions module. But I jus wanted to know that on updating the table how does openser get updated without restarting the server. Is there a FIFO command or something. pls let me kno cause I did not understand the example mentioned in the docs properly. One more thing, Does Openser 0.9.5 support use_domain parameter mentioned in the docs. thanx.. jayesh
____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Hi Jayesh,
see my inline comments.
regards, bogdan
jayesh nambiar wrote:
hi all, I went through the avp docs in voicesystem.ro and i thought the source_ip trusting in multi domain environment would be useful to me. I used permissions to do this before, but i think multidomain support is not possible in permissions module.
have you tried to use the "from" field in trusted table? for multi-domain purposes....
But I jus wanted to know that on updating the table how does openser get updated without restarting the server. Is there a FIFO command or something. pls let me kno cause I did not understand the example mentioned in the docs properly.
depends on the module: first, depends if the module does caching of the DB info or not; second, depends if the module implements a "reload" FIFO command or not. permissions: may do caching and implements a FIFO cmd for reloading the trusted table; avpops: no DB caching, so no need of "reload" - it just read from DB each time.
One more thing, Does Openser 0.9.5 support use_domain parameter mentioned in the docs.
"use_domain" is a per-module parameter, not a global one. See the docs of the interested module to see if this parameter make sense for the module and if it does, see if it is present.
maybe a description of your scenario will help in guiding you better.....
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
avpops: no DB caching, so no need of "reload" - it just read from DB each time.
i was thinking that it might make sense to have also shared memory, transaction independent avps to store information that is dynamic, but does not change often.
I'm already considering adding two types of AVPs: - script avp - not attached to any transaction they will leave only during a route - excellent to perform temp operation in script without carrying about sync, removing them, etc.... - global avp - which will be visible everywhere in OpenSER, for all messages - they will be used to control overall behaviour of OpenSER and they will be provision via external cmds or DB table - something like gflag for flags.
you can see script AVPs as a particular case of global AVPs (limited life time) and may be skipped :).
The only issue here is know to specify the AVPs in order to make distinction between the AVP types in their specifications....which is global and which is per transaction and so on....
regards, bogdan
Bogdan-Andrei Iancu writes:
- global avp - which will be visible everywhere in OpenSER, for allmessages - they will be used to control overall behaviour of OpenSER and they will be provision via external cmds or DB table - something like gflag for flags.
yes, this would make sense.
The only issue here is know to specify the AVPs in order to make distinction between the AVP types in their specifications....which is global and which is per transaction and so on....
either by new avp function names or by a new parameter to existing ones.
-- juha
-
Bogdan-Andrei Iancu -
jayesh nambiar -
Juha Heinanen