The fundamental operating modes of the PBX are configured on this page. These parameters are stored in the config file. All other PBX config is stored in the LDAP.
|PBX Mode||The PBX operating mode
|System Name||The system Name. On all PBX within a multisite installation the same System Name must be configured. For H.323 endpoints this name is the gatekeeper identifier, for SIP endpoints it is the server name.|
|PBX Name||The name of the PBX on this device. With this name a PBX is associated to a node. The field 'Name' (not Long Name) of a PBX Node object relates to this name.|
|Unknown Registrations||If this checkmark is set, the PBX accepts 'unknown' registrations. This means registrations with no matching object configured. If from an endpoint registered in this way a number of an object is dialed, which has no registration active and no 'HW-ID' configured the name used for the registration is configured as 'HW-ID' of this object. This is an easy way to deploy large numbers of phones.|
|Music On Hold URL||A URL for the Music On Hold. This file is read by the PBX using HTTP and sent to a held endpoint via RTP. The format of this URL is
http://<addr>/<file>.$coder?coder=g729,g711a,g711u,g723&repeat=true. <addr> is the IP address of the http server, no dns name is allowed here. <file> is the filename. $coder will be replaced by the actual coder used. Parameters: coder=g729,g711a,g711u,g723 is the list of available coders. Only these coders must be specified for which a corresponding file exists. repeat=true should be specified in order to loop the file endlessly. random=true can be used to start the music on hold on a random point (this will work only if the URL is not local though).
By default the built-in Music-On-Hold is played (Pseudo URL: "MOH?coder=g729,g711a,g723&repeat=true"). You can also play a dial tone (Pseudo URL "TONE") or a ring-back tone (Pseudo URL "TONE?tone=ringback"). If you configure a wrong (or invalid) URL then you will have silence as MOH.
|External Music On Hold||To offload the device from playing the Music on hold, the Music On Hold can be played by a seperate device. This device can register with a name configured here. To retrieve the Music On Hold a call is sent to this device. For each held endpoint a call is sent.|
|Response Timeout||Global timeout (in seconds) after which any action for no response is taken (e.g. Call Forward on No Response). A timeout configured at any object overrides this value.|
|Dial Complete Timeout||Global timeout (in seconds) after which any action for incomplete dialed number is taken (e.g. incomplete destination at trunk object).|
|No. of Regs w/o Pwd||Number of registration without password authentication which are allowed per user. If 0 is configured no registration without password is possible.|
|Recall Timer||A value configured here enables recall after transfer. If a call is transfered and not answered within this time, the call is sent back to the transfering endpoint.|
|Pickup Prefix V7||In V7, the pickup prefix is obsolete. Please use the pbx object DTMF Featurecodes.|
|Enable External Transfer||Unless this checkbox is set any attempt to transfer an external call back to an external destination will result in disconnection of the call.|
|RTP Proxy||If this checkbox is set, all media traffic is routed thru the PBX. Check this only if you need to have this, since it creates CPU load on the PBX.|
|Generate CDRs||If this checkbox is set, the PBX generates CDRs for all calls. See Reference:Call_Detail_Record_CDR_PBX for a description of the CDRs.|
|Route Root-Node External Calls to||Destination object (Long Name) of Root-Node external calls. This configuration option is available on the Master or Standby PBX only. Any call call which cannot be terminated inside the PBX is sent to this destination as long as neither the source nor the destination of the call can be associated with a node with a PBX configured. This object must be assigned to this PBX.|
|Route PBX-Node External Calls to||Destination object (Long Name) of PBX-Node external calls. Any call which cannot be terminated inside the PBX is sent to this destination as long as the source nor the destination of the call can be associated with the node of this PBX. If a call is sent from or to an object defined inside the node of this PBX or in a node hierachically below the node of this PBX the call is associated to the node of this PBX. This object must be assigned to this PBX, that is, it has to register to this PBX.|
|Route Internal Calls to||Destination object (Long Name) to which any call is sent for which a PBX internal destination was found, except for those calls that originated from that object. This can be used to apply special routing on PBX internal calls.|
|Escape Dialtone from||The PBX object (Long Name) to which a call is made to get a dialtone if a dialtone is configured for the escape of a node. As above, this object must be assigned to this PBX.|
|Prefix for Intl/Ntl/Subscriber||Prefixes to be used to map International, National and Subscriber numbers.
If the PBX is operated in Slave mode, then the Slave PBX section is displayed
|Master||The IP address of the PBX master|
|Alternate Master||The IP address of an alternative PBX master (standby, if available|
|Password||The password to be used for registration at the Master as configured in the corresponding PBX Object|
|Route Master calls if no Master to||If the master is not available, master calls are sent to this destination|
|Max Calls to Master||This parameter can be used to limit the calls to the master. If a call is sent to the master and there are already calls to/from the master equal to or exceeding this value, the call is handled as if the master was not available.|
|Replication||This parameter allows you to select the replication style for the slave PBX: either All or Local (only users that need to be known in this PBX)|
The following figure shows the relation between master's PBX object and the slave's configuration. Click to view screenshot of Master - Slave registration
For complete replication from master to slave, check also password in Reference8:Administration/PBX/Security
If the PBX is operated in Standby mode, then the Standby PBX section is displayed
|Master||The IP address of the PBX master|
|Replicate from Master||Turns on full replication from the master PBX|
The following figure shows the relation between master and the standby unit's configuration. Click to view screenshot of Master - Standby registration
For complete replication from master to standby, check also password in Reference8:Administration/PBX/Security
A list of all installed PBX license with their current usage is displayed here.
|Count||The total number of installed licenses of this type.|
|Usage||The total usage of this license type|
|Local||The usage of this license on this PBX|
|Slaves||The usage of this license on PBX's registered to this PBX.|
see Reference8:Licenses for a description of the licenses.
The current number of registrations and the limit as defined by the base license is displayed here. Because this limit is defined by the base license it includes any registrations because of standby as well, which require no registration license.