PBXware 5.3 System

From Bicom Systems Wiki

File System

File System

System window administers the core PBXware components such as the file system, system services, server details, licensing, sound files, MOH (Music On Hold), etc.

All PBXware logs, sound recordings, CLI and CLIR files are stored on the local file system. Some of these files can grow to a size which will not leave any space on the system. This section provides management of how and when these files should be rotated or deleted in order to prevent such a scenario.

  • CDR Partitioning:
Partitioning enables tables to be subdivided into smaller manageable pieces and each small piece is called a "partition".

Template for database partitioning is added for archiving CDRs in the selected period. A CDR table will be partitioned and the data from the CDR table will be archived. Data will be archived by month.

For new installations of PBXware: On new installations CDR will be partitioned automatically and, by default, will keep up to 1 year of data. There is an option in GUI to change this time frame.

Existing Installations: In this case, partitioning won’t be performed during the upgrade.

GUI: Select in GUI for how long to keep the data (up to 5 years) and wait until the system create partitions. Partition will be performed the first Sunday after the option has been selected. This option can be found under System > File System.

CDR Partitioning

Archived Reports: Users can see reports in GUI Home > Reports > Archived reports, and download archived files.


The following files are rotated after a selected period of time

  • PBXware logs:
Time PBXware logs are kept on the filesystem
'/opt/pbxware/pw/var/pbxware/log'
(ex. Default value '4 weeks' )
(Select box)
  • Other log files:
Time Asterisk logs are kept on the filesystem
'/opt/pbxware/pw/var/log/asterisk'
(ex. Default value '4 weeks')
(Select box)
File System





Following files are deleted after selected period of time

  • PBXware CLIR files:
Time PBXware CLIR files are kept on the filesystem
'/opt/pbxware/pw/var/pbxware/cli'
(ex. Default value '4 weeks')
(Select box)
  • Asterisk Backup files:
Time Asterisk backup files are kept on the filesystem
'/opt/pbxware/pw/etc/asterisk/backup'
(ex. Default value '9 weeks')
(Select box)
  • Voicemail:
Time voicemail files are kept on the filesystem
'/opt/pbxware/pw/var/spool/asterisk/voicemail/default/$VOICE MAILBOX' 
(ex. Default value '6 weeks')
(Select box)
  • Call Recordings:
Time recording files are kept on the filesystem
'/opt/pbxware/pw/var/spool/asterisk/monitor'
Limit for keeping call recordings is extended to 7 years.
(ex. Default value 'week')
(Select box)
  • Fax:
Time fax files are kept on the filesystem
'/opt/pbxware/pw/var/pbxware/fax'
(ex. Default value 'week')


Archiving Storage

archiving-storage-CC-5.3.png

Archiving Storage is a feature that can be used to move local files to a remote location. This service is provided by the user.

It can either keep these files on both locations (your PBXware server and remote location) or set the files to be removed after a successful offload. The feature can be configured to run automatically at certain times (daily, weekly) or in specified hour intervals.

NOTE: On the configured service, files are stored in folders with the following structure:

'/resource/year/month/day/hour/filename'

Where:
resource Type of resource offloaded (E.g. 'Recordings')
year Year in which the resource was created (E.g. '2019')
month Month in which the resource was created, in a numeric form. (E.g. '11' for all resources created in November)
day Day of the month in which the resource was created. (E.g. '23')
hour Hour of the day in which the resource was created. (E.g. '11')
filename Resource-specific file name format described below.

Client

Users can here configure the service that will be used as a destination for offloaded files.

enable-button.gif

Click this toggle button to enable the configuration for a specific Client

(Toggle button)


  • Client Type
Select the Client to be used
(Select Box)
NOTE: Please note that depending on the selected client (FTP. Google Drive, Amazon S3, Dropbox), different required fields will be shown and enabled.
save-to-enable-button.png
After selecting a Client, all required fields need to be populated in order for configuration to be saved.
(Button)


6.0 archiving storage test.png
test-button.png
Click this button to run a test for the selected Client.
(Button)
NOTE: In case the provided options are valid, the pop-up window will appear saying that "Test finished successfully".

Amazon S3

6.0 archiving storage s3.png

In case users press the 'Enable' toggle button and select 'Amazon S3' as a 'Client Type', these following required fields need to be populated:

  • Access Key
Enter the Access Key
([a-z][0-9])
NOTE: This is acquired from the Amazon account.
  • Access Secret
