ISPadmin 4.10 beta2

New router types supported Cambium, Radwin a Edge. (Available in the tab "Nagios").
Fulltext searching now includes also notes for search results in the tab "Clients / Contacts".

Fixed some reported bugs.
In a task calendar it is possible to display list of unspecified tasks. Sorted by long-term tasks at first and below them are displayed other unspecified tasks for particular day sorted by insert day.
Now it is possible to re-open even already closed task if there is correct authorization for scheduling part assigned to a particular administrator / technician. Editing task is saved to a history log.

In the tab "Invoicing / Cash box" there is a new dividing of invoicing groups and years. While exporting payments in the tab "Cash box - Sent payments" there it is now possible to export CSV or different format from a context menu.
New rewritten pages also now displays line numbering.
In the tab "Invoicing / Overviews / Payments" there is now also total overview at bottom of the list.
Now it is also possible to create "Credit note" even for item with Reverse charge (CZ only - as we know).

In the tab "Invoicing / Invoices / Time period" there is now possible to export statement for defined time period to PDF (by clicking on a particular icon).
The statement includes information about invoices which belongs to a particular month.
Detail of particular month includes detailed preview of invoices for time period (by clicling on a PDF icon at each line).

Added support of UBNT Edge Router.
Added support of Cambium ePMP 1000.
Content filtering option has been also customized, so it is now possible to select "Router type" from pop-up menu and choose type "Ubiquiti Edge Router" or "Cambium".
When access details are filled in the system will start to retrieve interface list from routers (approx. in 5 minutes) and also will start to draw transfer graphs, signal graphs of connected clients (if available) and CPU graph.

In the tab "Settings / IP Pools" there is a new tab "NAT Pools".
There is possible to define public IP addresses used for NAT of clients.
While adding NAT pool there it is possible to define range of IP addresses (network number / mask) and also router which is that range defined on.
While adding Internet service in a client card there is now possible to defined IP address (on which NAT is provided) from pre-defined range. System provides NAT on particular router automatically (if enabled) for private IP address of the client.
To enable applying of NAT address on router, it is necessary to set up key "mikrotik_nat_for_end_user" to value "1" in the tab "Settings / Syst. settings / Mikrotik". In other case (value "0") NAT will not be applied to Mikrotik.
If enabled, every client will have applied another rules "dstnat" and "srcnat".
- /ip firewall nat add action=netmap chain=ispadmin_first_dstnat comment=ispadmin_NAT_1.2.3.4_10.10.0.100 dst-address=1.2.3.4 to-addresses=10.10.0.100
- /ip firewall nat add action=netmap chain=ispadmin_last_srcnat comment=ispadmin_NAT_10.10.0.100_1.2.3.4 to-addresses=1.2.3.4 src-address=10.10.0.100

The page "Active services" has been rewritten to new framework interface.
Billing information now also includes field "Invoicing day" where it is possible to fill in the date for invoicing of client service. This information will be used (when Invoicing part is rewritten to framework) to invoice client for whatever time period needed (e.g. from 15th of November to 14th of December). It is not applied yet.
Individual fields are now organized in a logical order for adding new internet service.
Fields "Access point" and "Switch" now provides also search option to fill in the name and find out search results faster.
Displaying of client IP address and IP of client's end device is now switched.
While filling in IP address it is now possible to define which will be used for NAT (mentioned above in article IP NAT POOLS) by clicking on a checkbox "Client NAT".

Suspension of clients which are authenticated via RADIUS has been customized. In the past when a client was suspended (e.g. because unpaid invoice) system refused authentication via RADIUS but there was a problem that client did not know if their service was suspended or disconnected due to some technical problems on provider's site.
Now it is customized and every suspended client persist authenticated via RADIUS but system forward them to a special info page where they can find information why their service is not available. So it means the same process as it is at standard Internet service without authentication via RADIUS.