YEess I have found an answer for my Q1 and Q2 and I will explain now what was it. first of all I edited my users file incorrectly
I should edit it like this:'”210987654321 Auth-Type := Accept
Quintum-h323-return-code = “h323-return-code=0”,
Quintum-h323-credit-amount = “h323-credit-amount=124”,
Quintum-h323-credit-time = “h323-credit-time=10” “to show here that my card number is 12 digits long as it is configured in my quintums pstntg 1 ivr related part. As I complained earlier that I am not seeing any access-request packet that was because I typed not 12 digit access code and my quintum even doesn`t send it to radius.
Now I can see it :rad_recv: Access-Request packet from host 192.168.1.3:24579, id=241, length=152
NAS-IP-Address = 192.168.1.3
User-Name = “210987654321”
User-Password = “210987654321”
NAS-Port-Type = Async
Quintum-h323-conf-id = “h323-conf-id=34323035 37326531 62360033 65390000”
Quintum-AVPair = “h323-ivr-out=ACCESSCODE:”
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 40
modcall[authorize]: module “preprocess” returns ok for request 40
modcall[authorize]: module “chap” returns noop for request 40
modcall[authorize]: module “mschap” returns noop for request 40
rlm_realm: No ‘@’ in User-Name = “210987654321”, looking up realm NULL
rlm_realm: No such realm “NULL”
modcall[authorize]: module “suffix” returns noop for request 40
rlm_eap: No EAP-Message, not doing EAP
modcall[authorize]: module “eap” returns noop for request 40
users: Matched 210987654321 at 153
modcall[authorize]: module “files” returns ok for request 40
modcall: group authorize returns ok for request 40
rad_check_password: Found Auth-Type Accept
rad_check_password: Auth-Type = Accept, accepting the user
Sending Access-Accept of id 241 to 192.168.1.3:24579
Quintum-h323-return-code = “h323-return-code=0”
Quintum-h323-credit-amount = “h323-credit-amount=124”
Quintum-h323-credit-time = “h323-credit-time=10”
Finished request 40
Going to the next request
— Walking the entire request list —
Waking up in 6 seconds…
— Walking the entire request list —
Cleaning up request 40 ID 241 with timestamp 42052c3c
Nothing to do. Sleeping until we see a request.
rad_recv: Accounting-Request packet from host 192.168.1.3:24579, id=242, length=566
NAS-IP-Address = 192.168.1.3
Quintum-NAS-Port = “0 0/2/3”
NAS-Port-Type = Async
User-Name = “210987654321”
Called-Station-Id = “”
Calling-Station-Id = “”
Acct-Status-Type = Stop
Acct-Delay-Time = 0
Acct-Input-Octets = 0
Acct-Output-Octets = 0
Acct-Session-Id = “2020202000000079”
Acct-Session-Time = 18
Acct-Input-Packets = 0
Acct-Output-Packets = 0
Service-Type = 0
Quintum-h323-conf-id = “h323-conf-id=34323035 37326531 62360033 65390000”
Quintum-AVPair = “h323-incoming-conf-id=34323035 37326531 62360033 65390000”
Quintum-h323-gw-id = “h323-gw-id=”
Quintum-h323-call-origin = “h323-call-origin=answer”
Quintum-h323-call-type = “h323-call-type=Telephony”
Quintum-h323-setup-time = “h323-setup-time=01:29:05.340 UTC Sun Feb 6 2005”
Quintum-h323-connect-time = “h323-connect-time=01:29:05.600 UTC Sun Feb 6 2005”
Quintum-h323-disconnect-time = “h323-disconnect-time=01:29:23.570 UTC Sun Feb 6 2005”
Quintum-h323-disconnect-cause = “h323-disconnect-cause=29”
Quintum-h323-voice-quality = “h323-voice-quality=0”
Processing the preacct section of radiusd.conf
modcall: entering group preacct for request 41
modcall[preacct]: module “preprocess” returns noop for request 41
rlm_acct_unique: WARNING: Attribute NAS-Port was not found in request, unique ID MAY be inconsistent
rlm_acct_unique: Hashing ‘,Client-IP-Address = 192.168.1.3,NAS-IP-Address = 192.168.1.3,Acct-Session-Id = “2020202000000079”,User-Name = “210987654321”‘
rlm_acct_unique: Acct-Unique-Session-ID = “206a051e3218719e”.
modcall[preacct]: module “acct_unique” returns ok for request 41
rlm_realm: No ‘@’ in User-Name = “210987654321”, looking up realm NULL
rlm_realm: No such realm “NULL”
modcall[preacct]: module “suffix” returns noop for request 41
modcall[preacct]: module “files” returns noop for request 41
modcall: group preacct returns ok for request 41
Processing the accounting section of radiusd.conf
modcall: entering group accounting for request 41
radius_xlat: ‘/var/log/radius/radacct/192.168.1.3/detail-20050206’
rlm_detail: /var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /var/log/radius/radacct/192.168.1.3/detail-20050206
modcall[accounting]: module “detail” returns ok for request 41
modcall[accounting]: module “unix” returns noop for request 41
radius_xlat: ‘/var/log/radius/radutmp’
radius_xlat: ‘210987654321’
rlm_radutmp: No NAS-Port seen. Cannot do anything.
rlm_radumtp: WARNING: checkrad will probably not work!
modcall[accounting]: module “radutmp” returns noop for request 41
modcall: group accounting returns ok for request 41
Sending Accounting-Response of id 242 to 192.168.1.3:24579
Finished request 41
Going to the next request
— Walking the entire request list —
Waking up in 6 seconds…
— Walking the entire request list —
Cleaning up request 41 ID 242 with timestamp 42052c44
Nothing to do. Sleeping until we see a request.
Now I think I should find the way to send in Access-response some attributes to get me in my quintum because it as it is shown here accepts it but then hungs up the line I do not know why right now If some of you can read this given output and gave me some clue what is happeninng I would appreciate much