Tools — How-To Guides

Step-by-step instructions for audio messages, disk management, CPU monitoring, and data export. The Tools section has tabs: Lists, Audio Messages, Alert Manager, SMS Gateway, Control Port, DISA, Disk Analyzer, CPU Load.

Record a new audio message

Goal: Record a new audio message using your computer's microphone — for use as a voicemail greeting, a DISA menu prompt, or music on hold.

1. Go to Tools > Audio Messages.
2. At the top, select Manage messages for user: SYSTEM (for system-wide messages like DISA greetings) or a specific username (for personal voicemail).
3. Click the Record New tab.
4. Adjust the Recording volume slider if needed (default: 100%).
5. Click Start recording. Your browser will ask for microphone permission — allow it.
6. Speak your message. Click Stop when done.
7. The recording is saved and becomes available in the Manage Existing tab.

Create an audio message using Text-to-Speech

Goal: Create an audio message by typing text and letting the Abilis convert it to speech — useful when you need a quick greeting without recording your own voice.

1. Go to Tools > Audio Messages > Text To Speech tab.
2. Type your message in the text area (maximum 800 characters, counter shown at top).
3. Select a voice from the dropdown (e.g. en-GB-Wavenet-A for English British female).
4. Click Play to preview the audio.
5. Click Download audio to save the file, then assign it to a DISA service or voicemail through the Manage Existing tab.

Upload an audio file from your computer

Goal: Upload an audio file (MP3 or WAV) from your computer to the Abilis — for example, a professionally recorded greeting or a music-on-hold track.

1. Go to Tools > Audio Messages > Edit Audio File tab.
2. Click Upload audio.

3. Click Choose file and select an audio file from your computer.
4. Click Close when done. The file appears in the editor where you can trim or adjust it.

Edit or trim an audio file

Goal: You have an audio message that is almost right but needs a small adjustment — trim a few seconds of silence from the start of a voicemail greeting, cut off a throat-clearing at the end of a DISA announcement, or shorten a piece of music-on-hold that is slightly too long. The Abilis has a built-in editor so you don't need Audacity or any external tool.

