Reference7:Administration/PBX/Objects

From innovaphone-wiki

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

This page is used for the administration of PBX objects. A list of already configured objects can be displayed filtered by various criterias. New objects can be created and existing objects can be changed or deleted.

Contents

Display of existing Objects

By pressing the show link, existing objects are displayed. With the filter field (the input field left to the show link) the displayed objects are limited to those matching the filter. The filter is first applied to the 'Long Name' of the objects meaning a non case sensitive head match of the filter and the 'Long Name' is performed. If there are matching objects these are displayed.

If there are no matching objects the filter is used to match the Number of the objects including any node prefixes. This way objects of a given node with all subnodes can be displayed by entering the prefix of a node here.

Below the filter input field is a list of all PBXs in the system (at least the part of the system which is replicated to this device). By clicking on a PBX in the list only the objects which are assigned to this PBX are displayed and the groups configured on this PBX are displayed as well. By clicking on a group only the members of this group are displayed.

List of Objects

On the right side the list of objects is displayed. The most important configuration properties are displayed in this list to provide an overview. To view the full configuration of a given object it must be opened for editing by clicking the Long Name. The list can be sorted by clicking the table headers.

The Number of the objects in this list is not the number configured in the object but it is expanded with the prefixes of the nodes in which the object is configured.

Group memberships and Call Forwarding for an object are changed by clicking on the 'Groups' or 'CF*' link of the object. A '*' appended to a group displayed in this list means that the active flag of this group membership is set. A '!' appended to a group displayed in this list means that group indications are configured for this group.

The last column are the IP addresses of registered endpoints for a given object. If the physical location of the endpoint is not the same as the PBX, the physical location is indicated by @<physical-location> added to the IP address. A '*' appended to this field means that this is an password authenticated registration. Registrations which are because of a standby situation, which means they are not at the PBX for which they are configured, are marked with a special color (by default this is red).

New Objects

New objects are created by selecting the type of object in the drop down list and clicking the new link. If the list of displayed objects is limited to a PBX/Group (see above), the PBX property of the new object is preset accordingly and the group membership is added to the object.

Object Properties

* Note : never use special character "@" in any Object (Name, Long Name, Display Name), see also Support:Using @ in the Objects Names considered harmful in Master Slave Scenarios .

Depending on the type of the object different configuration parameters are available. Some configuration parameters are common for all objects.

Long Name This name is used to identify the object in the database and for display purposes. The long name must be unique throughout the system.
Name The name of the object. This name is used for signalling (like a call number) and must be unique throughout the system.
Hardware ID The hardware ID is a name which can be used to register an endpoint to this object. This name is not displayed and cannot be used to call the object. Some endpoints use default names to register based on the MAC address of the endpoint, which can be configured here. This way there is no need to configure any Name/Number on the endpoint itself.
Node The node that the object is assigned to. A Node hierachy can be configured using Node Objects. Objects which are assigned to the same node can call each other with just the number. To call an object in a different node escapes and node prefixes have to be used. If no node is configured, the object is assigned to the node of the respective local pbx. See Reference7:PBX Locations.
PBX The PBX that the object is assigned to. This PBX accepts registrations for the object. If no PBX is configured, the object is assigned to the respective local PBX.
Local Marks an object as local. Local means that it can be called from endpoints physically located at the same PBX without prefixes even if the calling endpoint is in a different node. Where the endpoint is physical located is defined by the PBX the endpoint contacts first (it may be redirected to another PBX then for registration). If the object does not have a PBX configured the call is routed to the PBX where the calling endpoint is registered.
Hide from LDAP This flag is effective only for LDAP clients connecting to the PBX with the read-only LDAP account "ldap-guest". This is the account used by the phone's default configuration.

It's intended to hide some default PBX objects and other objects not useful on a normal phone directory (for example FAX numbers).

Send Number If an object does a call, the calling party number for this call will be replaced by the number given (if any). Used to hide an extension. Currently works for non-gateway object types only.
Password / Retype Password If a registration password is allocated here, then it must be specified during registration, or otherwise the registration will fail.
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 which calls may be diverted to by a endpoint registered to this object
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 at a trunk object is executed for calls rejected because of this.
CFNR Timeout Overides the PBX global CFNR timeout for this object
Busy on n Call(s) 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.
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.
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.
Group Indications The group for which group indications are sent to the registered endpoints. The object must be active member in this group. The other objects (for which group indications are sent) need not to be active. To monitor other endpoints on a phone with a Partner/Pickup function key group indications are needed for the endpoints. The maximal length of the Group Indication Name in V7 is set to 48 characters.

Objects with empty node or PBX

If an object has no PBX configured, it will be replicated (if replication is turned on) to all slaves. Furthermore, any PBX will satisfy incoming registration requests. Calls to such objects that are built-in to the PBX and thus do not require a registration to work (e.g. Waiting Queue) will be processed by each PBX the call is presented to.

If an object has no Node configured, each PBX will consider this object to be defined within the node the PBX itself is assigned to. So if an object has neither Node nor PBX configured, it will be present in all nodes that have a PBX and calls to such objects will be processed locally for objects that are built-in to the PBX.

PBX Object Types

Personal tools