Enter the Access Secret
([a-z][0-9])
NOTE: This is acquired from the Amazon account.
  • Bucket
Define the S3 bucket to be used
([a-z][0-9])

Dropbox

6.0 archiving storage dropbox.png

In case users press the 'Enable' toggle button and select 'Dropbox' as a 'Client Type', these following required fields need to be populated:

  • Code
Press 'Get Code' to acquire a code
([a-z][0-9])
NOTE: This is acquired from the Dropbox authentication window.
  • Token
Press 'Get Token' after the code is set
([a-z][0-9])
NOTE: This token is automatically generated.

Setup Procedure

To set up the Dropbox service, please do the following:
  • Press the Get Code button after which the pop-up window will appear.
  • Log in to the Dropbox account.
  • Press the Allow button.
  • Copy the code displayed.
  • Populate the 'Code' field with the code.
  • Press the Get Token button.
NOTE: Dropbox has certain limitations for standard and advanced accounts (25,000 API calls/month for data transport partners).
For more information, please refer to their website: https://www.dropbox.com/plans?trigger=nr

FTP

6.0 archiving storage ftp.png

In case users press the 'Enable' toggle button and select 'FTP' as a 'Client Type', these following required fields need to be populated:

  • Server:
Enter the server's address/IP
([a-z][0-9])
  • User:
Enter the username to be used for registration
([a-z][0-9])
  • Password:
Enter the password to be used for registration
([a-z][0-9])
NOTE: For FTP servers with allowed anonymous users, only the Server field is required.

Google Drive

6.0 archiving storage google.png

In case users press the 'Enable' toggle button and select 'Google Drive' as a 'Client Type', these following required fields need to be populated:

  • Folder Name
Defines a folder name on Google Drive in which the offloaded files will be stored
([a-z][0-9])
NOTE: Please note that this folder does not need to exist. It will be created by Archiving Storage.
  • Code
Press 'Get Code' to acquire a code
([a-z][0-9])
NOTE: This is acquired from the Google Drive authentication window.
  • Token
Press 'Get Token' after the code is set
([a-z][0-9])

Setup Procedure

To set up the Google Drive service, please do the following:
  • Press the Get Code button after which the pop-up window will appear.
  • Log in to the Google Drive account.
  • Press the Allow button.
  • Copy the code displayed.
  • Populate the 'Code' field with the code.
  • Press the Get Token button.
NOTE: Please note that if both folder names are the same in the Client section and the Files section, Archiving Storage will fail to offload files. To avoid this, please use diferent names for each section.

Files

files-section-CC-archiving-storage.png

Users can here configure which files from the system will be offloaded. They can also configure how the files will be displayed on the service used.

  • Resources
Select Resources which should be uploaded
(E.g. Recordings)
(Select box)
Each Resource has a specific format for naming files. The available options and their filename formats are as follows:
  • Fax: 'date-time-src-ext-uniqueid.format'
  • CLIR Reports: 'uniqueid.log.gz'
  • Recordings: 'date-time-src-dst-uniqueid.format'
  • Voicemail: 'date-time-src-dst-uniqueid.format'
NOTE: In order to enable offload for CLIR Reports, the Recordings Resource has to be selected as well.
NOTE: Most Resources can offload multiple files for the same Resource. They will have the same name but different file Extensions.
(E.g. Voicemails will cause 2 files to be offloaded: one audio file and one txt file.)
  • Filename Date Format
Select the date format used for the date part of the above described Resource's file name
(E.g. 14 Apr 2021)
(Select Box)
  • Folder Name
Sets up a subfolder inside the configured services' starting folder where all the data for the system will be stored. This allows users to use the same service credentials on multiple systems while keeping the files separate for each system.
(E.g. Test)
([a-z][0-9])
The example shows a situation in which a user is utilizing 'Google Drive' as a Client.
  • In the first 'Client' section, the Folder Name is set to ArchivingStorage.
  • In the second 'Files' section, the Folder Name is set to MySystem.
  • As a result, all files offloaded for this system will be stored on 'Google Drive' in the ArchivingStorage/MySystem folder.
  • Filename Time Format
Define a time format used for the time part of the above described Resource's file name
(E.g. 24 Hour Format)
(Select Box)
  • Upload Older Than
Define how old a file has to be for Archiving Storage to offload it
(E.g. 1 week)
(Select Box)
NOTE: This is checked at the configured Archiving Storage execution time. For more information, please see the Schedule section. However, there will be files older than this configured time on the system. For example, if '2 weeks' is set and Archiving Storage is configured to run weekly, there can be up to 3 weeks old files on the system.
  • Convert to MP3
Define whether to convert files to MP3 before upload
(E.g. Yes)
(Toggle Button)
NOTE: This option applies only to the Recordings Resource.

Network

network-archiving-storage-cc-5.3.png

User can here configure the amount of system and network Resources that Archiving Storage will use.

  • Max Simultaneous Uploads:
Define the maximum number of concurrent uploads
(E.g. 1)
([0-9])
NOTE: The default number of maximum simultaneous uploads is 5. Please note that it may get lower during execution due to client limitations. For example, the FTP server has maximum connections per user configured.
  • Max Retries:
Define the number of retries on a failed upload in case of a non-critical error
(E.g. 10)
([0-9])
NOTE: The default number of retries is 10.
  • Upload Rate (Kbytes):
Define the upload rate limitation in kilobytes. The limit is set cumulatively for all uploads.
(E.g. 200)
(Select Box)
NOTE: The default upload rate is '5120'.

E-mail Notifications

6.0 archiving storage notifications.png

Users can here configure e-mail notifications which can be sent after Archiving Storage has finished offloading data.

enable-button.gif

Click this toggle button to enable e-mail nofitications

(Toggle button)


  • Send on Error Only:
send-on-error-only.gif
Click this button to generate an e-mail only in case the execution status is 'failed' or 'partial'
(Toggle Button)


  • E-mail:
Enter the e-mail address of a user who is going to receive this e-mail notification
(E.g. test@test.com)
([a-z][0-9])

Schedule

6.0 archiving storage schedule.png

Users can here configure the frequency of the Archiving Storage execution.

  • Schedule Type:
Select a schedule type that Archiving Storage will use.
(E.g. Disable/Hours/Daily/Weekly)
(Select Box)
  • Schedule Interval:
Define the number of time intervals in between offloads
(E.g. 5)
([0-9])
NOTE: The minimum schedule interval is one hour.
  • Schedule Time:
Define a specific time at which Archiving Storage should start offloads
(E.g. 03:10)
(Select box)

The options are as follows:

Disable The execution will never start automatically.
schedule-disable.png



Hours Archiving Storage will start offloading every N hours, where N is defined in the Schedule Interval field.
schedule-hour.png




Daily Archiving Storage will start offloading once a day at the time specified in the Schedule Time field.
schedule-daily.png




Weekly Archiving Storage will start offloading once a week, during the weekend.
schedule-weekly.png



NOTE: Archiving Storage can run only once at any given point of time. Please note that if the previous offload instance is ongoing when the next execution time arrives, that execution will be skipped.

System

6.0 archiving storage system.png
  • Remove Files
Enable this to remove files from the system after a successful offload
(E.g. Yes)
(Toggle Button)

Remote Recording Playback

Recordings that are offloaded to certain services with Archiving Storage can be listened to and downloaded from the 'Reports' page.

This feature is supported for the following services:
  • Amazon S3
  • FTP
  • Google Drive
For more information on this feature, please see Reports.

NOTE: Listen and download must be enabled in the license.

Services

This window controls the basic actions (start, stop, restart, reload) of PBXware services

Services
  • System
Stop/Start/Restart the system
(ex. Clicking on the 'Restart' button would reboot the system)
(Command button)
  • PBX service
Stop/Start/Restart/Reload the Asterisk (The core PBXware runs on)
(ex. Clicking on the 'Restart' button would restart the Asterisk)
(Command button)
  • PBXware:
Stop/Start/Restart/Reload the PBXware
(ex. Clicking on the 'Restart' button would restart the PBXware)
(Command button)
  • HTTP service
Stop/Start/Restart/ the nginx web server
(ex. Clicking on the 'Restart' button would restart the nginx web server. If you cannot reach the PBXware login screen this is the service you need to start/restart)
(Command button)
  • Database service
Stop/Start/Restart/Reload the MySQL database
(ex. Clicking on the 'Restart' button would restart the MySQL database server)
(Command button)
  • TFTP service
Stop/Start/Restart/ the TFTP server
(ex. TFTP is used for storing and serving the UAD/Phone auto-configuration files)
(Command button)
  • Jabber service
Stop/Start/Restart/Reload the Jabber messaging server
(ex. Clicking on the 'Restart' button would restart the Jabber server)
(Command button)
  • Memcached
Stop/Start/Restart the memcached service
(ex. Memcached service stores information which is read by PBXware Proxy)
(Command button)
  • PBXware Proxy
Stop/Start/Restart the PBXware Proxy
(ex. PBXware Proxy is connecting to asterisk manager and reading events which are then put into memcached for later usage. Based on that data, monitoring section will show information that user wants)
(Command button)


Server Details

This window resets the root PBXware password, timezone, and hostname

Server Details
  • Root Password:
PBXware prompts for this password during the system/ssh login and when accessing system services through the interface
([a-z][0-9])
  • Confirm Password:
Re-type the Root Password entered in the field above
([a-z][0-9])
  • Time zone:
Select the appropriate time zone in which PBXware is located
(Select box)
  • Hostname:
The name given to the machine which will identify the system on the network
(ex. my host)
([a-z][0-9])

For information on the rest of the fields in the Server details, check section Getting Started


Licensing

This window (re)licenses the system. Free and requested licenses are available (both bond to a system MAC address). If you are upgrading your license just paste the license key in the 'License Number' field, select the MAC address assigned to a license key and click on the 'Save' button

NOTE: The system must have access to a fully operational Internet connection in order to license the system.
Licensing
  • License Type:
Select a system license type
(ex. The system comes with two license types. FREE license and 'Requested License')
(Select box)
  • License Number:
Provide a system license number as received in the email.
TIP This field will not be active if FREE license is requested
(ex. ABCDE123)
([a-z][0-9])
  • MAC:
Select a MAC address to which the license will be applied
(ex. If your system has multiple MAC addresses select the one you wish to assign the license to. If this MAC address changes in the future, you will have to re-license the system)
(Select options)


SMTP Configuration

SMTP Configuration
  • E-mail Account:
Address to which the email will go if a recipient is not specifically defined
(ex. john@domain.com)
([0-9][a-z] @)
  • SMTP Address:
The host to send mail to, in the form "host | IP_addr"
(ex. mail.domain.com)
([0-9][a-z])
  • SMTP port:
Port used to send emails to the host
(ex. Default port is 25)
([0-9])
  • Authentication:
Select whether authentication with the SMTP server is needed or not
(ex. On)
(Option buttons)
  • Username:
Username used for SMTP AUTH
(ex. username)
([a-z][0-9])
  • Password:
Password used for SMTP AUTH
(ex. password)
([a-z][0-9])
  • Allow From: Override:
Are users allowed to set their own From: address
Example:
  • YES - Allow the user to specify their own From: address
  • NO - Use the system generated From: address
(Option buttons)
  • Use SSL:
Specifies whether ssmtp uses TLS to talk to the SMTP server
(ex. The default is NO)
(Option buttons)
  • Use Start TLS:
Specifies whether ssmtp does a EHLO/STARTTLS before starting SSL negotiation
(ex. See RFC 2487)
(Option buttons)


Sound Files

This section administers all sound files used by PBXware

Sound Files


Filter

Sound Files filter
  • Directory
Select directory from the drop down list to display only files located in that specific system directory.
The directory is sorted alphabetically.
  • Type
Select the type from the drop down list to display the files with the specified format.
Select one of the available options (gsm, ulaw, alaw, ilbc, sln) to display system sound files of that type.
e.g. Selecting 'gsm' will display all system sounds with the .gsm file type)
(Select box)
  • Letter
Select a letter from the drop down list to display the files whose names begin with the selected letter.
A-Z, 0-9

Convert

Sound Files options
  • Convert:
Convert the selected file to the desired codec.
E.g. After selecting a sound file(s) and clicking ‘Convert’, users can choose a codec to which they want to convert file from the drop-down list. The chosen sound file will then be converted.
(Command button)

NOTE: It is possible to convert more than one file at the same time.

  • Rename:
Renames the selected sound file (characters a-zA-Z0-9-_ are allowed).
E.g. Select a box next to a sound file, and then click on the sound file name and make desired changes. After changing, click on the ‘Rename’ command button and changes will be made.
(Command button)

NOTE: It is possible to rename more than one file at the same time.

  • Delete:
Deletes the selected sound file
E.g. Select a box next to a sound file(s) and click the ‘Delete’ command button.

NOTE: It is possible to delete more than one file at the same time.

  • Download:
Downloads the selected sound file to the user's computer.
(ex. Select a box next to a sound file(s) and click the 'Download' button to download the selected file to your computer.)
(Command button)
  • Upload
