Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- Security
- Security Knowledge Base
- CDR configuration with Radius Accounting
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
11530
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
06-09-2009 09:23 PM - edited 02-21-2020 09:53 PM
- Overview
- Reference Links
- Key Fields
- Configuration and Sample Attribute Examples
- Basic Configuration with Standard Attributes
- VSA Configuration
- VSA with Detailed VoIP Attributes
Overview
AAA Accounting with RADIUS can provide very detailed information for VoIP calls beyond just what number was called and for how long. By understanding the options and some of the details of the output, they can also be a useful tool in monitoring the quality of calls and aid in troubleshooting.
Listed below are examples of three different configurations along with example output of what records are sent. The examples below are configured for "stop-only" which means that a record is generated at the end of the call as opposed to "start-stop" which will generate a record at the beginning of the call and at the end.
Each call will generate two records for each of the call legs (both incoming and outgoing) of a call. To understand more about call legs, see Understanding Dial Peers and Call Legs on Cisco IOS Platforms.
The configuration and debug output below was from a Cisco 5400XM running 12.4T software for a call between a H323 device and ISDN PRI trunk. Much of the output and configuration references H323 but the configuration and records are applicable for SIP as well. For MGCP controlled ports, some output on the records may be available while others may not be.
The sample output below is broken down into three different configurations and debug output. Using "debug radius" to display the attribute values sent. The configurations are:
- Basic AAA accounting information with standard RADIUS attributes
- AAA accounting configuration with VSA attributes
- AAA accounting with detailed VoIP VSA attributes present
The Vendor Specific Attributes (VSA) provide more details on the VoIP call processing and DSP statistics. This can be very useful for monitoring the quality of calls and as a troubleshooting aid.
The "acct-template callhistory-detail" configuration below for detailed VoIP attributes basically sends all values. There is something called CDR template that allows control of which of these extra values you would want to send as well. This does allow for some customization on what attributes the gateway will send. For example, to send the "remote-media-udp-port" information in the CDR (which is not in the default VSA attributes), could use a custom CDR template to send this instead of sending all extra attributes when "acct-template callhistory-detail" is configured. See Configuring RADIUS Accounting for RADIUS accounting information along with a CDR template example.
Now, with VSA you will need a RADIUS server that can properly display this information. There are many RADIUS servers on the market and many are free. Many allow custom dictionaries to be defined so that if a particular attribute does not decode properly, given some of the information below, a proper entry could be made to add this value.
FreeRadius is a popular free RADIUS server application and has a built-in Cisco dictionary though some of the values given below may not be present. [1] has a list of various RADIUS servers.
How would you use some of this information? The tool is there to use as you will.
For example, by looking at the "tx-duration" along with the NSA-Port-Id could be used to identify an issues with a particular timeslot or voice port.
The 'h323-voice-quality' to understand when some set of calls falls below the baseline threshold. This value is based upon the codec being use, delay and packet loss on that session and can be used to help identify possible network related issues when the value drops below the typical value for the network.
h323-disconnect-cause can be used to raise awareness of abnormal call setup/teardown that may need attention. This with the release-source value to see if this points to a telephony or IP signaling side issue.
The lost-packets count would be another value that could help identify issues pointing back to the network.
This information can be used in conjunction with other sources of information like the QRT reports or CDR/CMR reports from callmanager.
This will not remove the need for detailed traces/debugs in all cases but can be a good monitoring tool and an useful aid to troubleshooting.
Much of this information is available in more detail across several different source at www.cisco.com. The intent here is to show what is available that may aid in the use of these call detail records (CDR) for monitoring and troubleshooting.
Reference Links
Configuring RADIUS for VOIP (shows examples of creating a CDR template as well): http://www.cisco.com/en/US/docs/ios/voice/cdr/developer/guide/cdradius.html
Breakdown on the various fields in the detailed CDR such as gapfill-with-prediction: http://www.cisco.com/en/US/docs/ios/voice/cdr/developer/guide/cdrcsv.html
This goes into some details for release-source, h323-call-origin, session-protocol, h323-conf-id and other fields. It does break out some of the values included in the example RADIUS attributes: http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/feature/module/9.7_3_/radius.html
Key Fields
Each call consists of two call legs. Normally this would be one telephony call leg and one voip call leg. When configured for accounting, each call leg will generate a RADIUS accounting stop record.
The tie between each record for a call will be the "h323-conf-id" which will be the same for both call legs. Generally though you can just look at the order of the records as typically the call legs will drop at the same time.
Listed below are some of the more interesting fields in the accounting records below, what they represent and some links for further information and also included. Also indicated are indications on when these attribute values are present based upon the configuration.
- 'standard radius attribute' is the basic radius accounting information - 'vsa attribute' is the additional voip vsa values that are sent when 'radius-server vsa send accounting' is configured - 'vsa detailed attribute' is the more detailed information present when "acct-template callhistory-detail" is configured.
- Calling-Station-Id and Called-Station-Id:
- show the ani and dnis for the call
- The values will usually show up in other fields but these attributes are standard radius accounting values so can be easier to pull from the radius server
- standard radius attribute
- h323-call-type:
- indicates where this is the voip or telephony call leg
- vsa attribute
- h323-call-origin:
- indicate if this is the originating or terminating call leg
- Again, we have two call legs in a call. One that comes into the gateway (ie telephony) and one that goes out (ie voip)
- vsa attribute
- session-protocol:
- indicates the voip protocol used
- "cisco" is h323
- sipv2 for sip
- vsa attribute
- h323-setup-time, h323-connect-time, h323-disconnect-time:
- indicates what time that call legs was started, when it was connected (answered) and when it was disconnected **can be used to calculate the duration of the call
- see also "tx-duration"
- vsa attribute
- h323-voice-quality:
- GW creates a ICPIF values for calls with duration greater than 10 seconds
- These values are based upon ITU G.113
- Calculated from packet loss and delay depending on the codec value used
- see http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00800946f8.shtml
- vsa attribute
- NAS-Port-Id:
- indicates the ISDN trunk/timeslot that the call came in on
- The last digit in the output is the timeslot on that T1
- standard radius attribute
- h323-disconnect-cause:
- cause code associated with the disconnect
- This is in hex and "10" is normal call clearing
- this is useful in tracking down abnormal call setup/teardown issues
- see http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a0080094e72.shtml
- see http://www.cisco.com/en/US/docs/voice_ip_comm/bts/3.5/command/reference/992M.html
- see also "disconnect-text" vsa attribute
- vsa attribute
- release-source:
- indicates which call leg released the call
- in conjunction with the h323-disconnect-cause can be useful in narrowing down abnormal call setup/teardown issues
- The decode of these values can be found in the cisco radius link above
- vsa attribute
- h323-remote-address:
- IP address of the signaling device for this call
- this can and in CUCM environments typically is different than the media address
- vsa attribute
- remote-media-address:
- shows the RTP information of the remote voip device
- this can and in CUCM environments typically is different than the signaling address
- vsa attibute
- remote-media-udp-port:
- UDP port for the RTP stream that the GW is sending
- vsa detailed attribute
- dsp-id
- identifier of the DSP used for this call
- this can be used when attempting to correlate some behavior to a particular dsp
- vsa attribute
- gapfill-with-prediction
- report from the DSP in msec how often it masked lost voice packets
- indication of typically some network condition impacting the incoming RTP stream
- 50msec of less can be normal to see. When it climbs to the 100/1000s of msec that it may require further investigation
- vsa detailed attribute
- lost-packets
- number RTP packets not received
- typically indicates some network issue causing impairment on the incoming stream
- vsa detailed attribute
- tx-duration
- total duration of the call
- this can be calculated from the h323-setup-time and h323-disconnect-time
- vsa detailed attribute
Configuration and Sample Attribute Examples
Basic Configuration with Standard Attributes
aaa accounting connection h323 stop-only group radius
gw-accounting aaa
radius-server host <ip address>
radius-server key <key>
000316: Jan 16 19:51:17.082: RADIUS(00000009): Send Accounting-Request to 171.69.88.181:1646 id 1646/8, len 114
000317: Jan 16 19:51:17.082: RADIUS: authenticator 3D 78 34 08 D8 29 7B 1D - 8F E8 33 FC 94 82 84 13
000318: Jan 16 19:51:17.082: RADIUS: Acct-Session-Id [44] 10 "0000000B"
000319: Jan 16 19:51:17.082: RADIUS: Calling-Station-Id [31] 12 "4085268425"
000320: Jan 16 19:51:17.082: RADIUS: Called-Station-Id [30] 6 "6662"
000321: Jan 16 19:51:17.082: RADIUS: Acct-Input-Octets [42] 6 537160728
000322: Jan 16 19:51:17.082: RADIUS: Acct-Output-Octets [43] 6 1771578636
000323: Jan 16 19:51:17.082: RADIUS: Acct-Input-Packets [47] 6 1494
000324: Jan 16 19:51:17.082: RADIUS: Acct-Output-Packets [48] 6 1500
000325: Jan 16 19:51:17.082: RADIUS: Acct-Session-Time [46] 6 30
000326: Jan 16 19:51:17.082: RADIUS: User-Name [1] 12 "4085268425"
000327: Jan 16 19:51:17.082: RADIUS: Acct-Status-Type [40] 6 Stop [2]
000328: Jan 16 19:51:17.082: RADIUS: Service-Type [6] 6 Login [1]
000329: Jan 16 19:51:17.082: RADIUS: NAS-IP-Address [4] 6 172.16.175.184
000330: Jan 16 19:51:17.082: RADIUS: Acct-Delay-Time [41] 6 0
000331: Jan 16 19:51:17.082: RADIUS/ENCODE(00000008):Orig. component type = VOICE
000332: Jan 16 19:51:17.082: RADIUS(00000008): Config NAS IP: 0.0.0.0
000333: Jan 16 19:51:17.082: RADIUS(00000008): sending
000334: Jan 16 19:51:17.082: RADIUS/ENCODE: Best Local IP-Address 172.16.175.184 for Radius-Server 171.69.88.181
000335: Jan 16 19:51:17.082: RADIUS(00000008): Send Accounting-Request to 171.69.88.181:1646 id 1646/9, len 140
000336: Jan 16 19:51:17.082: RADIUS: authenticator 43 55 DD 30 C7 22 F9 42 - 41 C6 7A 90 A8 81 7D CF
000337: Jan 16 19:51:17.082: RADIUS: Acct-Session-Id [44] 10 "0000000A"
000338: Jan 16 19:51:17.082: RADIUS: Calling-Station-Id [31] 12 "4085268425"
000339: Jan 16 19:51:17.082: RADIUS: Called-Station-Id [30] 6 "6662"
000340: Jan 16 19:51:17.082: RADIUS: Acct-Input-Octets [42] 6 240000
000341: Jan 16 19:51:17.082: RADIUS: Acct-Output-Octets [43] 6 250992
000342: Jan 16 19:51:17.082: RADIUS: Acct-Input-Packets [47] 6 1500
000343: Jan 16 19:51:17.082: RADIUS: Acct-Output-Packets [48] 6 1494
000344: Jan 16 19:51:17.082: RADIUS: Acct-Session-Time [46] 6 30
000345: Jan 16 19:51:17.082: RADIUS: User-Name [1] 12 "4085268425"
000346: Jan 16 19:51:17.082: RADIUS: Acct-Status-Type [40] 6 Stop [2]
000347: Jan 16 19:51:17.082: RADIUS: NAS-Port-Type [61] 6 Async [0]
000348: Jan 16 19:51:17.082: RADIUS: NAS-Port [5] 6 0
000349: Jan 16 19:51:17.082: RADIUS: NAS-Port-Id [87] 14 "ISDN 7/2:D:1"
000350: Jan 16 19:51:17.082: RADIUS: Service-Type [6] 6 Login [1]
000351: Jan 16 19:51:17.082: RADIUS: NAS-IP-Address [4] 6 172.16.175.184
000352: Jan 16 19:51:17.082: RADIUS: Acct-Delay-Time [41] 6 0
000353: Jan 16 19:51:17.350: RADIUS: Received from id 1646/8 171.69.88.181:1646, Accounting-response, len 20
000354: Jan 16 19:51:17.350: RADIUS: authenticator 48 73 45 FF B8 23 FA 8E - C9 E1 A4 92 F6 F3 A7 D3
000355: Jan 16 19:51:17.350: RADIUS: Received from id 1646/9 171.69.88.181:1646, Accounting-response, len 20
000356: Jan 16 19:51:17.350: RADIUS: authenticator EA 31 3C DE BA F4 37 5A - C2 E3 94 CD 4D 49 70 BC
VSA Configuration
aaa accounting connection h323 stop-only group radius
gw-accounting aaa
radius-server host <ip address>
radius-server key <key>
radius-server vsa send accounting
000450: Jan 16 19:53:15.407: RADIUS(0000000C): Send Accounting-Request to 171.69.88.181:1646 id 1646/12, len 1127
000451: Jan 16 19:53:15.407: RADIUS: authenticator D2 CC AD 61 D3 12 15 1F - FB 55 D3 71 FA 4B 05 97
000452: Jan 16 19:53:15.407: RADIUS: Acct-Session-Id [44] 10 "00000010"
000453: Jan 16 19:53:15.407: RADIUS: Calling-Station-Id [31] 12 "4085268425"
000454: Jan 16 19:53:15.407: RADIUS: Called-Station-Id [30] 6 "6662"
000455: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 66
000456: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 60 "call-id=13F56D9D-E33E11DD-8019E742-D749E247@172.16.175.184"
000457: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 56
000458: Jan 16 19:53:15.407: RADIUS: h323-setup-time [25] 50 "h323-setup-time=12:52:45.331 PDT Fri Jan 16 2009"
000459: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 30
000460: Jan 16 19:53:15.407: RADIUS: h323-gw-id [33] 24 "h323-gw-id=esc-5400XM."
000461: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 56
000462: Jan 16 19:53:15.407: RADIUS: Conf-Id [24] 50 "h323-conf-id=13F4D175 E33E11DD 8005001E 13D106CC"
000463: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 34
000464: Jan 16 19:53:15.407: RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate"
000465: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 27
000466: Jan 16 19:53:15.407: RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP"
000467: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 65
000468: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=13F4D175 E33E11DD 8005001E 13D106CC"
000469: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 30
000470: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
000471: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 30
000472: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 24 "session-protocol=sipv2"
000473: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 37
000474: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 31 "gw-rxd-cdn=ton:0,npi:0,#:6662"
000475: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 135
000476: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 129 "feature-vsa=fn:TWC,ft:01/16/2009 12:52:45.327,cgn:4085268425,cdn:6662,frs:0,fid:8,fcid:13F4D175E33E11DD8005001E13D106CC,legID:8"
000477: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 58
000478: Jan 16 19:53:15.407: RADIUS: h323-connect-time [28] 52 "h323-connect-time=12:52:45.379 PDT Fri Jan 16 2009"
000479: Jan 16 19:53:15.407: RADIUS: Acct-Input-Octets [42] 6 1617159084
000480: Jan 16 19:53:15.407: RADIUS: Acct-Output-Octets [43] 6 1710074964
000481: Jan 16 19:53:15.407: RADIUS: Acct-Input-Packets [47] 6 0
000482: Jan 16 19:53:15.407: RADIUS: Acct-Output-Packets [48] 6 1500
000483: Jan 16 19:53:15.407: RADIUS: Acct-Session-Time [46] 6 30
000484: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 61
000485: Jan 16 19:53:15.407: RADIUS: h323-disconnect-tim[29] 55 "h323-disconnect-time=12:53:15.403 PDT Fri Jan 16 2009"
000486: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 32
000487: Jan 16 19:53:15.407: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"
000488: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 41
000489: Jan 16 19:53:15.407: RADIUS: h323-remote-address[23] 35 "h323-remote-address=172.16.175.23"
000490: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 24
000491: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 18 "release-source=1"
000492: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 28
000493: Jan 16 19:53:15.407: RADIUS: h323-voice-quality [31] 22 "h323-voice-quality=0"
000494: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 42
000495: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 36 "remote-media-address=172.16.175.23"
000496: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 53
000497: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 47 "gw-rxd-cgn=ton:2,npi:1,pi:0,si:0,#:4085268425"
000498: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 46
000499: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 40 "gw-final-xlated-cdn=ton:0,npi:0,#:6662"
000500: Jan 16 19:53:15.407: RADIUS: Vendor, Cisco [26] 62
000501: Jan 16 19:53:15.407: RADIUS: Cisco AVpair [1] 56 "gw-final-xlated-cgn=ton:2,npi:1,pi:0,si:0,#:4085268425"
000502: Jan 16 19:53:15.407: RADIUS: User-Name [1] 12 "4085268425"
000503: Jan 16 19:53:15.407: RADIUS: Acct-Status-Type [40] 6 Stop [2]
000504: Jan 16 19:53:15.407: RADIUS: Service-Type [6] 6 Login [1]
000505: Jan 16 19:53:15.407: RADIUS: NAS-IP-Address [4] 6 172.16.175.184
000506: Jan 16 19:53:15.407: RADIUS: Acct-Delay-Time [41] 6 0
000507: Jan 16 19:53:15.407: RADIUS/ENCODE(0000000B):Orig. component type = VOICE
000508: Jan 16 19:53:15.407: RADIUS(0000000B): Config NAS IP: 0.0.0.0
000509: Jan 16 19:53:15.407: RADIUS(0000000B): sending
000510: Jan 16 19:53:15.411: RADIUS/ENCODE: Best Local IP-Address 172.16.175.184 for Radius-Server 171.69.88.181
000511: Jan 16 19:53:15.411: RADIUS(0000000B): Send Accounting-Request to 171.69.88.181:1646 id 1646/13, len 988
000512: Jan 16 19:53:15.411: RADIUS: authenticator 0B AA 13 4C 10 03 0C D9 - 2C 69 08 E2 7C 31 D2 2B
000513: Jan 16 19:53:15.411: RADIUS: Acct-Session-Id [44] 10 "0000000F"
000514: Jan 16 19:53:15.411: RADIUS: Calling-Station-Id [31] 12 "4085268425"
000515: Jan 16 19:53:15.411: RADIUS: Called-Station-Id [30] 6 "6662"
000516: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 56
000517: Jan 16 19:53:15.411: RADIUS: h323-setup-time [25] 50 "h323-setup-time=12:52:45.327 PDT Fri Jan 16 2009"
000518: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 30
000519: Jan 16 19:53:15.411: RADIUS: h323-gw-id [33] 24 "h323-gw-id=esc-5400XM."
000520: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 56
000521: Jan 16 19:53:15.411: RADIUS: Conf-Id [24] 50 "h323-conf-id=13F4D175 E33E11DD 8005001E 13D106CC"
000522: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 31
000523: Jan 16 19:53:15.411: RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer"
000524: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 32
000525: Jan 16 19:53:15.411: RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony"
000526: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 65
000527: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=13F4D175 E33E11DD 8005001E 13D106CC"
000528: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 30
000529: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
000530: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 37
000531: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 31 "gw-rxd-cdn=ton:0,npi:0,#:6662"
000532: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 32
000533: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 26 "calling-party-category=9"
000534: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 33
000535: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0"
000536: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 135
000537: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 129 "feature-vsa=fn:TWC,ft:01/16/2009 12:52:45.327,cgn:4085268425,cdn:6662,frs:0,fid:7,fcid:13F4D175E33E11DD8005001E13D106CC,legID:7"
000538: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 58
000539: Jan 16 19:53:15.411: RADIUS: h323-connect-time [28] 52 "h323-connect-time=12:52:45.379 PDT Fri Jan 16 2009"
000540: Jan 16 19:53:15.411: RADIUS: Acct-Input-Octets [42] 6 240000
000541: Jan 16 19:53:15.411: RADIUS: Acct-Output-Octets [43] 6 0
000542: Jan 16 19:53:15.411: RADIUS: Acct-Input-Packets [47] 6 1500
000543: Jan 16 19:53:15.411: RADIUS: Acct-Output-Packets [48] 6 0
000544: Jan 16 19:53:15.411: RADIUS: Acct-Session-Time [46] 6 30
000545: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 61
000546: Jan 16 19:53:15.411: RADIUS: h323-disconnect-tim[29] 55 "h323-disconnect-time=12:53:15.387 PDT Fri Jan 16 2009"
000547: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 32
000548: Jan 16 19:53:15.411: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"
000549: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 35
000550: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 29 "h323-ivr-out=Tariff:Unknown"
000551: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 24
000552: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 18 "release-source=1"
000553: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 28
000554: Jan 16 19:53:15.411: RADIUS: h323-voice-quality [31] 22 "h323-voice-quality=0"
000555: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 20
000556: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 14 "dsp-id=1/1:1"
000557: Jan 16 19:53:15.411: RADIUS: Vendor, Cisco [26] 53
000558: Jan 16 19:53:15.411: RADIUS: Cisco AVpair [1] 47 "gw-rxd-cgn=ton:2,npi:1,pi:0,si:0,#:4085268425"
000559: Jan 16 19:53:15.411: RADIUS: User-Name [1] 12 "4085268425"
000560: Jan 16 19:53:15.411: RADIUS: Acct-Status-Type [40] 6 Stop [2]
000561: Jan 16 19:53:15.411: RADIUS: NAS-Port-Type [61] 6 Async [0]
000562: Jan 16 19:53:15.411: RADIUS: NAS-Port [5] 6 0
000563: Jan 16 19:53:15.411: RADIUS: NAS-Port-Id [87] 14 "ISDN 7/2:D:1"
000564: Jan 16 19:53:15.411: RADIUS: Service-Type [6] 6 Login [1]
000565: Jan 16 19:53:15.411: RADIUS: NAS-IP-Address [4] 6 172.16.175.184
000566: Jan 16 19:53:15.411: RADIUS: Acct-Delay-Time [41] 6 0
000567: Jan 16 19:53:15.611: RADIUS: Received from id 1646/12 171.69.88.181:1646, Accounting-response, len 20
000568: Jan 16 19:53:15.611: RADIUS: authenticator AD 65 7C A1 3D EF 0A 81 - C9 77 D2 DD 1C BB 56 C6
000569: Jan 16 19:53:15.615: RADIUS: Received from id 1646/13 171.69.88.181:1646, Accounting-response, len 20
000570: Jan 16 19:53:15.615: RADIUS: authenticator 7E 0B 15 FD 88 55 1D D4 - 2B 27 A9 98 05 BE 79 0A
000571: Jan 16 19:53:24.351: %CALLTRKR-6-CALL_RECORD: ct_hndl=4, service=None, origin=Answer, category=Modem, DS0 slot/port/ds1/chan=7/2/2/0, called=6662, calling=4085268425, resource slot/port=(n/a)/(n/a), userid=(n/a), ip=0.0.0.0, account id=14, setup=01/16/2009 12:52:45, conn=0.06, phys=0.00, service=0.00, authen=0.00, init-rx/tx b-rate=64000/64000, rx/tx chars=0/0, charged units=0, time=30.06, disc subsys=ISDN, disc code=0x10, disc text=Normal call clearing, sig type=Unknwn
VSA with Detailed VoIP Attributes
aaa accounting connection h323 stop-only group radius
gw-accounting aaa
acct-template callhistory-detail
radius-server host <ip address>
radius-server key <key>
radius-server vsa send accounting
000662: Jan 16 20:05:12.508: RADIUS(0000000F): Send Accounting-Request to 171.69.88.181:1646 id 1646/16, len 1829
000663: Jan 16 20:05:12.508: RADIUS: authenticator 84 DC 23 57 AD C7 9D 74 - 7B 03 CB 8A 45 5B 9F 73
000664: Jan 16 20:05:12.508: RADIUS: Acct-Session-Id [44] 10 "00000015"
000665: Jan 16 20:05:12.508: RADIUS: Calling-Station-Id [31] 12 "4085268425"
000666: Jan 16 20:05:12.508: RADIUS: Called-Station-Id [30] 6 "6662"
000667: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 66
000668: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 60 "call-id=C625DBE0-E33F11DD-801FE742-D749E247@172.16.175.184"
000669: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 56
000670: Jan 16 20:05:12.508: RADIUS: h323-setup-time [25] 50 "h323-setup-time=13:04:53.779 PDT Fri Jan 16 2009"
000671: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 30
000672: Jan 16 20:05:12.508: RADIUS: h323-gw-id [33] 24 "h323-gw-id=esc-5400XM."
000673: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 56
000674: Jan 16 20:05:12.508: RADIUS: Conf-Id [24] 50 "h323-conf-id=C6253FB8 E33F11DD 8006001E 13D106CC"
000675: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 34
000676: Jan 16 20:05:12.508: RADIUS: h323-call-origin [26] 28 "h323-call-origin=originate"
000677: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 27
000678: Jan 16 20:05:12.508: RADIUS: h323-call-type [27] 21 "h323-call-type=VoIP"
000679: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 65
000680: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=C6253FB8 E33F11DD 8006001E 13D106CC"
000681: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 30
000682: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
000683: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 30
000684: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 24 "session-protocol=sipv2"
000685: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 37
000686: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 31 "gw-rxd-cdn=ton:0,npi:0,#:6662"
000687: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 136
000688: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 130 "feature-vsa=fn:TWC,ft:01/16/2009 13:04:53.779,cgn:4085268425,cdn:6662,frs:0,fid:10,fcid:C6253FB8E33F11DD8006001E13D106CC,legID:A"
000689: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 58
000690: Jan 16 20:05:12.508: RADIUS: h323-connect-time [28] 52 "h323-connect-time=13:04:53.831 PDT Fri Jan 16 2009"
000691: Jan 16 20:05:12.508: RADIUS: Acct-Input-Octets [42] 6 1708473512
000692: Jan 16 20:05:12.508: RADIUS: Acct-Output-Octets [43] 6 1771591596
000693: Jan 16 20:05:12.508: RADIUS: Acct-Input-Packets [47] 6 0
000694: Jan 16 20:05:12.508: RADIUS: Acct-Output-Packets [48] 6 933
000695: Jan 16 20:05:12.508: RADIUS: Acct-Session-Time [46] 6 19
000696: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 61
000697: Jan 16 20:05:12.508: RADIUS: h323-disconnect-tim[29] 55 "h323-disconnect-time=13:05:12.508 PDT Fri Jan 16 2009"
000698: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 32
000699: Jan 16 20:05:12.508: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"
000700: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 41
000701: Jan 16 20:05:12.508: RADIUS: h323-remote-address[23] 35 "h323-remote-address=172.16.175.23"
000702: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 24
000703: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 18 "release-source=4"
000704: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 28
000705: Jan 16 20:05:12.508: RADIUS: h323-voice-quality [31] 22 "h323-voice-quality=0"
000706: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 42
000707: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 36 "remote-media-address=172.16.175.23"
000708: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 53
000709: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 47 "gw-rxd-cgn=ton:2,npi:1,pi:0,si:0,#:4085268425"
000710: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 46
000711: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 40 "gw-final-xlated-cdn=ton:0,npi:0,#:6662"
000712: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 62
000713: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 56 "gw-final-xlated-cgn=ton:2,npi:1,pi:0,si:0,#:4085268425"
000714: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 23
000715: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 17 "charged-units=0"
000716: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 49
000717: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 43 "disconnect-text=normal call clearing (16)"
000718: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 25
000719: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 19 "peer-address=6662"
000720: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 24
000721: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 18 "info-type=speech"
000722: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 21
000723: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 15 "peer-id=66662"
000724: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 25
000725: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 19 "peer-if-index=227"
000726: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 26
000727: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 20 "logical-if-index=0"
000728: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 23
000729: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 17 "codec-bytes=160"
000730: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 32
000731: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 26 "coder-type-rate=g711ulaw"
000732: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 27
000733: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 21 "ontime-rv-playout=0"
000734: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 28
000735: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 22 "remote-udp-port=5060"
000736: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 35
000737: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 29 "remote-media-udp-port=17762"
000738: Jan 16 20:05:12.508: RADIUS: Vendor, Cisco [26] 26
000739: Jan 16 20:05:12.508: RADIUS: Cisco AVpair [1] 20 "vad-enable=disable"
000740: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 27
000741: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 21 "receive-delay=65 ms"
000742: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 29
000743: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 23 "round-trip-delay=0 ms"
000744: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 35
000745: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 29 "hiwater-playout-delay=65 ms"
000746: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 35
000747: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 29 "lowater-playout-delay=65 ms"
000748: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 39
000749: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 33 "gapfill-with-interpolation=0 ms"
000750: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 36
000751: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 30 "gapfill-with-prediction=0 ms"
000752: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 36
000753: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 30 "gapfill-with-redundancy=0 ms"
000754: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 33
000755: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 27 "gapfill-with-silence=0 ms"
000756: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 23
000757: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 17 "early-packets=0"
000758: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 22
000759: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 16 "late-packets=0"
000760: Jan 16 20:05:12.512: RADIUS: Vendor, Cisco [26] 22
000761: Jan 16 20:05:12.512: RADIUS: Cisco AVpair [1] 16 "lost-packets=0"
000762: Jan 16 20:05:12.512: RADIUS: User-Name [1] 12 "4085268425"
000763: Jan 16 20:05:12.512: RADIUS: Acct-Status-Type [40] 6 Stop [2]
000764: Jan 16 20:05:12.512: RADIUS: Service-Type [6] 6 Login [1]
000765: Jan 16 20:05:12.512: RADIUS: NAS-IP-Address [4] 6 172.16.175.184
000766: Jan 16 20:05:12.512: RADIUS: Acct-Delay-Time [41] 6 0
000767: Jan 16 20:05:12.516: ISDN Se7/2:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x9C8D
Cause i = 0x8090 - Normal call clearing
000768: Jan 16 20:05:12.528: ISDN Se7/2:23 Q931: RX <- RELEASE pd = 8 callref = 0x1C8D
000769: Jan 16 20:05:12.528: ISDN Se7/2:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x9C8D
000770: Jan 16 20:05:12.528: RADIUS/ENCODE(0000000E):Orig. component type = VOICE
000771: Jan 16 20:05:12.528: RADIUS(0000000E): Config NAS IP: 0.0.0.0
000772: Jan 16 20:05:12.528: RADIUS(0000000E): sending
000773: Jan 16 20:05:12.528: RADIUS/ENCODE: Best Local IP-Address 172.16.175.184 for Radius-Server 171.69.88.181
000774: Jan 16 20:05:12.528: RADIUS(0000000E): Send Accounting-Request to 171.69.88.181:1646 id 1646/17, len 1333
000775: Jan 16 20:05:12.528: RADIUS: authenticator 8C 53 DD A1 BD 4A 5D BC - 7A 32 64 BB 81 4A EF 3E
000776: Jan 16 20:05:12.528: RADIUS: Acct-Session-Id [44] 10 "00000014"
000777: Jan 16 20:05:12.528: RADIUS: Calling-Station-Id [31] 12 "4085268425"
000778: Jan 16 20:05:12.528: RADIUS: Called-Station-Id [30] 6 "6662"
000779: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 56
000780: Jan 16 20:05:12.528: RADIUS: h323-setup-time [25] 50 "h323-setup-time=13:04:53.775 PDT Fri Jan 16 2009"
000781: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 30
000782: Jan 16 20:05:12.528: RADIUS: h323-gw-id [33] 24 "h323-gw-id=esc-5400XM."
000783: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 56
000784: Jan 16 20:05:12.528: RADIUS: Conf-Id [24] 50 "h323-conf-id=C6253FB8 E33F11DD 8006001E 13D106CC"
000785: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 31
000786: Jan 16 20:05:12.528: RADIUS: h323-call-origin [26] 25 "h323-call-origin=answer"
000787: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 32
000788: Jan 16 20:05:12.528: RADIUS: h323-call-type [27] 26 "h323-call-type=Telephony"
000789: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 65
000790: Jan 16 20:05:12.528: RADIUS: Cisco AVpair [1] 59 "h323-incoming-conf-id=C6253FB8 E33F11DD 8006001E 13D106CC"
000791: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 30
000792: Jan 16 20:05:12.528: RADIUS: Cisco AVpair [1] 24 "subscriber=RegularLine"
000793: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 37
000794: Jan 16 20:05:12.528: RADIUS: Cisco AVpair [1] 31 "gw-rxd-cdn=ton:0,npi:0,#:6662"
000795: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 32
000796: Jan 16 20:05:12.528: RADIUS: Cisco AVpair [1] 26 "calling-party-category=9"
000797: Jan 16 20:05:12.528: RADIUS: Vendor, Cisco [26] 33
000798: Jan 16 20:05:12.528: RADIUS: Cisco AVpair [1] 27 "transmission-medium-req=0"
000799: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 135
000800: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 129 "feature-vsa=fn:TWC,ft:01/16/2009 13:04:53.775,cgn:4085268425,cdn:6662,frs:0,fid:9,fcid:C6253FB8E33F11DD8006001E13D106CC,legID:9"
000801: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 58
000802: Jan 16 20:05:12.532: RADIUS: h323-connect-time [28] 52 "h323-connect-time=13:04:53.831 PDT Fri Jan 16 2009"
000803: Jan 16 20:05:12.532: RADIUS: Acct-Input-Octets [42] 6 149280
000804: Jan 16 20:05:12.532: RADIUS: Acct-Output-Octets [43] 6 0
000805: Jan 16 20:05:12.532: RADIUS: Acct-Input-Packets [47] 6 933
000806: Jan 16 20:05:12.532: RADIUS: Acct-Output-Packets [48] 6 0
000807: Jan 16 20:05:12.532: RADIUS: Acct-Session-Time [46] 6 19
000808: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 61
000809: Jan 16 20:05:12.532: RADIUS: h323-disconnect-tim[29] 55 "h323-disconnect-time=13:05:12.528 PDT Fri Jan 16 2009"
000810: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 32
000811: Jan 16 20:05:12.532: RADIUS: h323-disconnect-cau[30] 26 "h323-disconnect-cause=10"
000812: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 35
000813: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 29 "h323-ivr-out=Tariff:Unknown"
000814: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 24
000815: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 18 "release-source=4"
000816: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 28
000817: Jan 16 20:05:12.532: RADIUS: h323-voice-quality [31] 22 "h323-voice-quality=0"
000818: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 20
000819: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 14 "dsp-id=1/1:1"
000820: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 53
000821: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 47 "gw-rxd-cgn=ton:2,npi:1,pi:0,si:0,#:4085268425"
000822: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 23
000823: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 17 "charged-units=0"
000824: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 49
000825: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 43 "disconnect-text=normal call clearing (16)"
000826: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 31
000827: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 25 "peer-address=4085268425"
000828: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 24
000829: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 18 "info-type=speech"
000830: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 20
000831: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 14 "peer-id=5001"
000832: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 25
000833: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 19 "peer-if-index=230"
000834: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 28
000835: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 22 "logical-if-index=107"
000836: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 21
000837: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 15 "acom-level=12"
000838: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 32
000839: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 26 "coder-type-rate=g711ulaw"
000840: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 30
000841: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 24 "noise-level=4294967212"
000842: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 34
000843: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 28 "voice-tx-duration=18670 ms"
000844: Jan 16 20:05:12.532: RADIUS: Vendor, Cisco [26] 28
000845: Jan 16 20:05:12.532: RADIUS: Cisco AVpair [1] 22 "tx-duration=18670 ms"
000846: Jan 16 20:05:12.532: RADIUS: User-Name [1] 12 "4085268425"
000847: Jan 16 20:05:12.532: RADIUS: Acct-Status-Type [40] 6 Stop [2]
000848: Jan 16 20:05:12.532: RADIUS: NAS-Port-Type [61] 6 Async [0]
000849: Jan 16 20:05:12.532: RADIUS: NAS-Port [5] 6 0
000850: Jan 16 20:05:12.532: RADIUS: NAS-Port-Id [87] 14 "ISDN 7/2:D:1"
000851: Jan 16 20:05:12.532: RADIUS: Service-Type [6] 6 Login [1]
000852: Jan 16 20:05:12.532: RADIUS: NAS-IP-Address [4] 6 172.16.175.184
000853: Jan 16 20:05:12.532: RADIUS: Acct-Delay-Time [41] 6 0
000854: Jan 16 20:05:12.644: RADIUS: Received from id 1646/16 171.69.88.181:1646, Accounting-response, len 20
000855: Jan 16 20:05:12.644: RADIUS: authenticator 97 6A E8 69 E9 77 BA 95 - A5 6F BF 62 E8 9B 17 D3
000856: Jan 16 20:05:12.644: RADIUS: Received from id 1646/17 171.69.88.181:1646, Accounting-response, len 20
000857: Jan 16 20:05:12.644: RADIUS: authenticator 72 25 D8 B6 35 30 52 10 - 85 78 02 8F 39 0F 37 0B
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents