The fundamental operating modes of the PBX are configured on this page.
- PBX Mode
- The PBX operating mode
- Off - The PBX is disabled. After enabling the PBX a browser refresh is needed to activate additional PBX webpages.
- Master - The PBX on this device acts as Master. Within a multisite installation exactly one PBX must be configured as Master.
- Slave - The PBX on this device acts as Slave. Within a multisite installation several PBXes can be configured as Slave.
- Standby - The PBX on this device acts as Standby for the Master. As long as the master is available, this PBX is not active, but just monitors the Master. If the Master is not available this PBX is active.
- Standby-Slave - The PBX on this device acts as Standby for a Slave. As long as the slave is available, this PBX is not active, but just monitors the slave. If the slave is not available this PBX is active.
- 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.
- Use as Domain
- Uses the System Name as domain name, together with the name field in the user object the PBX constructs the email address (used for sending emails out ox myPBX). This mechanism is also used for Federation, to federate with other domains.
- 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.
- DNS Name of the PBX. If configured this will be used for myPBX redirects if a client tries to register at a PBX on which the user is not configured.
- 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.
- With PBX Pwd only: If checked only registrations with a PBX authentication or a verfiied certificate in case of H.323/TLS are accepted. In this case either "PBX Pwd" or "TLS only" is set in a device generated.
- Reverse Proxy Addresses
- Up to 8 addresses (no DNS names allowed) can be entered in this field, separated by comma. Registrations from one of these addresses are assumed to be routed through a Reverse Proxy. To the address '/<certificate name>' can be added to also check the TLS certificate of the Reverse Proxy. If the reverse proxy certificate is to be verified, the certificate or the issuer of the reverse proxy certificate must be trusted in the PBX.
- Assume TLS
- If the Assume TLS checkmark is set, it is assumed, that the reverse Proxy did a successful check of the TLS certificate against the registration name.
- 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=opus-wb,g722,g711a,g711u,g729,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=opus-wb,g722,g711a,g711u,g729,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. To prevent this situation when the MoH for some specific context/user(see below) is missing and silence is played instead of any MoH, an additional parameter fallback=true is available. If the file provided in the URL is missing (HTTP Error 404 Not Found is delivered by the HTTP Server) and the parameter fallback is provided, the default MoH will be played instead of silence. To use a custom file as fallback MoH, instead of default MoH, any file name can be provided with the fallback parameter: e.g. fallback=other_filename. The file other_filename.g7xx must be placed in the same folder as a file provided with URL. A special filename fallback=ringback can be used to generate a ringback tone (equivalent to TONE?tone=ringback) instead to play an alternative file.
- Within the URL %<id> can be used to put in some context information of the call. The information refers to the party which has put the receiving party on hold. For information about the receiving party itself, the id has to be preceded by '.' (e.g. .l).
- l Long Name
- h Name (H.323 id)
- n Number
- N Node
- P PBX
- d Diverting Name
- #d Diverting Number
- Example to use a specific soundfile for every node: http://<addr>/%N.$coder?coder=opus-wb,g722,g711a,g711u,g729,g723&repeat=true
- External Music On Hold
- To offload the device from playing the Music on hold, the Music On Hold can be played by a separate 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.
Pls. note that registrations from 127.0.0.1 w/o password will be accepted anyway
- Recall Timeout
- A value configured here enables recall after transfer. If a call is transferred and not answered within this time, the call is sent back to the transferring endpoint.
- Max Call Duration (h)
- Number of hours until a call with media is disconnected automatically. Affects all calls with initialized media channels signalled via PBX.
- Max WebRTC calls
- Sets the max. amount of concurrent WebRTC calls. Usage: x (max y) The counters x and y show the current amount of WebRTC calls respectively the max. amount of concurrent calls, measured since the last reboot of the PBX.
Note: This option become obsolete and it was removed since 12r1 - 12r1 Service Release 28 (121266)/Firmware 12r2 - 12r2 Service Release 23 (125560).
- Group Default Visibility
- Allows to restrict default visibility to active group members. If changed active subscriptions are not affected. Is used to prevent standard users from getting access to sensitive information like activities/presences of group members in myPBX. If not generally allowed by the administrator via this setting, normal users are not able to change it via myPBX.
- Presence with Alert
- Enable presentation of presence on phone upon alert. Setting applies for all PBX users. Alternatively, display of presence subject only delivered by Exchange can be prohibited - see Exchange Calendar Connector : Omit Subject
- 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.
- No CLIR on Internal calls
- If checked numbers are displayed even if received with presentation restricted. When sending a call presentation restricted can still be set and should be honored by a public network.
- Media Relay
- No Media Relay is done in the PBX
- All media traffic is routed through the PBX. With the No Media Relay if Addresses are identical or private checkmark, this is not done if the two call endpoints registration addresses are either private or equal (i.e. external endpoints behind the same NAT router). To identify an address as private the "Private Networks" configuration from IP4/General/Settings is used.
- Media traffic is routed through the PBX if calls are between private and public registration addresses but not for calls between private and private or public and public registration addresses. To identify an address as private the "Private Networks" configuration from IP4/General/Settings is used. In v11 this was the behaviour if 'RTP Proxy was on.
- Please note that when media relay is in effect for a call, video is not working. With ICE (available from v12r1), media relay in the PBX should be obsolete except for special applications. Check On or Auto 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 Reference9:Concept_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 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.
- For calls from local PBX only: If set on a master, calls from a slave are not sent to this destination but sent back to the slave where the call came from. On the slave the call is then sent to a destination configured with 'Route Root-Node External Calls to'.
- 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 hierarchically 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. For example to send from the faxserver in the case that the received mail contains the number in international format, e.g. +email@example.com
- International Prefix (
- National Prefix (
- Subscriber Numbers (in Germany,
0is a commonly used trunk line access code).
- International Prefix (
- The tones scheme to be used for PBX generated dialtones. This applies to dialtones generated for node prefixes, ringback on transfer and some more.
If the PBX is operated in Slave mode, then the Slave PBX section is displayed
- The VOIP protocol used for the registration to the master. Possible choices are H.323, H.323/TCP or H.323/TLS.
- The IP address of the PBX master
- License Only
- If set, the PBX obtains license from master, but acts as master in all other respects.
- Alternate Master
- The IP address of an alternative PBX master (standby, if available)
- The password to be used for registration at the Master as configured in the corresponding PBX Object (The length of the password is limited to 16 characters)
- Master GK-ID
- The System Name/Gatekeeper ID of the PBX Master were will register (Optional, usually used for DynPBX).
- 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).
- dyn PBX ID
- This parameter allows to set replication from a specific DynPBX configured on the Master Device.
- Use local static User DB
- A dynPBX has also this checkmark. The database of the main PBX is used, but be careful due to the increased memory usage. The dynPBX will create its own PBX datastructure which allocates memory.
- Route Master calls if no Master to
- If the master is not available, master calls are sent to this destination. Destination has to be an object with active registration.
- Max Calls to Master/No Reroute
- 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 rejected if No Reroute is set or is handled as if the master was not available otherwise.
- License Limits
- Here we can set limit of licensing for this Slave PBX for Port, Mobility, Operator and Softwarephone.
For complete replication from master to slave, check also password in Reference9:Administration/PBX/Security
If the PBX is operated in Standby mode, then the Standby PBX section is displayed
- The IP address of the PBX master
- Replicate from Master
- Turns on full replication from the master PBX
- use TLS
- Use LDAPS (TLS) instead of LDAP (TCP).
- dyn PBX Id
- Replicate objects from a specific dynPBX.
For complete replication from master to standby, check also password in Reference9:Administration/PBX/Security
A list of all installed PBX license with their current usage is displayed here.
- The total number of installed licenses of this type.
- The total usage of this license type
- The usage of this license on this PBX
- The usage of this license on PBX's registered to this PBX.
see Reference10: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.