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
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…
To enable the ability for Soft-Cap Data Products to be considered for Roll-Over the following must be implemented: The setting to allow the system to consider this needs to be enabled. This can be found under Data -> Radius Setup -> Radius Settings With this setting enabled, the system will Read more…
DataTill has released an improvement to the Unknown Devices Report with version 1.5.01. First, there are a few things the user needs to be aware of concerning this report: The report is automatically set to default to a 3 hour window period. DataTill recommends that users leave this as the Read more…
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…
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:
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:
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…
During the festive period, we noticed a few of our customers had not changed their VAT settings to the increased 15 %, effective from 01 April 2018. It is important to note that any invoices issued from this date onwards (01 April 2018) must be charged at 15 % VAT. Read more…
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:
Support for LFTP Backups DataTill has introduced the FTP backup setting to allow for the use of the external third party LFTP library. When the user navigates to Setup > System Settings > System Backups > under the FTP Settings | FTP Method, the user will now see Read more…
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.
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.
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.
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.
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.
After your DataTill has been set up and your system administrator has created an admin user for you and sent you your login details you can start watching the Youtube video to introduce you to how to start using DataTill.