ISP Inventory management

Inventory management

Splynx brings Internet providers efficient and simple way to manage their inventory and stock. Feature is available from 2.0 release.
Inventory dashboard shows amount of items, products, suppliers and invoices in the system. Splynx allows to scan and quickly work with barcodes.

Suppliers are companies that sell equipment and issue invoices. Splynx stores and links items/equipment units with particular supplier’s invoice.

Products are routers, switches, cable units, antennas and similar. Administrator can define default price that will be used by system when equipment is rented or sold to customer. Vendors section store information about producers of equipment such as Mikrotik, Cisco, Radwin or Ubiquiti.

Items is the most used section, it’s a common table with all equipment units. Administrator is able to assign equipment units to other administrator, set as internally used, move units from stock to customer or mark them as broken and send back to supplier.

 

 

Barcodes. You can use any barcode reader and scan barcodes of equipment when entering it to stock. Then find simply equipment unit using it’s barcode. Our search barcode feature allows to select multiple barcodes and work quickly with barcode scanner instead of typing long useless numbers.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Should you have any questions or further information is needed, please contact us or schedule a call with our engineer.

Please check inventory management in video tutorial :

Splynx Radius server

Splynx ISP framework consists of different sub-systems. One of the main and most important parts of the framework is Splynx Radius server. PPPoE, DHCP, IPoE, Hotspot, Wireless or Static IP/MAC authentication. Splynx solution also provides smart bandwidth management, billing other useful features.

Splynx Radius server is used to perform AAA tasks.
Authentication – Networking equipment perform check over Radius server if login/password of connecting device or user is correct. If it matches with an entry in Radius server, device or user is able to access the equipment or get the service.
Authorization – defines which actions are allowed for user or device and it’s privilege level.
Accounting – statistics of the usage of Internet or information about what was done on equipment.

1. Administrative AAA.
Authentication: With Splynx you can setup that when administrator accesses equipment, his credentials will be checked over Radius server database.
If his username/password is correct, he will be able to login to equipment. If not, he will not get access. This is very convenient approach comparing to local login.
Imagine when you hire a new administrator and you need to update hundreds of routers, APs and switches to create him local login everywhere.
Or you can give him one common login/password, but when a person leaves the company, you should change that credentials everywhere.
Better is to connect all networking devices to Radius server and verify administrator login using Radius protocol.
Authorization: means that different levels of access can be implemented. Some administrators can change the configurations, some can only view and read config.
Accounting: Splynx stores information of when the network unit was accessed by an administrator and what was done there.

Below are tutorials showing how to configure admin login using Radius Splynx server on different platforms :

Mikrotik: Radius admin login to Mikrotik routers

Administrative login to Cisco devices

2. Customer’s AAA.
Splynx Radius server supports different ways of customers’ central authentication in the network of Internet provider. It always depends on the topology of an ISP and technology that he decides to use. Access technologies are widely used and their advantages and disadvantages are described below:

PPPoE – easy to maintain and implement. Customer on CPE device setups username and password and all networking settings CPE receives from PPPoE NAS (Network Access Server). Also provides encryption if needed and accounting for getting statistics of usage. Had issues with MTU in the past, but in last years these issues were fixed by main vendors.

IPoE (or DHCP) – DHCP is based on MAC address of the client. Also can be linked to the port of switch were a customer is connected (DHCP option 82). In several vendors don’t provide accounting capability (Mikrotik routers).

Wireless Authentication – when ISP has a wireless network, he needs to maintain access of CPE devices to his Access Points. For this purpose, several wireless authentication methods are used, such as a password inside TDMA protocols or wireless access-lists.

Hotspot – customer has to enter his username and password on the webpage before using the Internet. Many hotspot networks allow free limited access and then charge customers for additional usage or advanced plans.

Static IP addressing – some ISPs don’t have central management of authentication and setup static IP addresses to CPE devices. With Mikrotik RouterOS platform Splynx can manage even customers who’s got static IPs in Vlan per customer or plain IPv4 connection. Also Splynx can grab statistics from Mikrotik routers for such customers.

Below are manuals for different types of user authentication in Splynx ISP Framework :

Mikrotik: DHCP using Radius

Mikrotik: PPPoE and other PPP tunnels using Radius

Mikrotik: Hotstpot with Radius

Mikrotik: Static IP addressing with API authentication/accounting

Mikrotik: Local DHCP with Mikrotik API

Ubiquiti: Wireless authentication with Radius

Ubiquiti: PPPoE authentication on Edge Routers


Should you have any questions regarding Splynx RADIUS server or further information is needed, please contact us or schedule a call with our engineer.

Payment gateways

Charge your customers with Paypal, Braintree, Authorize.net, SEPA, GoCardless, Cashdesk, Payfast or SagePay.

Splynx has a strong billing engine. You can issue Recurring Invoices and send them to your customers or charge customers with Prepay Mode.

Recurring invoicing
Invoices can be issued in advance or in Postpay Mode. One month in advance means that 1st of May Splynx will generate invoices for 1-31 of May. Postpay means that Splynx generates invoices on 1st of May for period of 1-30 of April.

