Routing Script Tutorial: Radius Authorization - Revision history

Allyntree at 15:23, 3 April 2024

2024-04-03T15:23:25Z

← Older revision		Revision as of 11:23, 3 April 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:Radius Authorization}}		{{DISPLAYTITLE:Radius Authorization}}

	Beginning with release 2.7, yo can issue RADIUS authorization requests from routing scripts. To do so, the params[:authorization] object must be filled with the required RADIUS attributes and [[#Refuse\|an exception must be raised]] with reason :authorization_required.		Beginning with release 2.7, you can issue RADIUS authorization requests from routing scripts. To do so, the params[:authorization] object must be filled with the required RADIUS attributes and [[#Refuse\|an exception must be raised]] with reason :authorization_required.

	When the authorization is completed, the routing script is called again with the result. The params[:authorization] object will be filled with the RADIUS attributes from the response. The params[:authorization][:result] field will also contain a string indicating the result of the authorization:		When the authorization is completed, the routing script is called again with the result. The params[:authorization] object will be filled with the RADIUS attributes from the response. The params[:authorization][:result] field will also contain a string indicating the result of the authorization:

Allyntree at 15:23, 3 April 2024

2024-04-03T15:23:11Z

← Older revision		Revision as of 11:23, 3 April 2024
Line 9:		Line 9:
	* ''challenge'': The authorization was challenged.		* ''challenge'': The authorization was challenged.
	* ''timeout'': The authorization was not answered.		* ''timeout'': The authorization was not answered.

			[[Image:BackToMain.png\|thumb\|center\|400px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: Created page with "{{DISPLAYTITLE:Radius Authorization}} Beginning with release 2.7, yo can issue RADIUS authorization requests from routing scripts. To do so, the params[:authorization] object must be filled with the required RADIUS attributes and an exception must be raised with reason :authorization_required. When the authorization is completed, the routing script is called again with the result. The params[:authorization] object will be filled with the RADIUS attributes f..."

2024-03-29T17:47:46Z

Created page with "{{DISPLAYTITLE:Radius Authorization}} Beginning with release 2.7, yo can issue RADIUS authorization requests from routing scripts. To do so, the params[:authorization] object must be filled with the required RADIUS attributes and an exception must be raised with reason :authorization_required. When the authorization is completed, the routing script is called again with the result. The params[:authorization] object will be filled with the RADIUS attributes f..."

New page

{{DISPLAYTITLE:Radius Authorization}}

Beginning with release 2.7, yo can issue RADIUS authorization requests from routing scripts. To do so, the params[:authorization] object must be filled with the required RADIUS attributes and [[#Refuse|an exception must be raised]] with reason :authorization_required.

When the authorization is completed, the routing script is called again with the result. The params[:authorization] object will be filled with the RADIUS attributes from the response. The params[:authorization][:result] field will also contain a string indicating the result of the authorization:

* ''accept'': The authorization was successful.
* ''reject'': The authorization was refused.
* ''challenge'': The authorization was challenged.
* ''timeout'': The authorization was not answered.