Uploads the selected sound file from the user's computer.
(ex. Click the 'Upload' button and select the preferred sound file from your computer to upload it on your system)
(Command button)

NOTE: If you are uploading an .mp3 or a .wav file, these will be auto-converted to other native formats. Other file formats apart from mp3 and wav will just be uploaded without automatic conversion.

A progress bar will be shown when uploading a file.
  • Listen
Listen
This option allows listening to a sound file. Select a box next to a sound file and click ‘Listen’ to hear it.
(Command button)


TIP

PBXware will play only sound file types equal to enabled codecs on dialing extension.

For example, Extension 1000 has only gsm codec enabled. When the same Extension logs in as a Queue Agent by dialing '*202 + $AGENT_NUMBER', all sounds played by PBXware (asking for password etc...) will be in '.gsm' format.

If multiple codecs are enabled for Extension 1000(ulaw,alaw,gsm), PBXware will play sound files with better sound quality (ulaw/alaw).

Music on Hold

Music on Hold is a music or advertisements played to callers while they are, for example, waiting for an agent or when put on hold.

Music on Hold


Content

MOH content window administers all PBXware MOH sound files. They are listed here with the following details

  • Name:
MOH sound file name
(ex. Motorbreath)
(Display)
  • Class:
MOH class sound file belongs to
(ex. Default)
(Display)
  • Status:
MOH sound file status
(ex. On/Off)
(Display)
  • 5.0.edit.png Edits the MOH file configuration
(ex. Click to edit MOH file configuration)
(Button)
  • 5.0.delete.png Deletes a MOH file from the system
(ex. Click to delete a MOH file from the system)
(Button)


Search

Search
  • Search:
Search phrase
(ex. Provide a search phrase here and hit enter to filter the records)
([a-z][0-9])
  • Name:
Should the search filter be applied to track names
(ex. Check the box to search track names)
(Check box)


Add/Edit Record

Add/Edit Content
  • Clip name:
Audio file name
(ex. Für Elise)
([a-z][0-9])
  • File:
Displays the full path to the music file on local computer. Click 'Browse' button to select a file
(ex. D:\Music\Ludwig van Beethoven\Ludwig van Beethoven - Für Elise.mp3)
([a-z][0-9])
  • Class:
Select the MOH class the sound file belongs to
(ex. default)
(Select box)
  • Status:
Set the status of the uploaded file(active/inactive)
(ex. On/Off)
(Option buttons)

Classes

Classes

MOH classes are something like folders on a computer filled with music files. Once a MOH class is assigned to the queue, for example, all sound files that belong to 'default' class are played back in random order. MOH classes are listed here with the following details

  • Name:
MOH class name
(ex. test)
(Display)
  • Status:
MOH class system status. When disabled, sound files that belong to the class will not be played anywhere on the system
(ex. On/Off)
(Display)
  • 5.0.edit.png Edits the the MOH file configuration
(ex. Click to edit MOH file configuration)
(Button)
  • 5.0.delete.png Deletes a MOH file from the system
(ex. Click to delete a MOH file from the system)
(Button)


Search

Search
  • Search:
Search phrase
(ex. Provide a search phrase here and hit enter to filter the records)
([a-z][0-9])
  • Name:
Should the search filter be applied to class names
(ex. Check the box to search class names)
(Check box)


Add/Edit Classes

Add/Edit MOH
  • Class Name:
MOH class name
(ex. IVR greetings)
([a-z][0-9])
  • Stream URL:
In latest version of PBXware we implemented support for easy MoH streaming. All you have to do is to create new MoH class and enter the link to your stream in Stream URL field.
  • Status:
Set the class status
(ex. On/Off)
(Option buttons)
  • Sort files:
Whether the files assigned to this class be played alphabetically or randomly
(Option buttons)

Sangoma Cards

This part of the interface is used to set Sangoma cards: PRI and Analog.

Sangoma Cards

Depending on the cards inserted and the number of ports on them, appropriate row of information will show up in the list of the cards. Also whether PRI or Analog card is inserted, they will have different configuration settings.


PRI Cards

When PRI card is inserted (like A101 which has one port) you will get as many "items" in the list as you have ports on that particular card. In this case, A101 has one port hence one item or card in the list. If you insert A102 you will get two items in the list because that card has two ports.

So, you need to configure every port individually, that's why there is a separate Configure button by every port.

PRI Cards

When the card is inserted you will see 'Not connected' Status. You need to connect the cable to it and click on the Configure button.

