07-25-2005 04:59 AM - edited 03-17-2019 08:29 PM
I had a Cisco 3725 router with Version 12.3(8)T to use as a gatekeeper for a Video over IP network.
The gatekeeper is sitting on the network and all i configure is more on the zone local and subnet, prefix and gw-type prefixes. I think its doing its job to allow pre-defined IPs to connect and use the video service. But unfortunately, i don't know how to generate the CDR parameters for billing system purposes.
What is the best way to capture the CDR parameters using the GK? pls help. thanks.
07-29-2005 02:40 AM
Or accounting functions within RADIUS??
11-13-2006 12:43 PM
I got all that correct but recently I have noticed that my radius message are been generated like this:
*Nov 13 15:38:50.099: RADIUS: User-Name [1] 12 "6043086884"
*Nov 13 15:38:50.103: RADIUS: Acct-Authentic [45] 6 RADIUS [1]
*Nov 13 15:38:50.103: RADIUS: Acct-Status-Type [40] 6 Stop [2]
*Nov 13 15:38:50.103: RADIUS: Service-Type [6] 6 Login [1]
*Nov 13 15:38:50.103: RADIUS: NAS-IP-Address [4] 6 66.38.205.194
*Nov 13 15:38:50.103: RADIUS: Acct-Delay-Time [41] 6 0
*Nov 13 15:38:50.123: RADIUS: Received from id 1646/101 66.38.205.196:1813, Accounting-response, len 20
*Nov 13 15:38:50.127: RADIUS: authenticator 17 12 C0 36 4D 35 18 B7 - B9 61 99 5C 04 A5 97 B1
*Nov 13 15:39:03.403: RADIUS/ENCODE(00005D26):Orig. component type = VOICE
*Nov 13 15:39:03.407: RADIUS(00005D26): Config NAS IP: 0.0.0.0
*Nov 13 15:39:03.407: RADIUS(00005D26): sending
*Nov 13 15:39:03.407: RADIUS/ENCODE: Best Local IP-Address 66.38.205.194 for Radius-Server 66.38.205.196
*Nov 13 15:39:03.407: RADIUS(00005D26): Send Accounting-Request to 66.38.205.196:1813 id 1646/102, len 922
*Nov 13 15:39:03.407: RADIUS: authenticator 52 12 89 ED EA 9E F7 E9 - CD B5 13 5C 1A AA A4 D6
*Nov 13 15:39:03.407: RADIUS: Acct-Session-Id [44] 10 "00009B2A"
*Nov 13 15:39:03.407: RADIUS: Calling-Station-Id [31] 12 "6043086884"
*Nov 13 15:39:03.407: RADIUS: Called-Station-Id [30] 12 "6477220426"
*Nov 13 15:39:03.407: RADIUS: Vendor, Cisco [26] 57
*Nov 13 15:39:03.407: RADIUS: h323-setup-time [25] 51 "h323-setup-time=*15:38:11.115 UTC Mon Nov 13 2006"
*Nov 13 15:39:03.407: RADIUS: Vendor, Cisco [26] 36
*Nov 13 15:39:03.407: RADIUS: h323-gw-id [33] 30 "h323-gw-id=a5400.prepaid.gw."
*Nov 13 15:39:03.407: RADIUS: Vendor, Cisco [26] 56
*Nov 13 15:39:03.407: RADIUS: Conf-Id [24] 50 "h323-conf-id=CD693990 726311DB A0A80001 42B36188"
*Nov 13 15:39:03.407: RADIUS: Vendor, Cisco [26] 31
*Nov 13 15:39:03.407: RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer"
*Nov 13 15:39:03.407: RADIUS: Vendor, Cisco [26] 32
*Nov 13 15:39:03.407: RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony"
*Nov 13 15:39:03.407: RADIUS: Vendor, Cisco [26] 65
*Nov 13 15:39:03.411: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=CD693990 726311DB A0A80001 4
2B36188"
*Nov 13 15:39:03.411: RADIUS: Vendor, Cisco [26] 30
*Nov 13 15:39:03.411: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
*Nov 13 15:39:03.411: RADIUS: Vendor, Cisco [26] 43
*Nov 13 15:39:03.411: RADIUS: Cisco AVpair [1] 37 "gw-rxd-cdn=ton:2,npi:1,#:6477220426"
*Nov 13 15:39:03.411: RADIUS: Vendor, Cisco [26] 32
*Nov 13 15:39:03.411: RADIUS: Cisco AVpair [1] 26 "calling-party-category=9"
*Nov 13 15:39:03.411: RADIUS: Vendor, Cisco [26] 33
*Nov 13 15:39:03.411: RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0"
*Nov 13 15:39:03.411: RADIUS: Vendor, Cisco [26] 59
*Nov 13 15:39:03.411: RADIUS: h323-connect-time [28] 53 "h323-connect-time=*15:38:11.119 UTC Mon Nov 13 200
As you can see my Cisco is introducint this (*) with the replies to the radius server causing a problem when the radius server is trying to understand the timestamps.
Can you tell me why may this be hapening with my cisco radius?
Do i need to reload the IOS?
Kind regards,
Saul
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide