UTM5 - a complete ISP billing solution


 
Thread Tools Search this Thread
The Lounge Sponsored UTM5 - a complete ISP billing solution
# 1  
Old 10-10-2008
UTM5 - a complete ISP billing solution

UTM5 is a high-performance ISP billing software developed by NetUP Inc. for small to large telecoms. The software is designed to control Internet access and Voice over IP services. With UTM5 an ISP can charge subscribers per traffic volume or per connection time, set monthly caps or provide flat rates with dynamic bandwidth shaping, and do much more.

UTM5 is a complete billing solution that includes billing mediation platform, rating engine, invoicing subsystem, etc. It can interface directly with networking equipment, such as routers, firewalls, network access servers, VoIP gateways, etc. via various up-to-date protocols, e.g., Netflow, RADIUS, SNMP, sFlow, etc. The billing system supports usage-based billing and works in real time, that is especially important for prepaid tariffs.

UTM5 has over 2000 deployments all over the world - Australia, Thailand, India, Russia and CIS, Eastern and Western Europe, Africa, USA and Canada. In these solutions the billing system is used with many various connection technologies: wired Ethernet, ADSL, Wi-Fi, Wi-Max, FTTH, etc.

More details at www.utm-billing.com

Sponsored thread approved by The UNIX and Linux Forums. Please take a minute to visit our forum supporters.
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

BASH complete-filename & menu-complete together

Hi, Does anyone know how to make BASH provide a list of possible completions on the first tab, and then start cycling through the possibilites on the next tab? Right now this is what I have in my .bashrc: bind "set show-all-if-ambiguous on" bind \\C-o:menu-complete This allows... (0 Replies)
Discussion started by: Mithu
0 Replies
Login or Register to Ask a Question
NETWORKS(5)						      BSD File Formats Manual						       NETWORKS(5)

NAME
networks -- Internet Protocol network name data base DESCRIPTION
The networks file is used as a local source to translate between Internet Protocol (IP) network addresses and network names (and vice versa). It can be used in conjunction with the DNS, as controlled by nsswitch.conf(5). While the networks file was originally intended to be an exhaustive list of all IP networks that the local host could communicate with, dis- tribution and update of such a list for the world-wide Internet (or, indeed, for any large "enterprise" network) has proven to be prohibi- tive, so the Domain Name System (DNS) is used instead, except as noted. For each IP network a single line should be present with the following information: name network [alias ...] These are: name Official network name network IP network number alias Network alias Items are separated by any number of blanks and/or tab characters. A ``#'' indicates the beginning of a comment; characters up to the end of the line are not interpreted by routines which search the file. Network number may be specified in the conventional dot (``.'') notation using the inet_network(3) routine from the IP address manipulation library, inet(3). Network names may contain "a" through "z", zero through nine, and dash. IP network numbers on the Internet are generally assigned to a site by its Internet Service Provider (ISP), who, in turn, get network address space assigned to them by one of the regional Internet Registries (e.g. ARIN, RIPE NCC, APNIC). These registries, in turn, answer to the Internet Assigned Numbers Authority (IANA). If a site changes its ISP from one to another, it will generally be required to change all its assigned IP addresses as part of the conver- sion; that is, return the previous network numbers to the previous ISP, and assign addresses to its hosts from IP network address space given by the new ISP. Thus, it is best for a savvy network manager to configure his hosts for easy renumbering, to preserve his ability to easily change his ISP should the need arise. FILES
/etc/networks The networks file resides in /etc. SEE ALSO
getnetent(3), nsswitch.conf(5), resolv.conf(5), hostname(7), dhclient(8), dhcpd(8), named(8) Classless IN-ADDR.ARPA delegation, RFC 2317, March 1998. Address Allocation for Private Internets, RFC 1918, February 1996. Network 10 Considered Harmful, RFC 1627, July 1994. Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy, RFC 1519, September 1993. DNS Encoding of Network Names and Other Types, RFC 1101, April 1989. HISTORY
The networks file format appeared in 4.2BSD. BSD
November 17, 2000 BSD