Card Options
  • Media type:
This is the type of the PRI system that the card is connecting to
Example:
  • T1 - PRI in US
  • E1 - PRI in EU
  • J1 - PRI in Japan
(Select box)
  • Coding:
This is the coding type for this port. This is automatically selected with Media type, so there is no need to change this option.
(ex. B8ZS)
(Select box)
  • Framing:
This is the framing used for this port. This is automatically selected with Media type, so there is no need to change this option.
(ex. ESF)
(Select box)
  • Clock:
Select whether the card will give a clock to devices (Master), or use a clock generated from telco (Normal)
(ex. Master)
(Select box)
  • Reference clock:
This option allows one to use the incoming clock from a different port as a clock source to this port.
NOTE: This option works only if Clock is Master.
(ex. 2)
([0-9])
  • Hardware DTMF:
Enable/Disable Hardware DTMF detection
(ex. Yes, No, N/A)
(Option buttons)

When you choose which type of connection is used and whether the card will use a clock source from the provider or generating one, click on the Save button. After that, click on Apply and then Restart the PBXware button.

If the cable was connected and configuration done properly, the system will display 'Connected' by the cards port.


Analog Cards

When you insert an analog Sangoma card, each card has one "item" in the list, regardless of the number of ports that it has on it. Under Port, it will show you how many FXS and/or FXO ports are configured.

Analog Cards
Analog Cards
  • Codec:
Codec used for this card
(ex. MULAW)
(Select box)
  • FXO Operation mode:
FXO Operation mode.
(ex. FCC)
(Select box)
  • Hardware DTMF:
Enable/Disable Hardware DTMF detection
(ex. Yes, No, N/A)
(Option buttons)

Procedure for configuring FXS/FXO ports is simplest. Click on Configure, Save, click on Apply, and then Restart PBXware.


TIP

If you change the hardware configuration of the card (PCI slot, number of FXS/FXO modules etc.) first reset the settings by clicking on the Reset button in the Configuration window, and then Save.


Information

PBXware continuously monitors system services, load, ZAPTEL modules, etc... in order to achieve and maintain high quality operations across the system and network. The result of these monitoring operations are also accessible to an authorized user.

System Information
  • Refresh Interval:
Time interval in seconds at which data is to be refreshed
(ex. 10 sec)
(Select box)
  • PBXware Uptime:
Total time PBXware is available for service
(ex. 1 hour, 16 minutes, 42 seconds)
(Display)
  • Last Reload:
Total time since PBXware was last reloaded
(ex. 10 minutes, 34 seconds)
(Display)
  • Load:
Load shown for the past 1, 5 and 15 minutes
(ex. 0.16)
(Display)
  • CPU:
CPU usage by: user, kernel and idle
(ex. 2.3%)
(Display)
  • Memory:
Memory usage by: Used, Cache, and Free
(ex. 299.1M)
(Display)
  • Swap:
Swap space usage
(ex. 5.2M)
(Display)
  • Processes:
Processes by Running, Sleeping, Stopped, and Zombie
(ex. 1, 96, 0, 0)
(Display)
  • rootfs:
File systems present shows by type, mount, usage, and free status
(ex. 0B, 0B, 3.3G, 1.5G)
(Display)
  • CPU Info:
Number of CPU's, Model, Speed, and Cache size
(ex. Pentium II (Deschutes), 398.28, 512KB)
(Display)
  • System:
General system details like Name, Kernel, Architecture, and Uptime
(ex. zenica.bicomsystems.com, Linux 2.4.21-27.0.1.EL, i686, 18d 1h 35m)
(Display)
  • Services:
Default system services running on the system
(ex. PBXware, Asterisk, TFTP)
(Display)
  • Modules:
Currently loaded ZAPTEL modules
(ex. wsusb)
  • Zaptel:
A list of all cards detected by the system is displayed here.
Channel Map displays used slots on TDM card. In this case, the first slot is filled with FXO module (displayed in black) while other 'Empty' slots are displayed in gray color).
(ex. Channel Map: 1: FXO, 2:FXS, 3:Empty, 4:FXO)
(Display)

TIP

With TDM cards, please make sure your power cable is connected. Message 'PLEASE CHECK TDM POWER CABLE' will be displayed if this happens.


Network Devices

In this section you are able to see status information of your network devices. Please note that in your case network devices section might look different and your network devices might have different names from devices presented in screenshot.




Next -> 18. Routes