Reference7:Administration/PBX/Objects/Config Template: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
(New page: Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the [[Reference7:Administration/PBX/Obj...)
 
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
Config templates can be used to set certain parameters for many users in an uniform fashion.  Templates can be defined and then assigned to users in the [[Reference7:Administration/PBX/Objects/User|user configuration]].  All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template.   
Config templates can be used to set certain parameters for many users in an uniform fashion.  Templates can be defined and then assigned to users in the [[Reference7:Administration/PBX/Objects/User|user configuration]] from the '''Config Template''' list.  All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template.   


Config templates can be nested by defining a config template for the config template.
Config templates can be nested by assigning a previously defined config template to another config template.
 
  '''Caution:'''
  Be careful when assigning a config template to another config template.
  Don't assign a template to itself and don't create a loop of templates.
 
This feature is only possible with H.323.

Latest revision as of 14:13, 31 March 2010

Config templates can be used to set certain parameters for many users in an uniform fashion. Templates can be defined and then assigned to users in the user configuration from the Config Template list. All parameters that are not set (that is, are empty) in the user configuration will be inherited from the template.

Config templates can be nested by assigning a previously defined config template to another config template.

 Caution:
 Be careful when assigning a config template to another config template.
 Don't assign a template to itself and don't create a loop of templates.

This feature is only possible with H.323.