Good day. I am still waiting for your answer on the below subject. Could you please guide me further so I can fix this issue with mod_rad_auth. I hope you understand what is my problem.
Abid, i cannot write the dialplan for you. This part you should do by yourself. I have explained how this module is supposed to work... and it really does.
you need to evaluate the response from auth_function and act accordingly (bridge or not bridge the call according to auth result)
again, here is an example:
module config:
<configuration name="rad_auth.conf" description="radius authentification module"> <settings> <!-- backward compatibility to allow radiusclient config file instead of an embedded config -->
<param name="radius_config" value="/usr/local/etc/radiusclient/radiusclient.conf"/> </settings>
<vsas> <!-- name: just a description value: direct input or variable pec: vendor ID (0 for default, 9 for cisco...) expr: 1 for channel variable, 2 for direct input
direction: in for radius-request, out for radius-response -->
<action application="execute_extension" data="RADIUS_ANI_AUTH XML default"/>
<!-- bind_meta_app can have these args <key> [a|b|ab] [a|b|o|s] <app> --> <action application="bind_meta_app" data="1 b s execute_extension::dx XML features"/>
<action application="bind_meta_app" data="2 b s record_session::$${recordings_dir}/${caller_id_number}.${strftime(%Y-%m-%d-%H-%M-%S)}.wav"/> <action application="bind_meta_app" data="3 b s execute_extension::cf XML features"/>
<action application="set" data="ringback=${us-ring}"/> <action application="set" data="transfer_ringback=$${hold_music}"/> <action application="set" data="call_timeout=30"/>