If you found that WinRadius displayed some Logs of coming sessions, congratulations, your configuration of Cisco access server is almost correct. In this condition, you can send us the detailed logs of WinRadius to us if you think WinRadius doesn't work well with Cisco access server, we will check the logs and help you to reach a correct configuration.

If WinRadius displayed no Logs of coming sessions, you must re-configure your Cisco access server. The following information may be helpful for you. This sample configures a Cisco AS5200 (enabled for AAA and communication with a RADIUS security server) for AAA services to be provided by the RADIUS server. Please pay attention to bold-font parts.

Router# show running-config
Building configuration...
Current configuration:
!
! Last configuration change at 08:41:12 PST Mon Jan 10 2000 by lab
!
version 12.1
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname GW
!
logging buffered 100000 debugging
aaa new-model
aaa authentication login default local group radius
aaa authentication login h323 group radius
aaa authentication login con none
aaa authorization exec h323 group radius
aaa accounting connection h323 start-stop group radius
!
username lab password xxx
username 111119 password xxx
!
!
!
controller T1 3
!
gw-accounting h323 vsa
!
interface FastEthernet0
ip address 16.0.0.2 255.xxx.255.0
no ip directed-broadcast
duplex full
speed 10
no cdp enable
!
ip classless
ip route 0.0.0.0 0.0.0.0 1.14.xxx.5
ip route 192.14.xxx.32 255.255.xxx.240 16.0.0.1
no ip http server
!
!
radius-server host 1.14.132.2 auth-port 1812 acct-port 1813
radius-server key WinRadius
radius-server vsa send accounting
radius-server vsa send authentication
!
end

If WinRadius doesn't still work well, please use "deb radius" & "deb aaa acc" commands to debug your TCL IVR scripts. WinRadius CAN answer Cisco NAS correctly.