Radius is an AAA (Authentication, Authorization, and Accounting) protocol originally developed by Livingston (now part of Lucent) for their dialup servers. (See: Radius Server History) Because the Radius protocol includes the capability of being easily extended, it has been used for many purposes beyond it's initial design target.
Today Radius is used for:
Diameter is a next generation Radius like protocol that hasn't gotten much traction yet.
Radius RFCs
See Also:
Today Radius is used for:
- Network Access Servers (dialup and broadband)
- Packetcable RKS servers
- VOIP Billing data collection
- etc.
Diameter is a next generation Radius like protocol that hasn't gotten much traction yet.
Radius RFCs
- RFC 2138 Obsolete - Remote Authentication Dial In User Service (RADIUS)
- RFC 2139 Obsolete - Radius Accounting
- RFC 2548 Microsoft Vendor-specific RADIUS Attributes
- RFC 2809 Implementation of L2TP Compulsory Tunneling via RADIUS
- RFC 2865 Remote Authentication Dial In User Service (RADIUS)
- RFC 2866 RADIUS Accounting
- RFC 2867 RADIUS Accounting Modifications for Tunnel Protocol Support
- RFC 2868 RADIUS Attributes for Tunnel Protocol Support
- RFC 2869 RADIUS Extensions
- RFC 2882 Network Access Servers Requirements: Extended RADIUS Practices
- RFC 3162 RADIUS and IPv6
See Also:
- Radius Servers
- OpenBloX Open Source Java Diameter Framework, with all IMS and SIP servers interfaces


Comments
333PortaOne Does Work with Asterisk
PortaBilling100 allows doing both prepaid and postpaid billing for any RADIUS based equipment, for example, Cisco, NextTone, Quintum, Mera MVTS, and open source Asterisk. Currently, PortaOne has tens of clients that use PortaBilling100 with Asterisk.
However, PortaOne provides technical support for its products only. We do NOT provide configuration assistance for Asterisk, Cisco or any other equipment as a part of our technical support program.
333Porta-On Doesn't Support Asterisk
any version of Asterisk with PortaOne. I'd suggest not using their billing software
where Asterisk is involved as you'll not get any support for them.
Additionally, I'd be leery of doing business with a company who advertises support
on their website (see "http://portaone.com/products/portabilling/pb100/" - they advertise
full support of Asterisk with the phrase:
"Full prepaid and postpaid billing support for Cisco, Quintum, open source Asterisk, Mera MVTS"
However, here's the response I have from support:
Dear Mike,
This is our official position.
> - Fri Jun 15 21:11:47 2007 Europe/Kiev:
>
> Hi Andrey,
>
> Thanks... it's really interesting that you state you don't support
> asterisk, but the features section of your marketing site for
> PortaBilling 100 which is located at:
>
> http://portaone.com/products/portabilling/pb100/
>
> states (verbatim):
>
> "Full prepaid and postpaid billing support for Cisco, Quintum, open
> source Asterisk, Mera MVTS"
>
> It would appear you need to update your website, or support the
> integration, correct? What I see is the your marketing site saying
> something's supported, but you guys telling me it's not. Now that's
> not a legitimate way to do business guys.
>
> ....
>
> I'd like to know that this is the official PortaOne stand on
> integration of any newer release of Asterisk with PortaBilling 100.
> If it is, I'll make sure to look to other sources for billing
> engines in future integrations that I do myself to ensure
> compatibility with not only hardware devices but also software PBX
> switches.
>
Anyone have any ideas of other AAA software which is capable of the same
features as Porta, but have a better support infrastructure?
Hope this helps anyone who has clients looking at purchasing this software.
I'd not even purchase it myself if there were other uses I would have for it -
if they falsely tout support for a softswitch they don't support, how many other
"mis-truths" are there?
333RADIUS client
333aaa