Reference9:PBX/Objects/Config 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 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.

Configuration Options available for Templates

The following configuration options can be configured thru templates:

Filter

The filter configured here restricts the numbers which may be called by a endpoint registered to this object

Diversion FDilter

The filter configured here restricts the numbers which calls may be diverted to by a endpoint registered to this object

Response Timeout

Overides 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.

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.

No Inband Disconnect

If this checkmark is set, a call disconect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediatelly without the inband information beeing sent.

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.

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.

Twin Phones

With this checkmark the twin phone mode is enabled for this object, which means that one user uses different phones. The main difference is, that if one phone is busy and additional call is sent to the busy phone only as call waiting and not to the other phones.

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.

Reporting

Enables Reporting for this user. A reporting license is needed to activate this. It is also needed to show up the call-list at the myPBX client.

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 excuted for calls rejected because of this.