In addition to RADIUS and REST, subscriber data can be retrieved from a number of supported billing systems.
Billing integrations support only IPv4 addresses.
Azotel
The BQN retrieves the customer bucket data and gets from it the speed limits to apply (uploadrate and downloadrate).
To activate Azotel, in the BQN GUI go to Configuration->RADIUS/REST/Billing->Billing Systems, select Azotel and enable the switch.
A user and password will also be needed for the REST API access. They must be created in the Azotel system, making sure access from BQN management IP address is allowed in the Azotel system. The BQN will use its management address for Azotel queries, but bear in mind that if the BQN reaches Azotel over the Internet through NAT, the Azotel system will see the NAT public IP address and this is the one that will need authorization by the Azotel system.
In the BQN GUI, configure also the Azotel system IP address or server name and port number (443 by default).
Azotel customers in a status other than “current” will be blocked (they are regarded as lacking a valid subscription). You can change this behaviour to non-blocking disabling the switch Block Inactive/Not Paying Subscribers.
Powercode
To activate Powercode in the BQN GUI, go to Configuration->RADIUS/REST/Billing->Billing Systems, select Powercode and enable the switch.
Provide the Powercode system IP address or server name and its SSH port number (22 by default).
The BQN server needs SSH access to the Powercode server using a Unix User/Password.
In the Powercode system, we shall require a MySQL user and password. If the MySQL user/password is different to the Unix user/password, that should be specified in MySQL Credentials in the BQN GUI. The MySQL user must have read access to the following tables of the Powercode MySQL database:
- Services
- InternetInfo
- Equipment
- Customer
- CustomerServices
- AddressRange
Powercode customers in a status other than “Active” will be blocked (they are regarded as lacking a valid subscription). You can change this behaviour to non-blocking disabling the switch Block Inactive/Not Paying Subscribers.
REST-API Powercode
Powercode billing restricts REST API to three requests per second. For that reason, the preferred integration is using the MySQL access described in the previous section. REST-API can be used when MySQL cannot be used and the number of subscribers is low (one thousand or less).
The BQN retrieves CPE equipment of a certain category (1 by default). For subscribers with that category of equipment, it will retrieve the rate limits of their Internet service (“internetInfo”).
To activate Powercode, go to Configuration->External Subscriber Data->Billing Systems , select Powercode enable the switch.
An API Key will also be needed. The API key must be created in the Powercode system, with allowed access from BQN IP address (the BQN will use its management address for Powercodequeries).
Provide also the Powercode system IP address or server name and port number (444 by default).
If the CPE equipment category in the Powercode database is other than 1, change it. More than one category can be specified typing the category numbers separated by spaces (e.g. “10 11 12” for categories 10, 11 and 12).
Sonar
Sonar v2 is supported (the one with GraphQL API).
The BQN retrieves the customer tariffs and the speed limits to apply.
To activate the Sonar integration, go to Configuration->RADIUS/REST/Billing ->Billing Systems in the BQN GUI, select Sonar and enable the switch.
An API key will be needed. They must be created in the Sonar system. See Sonar documentation for details here.
Finally, in the BQN GUI, configure the Sonar system IP address or server name and port number (443 by default) in Configuration->RADIUS/REST/Billing ->Billing Systems, iwith Sonar selected and enabled.
Sonar customers with account_status->namefield with a value other than “Active”, will be blocked (they are regarded as lacking a valid subscription). You can change this behaviour to non-blocking disabling the switch Block Inactive/Not Paying Subscribers.
Splynx
The BQN retrieves the customer tariffs, the speed limits to apply and the burst rates, together with burst thresholds and burst duration.
To activate Splynx in the BQN GUI, go to Configuration->RADIUS/REST/Billing->Billing Systems, select Splynx and enable the switch.
An API key and secret will be needed. They must be created in the Splynx system with the following settings:
- Enable basic authorization for this key.
- Leave empty Allowed list for IPs or include the BQN IP address. The BQN will use its management address for Splynx queries but bear in mind that if the BQN reaches Splynx over the Internet, Splynx will see a public IP address and this is the one that will need authorization by the Splynx system.
- Add view permissions for database items Tariff plans ->Internet and Customers->Customers online.
The following screenshots show the API KEY and the access permits:
In the BQN GUI, configure also the Splynx system IP address or server name and port number (443 by default).
Splynx customers with “1” in their blocked field, will be blocked (they are regarded as lacking a valid subscription). You can change this behaviour to non-blocking disabling the switch Block Inactive/Not Paying Subscribers.
Visp.net
The BQN retrieves the customer tariff and get from it the speed limits to apply and the burst rates, thresholds andduration.
To activate Visp, go to Configuration->RADIUS/REST/Billing ->Billing Systems, select Visp and enable the switch.
A valid client id and secret and user name and password must be provided to the BQN in order to request temporal API tokens. A client id is unique per Visp installation. A user is any of the valid user accounts in that client to access the system.
The provided IP address or server name will be used, along with the port (443 by default), to requests API tokens (https://<server>:<port>/token) and also to send API queries (https://<server>:<port>/graphql).
The following screen shows an example of Visp configuration:
Visp customers with “8” or “9” in their status field, will be blocked (suspended and hibernated states respectively, they are regarded as lacking a valid subscription). You can change this behaviour to non-blocking disabling the switch Block Inactive/Not Paying Subscribers.
