Reference12r2:PBX/Objects/User

From innovaphone-wiki

Jump to: navigation, search
There are other versions of this article: Reference | Reference7 | Reference9 | Reference10 | Reference11r1 | Reference12r2 (this version) | Reference13r1 | Reference13r2

With the User PBX object, the standard subscribers of the innovaphone PBX is configured.

Contents

Configuration Options available for User-Objects

Filter
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 numbers to which diversions can be entered by the user
Block Execution
If this checkmark is set diversions to the numbers matching the diversion filter are not executed
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.
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.
Reporting
Enables Reporting for this user. A reporting license is needed to activate this. To show up the call-list at the myPBX client, you also need to activate the reporting flag.
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.
Do Not Disturb
No calls are sent to the user if set. Can be set by 'External UC' applications (e.g. Estos Procall)
Hide Connected Endpoint
In some cases it is desireable not to reveal the final destination of a call to a caller. For example a call center agent should not be called directly by the customer or to suppress call forwarding destinations

General Configuration Options

The information about general configuration options shared by all objects can be found at Reference12r2:PBX/Objects.

Configuration Options which can be defined by a Template

Some of the configuration options of a user object can be defined by Templates. More information about these options can be found at Reference12r2:PBX/Objects/Config_Template

DECT configuration options

The following details are entered in the DECT section and are therefore only relevant for DECT handset registrations:

  • Gateway: The system name (Name) of the IP DECT device.
  • Display: A variable text that is output on the IP DECT handset display.
  • IPEI: The serial number of the IP DECT handset. Is required for unique registration of an IP DECT handset.
  • AC (Access Code): It is also possible to allocate an access code (a kind of PIN), which protects the IP DECT handset against unauthorised use.
Personal tools