When the invoice is generated there are several methods how to process the customer’s payment:

1. Direct debit order
When the invoices are generated, you can export all or some of them to Direct debit orders. It is available under the button “Charge” in Finance module of Splynx.

Direct debit order can be sent via Splynx module API to these payment gateways: Paypal, Braintree, Authorize.net, Stripe.com.
You can also charge your customers’ IBAN bank accounts using SEPA XML and GoCardless platform.

2. Bank statement processing
If customers pay their bills using bank transfers, Splynx can handle these files and process them.

 

Then the invoice is marked as paid, payment transaction is created and customer’s balance becomes “0”. Because of different formats of the files in banks, we always create a custom handler (php script) which processes our customer’s bank file.

Bank file can be imported manually to Splynx using Bank processing menu, or Splynx can connect to email or bank API and grab file every day or several times per day.

3. Cash payments
Cashdesk is a Splynx module for processing payments.

 

Administrator can create users of Cashdesk and provide them access to the module. User is not able to change and view any customer’s data, except his name/Company name, Invoice Numbers and actual Balance.

The Cashdesk can be used by accountants, who doesn’t have to get access to Splynx but only process the incoming payments. It can be also used by resellers. Reseller will only see his customers and will be able to enter payments to Splynx when he receives money from customer.

4. Other type, manual processing
If none of above payment methods fits you, there is always an option to add a payment manually in Splynx, or mark invoice as paid. It will create a credit transaction in Splynx and also it will add the payment to customer’s balance.

Prepaid billing
Prepaid billing is used when ISP charges customer in advance and provide him access for certain period of time. When balance of the customer reaches set limit, he is disconnected.

With combination of self-registration feature, customers in ISP network can register themselves on ISP’s website, order a service and pay online for the selected period of time. They can pay via credit cards using Paypal, Braintree or Authorize.net platforms. Braintree even supports Apple Pay, Android Pay and Bitcoins.


Should you have any questions billing engines, payment systems or further information is needed, please contact us or schedule a call with our engineer.

Voice Billing

Splynx ISP framework has useful feature to rate phone calls, messages, data and charge customer for voice services. System allows to rate VoIP (Voice over IP) calls, LTE data transfers or work with full mobile phone services that include calls, messages and data.

Customer rating and Provider rating

Splynx can rate calls, messages and data for end user – such rating is called customer rating. Customer rating has own tables with destination prefixes, prices, tariffication steps and other important fields. Based on these data Splynx sets final price for each call, message or data unit.

Also system is able to calculate the cost of each call, message or data unit. This second type of rating is called provider rating and is useful to control voice expenses and understand if our voice/mobile provider has correct charging tables that he applies. The final rating table can have 3 prices in output. Customer price, RBP(rated buy price by Splynx) and CBP (CDR buy price that our provider provides us). Of course RBP and CBP are displayed only to administrator, customer sees only his final customer price. Presence of these prices allows to create custom reports and analyse efficiency of voice services.

 

Voice plans 

When all rates are set and prefixes with categories are imported, administrator should define voice plans. Each voice plan could have own rate table or multiple plans can share one rate table. If destination is not found in list of prefixes inside rate table, simple increasing of buy price can be applied. Splynx voice billing engine provides flexible configuration of plans, for example defining included amount of minutes per category, amount of free SMS or data that are part of the tariff plan.

Also additional policies can be applied to the rates in group settings of voice plan. For example, it’s possible to change tariffication step for certain call categories or additionally add establish fee.

 

CDR processing

Our voice billing engine is very flexible in processing of CDRs. Framework can process CDR that are imported manually, but also can be connected to REST API of soft switch. Software can grab CDRs from FTP of voice provider. In next release Radius support will be added. Splynx allows to create custom format handler that will exactly match your CDR format.

Statistics

When CDR has been processed, Splynx stores voice statistics in different places:

  • Voice processing history, where we can see all processed calls by Splynx in certain day
  • Customer voice service – there are displayed raw per number CDR statistics
  • Customer statistics – these are stats with per category aggregation and with separate displaying of SMS and Data usage. Customer voice stats are available for customer in his portal together with internet data usage.

 

Invoicing

Rates are configured, Voice plans have been created and CDRs were processed by Splynx. All information about phone calls, messages and data usage is available in customer statistics. The last part of Splynx voice engine is connection phone calls to recurring billing engine. Voice CDR records are automatically attached to customer invoice when next recurring charge is made. Example : we imported CDRs 31st of February for February calls. 1nd of March Splynx runs automatic generation of invoices. All uncovered voice services, calls, messages and data are added to these invoices. Separate debit transaction for voice number is created in Splynx during this process.

Example of such invoice is below :

 

From version 2.3 Splynx supports auto processing of CDRs and FTP connections to any Voip softswitch or Voice provider that supports FTP for storing CDR files. Learn more about FTP CDR connection – https://splynx.com/5069/auto-cdr-processing-from-ftp/

To see Splynx Voice Billing Engine in action, please watch our video :

Should you have any questions regarding VoIP service configuration in Splynx or further information is needed, please contact us or schedule a call with our engineer.