Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 63 Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 73 Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 89 Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 102 Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Cookie/Jar.php on line 111 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82 Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/www/users/datatvvwuz/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91 Jana Louw – DataTill

Top-up Roll-Over Methods

There are two Methods for calculating Roll-Over for Top-ups in DataTill. Please see the explanation and calculation for both to assist you in choosing the correct one for your company   These settings can be found under the menu Data -> Radius Settings -> Radius Setup  Method 1 Calculate all months together  Read more…

ICASA: Out-of-Bundle Billing

If customers have auto top settings on then they have opted into out-of-bundle billing. To opt in or out of out-of-bundle billing the customer can manage this setting in the customer portal by navigating to Usage -> Auto top-up  They can then enable the settings as seen below: Auto Read more…

ICASA: Setting up Data Rollover using Data Products

Data Rollovers can be managed for Individual Packages using the Edit Data Products feature. If you would rather manage rollover settings on a Customer level, please refer to this blog instead: ICASA: Setting up Data Rollover using Customer Categories.

NOTE: If both the Data Product and Customer Category Roll over settings are enabled, the data product rollover settings will take precedence. (Wisps are encouraged to only use the rollover settings on individual products)

Any data (monthly and /or top-ups) which is rolled over from this setting will appear as an auto rolled over top-up on the customer profile:

(more…)

ICASA: Setting up Data Rollover using Customer Categories

Data Rollovers can be managed for customers using the customer categories feature. If you would rather manage rollover settings on a product level, please refer to this blog instead: ICASA: Setting up Data Rollover using Data Products

NOTE: If both the Data Product and Customer Category Roll over settings are enabled, the data product rollover settings will take precedence. (Wisps are encouraged to only use the rollover settings on individual products)

Any data (monthly and /or top-ups) which is rolled over from this setting will appear as an auto rolled over top-up on the customer profile:

(more…)

New – Sales Lead Invoice Report

DataTill has added a new monthly reporter for figures generated from the Lead to Receipt process. This report includes comprehensive dropdowns, graphs and data point summaries. This report can be located by navigating to Reports > Statistics > Sales Lead Invoice Report. It is important to note, that the report Read more…

Circuit / Caller ID on Data Accounts

Circuit / Caller ID on Data Accounts

 

DataTill has added a few improvements to the Data Accounts menu.

A new column, Circuit ID (enabled under the Show/Hide Columns button) can now be displayed on the Data Accounts list view.

 

The Circuit ID for Telkom radius accounts will be auto-collected from the active radius session. For other radius accounts (wireless Services) the Caller ID or MAC address is collected and stored in this field.

 

The Caller ID / Circuit ID shows on the customer’s:

  • data account widget,
  • the active session widget and
  • the recently closed session widget

(more…)

Improvements to the Sage One Sync tool to fix errors.

When attempting to sync your Sage One data with DataTill, a few issues may arise due to the following scenarios:

  • A customer already exists in Sage One when trying to sync the customer from DataTill.
  • Syncing a customer with an invalid email address format.
  • Existing Sage One Integration ID is different to the DataTill Integration ID.
  • A very rare case, where the same Customer code exists as duplicates.

These issues will prevent the sync from taking place and an error message/log will be visible.

DataTill has now improved the Sage One Sync Queue, to include automatic fixes and proposed solutions for common errors.

In the example below, you will see records that were not sucessfully synced now have a new orange tool icon next to them.

(more…)

SMS Topup Message Intelligence

SMS Topup Message Intelligence

 

 

DataTill has introduced a new Artificial Intelligence feature to the Notification Setup.

View the You tube video: SMS Top-up settings for helpdesk

 

Customers already had the ability to request Topups by responding to SMS notifications sent from DataTill. In most other instances, customers would often respond to SMS notifications relating to other items.

SMS Topups: How To Do Automatic Topups With SMS

Therefore, the SMS Topup Message Intelligence feature has been built in to work with the “Enable Customer Topups via SMS Reply” setting. The user can navigate to Setup > Notifications to find this menu.

Please remember to set up your helpdesk department settings here to make sure only the department and user you set up here will receive SMS topup helpdesk notification mails.

(more…)

Using Mikrotik devices for power monitoring.

Using MikroTik devices for power monitoring:

 

 

A problem arises when not all highsites have power monitors installed. A solution to this problem would be to use the Mikrotik Router onsite that can supply battery voltage information, to monitor the site voltage.

The Mikrotik voltage reading is not 100% accurate, hence an offset value must be added (or subtracted) from the Mikrotik voltage reading to determine the actual voltage onsite.

A new tab called Voltage has been added to the  Network Devices menu/page. This tab is to accommodate a flag which indicates whether this router should be used for voltage monitoring, as well as the offset value to be used.

(more…)

Choose To Block Or To Redirect Users On Suspension

Choose to block to redirect users on suspension:

 

 

You can choose to block or to redirect your data account users when they get suspended.

Suspension for non-payment can be done by manually blocking a data account or by suspending the customer account.

How to suspend the customer account depends on whether or not the suspension approval process is activated.

 

To access suspend account blocking settings;

Go to Setup, then Radius Server, to access the radius server setup and scroll down to “Suspended Account Blocking”

 

Summary of the 3 options on how data account suspension blocking can get handled:

  • Address List – All suspended data accounts with fixed IP addresses will be assigned to an address list. Data accounts without a fixed IP address will be blocked by radius from authenticating.
    A firewall will need to be configured to redirect user in the suspended address list to a static page.
  • IP Pool – All suspended data accounts will be assigned an IP from an IP pool. This pool must exist either in DataTill or on the highsite NAS router. If a suspended data account has a fixed IP assigned this IP will be ignored when the account is suspended.
  • Radius Block – All suspended data accounts will be blocked by radius, so the account will not be able to obtain access to the network.

(more…)

Update On Clickatell SMS Gateway

Note that the Clickatell SMS gateway on DataTill requires you to have a normal account and not a developer account

DataTill’s Clickatell SMS gateway integration used to make use of an API sending method.

As Clickatell developed further we changed the SMS gateway integration to adapt to their new methods.
Clickatell now makes use of the new platform sending method, this is what we have adapted the integration to.

(more…)