Cisco Cisco Smart CallConnector Server and Advanced Client Manual De Manutenção
Cisco Router Configuration
Administrator Guide 4-19
Below is an example of the router configuration file showing the Radius parameter settings for
sending Radius messages to multiple Radius servers.
aaa new-model
!
aaa group server radius uccserver
server 192.168.1.2 auth-port 1645 acct-port 1646
!
aaa group server radius syslogserver
server 192.168.1.3 auth-port 1645 acct-port 1646
!
aaa accounting update newinfo
aaa accounting connection h323 start-stop broadcast group uccserver group syslogserver
!
aaa session-id common
!
!
gw-accounting syslog
gw-accounting aaa
!
radius-server host 192.168.1.2 auth-port 1645 acct-port 1646
radius-server host 192.168.1.3 auth-port 1645 acct-port 1646
radius-server key uccserver
radius-server vsa send accounting
radius-server vsa send authentication
!
sending Radius messages to multiple Radius servers.
aaa new-model
!
aaa group server radius uccserver
server 192.168.1.2 auth-port 1645 acct-port 1646
!
aaa group server radius syslogserver
server 192.168.1.3 auth-port 1645 acct-port 1646
!
aaa accounting update newinfo
aaa accounting connection h323 start-stop broadcast group uccserver group syslogserver
!
aaa session-id common
!
!
gw-accounting syslog
gw-accounting aaa
!
radius-server host 192.168.1.2 auth-port 1645 acct-port 1646
radius-server host 192.168.1.3 auth-port 1645 acct-port 1646
radius-server key uccserver
radius-server vsa send accounting
radius-server vsa send authentication
!
4.7.5 Verifying Radius Settings
Use the ‘Show Running-Config’ from the CLI to verify your router settings.
Verify that each router is sending the accounting messages to the correct
Verify that each router is sending the accounting messages to the correct
CallConnector Server IP Address and port. Use the Debug Radius Accounting and see
example below.
example below.
Verify in the debug messages that you are getting Radius messages for Off-hook, Ring,
Connect and Hang-up.
Verify that the source IP address in the Radius messages is the same as the Cisco
router IP Address being used by the IP Phones.
Once the CallConnector Server has been setup, you can verify using the ‘View Radius
Message’ utility to view the messages being received from the routers.
Verify that the Radius parameters have been setup correctly on all the routers.
4.7.5.1 Example of Radius Accounting Debug Messages
Note: The Send Accounting Request to IP-Address and the corresponding response indicating
receipt and acknowledgement from CallConnector Server.
26 20:19:56.442: RADIUS(000549E7): Send Accounting-Request to 192.168.1.99:1646 id
1646/138, len 867
26 20:19:56.442: RADIUS: authenticator 58 A6 38 48 9F 73 B4 92 - 44 05 5E 12 37 B5 8F A1
26 20:19:56.442: RADIUS: Acct-Session-Id [44] 10 "000A92A9"
26 20:19:56.442: RADIUS: Calling-Station-Id [31] 6 "4002"
26 20:19:56.442: RADIUS: Vendor, Cisco [26] 61
26 20:19:56.442: RADIUS: h323-setup-time [25] 55 "h323-setup-time=*12:19:54.786 central
Wed Dec 26 2007"
26 20:19:56.442: RADIUS: Vendor, Cisco [26] 40
26 20:19:56.442: RADIUS: h323-gw-id [33] 34 "h323-gw-id=cc3845.yourdomain.com"
receipt and acknowledgement from CallConnector Server.
26 20:19:56.442: RADIUS(000549E7): Send Accounting-Request to 192.168.1.99:1646 id
1646/138, len 867
26 20:19:56.442: RADIUS: authenticator 58 A6 38 48 9F 73 B4 92 - 44 05 5E 12 37 B5 8F A1
26 20:19:56.442: RADIUS: Acct-Session-Id [44] 10 "000A92A9"
26 20:19:56.442: RADIUS: Calling-Station-Id [31] 6 "4002"
26 20:19:56.442: RADIUS: Vendor, Cisco [26] 61
26 20:19:56.442: RADIUS: h323-setup-time [25] 55 "h323-setup-time=*12:19:54.786 central
Wed Dec 26 2007"
26 20:19:56.442: RADIUS: Vendor, Cisco [26] 40
26 20:19:56.442: RADIUS: h323-gw-id [33] 34 "h323-gw-id=cc3845.yourdomain.com"