1. Go to Tools > Audio Messages and switch to the Edit Audio File tab.
2. Load the file to edit. You have two options:
   • Click Upload audio to pick a file from your computer (if it's not already on the Abilis).
   • Or select an existing file from the Manage Existing list — it opens in the editor for modification.
3. The audio waveform appears in the editor. Typical controls:
   • Play / Pause — listen to the current version.
   • Selection handles — drag to mark the region you want to keep (or the region you want to delete).
   • Trim — keep only the selected region; everything else is discarded.
   • Delete — remove the selected region; the rest of the audio joins together.
4. Preview the result with Play. If it sounds right, click Save. Otherwise undo and adjust the selection.
5. The edited file replaces the one in the audio library — every DISA service, voicemail, or MIX that references it now uses the updated version immediately.

Check disk usage and clean up space

Goal: Check how much disk space the Abilis is using and what is consuming it — recordings, logs, audio files — and clean up if the disk is getting full. and lets you check disk health.

1. Go to Tools > Disk Analyzer.
2. The table shows all connected disks: ID, Size, and Partitions (drive letters like C:, D:, E:).
3. Click on a disk to see details.

4. The detail view shows:
   • Status: Ok or error state.
   • Partitioning: supported or not.
   • A visual map of partitions (blue blocks).
   • Per partition: Drive letter, Serial Number, State, File System (FAT32, NTFS…), Size with free space and percentage, Interface (AHCI, USB…).
5. Click Check disk to run a health check on the selected partition.

Free up disk space when the Abilis is getting full

Goal: You've checked disk usage and one of the partitions is near full. You want to free space — safely, without deleting anything critical — so the Abilis keeps running normally and has room for new recordings, logs, and firmware upgrades.

What usually fills the disk, in order of how much space each can take:

1. Video recordings from cameras — by far the biggest space consumer on units with videorecorder.
2. Old firmware versions kept on disk after upgrades.
3. Call recordings.
4. Old audio-message versions and unused greetings.
5. Logs, configuration backups, and crash dumps.

1. Recordings first. On units with cameras, open Videorecorder and review the Storage and Recording max age settings per camera. Lowering the max age from 30 days to 14 days typically recovers most of the space — see Manage recording storage. Old recordings are deleted automatically the next time the retention job runs.
2. Old firmware versions. Go to Boot Management. If several older firmware versions are listed under Select next boot version, keep the current one and the most recent previous one as a rollback safety net, and delete the rest. Each version saved is typically 50–150 MB.
3. Call recordings. Go to Phone > Recent Calls. Calls with recordings attached have a player icon. Export any you need to keep, then delete the rest. For bulk cleanup of old recordings, filter by date range first.
4. Unused audio messages. In Tools > Audio Messages > Manage Existing, review the list and delete old greetings that are no longer referenced by any DISA service or voicemail. Be cautious — deleting a greeting that is in use will break the corresponding DISA route until you replace it.
5. After each round of deletion, go back to Tools > Disk Analyzer, click the partition, and confirm the free-space percentage has improved.

Monitor CPU load

Goal: Check whether the Abilis processor is under stress — and if it is, find out whether it's a temporary spike or an ongoing problem that needs attention.

1. Go to Tools → CPU Load. The page shows the current processor load as a percentage with a visual bar indicator. A quick glance tells you if the system is idle (0–10%), working normally (10–30%), or under heavy load (above 50%).
2. Check the CPU Load History tab (next to CPU Load at the top). This shows a graph of CPU usage over time — useful for spotting patterns like "CPU spikes every day at 9am when everyone arrives" or "CPU has been climbing steadily over the past week."
   Note: If the History tab shows "Variable with not logged OID in request" instead of a graph, SNMP logging for the CPU metric hasn't been configured. The real-time CPU Load tab still works — History just needs SNMP polling to be active to record data over time. If you need historical CPU trends, SNMP logging for the CPU metric must be enabled — this is a unit-wide setting; contact Anteklab to turn it on.
3. Interpret what you see:

   Load	What it means
   0–30%	Normal. The Abilis is comfortable.
   30–70%	Moderate. Busy but has headroom. Watch it during peak hours.
   Above 70%	Heavy. The web interface may respond slowly. Check what's causing it — many simultaneous phone calls (especially with transcoding), HD camera recording, heavy VPN traffic, or an automation script running at high frequency.
   Above 90% sustained	Overloaded. Calls may drop, cameras may stutter. Reduce active services or contact Anteklab support.

Export logs and call data

Goal: Download call logs, system logs, or traffic data from the Abilis to your computer — for reporting, auditing, or sending to support when diagnosing a problem.

1. Decide what you need to export. The Abilis stores several types of data, and each is exported from a different page:

   What you need	Where to find it	What you get
   Call history (who called whom, when, duration)	Phone → Statistics	CSV with answered, failed, busy, abandoned calls per extension
   Bandwidth usage per connection	Networking → Info → Line Load	CSV with throughput data over time
   Sensor readings (temperature, humidity, etc.)	Automation → Monitoring	CSV with timestamped sensor values

2. Navigate to the relevant page from the table above.
3. Generate the report or graph you want to export (select the time range, the user or connection, etc.).
4. Click "Export to CSV". The button appears once the data is displayed. Your browser will download a .csv file that you can open in Excel, Google Sheets, or any spreadsheet application.

Send a bulk SMS blast from a CSV file

Goal: You need to send the same SMS — or personalised variants — to many recipients at once. Customer appointment reminders, a delivery notification to a distribution list, a service-outage warning, invitations for an event. Typing each one in the web form would take hours; uploading a CSV takes one minute.

1. Prepare the CSV file on your computer. A minimal layout:

   +393481234567,Hello Mario — your order is ready for pickup.
   +393482345678,Hello Giulia — your order is ready for pickup.
   +393483456789,Hello Paolo — your order is ready for pickup.

   Numbers must be in international format with leading + and country code. The text is everything after the first comma on each line; commas inside the text need to be quoted according to standard CSV rules.
2. Go to Tools > SMS Gateway and open the Upload File tab.
3. Click Choose file, pick your CSV, and click Upload. The file appears in the list with a record count (so you can verify it parsed correctly — the count should match your row count).
4. Click the uploaded file to review the recipients. Spot-check a few rows before sending.
5. Click Send. The Abilis starts dispatching through the SIM modem, typically one message per second or two.
6. Monitor delivery on the SMS Sent / Received tab — each message shows as Sent, Delivered, or Failed. Failures are usually bad numbers or a modem reset; the rest go through.

View, search, and manage received SMS

Goal: The Abilis SIM receives SMS — 2FA codes sent to a company number, customer replies, delivery confirmations from carriers, alerts from other systems. You want to see the inbox, search the history, and clean up old messages.

1. Go to Tools > SMS Gateway and open the SMS Sent / Received tab.
2. The list shows every SMS, most recent first, with columns:
   • Direction: incoming or outgoing.
   • Date / Time: when the Abilis handled the message.
   • Number: sender (for incoming) or recipient (for outgoing).
   • Status: Delivered, Sent, Received, or Failed.
   • Text: the message contents, truncated.
3. Filter the list:
   • Direction dropdown — narrow to only incoming, only outgoing, or only failed.
   • Search box — type a phrase to find messages containing that text, or a number to find messages to/from that recipient.
   • Date range — restrict the view to a specific period.
4. Click a row to see the full message text if it was truncated in the list.
5. Tidy up when the list gets long. Tick the checkboxes next to messages no longer needed and click Delete. SMS records don't take much disk space but a cleaner list is easier to search.
6. Export the history for audit or reporting: click Export to CSV with the filter still applied — you get exactly what is currently visible.

Forward incoming SMS to email or another mobile

Goal: The Abilis SIM receives an SMS — a two-factor authentication code for a bank or ERP system, a delivery alert from a carrier, a reply from a customer — and the message needs to reach a person or a team, not sit unread in the Abilis inbox. You want every incoming SMS (or ones matching specific patterns) to be relayed immediately to email, to another mobile, or to both.

Common uses: shared-account 2FA codes going to the staff currently on duty; delivery alerts going to a dispatch distribution list; customer replies going to the sales desk.

Prerequisite: if forwarding to email, the SMTP sender must be configured — see Configure the email sender (SMTP).

1. Go to Tools > SMS Gateway and open the Forwarding Rules tab.
2. Click New + and configure the rule:
   • Match: what triggers this rule. Options:
     • Any SMS — every incoming message is forwarded (simplest case).
     • From specific number — e.g. only messages from the bank's SMS gateway.
     • Containing text — e.g. messages containing the word code (useful to catch 2FA without catching marketing SMS).
   • Action — Forward to email: one or more addresses, separated by commas. A distribution list works well for team forwarding. The email subject includes the sender's number; the body contains the full SMS text.
   • Action — Forward to mobile: one or more destination numbers in international format. Each gets a copy as a new SMS.
   • Delete after forwarding: optional. Keeps the inbox clean but loses the Abilis-side audit trail. Recommended off unless you have external logging.
3. Save. The rule is active immediately for the next incoming SMS.
4. Test. Send a test SMS to the Abilis SIM from a phone that matches the rule. Confirm the email or SMS arrives at the destination within seconds. Check the spam folder on the first email test.