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 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. Referenced templates must not reference other templates in turn (these will be ignored then).
Note When editing a Config template the changes will be applied to the User Objects that have this config template but if you delete the Config Template and create a new Template with the same Name and different settings no changes will be done on the User Object. So in that case you need to go to the User Object and delete the previous Config Template and then select again the config template that looks the same since have the same name (Select Blank, click Apply, Select Config Template and click Apply/OK).
See Reference13r1:PBX/Objects#General_Object_Properties for generic object properties.
Configuration Options available for Templates
The following configuration options can be configured thru templates:
- The filter configured here restricts the numbers which may be called by a endpoint registered to this object
- Diversion Filter
- The filter configured here restricts the creation of call forwarding to matching numbers that can be set up by an H.323 endpoint registered to this object
- Block Execution
- If enabled, the Diversion Filter prevents the execution of the call forwarding to matched numbers. This option is available at the User Object only.
- Response Timeout
- Overrides the PBX global response timeout for this object
- Busy on ... Calls
- If this value is set a call to this user object is rejected with User Busy if n or more calls are active on this user object. If the object is of the gateway type (Gateway, Trunk, ...) calls from endpoints registered to this object are rejected as well in this case. The switch will have no effect if the option 'Twin Phones' is set.
- External UC
- A Long Name of a External UC object can be configured here. Presence Information for this user is then obtained from a UC Server which is registered to this Object. Instant messaging Sessions for this user are also forwarded to the External UC interface.
- define use of messaging
- Name of the Push object that should be used for push notifications towards myPBX for mobile phones.
- No Inband Disconnect
- If this checkmark is set, a call disconnect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediately without the inband information being sent.
- Store Phone Config
- If this checkmark is set, the PBX stores the config of the phone. The first time a phone registers the predefined config at the PBX is sent to the phone even if it is empty. Then the local config stored at the phone is merged into the received config and the result is returned to the PBX. After this the local config is deleted and no local config is stored on the phone anymore. Later config changes on the phone will be sent to the PBX and stored there. On registration the PBX sends the complete config to the phone again.
- Discard Phone Config
- If this checkmark is set in addition to Store Phone Config the local config stored at the phone is discarded but not returned to the PBX when the phone registers the first time, i.e. the phone is configured with the config predefined at the PBX. This checkmark should be activated during normal PBX operation. When migrating from a system with phone based config to PBX based config it might be required to disable the Discard Config on Phone flag. After the migration from local stored to pbx stored phone config is complete, the Discard Config on Phone should be re-enabled.
- Twin Phones
- With this checkmark the twin phone mode is enabled for this object. Checkmark off (is not set) means that any additional calls a user may receive while in an existing call will signal on any other phone on which the user has an active registration. Checkmark on (is set) means if one phone is busy any additional calls are sent to the busy phone only (as call waiting) and not to the other phones on which the user may have active registrations. If "Call Waiting" is disabled on the busy phone a second call gets a busy tone and a missed call is displayed when the active call is terminated.
- Reject ext. Calls
- If this checkmark is set a call from an external source to this object is rejected. A calling party numbering plan private is used to decide that the call is coming from an internal source. An invalid number destination is executed for calls rejected because of this.
- Hide Connected Endpoint
- With this check the destination to which a call is forwarded can be hidden to the caller. Helpful when e.g. forwarding a call to a non-public number.
- Call forward based on Presence
- Use presence as indicator to forward calls to set destinations. When this checkmark is set, incoming calls are forwarded directly to targets defined as CFB if the initially called extension has set an active presence of type Busy/DND and targets defined as CFNR for presence of type Away.