From innovaphone-wiki

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

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 verified 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.
IP address for App Platform
The ip address of an App Platform can be configured here, with a DNS name used for it. If myApps uses a host to access the PBX different from the configured DNS name of the PBX, the hostname in any App url, which matches the configured AP DNS, is replaced by the AP IP. This way it is possible to configure a PBX with DNS names and access it with myApps when the DNS is not yet set up. If the checkmark Operation without DNS is set as well any matching DNS name is replaced also when an App service requests the URL of another App service (Example: Users requesting the URL of Devices for provisioning) and in the URL sent to the App services itself (Example: Devices uses this URL to construct the URL set at devices for the Devices registration).
Note that this mode is intended to be able to run the PBX using DNS names while the DNS is not yet in place. Once the DNS is up and running, neither the DNS name of the AP nor its IP address should be configured here.
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=g711a,g711u,g722,g723,g729,opus-nb,opus-wb&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,opus-nb,opus-wb 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").
The maximum length of the URL is limited to 500 characters (bytes).
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
d Diverting Name
#d Diverting Number
See Howto:Dynamic_MOH for more details on how to use dynamic music on hold.
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 w/o password will be accepted anyway

Security block time(s)
Time for which a registration to a user is blocked after attempt with wrong password. Default is 20s. With a value of 0 this features is turned off.
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.
Retries on busy (14s)
Number of retries (Each attempt runs for 14 seconds) of blind transfer to a busy endpoint, before a recall back to the initiator is executed. During an attempt, the PBX waits to see if the target is free, and then delivers the call. The default value are 4-retries if the field is empty. If there is a 0 configured no further (in addition to the initial) will be executed. (This function depends on the Recall Timeout so the Recall Timeout must not be empty)
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.
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.
Reverse Lookup URL
A String in the LDAP URL Format according RFC2255 which will be used by the PBX to make a lookup for all external numbers.
Number resolutions will be forwarded to internal applications like generated CDRs, Phone App etc..
Example: ldaps://,sn,company?sub?(metaSearchNumber=+%n)?\contacts
  • dn: dc=entries
  • attributes: givenname,sn,company
  • scope: sub
  • filter: (metaSearchNumber=+%n)
    • %n is a placeholder for the given cgpn
  • extension:\contacts
    • The username for the authentication.
  • %n - cgpn
  • %u - h323 name of the current object
Also there is an additional field for the LDAP password
Examples are listed in the Concept Article
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.
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/Area-Code/Country-Code
Prefixes to be used to map International, National and Subscriber numbers.
  • International Prefix (000 in Germany).
  • National Prefix (00 in Germany).
  • Subscriber (in Germany, 0 is a commonly used trunk line access code).
The SubscriberID is used for hotkey-actions within myAPPs-launcher. By use of node-objects, adjust the Subscriber Prefix in the respective node object number mapping.
For myPBX-launcher hotkeys, refer to the dialing location settings.
  • Area-Code (in Germany for example, the town Mannheim has area code 621).
  • Country-Code (for Germany, 49 would be used)
These settings resemble the same settings found in the Node and PBX object. However, they apply to the root node instead (and should be consistent through all PBXs in a multi-PBX system).
Adjust LDAP results for e.164
Add a "+" prefix to an PBX-internal LDAP-contact-search result. This is used for 3rd-party- and DECT-phones which are not able to benefit from the Dialing Location settings in case of LDAP-search in an E.164-setup. See also concept description.
The tones scheme to be used for PBX generated dialtones. This applies to dialtones generated for node prefixes, ringback on transfer and some more.

Slave PBX

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). For the replication process the PBX Password is used which have to be the same password on all PBXes in the system.
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

Standby PBX

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

For complete replication from master to slave or standby, check also password in Reference9:Administration/PBX/Security

License Status


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.

Personal tools