RadiusCat is a Remote Authentication Dial-In User Service (RADIUS) Billing Software Application that is able to provide Billing Interoperability for any Gateway|Device|PBX that supports the RADIUS Protocol like: Brekeke SIP/PBX, Quintum Gateways, EPYGI, SANSAY, CISCO, etc
RADIUS is a security authentication client/server protocol widely used by client devices to access resources on remote servers. RADIUS is an industry standard protocol (RFCs 2865 and 2866, "Remote Authentication Dial-in User Service (RADIUS)" and "RADIUS Accounting") for providing authentication, authorization, and accounting services for distributed dial-up networking. A RADIUS client, typically a dial-up server used by an Internet service provider (ISP), a client Quintum Tenor VoIP switch (eg Tenor ASX800) or Brekeke SIP/PBX, sends user and connection information to a RADIUS server. The RADIUS server then authenticates and authorizes the RADIUS client request and send a response back to the client. The Quintum Tenor then uses the information received from the RADIUS server to decide wether or not to place the call.
How RadiusCat works
RadiusCat receives and processes RADIUS authentication, authorization, and accounting (AAA) requests from an unlimited number of Devices (called RADIUS clients, e.g: Brekeke SIP/PBX, Quintum CMS) and sends RADIUS responses back to the devices.
- The device (e.g: Brekeke SIP/PBX, Quintum CMS) sends Access-Request packets to the RadiusCat Server where the Access-Request packets are processed to determine whether the caller is allowed access to services hosted by the device. The RadiusCat Server makes a determination based on account information that has been defined for that caller in the RadiusCat Billing module.
- After processing the Access-Request packet the RadiusCat Server sends either an Access-Accept or an Access-Reject packet back to the device.
- The device in the case of an Access-Reject packet either, disconnects the caller or gives the caller another chance to enter account information. In the case of an Access-Accept packet the device either places the call and connects the caller or sends another Access-Request message back to the RadiusCat Server where more information is provided for processing.
- At this stage the RadiusCat Server processes the request and either sends another Access-Accept or Access-Reject packet back to the device. The device will either place the call and connect the caller or disconnect the call.
- For a successful authorization and authentication when the call is ended the device sends an Accounting-Request packet to the RadiusCat Server. RadiusCat Server processes the Accounting-Request packet and uses the information to update the callers account with billing information.
http://svkwiki.com/wiki/What-is-RADIUS