Admin Settings

In order to change the settings that affect the whole system, you need to be logged in with administrator privileges.

System Settings

Here you can configure some general system settings.

  • Expand the menu General under "Settings".
  • From the expanded General menu, click on System.

Explanation of the Settings


  • System Name: This field allows the administrator to set a name for the system. The name is used in several places to identify the system. For example, when the system sends out emails with system performance information, the system name will be placed into the subject line of the e-mail.
  • System management DNS address: This is the address under which the system administrator can log in. If set and when using the ACME protocol to issue certificates, the PBX will attempt to generate a X-509 certificate for this address.
  • Default IVR Language: This setting represents the language that is used for voicemail and IVR prompts. Only U.S.-English prompts are included in the installer, but additional languages can be installed.
  • Default Tone Language: This setting allows you to control the ringback and busy tones that a caller hears during voicemail prompts and IVR interaction. The files that influence this setting are ringback.wav and busy.wav. These files are located in the audio_* directory. The * represents a language identifier code.
  • Default Web Language: This setting controls the language used on the web interface. The file that influences this setting is lang.*.xml, where * represents a language identifier code.
  • Time Zone: The Time Zone setting is used to set the local time zone. It influences the time that appears on a user’s mailbox messages, telephone display, and voicemail. The system is capable of dealing with several time zones at once, making it possible for every user to select his or her own time zone.


From this section, you can set the performance-related settings.

  • Maximum Number of Calls: This setting defines the number of simultaneously calls allowed by the system. Because every call requires a certain portion of the available CPU, allowing too many calls will affect the quality of all ongoing calls. By limiting the number of calls on the CPU, you can reject calls that would otherwise potentially degrade overall performance. On modern PCs, 100 or more calls can run on one computer; however, on an embedded system, you will probably have much less CPU power and thereby increase the probability of running out of CPU power if you allow that many calls. If this field is left blank, the key in the system will limit the calls, or the CPU limitation, when reached, will limit the calls.
  • Process Affinity Mask: This field allows the administrator to assign a particular CPU to the pbxctrl system process. When using a multiple-core CPU, the operating system has to assign processes to processors. By default, the operating system tries to balance out the load so that the overall system performance is as fast as possible. However, the disadvantage with this approach is that the whole process gets stuck for some time while moving the processes from one CPU to another. If during that time the CPU should play out media, it will come across as stuttering and be perceived as jitter coming from the system. In order to avoid this problem, bind the pbxctrl to one fixed CPU. Depending on the operating system, you can do this manually or you can ask the system processes to do this during startup. Changes to this field require a system restart. The processor affinity is represented as a bitmask, with the lowest order bit corresponding to the first logical CPU and the highest order bit corresponding to the last logical CPU. For example:
  • 0x00000001 = 1 = 0001, is CPU0 (first processor)
    0x00000003 = 3 = 0011, is CPU0 and CPU1
    0x00000004 = 4 = 0100, is CPU2 (3rd processor)
  • If this field is left empty, the PBX will default the value to 1, meaning it will bind itself to CPU 0 (or core 0). In a 4-core (4 CPU) processor, if you want the PBX to bind itself to CPU0 and CPU3, then you have to set the value to 9 (binary value 1001 = 9). If you want it on all cores, then set this value to 15 (binary 1111 = 15). I think you get the point now. So, depending on the number of CPUs on the processor and your requirement, you can come up with a proper number to set here.
  • Maximum Duration of Call Recording: This setting allows you to establish an upper limit on call recordings. This is important since large recordings can cause problems with system performance. (Recordings left in voicemail boxes consume disk space and can have limitations placed on file size.)
  • Max. size of a configuration backup file: This setting allows you to establish the maximum size, in bytes, of the backup file. The default is 1 MB. If your system has a lot of data to be backed up, increase this value. The backup feature through the web interface is used mostly in the appliances (in embedded systems where the file access is primitive). On other systems, it is advisable to use the OS file manager to do the backup.
  • Max. number of concurrent registrations per extension: This setting controls how many user agents (i.e., phones) can be registered against an extension. This feature is useful if you want to restrict the number of phones that can be registered to an extension. If this field is left blank, the extension will have no limit.
  • Minimum Registration Time (s): In a SIP environment, the registrar determines how long a user agent may be registered. Short registration times have a negative impact on the performance; however, it is critical that user agents stabilize quickly once they’ve lost their connection to the system. This setting defines the lower limit for the registration time. The default is 30 seconds.
  • Maximum Registration Time (s): This setting is used to define the upper limit for the registration time. The default value is 360 seconds.
  • UDP NAT Refresh (s): If the registering user agent is behind NAT, the system uses this setting to control the registration. The system registers agents that use the UDP transport layer only for a short time, so that the user agents will re-register quickly and keep the NAT bindings alive. Typically, the settings for UDP should be from 15 to 45 seconds since most NAT routers close ports after 60 seconds of inactivity. The default is set to 30 seconds.
  • TCP/TLS NAT Refresh (s): This is similar to UDP NAT refresh setting. Since TCP/TLS connections do not need to refresh the bindings as often, a value of a few minutes are okay in most situations. The default is set to 180 seconds (3 minutes).
  • Maximum call duration: This setting establishes an upper limit for the call duration. By default, the setting is 2 hours (7200 seconds), but you can increase it if you lean toward longer phone calls. This setting is crucial for keeping your call list clean, for example, if one mailbox talks to another mailbox or if a call does not drop properly, the system can automatically clean this up.
  • Note: If your license has limitations on the call duration, then lesser of the two will be used.
  • Maximum ring duration (s): This setting determines the length of time the PBX willwait before it disconnects a call.

Domain Admin Permission

These settings allow the administrator to restrict certain functions from the domain admin:

  • Allow domain admin to change trunks: If this setting is disabled, the domain admin will be unable to change the trunks that have been configured for the domain.
  • Allow domain admin to change dial plans: If this setting is disabled, the domain admin will be unable to change the dial plans that have been configured for the domain.
  • Allow domain admin to create or change accounts: If this setting is disabled, the domain admin will be unable to create new accounts or change existing accounts.
  • Allow domain admin to create or change ANI: If this setting is disabled, the domain admin will be unable to create new ANIs or change ANIs.
  • Hide aliased rows under domains page: This setting allows you to control whether the alias account of your domain will be displayed on the Domains page. When this setting is set to No, the list of domains will include the alias in addition to the primary domain, which may be confusing since it appears that more domains are on the system than there actually are. When this setting is set to Yes, only the primary domain will be displayed.

Recording/CDR Settings

Here you can configure CDR and recording settings.

  • Expand the menu General under "Settings".
  • From the expanded General menu, click on Recording/CDR.

Explanation of the Settings

  • Default CDR listing size: A Call Detail Record (CDR) is a record that is produced by the system and contains the details of calls that have terminated on the system. CDRs include the date and time the call started, the number that made the call, the number that received the call, and the call duration. Use this field to limit the number of CDRs that will be displayed in the web interface (CDRs can be memory consuming). The default is 30 CDRs.
  • Keep CDR Duration: This setting defines the length of time CDRs are kept on the file system. CDRs can consume large amounts of disk space, so be careful when setting this field. If too many CDRs are on a busy system, the system will not start. The default is 7 days. The duration can be expressed in various time units:
    Seconds: Enter an s after the number (e.g., 60s for 60 seconds)
    Minutes: Enter an m after the number (e.g., 60m for 60 minutes)
    Hours: Enter an h after the number (e.g., 24h for 24 hours)
    Days: Enter a d after the number (e.g., 7d for 7 days)
  • Maximum number of CDRs (per type): This setting allows the admin to control the number of CDRs, according to type, that will be retained on the system. The CDRs are classified according to extension, trunk, and ivr and are stored in the cdre, cdrt, and cdri folders, respectively.
  • CDR URL: The CDR URL field controls where CDRs are written. The system can write CDRs to a CSV file, an email address, a server address, or to a SOAP destination. To populate the CDR URL field, use the syntax shown below. CDRs can be viewed only after they have been collected and organized through an external call accounting application. The detail information about CDR can be found on the CDR page.
  • Record Location: This field determines where system-initiated recordings will be stored on the system. By default, $r/$o/$a/$d-$t-$i-$n.wav is the string used in this field. If you wanted to set an absolute path for the recordings, you would use something like /tmp/test/$d-$t-$i.wav. For more information about recording calls and how to create a string for the Record Location field, see Record Location.
  • Compress Recordings: The system will compress recordings when this setting is enabled. Otherwise, recordings will be saved as 16 bits/sample.
  • Maximum Duration of Call Recording: This setting allows you to establish an upper limit on call recordings, which is important since large recordings can cause problems with system performance. To further conserve disk space, you can limit the number of messages that can be stored in a user’s voicemail box (see the Voicemail Size setting in Domains).
  • Delete the call recording files along with the CDR: Whenever the CDR related to that call is deleted, the call recording will also be deleted. So, if the CDR gets deleted based on the time limit (7d, 1d, etc.) that has been set in the Keep CDR Duration setting, then the recording will be deleted along with it.

System Security Settings

These settings are located within Admin > Settings:

  • Web Session Timeout (s): This field determines the length of time a web session will stay active before it times out. The duration is set in seconds, and the default value is 3600 (1 hour). Increase or decrease this setting depending on whether you want the system to log you off after a certain period of time. Once timed out, the main login screen will be displayed
  • Password Strength: This field is used to specify the types of passwords that are acceptable. The default is “Accept All Passwords,” but it is advisable to require medium or high-security passwords. Users should be encouraged to avoid passwords that are dictionary words and to instead create passwords that are more challenging. A combination of letters, digits, and symbols is recommended.
―Accept all Passwords: All passwords will be accepted.
―Medium Security: The score must be 120 or higher.
―High Security: The score must be 200 or higher.
Character Type Points
Digits 10
Upper/lowercase letters 26
Symbols 28
  • SOAP Trusted IP: SOAP (Simple Object Access Protocol) is an XML message-based protocol specification that is used to allow computers to talk to each other over a network such as the Internet, typically as part of a Web service. SOAP can be used to pass almost any type of data between two applications. Because it is based on XML, SOAP is language- and platform-independent. The two applications could be written in different languages and could run on different operating systems. SOAP is often used to make Remote Procedure Calls (RPCs). When used to encode RPCs, SOAP is used as the request/response protocol. The SOAP Trusted IP field controls a SOAP request coming from random addresses and is available only if the license key contains a SOAP flag. Use this field to specify the IP address or the host names that are permitted to make SOAP requests to the system (i.e., management system). If you want to allow multiple systems to send SOAP requests, use a space to separate the entries.