Cisco IOS Voice Troubleshooting and Monitoring Guide, Release 12.4
Troubleshooting AAA and Billing Applications
Downloads: This chapterpdf (PDF - 413.0KB) The complete bookPDF (PDF - 2.89MB) | Feedback

Troubleshooting AAA and Billing Applications

Table Of Contents

Troubleshooting AAA and Billing Applications

Troubleshooting AAA for Voice

Using Debug Commands for AAA Voice Troubleshooting

debug radius

debug radius accounting

Using show Commands for AAA Voice Troubleshooting

show call accounting voice summary

show call accounting-template voice

show call aaa attributes

Accounting Server Connectivity Failure and Recovery Detection

Prerequisites for Accounting Server Connectivity Failure and Recovery Detection

Restrictions for Accounting Server Connectivity Failure and Recovery Detection

Information About Accounting Server Connectivity Failure and Recovery Detection

Global Accounting Script

How to Configure Accounting Server Connectivity Failure and Recovery Detection

Configuring the GAS

Loading the GAS

Starting the GAS

Verifying the GAS

Troubleshooting Accounting Server Connectivity Failure and Recovery Detection

Configuration Examples for Accounting Server Connectivity Failure and Recovery Detection

Configuring the GAS: Example

Loading the GAS: Example

Starting the GAS: Example

Verifying the GAS: Example

Troubleshooting Enhanced Billing Support for SIP Gateways

Troubleshooting Settlement

Settlement Database Not Set Up Properly

Tcl IVR Script Not Called

No Destination Pattern Set

No Session Target Settlement Set on Originating Gateway

No VoIP Inbound Dial Peer on Terminating Gateway

No Application Attribute on Terminating Gateway

Terminating Gateway Not Synchronized with Settlement Server

Settlement Provider Not Running

Router and Server Not Using SSL to Communicate

Multiple Dial Peers Have Random Order

H.323 Setup Connection Timeout

Problem Isolation


Troubleshooting AAA and Billing Applications


To troubleshoot authentication, authorization, and accounting (AAA), billing, and settlement issues for voice services, refer to the following sections:

Troubleshooting AAA for Voice

Accounting Server Connectivity Failure and Recovery Detection

Troubleshooting Enhanced Billing Support for SIP Gateways

Troubleshooting Settlement

Troubleshooting AAA for Voice

This section contains the following topics:

Using Debug Commands for AAA Voice Troubleshooting

Using show Commands for AAA Voice Troubleshooting

For more information about AAA troubleshooting, go to the "Diagnosing and Troubleshooting AAA Operations" chapter in the Cisco AAA Implementation Case Study document.

Using Debug Commands for AAA Voice Troubleshooting

debug radius

The output below is from troubleshooting AAA redirect using called number for an incoming POTS dial peer.

!In this example, an incoming call is set up using dial-peer voice 1000 pots. Applying 
voice-class aaa 1 to dial-peer voice 1000 redirects AAA requests to the server specified 
for method list sanj_aaa1:10.6.20.70 auth-port 1698 acct-port 1699. 

aaa group server radius sg1
 server 10.6.20.70 auth-port 1698 acct-port 1699
!
aaa group server radius sg6
 server 10.6.20.70 auth-port 1704 acct-port 1705
!
aaa group server radius sg7
 server 10.6.20.70 auth-port 1720 acct-port 1721
!
aaa authentication login sanj_aaa1 group sg1
aaa authorization exec sanj_aaa1 group sg1
aaa accounting connection sanj_aaa1 start-stop group sg1
!
aaa authentication login sanj_aaa6 group sg6
aaa authorization exec sanj_aaa6 group sg6
aaa accounting connection sanj_aaa6 start-stop group sg6
!
aaa authentication login sanj_aaa7 group sg7
aaa authorization exec sanj_aaa7 group sg7
aaa accounting connection sanj_aaa7 start-stop group sg7
!
voice class aaa 1
 authentication method sanj_aaa1
 authorization method sanj_aaa1
 accounting method sanj_aaa1
 accounting template cdr1
!
voice class aaa 2
 authentication method sanj_aaa6
 authorization method sanj_aaa6
 accounting method sanj_aaa6
 accounting template cdr2
!
voice class aaa 3
 authentication method sanj_aaa7
 authorization method sanj_aaa7
 accounting method sanj_aaa7
!
dial-peer voice 1000 pots
 application plain_debit
 incoming called-number 12345
 voice-class aaa 1
 port 0:D
!
dial-peer voice 1001 pots
 application plain_debit
 incoming called-number 12346
 voice-class aaa 2
 port 1:D


debug radius
Radius protocol debugging is on
Radius packet hex dump debugging is off
Radius packet protocol debugging is on
debug isdn q931
ISDN Q931 packets debugging is on

00:17:55: ISDN Se0:23: RX <-  SETUP pd = 8  callref = 0x009D
00:17:55:         Bearer Capability i = 0x8090A2
00:17:55:         Channel ID i = 0xE1808397
00:17:55:         Calling Party Number i = 0x0080, '4081234567', Plan:Unknown, 
Type:Unknown
00:17:55:         Called Party Number i = 0xE9, '12345', Plan:Private, Type:Abbreviated
00:17:55: RADIUS/ENCODE(0000000C): Unsupported AAA attribute timezone
00:17:55: RADIUS(0000000C): Encoding nas-port...Only port-type avlbl
00:17:55: RADIUS(0000000C): sending
00:17:55: RADIUS: Send to unknown id 4 10.6.20.70:1699, Accounting-Request, len 262
00:17:55: RADIUS:  authenticator 10 41 58 99 4C F2 B1 CD - 44 3E E3 60 5D 10 C3 A9
00:17:55: RADIUS:  Acct-Session-Id     [44]  10  "0000000C"
00:17:55: RADIUS:  Vendor, Cisco       [26]  56  
00:17:55: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=B8FE8B7F BF1711D3 800CE483 
89ADC43B"
00:17:55: RADIUS:  Vendor, Cisco       [26]  31  
00:17:55: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
00:17:55: RADIUS:  Vendor, Cisco       [26]  65  
00:17:55: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=B8FE8B7F BF1711D3 
800CE483 89ADC43B"
00:17:55: RADIUS:  User-Name           [1]   12  "4081234567"
00:17:55: RADIUS:  Acct-Status-Type    [40]  6   Start                     [1]
00:17:55: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:17:55: RADIUS:  Vendor, Cisco       [26]  19  
00:17:55: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
00:17:55: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:17:55: RADIUS:  Called-Station-Id   [30]  7   "12345"
00:17:55: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:17:55: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:17:55: RADIUS:  Delay-Time          [41]  6   0                         
00:17:55: ISDN Se0:23: TX ->  CALL_PROC pd = 8  callref = 0x809D
00:17:55:         Channel ID i = 0xA98397
00:17:55: ISDN Se0:23: TX ->  CONNECT pd = 8  callref = 0x809D
00:17:55: RADIUS: Received from id 4 10.6.20.70:1699, Accounting-response, len 20
00:17:55: RADIUS:  authenticator DC CD BA E8 7E 02 EA D1 - 12 67 DC 57 3C 73 56 75
00:17:55: ISDN Se0:23: RX <-  CONNECT_ACK pd = 8  callref = 0x009D
00:17:55: ISDN Se0:23: CALL_PROGRESS: CALL_CONNECTED call id 0x63, bchan 22, dsl 0
00:17:55: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4081234567 
00:18:01: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4081234567 
00:18:06: RADIUS(0000000C): Encoding nas-port...Only port-type avlbl
00:18:06: RADIUS/ENCODE(0000000C): acct_session_id: 12
00:18:06: RADIUS(0000000C): sending
00:18:06: RADIUS: Send to unknown id 3 10.6.20.70:1698, Access-Request, len 199
00:18:06: RADIUS:  authenticator 4B 2C 8C D7 12 54 45 3D - 51 44 30 05 C3 9B 44 B1
00:18:06: RADIUS:  User-Name           [1]   8   "777777"
00:18:06: RADIUS:  User-Password       [2]   18  *
00:18:06: RADIUS:  Vendor, Cisco       [26]  56  
00:18:06: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=61A46F2C 00000003 62E66E40 
62E3A5C8"
00:18:06: RADIUS:  Vendor, Cisco       [26]  36  
00:18:06: RADIUS:   Cisco AVpair       [1]   30  "h323-ivr-out=transactionID:3"
00:18:06: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:18:06: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:18:06: RADIUS:  Vendor, Cisco       [26]  19  
00:18:06: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
00:18:06: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:18:06: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:18:06: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:18:06: RADIUS: Received from id 3 10.6.20.70:1698, Access-Accept, len 200
00:18:06: RADIUS:  authenticator 9C AA 9E 4C 64 02 13 3A - 72 8C 3F D9 72 D0 3B 06
00:18:06: RADIUS:  Vendor, Cisco       [26]  27  
00:18:06: RADIUS:   Cisco AVpair       [1]   21  "h323-ivr-in=sanjose"
00:18:06: RADIUS:  Vendor, Cisco       [26]  34  
00:18:06: RADIUS:   Cisco AVpair       [1]   28  "h323-credit-amount=7777.77"
00:18:06: RADIUS:  Vendor, Cisco       [26]  26  
00:18:06: RADIUS:   Cisco AVpair       [1]   20  "h323-return-code=0"
00:18:06: RADIUS:  Vendor, Cisco       [26]  30  
00:18:06: RADIUS:   h323-credit-time   [102] 24  "h323-credit-time=54329"
00:18:06: RADIUS:  Vendor, Cisco       [26]  33  
00:18:06: RADIUS:   h323-billing-model [109] 27  "h323-billing-model=prepay"
00:18:06: RADIUS:  Vendor, Cisco       [26]  24  
00:18:06: RADIUS:   h323-currency      [110] 18  "h323-currency=US"
00:18:06: RADIUS:  Idle-Timeout        [28]  6   30                        
00:18:06: RADIUS: Received from id C
00:18:27: ISDN Se0:23: RX <-  DISCONNECT pd = 8  callref = 0x009D
00:18:27:         Cause i = 0x8290 - Normal call clearing
00:18:27: %ISDN-6-DISCONNECT: Interface Serial0:22  disconnected from 4081234567 , call 
lasted 32 seconds
00:18:27: ISDN Se0:23: TX ->  RELEASE pd = 8  callref = 0x809D
00:18:27: ISDN Se0:23: RX <-  RELEASE_COMP pd = 8  callref = 0x009D
00:18:27: RADIUS/ENCODE(0000000C): Unsupported AAA attribute timezone
00:18:27: RADIUS(0000000C): Encoding nas-port...Only port-type avlbl
00:18:27: RADIUS(0000000C): sending
00:18:27: RADIUS: Send to unknown id 5 10.6.20.70:1699, Accounting-Request, len 327
00:18:27: RADIUS:  authenticator 2D 65 1C 38 6D 5B B3 DD - C8 57 D6 02 B4 4F E4 4E
00:18:27: RADIUS:  Acct-Session-Id     [44]  10  "0000000C"
00:18:27: RADIUS:  Vendor, Cisco       [26]  56  
00:18:27: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=B8FE8B7F BF1711D3 800CE483 
89ADC43B"
00:18:27: RADIUS:  Vendor, Cisco       [26]  31  
00:18:27: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
00:18:27: RADIUS:  Vendor, Cisco       [26]  65  
00:18:27: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=B8FE8B7F BF1711D3 
800CE483 89ADC43B"
00:18:27: RADIUS:  Acct-Input-Octets   [42]  6   0                         
00:18:27: RADIUS:  Acct-Output-Octets  [43]  6   148000                    
00:18:27: RADIUS:  Acct-Input-Packets  [47]  6   0                         
00:18:27: RADIUS:  Acct-Output-Packets [48]  6   925                       
00:18:27: RADIUS:  Acct-Session-Time   [46]  6   32                        
00:18:27: RADIUS:  Vendor, Cisco       [26]  35  
00:18:27: RADIUS:   Cisco AVpair       [1]   29  "h323-ivr-out=Tariff:Unknown"
00:18:27: RADIUS:  User-Name           [1]   12  "4081234567"
00:18:27: RADIUS:  Acct-Status-Type    [40]  6   Stop                      [2]
00:18:27: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:18:27: RADIUS:  Vendor, Cisco       [26]  19  
00:18:27: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
00:18:27: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:18:27: RADIUS:  Called-Station-Id   [30]  7   "12345"
00:18:27: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:18:27: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:18:27: RADIUS:  Delay-Time          [41]  6   0                         
00:18:27: RADIUS: Received from id 5 10.6.20.70:1699, Accounting-response, len 20
00:18:27: RADIUS:  authenticator E5 B1 ED 3B AD A8 5B 5C - 49 83 63 BA DF 02 B2 00

An incoming call is set up using dial-peer voice 1001 pots. dial-peer voice 1001 has voice-class aaa 2 applied which should redirect AAA requests to the server specified for method list sanj_aaa6: 10.6.20.70  auth-port 1708 acct-port 1709.


00:30:05: ISDN Se1:23: RX <-  SETUP pd = 8  callref = 0x0004
00:30:05:         Bearer Capability i = 0x8090A2
00:30:05:         Channel ID i = 0xE1808397
00:30:05:         Calling Party Number i = 0x0080, '4081234567', Plan:Unknown, 
Type:Unknown
00:30:05:         Called Party Number i = 0xE9, '12346', Plan:Private, Type:Abbreviated
00:30:05: RADIUS/ENCODE(0000000E): Unsupported AAA attribute timezone
00:30:05: RADIUS(0000000E): Encoding nas-port...Only port-type avlbl
00:30:05: RADIUS(0000000E): sending
00:30:05: RADIUS: Send to unknown id 6 10.6.20.70:1709, Accounting-Request, len 262
00:30:05: RADIUS:  authenticator 2F 3A 09 3D 6B C4 10 D2 - F6 68 D6 F4 36 35 C3 DE
00:30:05: RADIUS:  Acct-Session-Id     [44]  10  "0000000E"
00:30:05: RADIUS:  Vendor, Cisco       [26]  56  
00:30:05: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=6C29BC16 BF1911D3 8010E483 
89ADC43B"
00:30:05: RADIUS:  Vendor, Cisco       [26]  31  
00:30:05: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
00:30:05: RADIUS:  Vendor, Cisco       [26]  65  
00:30:05: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=6C29BC16 BF1911D3 
8010E483 89ADC43B"
00:30:05: RADIUS:  User-Name           [1]   12  "4081234567"
00:30:05: RADIUS:  Acct-Status-Type    [40]  6   Start                     [1]
00:30:05: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:30:05: RADIUS:  Vendor, Cisco       [26]  19  
00:30:05: RADIUS:   cisco-nas-port     [2]   13  "ISDN 1:D:23"
00:30:05: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:30:05: RADIUS:  Called-Station-Id   [30]  7   "12346"
00:30:05: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:30:05: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:30:05: RADIUS:  Delay-Time          [41]  6   0                         
00:30:05: ISDN Se1:23: TX ->  CALL_PROC pd = 8  callref = 0x8004
00:30:05:         Channel ID i = 0xA98397
00:30:05: ISDN Se1:23: TX ->  CONNECT pd = 8  callref = 0x8004
00:30:05: ISDN Se1:23: RX <-  CONNECT_ACK pd = 8  callref = 0x0004
00:30:05: ISDN Se1:23: CALL_PROGRESS: CALL_CONNECTED call id 0x64, bchan 22, dsl 1
00:30:05: %ISDN-6-CONNECT: Interface Serial1:22 is now connected to 4081234567 
00:30:06: RADIUS: Received from id 6 10.6.20.70:1709, Accounting-response, len 20
00:30:06: RADIUS:  authenticator E1 AD 70 9F DC 09 29 32 - 74 47 96 9F 3F 77 27 82
00:30:11: %ISDN-6-CONNECT: Interface Serial1:22 is now connected to 4081234567 
00:30:19: RADIUS(0000000E): Encoding nas-port...Only port-type avlbl
00:30:19: RADIUS/ENCODE(0000000E): acct_session_id: 14
00:30:19: RADIUS(0000000E): sending
00:30:19: RADIUS: Send to unknown id 4 10.6.20.70:1708, Access-Request, len 199
00:30:19: RADIUS:  authenticator CE 16 21 8D A5 59 56 9F - B7 E9 CA 5C EC C5 89 A0
00:30:19: RADIUS:  User-Name           [1]   8   "777777"
00:30:19: RADIUS:  User-Password       [2]   18  *
00:30:19: RADIUS:  Vendor, Cisco       [26]  56  
00:30:19: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=61A46F2C 00000003 62E66E40 
634A0A64"
00:30:19: RADIUS:  Vendor, Cisco       [26]  36  
00:30:19: RADIUS:   Cisco AVpair       [1]   30  "h323-ivr-out=transactionID:4"
00:30:19: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:30:19: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:30:19: RADIUS:  Vendor, Cisco       [26]  19  
00:30:19: RADIUS:   cisco-nas-port     [2]   13  "ISDN 1:D:23"
00:30:19: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:30:19: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:30:19: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:30:20: RADIUS: Received from id 4 10.6.20.70:1708, Access-Accept, len 173
00:30:20: RADIUS:  authenticator FF 0D 40 72 0D 80 12 26 - 44 13 D5 0E C4 BB 71 BE
00:30:20: RADIUS:  Vendor, Cisco       [26]  34  
00:30:20: RADIUS:   Cisco AVpair       [1]   28  "h323-credit-amount=7777.77"
00:30:20: RADIUS:  Vendor, Cisco       [26]  26  
00:30:20: RADIUS:   Cisco AVpair       [1]   20  "h323-return-code=0"
00:30:20: RADIUS:  Vendor, Cisco       [26]  30  
00:30:20: RADIUS:   h323-credit-time   [102] 24  "h323-credit-time=54329"
00:30:20: RADIUS:  Vendor, Cisco       [26]  33  
00:30:20: RADIUS:   h323-billing-model [109] 27  "h323-billing-model=prepay"
00:30:20: RADIUS:  Vendor, Cisco       [26]  24  
00:30:20: RADIUS:   h323-currency      [110] 18  "h323-currency=US"
00:30:20: RADIUS:  Idle-Timeout        [28]  6   30                        
00:30:20: RADIUS: Received from id E
00:30:43: ISDN Se1:23: RX <-  DISCONNECT pd = 8  callref = 0x0004
00:30:43:         Cause i = 0x8290 - Normal call clearing
00:30:43: %ISDN-6-DISCONNECT: Interface Serial1:22  disconnected from 4081234567 , call 
lasted 37 seconds
00:30:43: ISDN Se1:23: TX ->  RELEASE pd = 8  callref = 0x8004
00:30:43: ISDN Se1:23: RX <-  RELEASE_COMP pd = 8  callref = 0x0004
00:30:43: RADIUS/ENCODE(0000000E): Unsupported AAA attribute timezone
00:30:43: RADIUS(0000000E): Encoding nas-port...Only port-type avlbl
00:30:43: RADIUS(0000000E): sending
00:30:43: RADIUS: Send to unknown id 7 10.6.20.70:1709, Accounting-Request, len 327
00:30:43: RADIUS:  authenticator 99 5A B4 45 67 C0 F4 91 - 9B 4B C3 1D 7E DE 7D D1
00:30:43: RADIUS:  Acct-Session-Id     [44]  10  "0000000E"
00:30:43: RADIUS:  Vendor, Cisco       [26]  56  
00:30:43: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=6C29BC16 BF1911D3 8010E483 
89ADC43B"
00:30:43: RADIUS:  Vendor, Cisco       [26]  31  
00:30:43: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
00:30:43: RADIUS:  Vendor, Cisco       [26]  65  
00:30:43: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=6C29BC16 BF1911D3 
8010E483 89ADC43B"
00:30:43: RADIUS:  Acct-Input-Octets   [42]  6   0                         
00:30:43: RADIUS:  Acct-Output-Octets  [43]  6   161920                    
00:30:43: RADIUS:  Acct-Input-Packets  [47]  6   0                         
00:30:43: RADIUS:  Acct-Output-Packets [48]  6   1012                      
00:30:43: RADIUS:  Acct-Session-Time   [46]  6   37                        
00:30:43: RADIUS:  Vendor, Cisco       [26]  35  
00:30:43: RADIUS:   Cisco AVpair       [1]   29  "h323-ivr-out=Tariff:Unknown"
00:30:43: RADIUS:  User-Name           [1]   12  "4081234567"
00:30:43: RADIUS:  Acct-Status-Type    [40]  6   Stop                      [2]
00:30:43: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:30:43: RADIUS:  Vendor, Cisco       [26]  19  
00:30:43: RADIUS:   cisco-nas-port     [2]   13  "ISDN 1:D:23"
00:30:43: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:30:43: RADIUS:  Called-Station-Id   [30]  7   "12346"
00:30:43: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:30:43: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:30:43: RADIUS:  Delay-Time          [41]  6   0                         
00:30:43: RADIUS: Received from id 7 10.6.20.70:1709, Accounting-response, len 20
00:30:43: RADIUS:  authenticator 78 80 AB D1 82 75 ED ED - E4 1F 12 25 D8 83 F9 6


!voice class aaa 3 is applied to dial-peer voice 1000 pots and a call is made. voice class aaa 3 uses server 10.6.20.70 with auth port 1720 and acct port 1721. The radius daemon has not started. AAA accounting and AAA authorization requests are sent to the appropriate server but no acknowledgement is recieved. Retries are attempted.


00:37:03: %SYS-5-CONFIG_I: Configured from console by console
00:37:11: ISDN Se0:23: RX <-  SETUP pd = 8  callref = 0x009E
00:37:11:         Bearer Capability i = 0x8090A2
00:37:11:         Channel ID i = 0xE1808397
00:37:11:         Calling Party Number i = 0x0080, '4081234567', Plan:Unknown, 
Type:Unknown
00:37:11:         Called Party Number i = 0xE9, '12345', Plan:Private, Type:Abbreviated
00:37:11: RADIUS/ENCODE(00000010): Unsupported AAA attribute timezone
00:37:11: RADIUS(00000010): Encoding nas-port...Only port-type avlbl
00:37:11: RADIUS(00000010): sending
00:37:11: RADIUS: Send to unknown id 8 10.6.20.70:1721, Accounting-Request, len 414
00:37:11: RADIUS:  authenticator EC F7 FD AB ED 0D 26 BF - F0 A4 D2 88 91 1E D9 22
00:37:11: RADIUS:  Acct-Session-Id     [44]  10  "00000010"
00:37:11: RADIUS:  Vendor, Cisco       [26]  56  
00:37:11: RADIUS:   h323-setup-time    [25]  50  "h323-setup-time=*00:37:09.095 UTC Sat 
Jan 1 2000"
00:37:11: RADIUS:  Vendor, Cisco       [26]  34  
00:37:11: RADIUS:   h323-gw-id         [33]  28  "h323-gw-id=router."
00:37:11: RADIUS:  Vendor, Cisco       [26]  56  
00:37:11: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=69EAABEB BF1A11D3 8014E483 
89ADC43B"
00:37:11: RADIUS:  Vendor, Cisco       [26]  31  
00:37:11: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
00:37:11: RADIUS:  Vendor, Cisco       [26]  32  
00:37:11: RADIUS:   h323-call-type     [27]  26  "h323-call-type=Telephony"
00:37:11: RADIUS:  Vendor, Cisco       [26]  65  
00:37:11: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=69EAABEB BF1A11D3 
8014E483 89ADC43B"
00:37:11: RADIUS:  Vendor, Cisco       [26]  30  
00:37:11: RADIUS:   Cisco AVpair       [1]   24  "subscriber=RegularLine"
00:37:11: RADIUS:  User-Name           [1]   12  "4081234567"
00:37:11: RADIUS:  Acct-Status-Type    [40]  6   Start                     [1]
00:37:11: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:37:11: RADIUS:  Vendor, Cisco       [26]  19  
00:37:11: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
00:37:11: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:37:11: RADIUS:  Called-Station-Id   [30]  7   "12345"
00:37:11: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:37:11: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:37:11: RADIUS:  Delay-Time          [41]  6   0                         
00:37:11: ISDN Se0:23: TX ->  CALL_PROC pd = 8  callref = 0x809E
00:37:11:         Channel ID i = 0xA98397
00:37:11: ISDN Se0:23: TX ->  CONNECT pd = 8  callref = 0x809E
00:37:11: ISDN Se0:23: RX <-  CONNECT_ACK pd = 8  callref = 0x009E
00:37:11: ISDN Se0:23: CALL_PROGRESS: CALL_CONNECTED call id 0x65, bchan 22, dsl 0
00:37:11: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4081234567 
00:37:16: RADIUS: Retransmit id 8
00:37:16: RADIUS: acct-delay-time for 4021D9EC (at 4021DB84) now 5
00:37:17: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4081234567 
00:37:21: RADIUS: Retransmit id 1
00:37:21: RADIUS: acct-delay-time for 4021D9EC (at 4021DB84) now 10
00:37:26: RADIUS: Retransmit id 2
00:37:26: RADIUS: acct-delay-time for 4021D9EC (at 4021DB84) now 15
00:37:31: RADIUS: Tried all servers.
00:37:31: RADIUS: No valid server found. Trying any viable server
00:37:31: RADIUS: Tried all servers.
00:37:31: RADIUS: No response for id 3
00:37:31: RADIUS/DECODE: parse response no app start; FAIL
00:37:31: RADIUS/DECODE: parse response; FAIL
00:37:35: RADIUS(00000010): Encoding nas-port...Only port-type avlbl
00:37:35: RADIUS/ENCODE(00000010): acct_session_id: 16
00:37:35: RADIUS(00000010): sending
00:37:35: RADIUS: Send to unknown id 5 10.6.20.70:1720, Access-Request, len 199
00:37:35: RADIUS:  authenticator 4B 6E 67 9F D4 1E 73 37 - 45 D3 CD 7C 70 FD C7 12
00:37:35: RADIUS:  User-Name           [1]   8   "777777"
00:37:35: RADIUS:  User-Password       [2]   18  *
00:37:35: RADIUS:  Vendor, Cisco       [26]  56  
00:37:35: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=61A46F2C 00000003 62E66E40 
634A0A64"
00:37:35: RADIUS:  Vendor, Cisco       [26]  36  
00:37:35: RADIUS:   Cisco AVpair       [1]   30  "h323-ivr-out=transactionID:5"
00:37:35: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:37:35: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:37:35: RADIUS:  Vendor, Cisco       [26]  19  
00:37:35: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
00:37:35: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:37:35: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:37:35: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:37:40: RADIUS: Retransmit id 5
00:37:45: RADIUS: Retransmit id 5
00:37:50: RADIUS: Retransmit id 5
00:37:55: RADIUS: Tried all servers.
00:37:55: RADIUS: No valid server found. Trying any viable server
00:37:55: RADIUS: Tried all servers.
00:37:55: RADIUS: No response for id 5
00:37:55: RADIUS/DECODE: parse response no app start; FAIL
00:37:55: RADIUS/DECODE: parse response; FAIL
00:38:00: %ISDN-6-DISCONNECT: Interface Serial0:22  disconnected from 4081234567 , call 
lasted 48 seconds
00:38:00: ISDN Se0:23: TX ->  DISCONNECT pd = 8  callref = 0x809E
00:38:00:         Cause i = 0x8090 - Normal call clearing
00:38:00: RADIUS/ENCODE(00000010): Unsupported AAA attribute timezone
00:38:00: RADIUS(00000010): Encoding nas-port...Only port-type avlbl
00:38:00: RADIUS(00000010): sending
00:38:00: RADIUS: Send to unknown id 9 10.6.20.70:1721, Accounting-Request, len 660
00:38:00: RADIUS:  authenticator C5 79 B7 D3 92 75 37 D0 - E7 5C 5B 84 99 6E 97 17
00:38:00: RADIUS:  Acct-Session-Id     [44]  10  "00000010"
00:38:00: RADIUS:  Vendor, Cisco       [26]  56  
00:38:00: RADIUS:   h323-setup-time    [25]  50  "h323-setup-time=*00:37:09.095 UTC Sat 
Jan 1 2000"
00:38:00: RADIUS:  Vendor, Cisco       [26]  34  
00:38:00: RADIUS:   h323-gw-id         [33]  28  "h323-gw-id=router."
00:38:00: RADIUS:  Vendor, Cisco       [26]  56  
00:38:00: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=69EAABEB BF1A11D3 8014E483 
89ADC43B"
00:38:00: RADIUS:  Vendor, Cisco       [26]  31  
00:38:00: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
00:38:00: RADIUS:  Vendor, Cisco       [26]  32  
00:38:00: RADIUS:   h323-call-type     [27]  26  "h323-call-type=Telephony"
00:38:00: RADIUS:  Vendor, Cisco       [26]  65  
00:38:00: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=69EAABEB BF1A11D3 
8014E483 89ADC43B"
00:38:00: RADIUS:  Vendor, Cisco       [26]  30  
00:38:00: RADIUS:   Cisco AVpair       [1]   24  "subscriber=RegularLine"
00:38:00: RADIUS:  Acct-Input-Octets   [42]  6   0                         
00:38:00: RADIUS:  Acct-Output-Octets  [43]  6   112160                    
00:38:00: RADIUS:  Acct-Input-Packets  [47]  6   0                         
00:38:00: RADIUS:  Acct-Output-Packets [48]  6   701                       
00:38:00: RADIUS:  Acct-Session-Time   [46]  6   49                        
00:38:00: RADIUS:  Vendor, Cisco       [26]  58  
00:38:00: RADIUS:   h323-connect-time  [28]  52  "h323-connect-time=*00:37:09.109 UTC Sat 
Jan 1 2000"
00:38:00: RADIUS:  Vendor, Cisco       [26]  61  
00:38:00: RADIUS:   h323-disconnect-tim[29]  55  "h323-disconnect-time=*00:37:57.739 UTC 
Sat Jan 1 2000"
00:38:00: RADIUS:  Vendor, Cisco       [26]  34  
00:38:00: RADIUS:   h323-disconnect-cau[30]  28  "h323-disconnect-cause=10  "
00:38:00: RADIUS:  Vendor, Cisco       [26]  35  
00:38:00: RADIUS:   Cisco AVpair       [1]   29  "h323-ivr-out=Tariff:Unknown"
00:38:00: RADIUS:  Vendor, Cisco       [26]  28  
00:38:00: RADIUS:   h323-voice-quality [31]  22  "h323-voice-quality=0"
00:38:00: RADIUS:  User-Name           [1]   12  "4081234567"
00:38:00: RADIUS:  Acct-Status-Type    [40]  6   Stop                      [2]
00:38:00: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
00:38:00: RADIUS:  Vendor, Cisco       [26]  19  
00:38:00: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
00:38:00: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
00:38:00: RADIUS:  Called-Station-Id   [30]  7   "12345"
00:38:00: RADIUS:  Service-Type        [6]   6   Login                     [1]
00:38:00: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
00:38:00: RADIUS:  Delay-Time          [41]  6   0                         
00:38:00: ISDN Se0:23: RX <-  RELEASE pd = 8  callref = 0x009E
00:38:00: ISDN Se0:23: TX ->  RELEASE_COMP pd = 8  callref = 0x809E
00:38:05: RADIUS: Retransmit id 9
00:38:05: RADIUS: acct-delay-time for 4021D9EC (at 4021DC7A) now 5
00:38:10: RADIUS: Retransmit id 4
00:38:10: RADIUS: acct-delay-time for 4021D9EC (at 4021DC7A) now 10
00:38:15: RADIUS: Retransmit id 5
00:38:15: RADIUS: acct-delay-time for 4021D9EC (at 4021DC7A) now 15
00:38:20: RADIUS: Tried all servers.
00:38:20: RADIUS: No valid server found. Trying any viable server
00:38:20: RADIUS: Tried all servers.
00:38:20: RADIUS: No response for id 6
00:38:20: RADIUS/DECODE: parse response no app start; FAIL
00:38:20: RADIUS/DECODE: parse response; FAIL

debug radius accounting

In the output below, cdr1 includes h323-call-origin but does not include VSA h323-gw-id. cdr2 includes h323-gw-id but does not include h323-call-origin.


show call accounting-template voice cdr1
CDR template cdr1 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
    The last load was successful.

    attr:  h323-call-origin (56)

 Totally 1 attrs defined.


show call accounting-template voice cdr2
CDR template cdr2 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr2.cdr
    The last load was successful.

    attr:  h323-gw-id (65)

 Totally 1 attrs defined.

!The output below is from a call that uses cdr1.cdr which allows only h323-call-origin. 

debug radius accounting
Radius protocol debugging is on
Radius packet hex dump debugging is off
Radius packet protocol (authentication) debugging is off
Radius packet protocol (accounting) debugging is on
02:41:32: RADIUS/ENCODE(00000023): Unsupported AAA attribute timezone
02:41:32: RADIUS(00000023): Encoding nas-port...Only port-type avlbl
02:41:32: RADIUS(00000023): sending
02:41:32: RADIUS: Send to unknown id 26 10.6.20.70:1699, Accounting-Request, len 
262
02:41:32: RADIUS:  authenticator 84 6E A0 C0 0F 27 79 03 - 59 96 FC 6C F4 17 05 
4D
02:41:32: RADIUS:  Acct-Session-Id     [44]  10  "00000023"
02:41:32: RADIUS:  Vendor, Cisco       [26]  56  
02:41:32: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=C925CD59 BF2B11D3 
8038E483 89ADC43B"
02:41:32: RADIUS:  Vendor, Cisco       [26]  31  
02:41:32: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
02:41:32: RADIUS:  Vendor, Cisco       [26]  65  
02:41:32: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=C925CD59 
BF2B11D3 8038E483 89ADC43B"
02:41:32: RADIUS:  User-Name           [1]   12  "4081234567"
02:41:32: RADIUS:  Acct-Status-Type    [40]  6   Start                     [1]
02:41:32: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
02:41:32: RADIUS:  Vendor, Cisco       [26]  19  
02:41:32: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
02:41:32: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
02:41:32: RADIUS:  Called-Station-Id   [30]  7   "12345"
02:41:32: RADIUS:  Service-Type        [6]   6   Login                     [1]
02:41:32: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
02:41:32: RADIUS:  Delay-Time          [41]  6   0                         
02:41:32: RADIUS: Received from id 26 10.6.20.70:1699, Accounting-response, len 
20
02:41:32: RADIUS:  authenticator 90 AD C8 09 60 D7 26 01 - DE E0 BC DC C1 F8 CA 
2F
02:41:32: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4081234567 
02:41:38: %ISDN-6-CONNECT: Interface Serial0:22 is now connected to 4081234567 
02:41:52: RADIUS(00000023): Encoding nas-port...Only port-type avlbl
02:41:59: %ISDN-6-DISCONNECT: Interface Serial0:22  disconnected from 4081234567 
, call lasted 26 seconds
02:41:59: RADIUS/ENCODE(00000023): Unsupported AAA attribute timezone
02:41:59: RADIUS(00000023): Encoding nas-port...Only port-type avlbl
02:41:59: RADIUS(00000023): sending
02:41:59: RADIUS: Send to unknown id 27 10.6.20.70:1699, Accounting-Request, len 
327
02:41:59: RADIUS:  authenticator 13 B7 10 EE 1C 55 7A D2 - 0F 4A A5 2F 1F 85 0E 
3A
02:41:59: RADIUS:  Acct-Session-Id     [44]  10  "00000023"
02:41:59: RADIUS:  Vendor, Cisco       [26]  56  
02:41:59: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=C925CD59 BF2B11D3 
8038E483 89ADC43B"
02:41:59: RADIUS:  Vendor, Cisco       [26]  31  
02:41:59: RADIUS:   h323-call-origin   [26]  25  "h323-call-origin=answer"
02:41:59: RADIUS:  Vendor, Cisco       [26]  65  
02:41:59: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=C925CD59 
BF2B11D3 8038E483 89ADC43B"
02:41:59: RADIUS:  Acct-Input-Octets   [42]  6   0                         
02:41:59: RADIUS:  Acct-Output-Octets  [43]  6   121600                    
02:41:59: RADIUS:  Acct-Input-Packets  [47]  6   0                         
02:41:59: RADIUS:  Acct-Output-Packets [48]  6   760                       
02:41:59: RADIUS:  Acct-Session-Time   [46]  6   27                        
02:41:59: RADIUS:  Vendor, Cisco       [26]  35  
02:41:59: RADIUS:   Cisco AVpair       [1]   29  "h323-ivr-out=Tariff:Unknown"
02:41:59: RADIUS:  User-Name           [1]   12  "4081234567"
02:41:59: RADIUS:  Acct-Status-Type    [40]  6   Stop                      [2]
02:41:59: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
02:41:59: RADIUS:  Vendor, Cisco       [26]  19  
02:41:59: RADIUS:   cisco-nas-port     [2]   13  "ISDN 0:D:23"
02:41:59: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
02:41:59: RADIUS:  Called-Station-Id   [30]  7   "12345"
02:41:59: RADIUS:  Service-Type        [6]   6   Login                     [1]
02:41:59: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
02:41:59: RADIUS:  Delay-Time          [41]  6   0                         
02:41:59: RADIUS: Received from id 27 10.6.20.70:1699, Accounting-response, len 
20
02:41:59: RADIUS:  authenticator 7F B2 88 3A 4A 96 05 C6 - D5 81 19 D8 25 3B 4D CB 

!The output below is from the show debug command. 
show debug
Radius protocol debugging is on
Radius packet protocol (accounting) debugging is on 

!The output below is from a call that uses cdr2 which allows h323-gw-id, but does not 
allow h323-call-origin. 

ADIUS/ENCODE(00000025): Unsupported AAA attribute timezone
02:51:35: RADIUS(00000025): Encoding nas-port...Only port-type avlbl
02:51:35: RADIUS(00000025): sending
02:51:35: RADIUS: Send to unknown id 28 10.6.20.70:1709, Accounting-Request, len 
265
02:51:35: RADIUS:  authenticator 15 F0 7E AB 75 07 10 70 - 5E 3C 54 78 09 18 83 
E5
02:51:35: RADIUS:  Acct-Session-Id     [44]  10  "00000025"
02:51:35: RADIUS:  Vendor, Cisco       [26]  34  
02:51:35: RADIUS:   h323-gw-id         [33]  28  "h323-gw-id=router."
02:51:35: RADIUS:  Vendor, Cisco       [26]  56  
02:51:35: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=306F55DD BF2D11D3 
803CE483 89ADC43B"
02:51:35: RADIUS:  Vendor, Cisco       [26]  65  
02:51:35: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=306F55DD 
BF2D11D3 803CE483 89ADC43B"
02:51:35: RADIUS:  User-Name           [1]   12  "4081234567"
02:51:35: RADIUS:  Acct-Status-Type    [40]  6   Start                     [1]
02:51:35: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
02:51:35: RADIUS:  Vendor, Cisco       [26]  19  
02:51:35: RADIUS:   cisco-nas-port     [2]   13  "ISDN 1:D:23"
02:51:35: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
02:51:35: RADIUS:  Called-Station-Id   [30]  7   "12346"
02:51:35: RADIUS:  Service-Type        [6]   6   Login                     [1]
02:51:35: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
02:51:35: RADIUS:  Delay-Time          [41]  6   0                         
02:51:35: %ISDN-6-CONNECT: Interface Serial1:22 is now connected to 4081234567 
02:51:35: RADIUS: Received from id 28 10.6.20.70:1709, Accounting-response, len 
20
02:51:35: RADIUS:  authenticator D3 D8 59 42 2B 48 96 8D - 5E 2E D8 61 9A 9D 0D 
5F
02:51:41: %ISDN-6-CONNECT: Interface Serial1:22 is now connected to 4081234567 
02:51:43: %ISDN-6-DISCONNECT: Interface Serial1:22  disconnected from 4081234567 
, call lasted 8 seconds
02:51:43: RADIUS/ENCODE(00000025): Unsupported AAA attribute timezone
02:51:43: RADIUS(00000025): Encoding nas-port...Only port-type avlbl
02:51:43: RADIUS(00000025): sending
02:51:43: RADIUS: Send to unknown id 29 10.6.20.70:1709, Accounting-Request, len 
330
02:51:43: RADIUS:  authenticator 55 35 AB CC 20 64 69 4B - 3F EE 79 04 11 E8 AE 
4F
02:51:43: RADIUS:  Acct-Session-Id     [44]  10  "00000025"
02:51:43: RADIUS:  Vendor, Cisco       [26]  34  
02:51:43: RADIUS:   h323-gw-id         [33]  28  "h323-gw-id=router."
02:51:43: RADIUS:  Vendor, Cisco       [26]  56  
02:51:43: RADIUS:   Conf-Id            [24]  50  "h323-conf-id=306F55DD BF2D11D3 
803CE483 89ADC43B"
02:51:43: RADIUS:  Vendor, Cisco       [26]  65  
02:51:43: RADIUS:   Cisco AVpair       [1]   59  "h323-incoming-conf-id=306F55DD 
BF2D11D3 803CE483 89ADC43B"
02:51:43: RADIUS:  Acct-Input-Octets   [42]  6   0                         
02:51:43: RADIUS:  Acct-Output-Octets  [43]  6   50240                     
02:51:43: RADIUS:  Acct-Input-Packets  [47]  6   0                         
02:51:43: RADIUS:  Acct-Output-Packets [48]  6   314                       
02:51:43: RADIUS:  Acct-Session-Time   [46]  6   8                         
02:51:43: RADIUS:  Vendor, Cisco       [26]  35  
02:51:43: RADIUS:   Cisco AVpair       [1]   29  "h323-ivr-out=Tariff:Unknown"
02:51:43: RADIUS:  User-Name           [1]   12  "4081234567"
02:51:43: RADIUS:  Acct-Status-Type    [40]  6   Stop                      [2]
02:51:43: RADIUS:  NAS-Port-Type       [61]  6   Async                     [0]
02:51:43: RADIUS:  Vendor, Cisco       [26]  19  
02:51:43: RADIUS:   cisco-nas-port     [2]   13  "ISDN 1:D:23"
02:51:43: RADIUS:  Calling-Station-Id  [31]  12  "4081234567"
02:51:43: RADIUS:  Called-Station-Id   [30]  7   "12346"
02:51:43: RADIUS:  Service-Type        [6]   6   Login                     [1]
02:51:43: RADIUS:  NAS-IP-Address      [4]   6   10.5.20.100                
02:51:43: RADIUS:  Delay-Time          [41]  6   0                         
02:51:43: RADIUS: Received from id 29 10.6.20.70:1709, Accounting-response, len 
20
02:51:43: RADIUS:  authenticator 45 31 ED 45 F4 06 ED 54 - 5E 6F 83 64 4D 2D 34 
90

Using show Commands for AAA Voice Troubleshooting

show call accounting voice summary

The show call accounting voice summary command shows the status of all accounting templates that are defined, loaded.


show call accounting voice summary
name         url                                    last_load  is_running
=========================================================================
cdr1         tftp://10.255.255.255/johndoe/sanjose/ success    is running
cdr2         tftp://10.255.255.255/johndoe/sanjose/ success    is running


show call accounting-template voice

The show call accounting-template voice template name command shows the VSAs that are contained in the accounting template.

show call accounting-template voice cdr1 
CDR template cdr1 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
The last load was successful.

    attr:  h323-call-origin (56)

 Totally 1 attrs defined.

show call accounting-template voice cdr2 
CDR template cdr2 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr2.cdr
    The last load was successful.

    attr:  h323-call-origin (56)

 Totally 1 attrs defined.


!The output below results from defining a template that does not exist or that cannot be 
reached. 

router(config)#$://10.255.255.255/johndoe/sanjose/cdr/cdr4000.cdr    
Reading cdr template cdr10 fail, put it on retry queue.

01:15:46: hifs ifs could not open file 

!The output below is for a template with an invalid VSA. 
show call accounting-template voice cdr1
CDR template cdr1 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
    The last load was successful.

    attr:  h323-call-origin (56)

 Totally 1 attrs defined. 

!Template cdr1.cdr is modified on the tftp server to enable an invalid VSA ( for example 
h323-call-origin) to be put into the template. 

call accounting-template voice reload cdr1
Loading johndoe/sanjose/cdr/cdr1.cdr from 10.255.255.255 (via Ethernet0): !
[OK - 88/4096 bytes]
cam: Fail to reload cdr template cdr1, unloading ...

02:27:29: hifs ifs file read succeeded. size=88, 
url=tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
02:27:29: Error: attr name invalid-vsa-h323-call-origin (0) is not valid in line 3.

sh call accounting-template voice cdr1    
CDR template cdr1 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
    Last load returned errno=8, Exec format error

    attr:  h323-call-origin (56)

 Totally 1 attrs defined.


The template has been rejected, and previous template still applied.

show call aaa attributes

The show call aaa attributes command displays the VSAs that are supported. Mandatory VSAs that are sent to the accounting server are not displayed.


show call aaa attributes
AAA ATTRIBUTE LIST:
    Name=disc-cause-ext                 Format=Enum
    Name=Acct-Status-Type               Format=Enum
    Name=acl                            Format=Ulong
    Name=addr                           Format=IP v4 Address
    .....				.....
    Name=gw-password                    Format=Binary
    Name=h323-billing-model             Format=String
    Name=h323-call-origin               Format=String
    .....				.....

!Use the show call accounting-template voice summary command to check if a template is 
loaded and running. 
!The output below shows two templates successfully loaded and running, and a template that 
failed to load.
show call accounting-template voice summary
name         url                                    last_load  is_running
=========================================================================
cdr1         tftp://10.255.255.255/johndoe/sanjose/ success    is running
cdr2         tftp://10.255.255.255/johndoe/sanjose/ success    is running
cdr10        tftp://10.255.255.255/johndoe/sanjose/ fail       is not running

!The output below shows reloading template cdr1 after modifying it. 
!Initially, the original template cdr1 is loaded as shown: 
show call accounting-template voice cdr1
CDR template cdr1 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
    The last load was successful.

    attr:  h323-call-origin (56)

 Totally 1 attrs defined.

!Additional VSAs are added to modify cdr1 on the tftp server as shown: 

call accounting 
call accounting-template voice reload cdr1
Loading johndoe/sanjose/cdr/cdr1.cdr from 10.255.255.255 (via Ethernet0): !
[OK - 1848/3072 bytes]

cam: Reload cdr template cdr1 success.
01:35:58: hifs ifs file read succeeded. size=1848, 
url=tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
show call accounting-template voice cdr1
CDR template cdr1 is running
    url: tftp://10.255.255.255/johndoe/sanjose/cdr/cdr1.cdr
    The last load was successful.
    attr:  h323-call-origin (56)
    attr:  h323-call-type (57)
    attr:  h323-connect-time (59)
    attr:  h323-disconnect-cause (63)
    attr:  h323-disconnect-time (64)
    attr:  h323-gw-id (65)
    attr:  h323-remote-address (73)
    attr:  h323-remote-id (74)
    attr:  h323-setup-time (76)
    attr:  h323-voice-quality (78)
    attr:  subscriber (79)
    attr:  in-portgrp-id (80)
    attr:  out-portgrp-id (81)
    attr:  charged-units (82)
    attr:  disconnect-text (83)
    attr:  info-type (84)
    attr:  logical-if-index (85)
    attr:  peer-address (86)
    attr:  peer-id (87)
    attr:  peer-if-index (88)
    attr:  acom-level (89)
    attr:  tx-duration (90)
    attr:  voice-tx-duration (91)
    attr:  fax-tx-duration (92)
    attr:  noise-level (94)
    attr:  codec-bytes (95)
    attr:  coder-type-rate (96)
    attr:  early-packets (97)
    attr:  late-packets (98)
    attr:  lost-packets (99)
    attr:  gapfill-with-interpolation (100)
    attr:  gapfill-with-prediction (101)
    attr:  gapfill-with-redundancy (102)
    attr:  gapfill-with-silence (103)
    attr:  lowater-playout-delay (104)
    attr:  hiwater-playout-delay (105)
    attr:  ontime-rv-playout (106)
    attr:  receive-delay (107)
    attr:  round-trip-delay (108)
    attr:  remote-udp-port (109)
    attr:  session-protocol (110)
    attr:  vad-enable (111)

 Totally 42 attrs defined.

Accounting Server Connectivity Failure and Recovery Detection

The Accounting Server Connectivity Failure and Recovery Detection feature provides the scriptable option to reject new calls entering the VoIP network and tear down all existing calls upon detecting connectivity failure to the method list that is associated with the RADIUS-based accounting server(s).

Prerequisites for Accounting Server Connectivity Failure and Recovery Detection

Restrictions for Accounting Server Connectivity Failure and Recovery Detection

Information About Accounting Server Connectivity Failure and Recovery Detection

How to Configure Accounting Server Connectivity Failure and Recovery Detection

Configuration Examples for Accounting Server Connectivity Failure and Recovery Detection

Prerequisites for Accounting Server Connectivity Failure and Recovery Detection

The following tasks are prerequisites to configuring the features:

Establish a working IP network. For more information about configuring IP, refer to the Cisco IOS IP Configuration Guide, Release 12.3.

Configure VoIP. For more information about configuring VoIP, refer to the Voice Configuration Library.

Configure a TFTP sever to perform storage and retrieval of the audio files, which are required by the Debit Card gateway or other features requiring Tool Command Language Interactive Voice Response (Tcl IVR) scripts and audio files.

Program and configure the interface between the RADIUS server and the Cisco voice gateway to operate with VSAs.

Create the accounting method list default that includes all RADIUS servers using the aaa accounting connection default start-stop group radius command in global configuration mode. This method list is required by the probe accounting records the Accounting Server Connectivity Failure and Recovery Detection feature uses to determine the state of connectivity to the method list.

Restrictions for Accounting Server Connectivity Failure and Recovery Detection

The Accounting Server Connectivity Failure and Recovery Detection feature is applicable only to the RADIUS accounting protocol. It is not applicable to any other protocols or servers, such as RADIUS access protocol, TACACS, or DIAMETER.

If both voice and dial calls need to be done on the same gateway, different accounting servers must be configured for each type of call.

Information About Accounting Server Connectivity Failure and Recovery Detection

To configure Accounting Server Connectivity Failure and Recovery Detection, you need to understand the following concept:

Global Accounting Script

Global Accounting Script

The Accounting Server Connectivity Failure and Recovery Detection feature uses a configurable, legless Global Accounting Script (GAS) to control algorithms that determine the state of connectivity to the method list that is associated with the accounting server. The Accounting Server Connectivity Failure and Recovery Detection feature has two major functional components:

Tcl legless GAS—Controls and drives the detection, recovery, and probe algorithms.

Application Tcl scripts—Performs the call treatments to incoming calls and existing calls when notified that the method list is unreachable.

The GAS is a Tcl script with configurable parameters that users can customize for their own network requirements. Users can configure one GAS for each method list, or one GAS script for multiple method lists.

Because the RADIUS accounting protocol is User Datagram Protocol (UDP)-based, it is connectionless, and there is no guaranteed connectivity with the RADIUS server. The Accounting Server Connectivity Failure and Recovery Detection feature uses the acknowledgment of accounting requests from the method list to detect connectivity.

The GAS determines the state transition of the method list and updates the AAA system with the latest method list status. If the method list is unreachable, the AAA system locates all the active calls associated with the unreachable method list and informs the application script instances of the server unreachable event. The application script applies the appropriate treatments for this new event to the existing calls. For incoming calls, the application script checks the method list status and applies the appropriate treatment. For example, the application can clear the existing calls and reject new incoming calls for this method list. When the method list becomes reachable, the application script instances are notified, and they can take the appropriate action.

How to Configure Accounting Server Connectivity Failure and Recovery Detection

This section contains procedures identified as either required or optional.

Configuring the GAS (optional)

Loading the GAS (required)

Starting the GAS (optional)

Starting the GAS in Global Configuration Mode (optional)

Verifying the GAS (optional)

Troubleshooting Accounting Server Connectivity Failure and Recovery Detection (optional)

Configuring the GAS

Perform this task to configure the GAS.

How the GAS Application Verifies Configuration Parameters

The GAS application reads in the configured method list and uses it to identify the configuration parameters associated with that method list. Configuration parameters associated with a method list are either mandatory or optional.

If a mandatory configuration parameter does not exist, the GAS application displays the following message:

TCL GAS: >> Mandatory Parameter <parameter name from configuration avpair> does not exist

If a mandatory configuration parameter has an invalid type or value, the GAS application displays the following message:

TCL GAS:  >> Mandatory Parameter <exact parameter from configuration avpair> invalid value 

At least one method list must be configured with the GAS application.

If the GAS application fails to read any of the mandatory configuration parameters, it fails and display this message:

TCL GAS:>>>> GasManager.Start  Exit Failure <<<<

SUMMARY STEPS

1. Download the GAS file.

2. Configure the GAS application and mandatory parameters.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Download the GAS file.

Download the GAS file at Technical Support Software Download for Cisco Tool Command Language Software at http://www.cisco.com/cgi-bin/tablebuild.pl/tclware. The GAS file contains the GAS and a ReadMe file.

Step 2 

Configure the GAS application and mandatory parameters.

Refer to the ReadMe file for script-specific information about configuration parameters, including which are mandatory and which are optional.

You must configure at least the mandatory parameters before loading the GAS.

You must configure the GAS for at least one method list.

For information on the changes to the Tcl application programming interface (API) included in the Accounting Server Connectivity Failure and Recovery Detection feature, refer to the TCL IVR Version 2.0 Programmer's Guide.

Note The GAS should be configured only by changing the value of its configuration parameters. The Technical Assistance Center (TAC) cannot support this feature, or the system on which it is loaded, if any changes are made to the script itself. Any changes to the GAS are supported by the Cisco Developer Support Program only, which requires a signed Developer Support Agreement. For more information, see the "Obtaining Technical Assistance" section on page xxvi.


Loading the GAS

Perform this task to load the GAS Tcl script.

Prerequisites

You must configure any script-specific parameters before loading the GAS.

SUMMARY STEPS

1. enable

2. call application voice load application-name

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

call application voice load application-name

Example:

Router# call application voice load GAS

Reloads the selected Tcl script from the URL.


Starting the GAS

You can start the GAS in privileged EXEC mode or global configuration mode. If it is started in privileged EXEC mode, it must be restarted every time the router is rebooted. If it is started in global configuration mode, it is saved in NVRAM and is started automatically when the router is rebooted.

Choose one of the following optional tasks to start the GAS.

Starting the GAS in Privileged EXEC Mode (optional)

Starting the GAS in Global Configuration Mode (optional)

Starting the GAS in Privileged EXEC Mode

Perform this task to start the GAS in privileged EXEC mode:

SUMMARY STEPS

1. enable

2. call application session start instance-name application-name

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

call application session start instance-name application-name

Example:

Router# call application session start session_1 GAS

Starts an instance of an application.


Starting the GAS in Global Configuration Mode

Perform this task to start the GAS in global configuration mode:

SUMMARY STEPS

1. enable

2. configure terminal

3. call application session start instance-name application-name

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

call application session start instance-name application-name

Example:

Router(config)# call application session start session_1 GAS

Starts a new instance (session) of a Tcl IVR 2.0 application.


Verifying the GAS

Perform this task to verify that the GAS has been configured and is working correctly.

SUMMARY STEPS

1. enable

2. show running-config

3. show voice accounting method

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2 

show running-config

Example:

Router# show running-config

(Optional) Displays the contents of the currently running configuration file.

Use the show running-config command to verify that the GAS parameters have the correct values.

Step 3 

show voice accounting method [method-list-name]

Example:

Router# show voice accounting method

(Optional) Displays connectivity status information for a specified accounting method list or all the accounting method lists.

Use the method-list-name argument to specify a single method list, or omit this argument to display information for all method lists.


Troubleshooting Accounting Server Connectivity Failure and Recovery Detection

The Accounting Server Connectivity Failure and Recovery Detection feature uses a privileged EXEC mode command to enable diagnostic output concerning various events relating to gateway accounting Application Subscribe/Notify Layer (ASNL) to be displayed on a console. The debug voice aaa asnl command is intended only for troubleshooting purposes, because the volume of output generated by the software can result in severe performance degradation on the router.

The following procedure minimizes the load on the router created by the debug voice aaa asnl commands, because the console port is no longer generating character-by-character processor interrupts. If you cannot connect to a console directly, you can run this procedure via a terminal server. If you must break the Telnet connection, however, you may not be able to reconnect because the router may be unable to respond due to the processor load of generating the debug voice aaa asnl output.

Perform the following task to minimize the impact of using the debug voice aaa asnl command.

SUMMARY STEPS

1. Attach a console directly to a router running Cisco IOS Release 12.3(8)T or a later release.

2. enable

3. configure terminal

4. no logging console

5. Use Telnet to access a router port and repeat Steps 2 and 3.

6. terminal monitor

7. end

8. debug voice aaa asnl

9. configure terminal

10. no terminal monitor

11. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Attach a console directly to a router running Cisco IOS Release 12.2(8)T or a later release.

Step 2 

enable

Example:

Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 3 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 4 

no logging console

Example:

Router(config)# no logging console

Disables all logging to the console terminal.

To reenable logging to the console, use the logging console command in global configuration mode.

Step 5 

Use Telnet to access a router port and repeat Steps 2 and 3, then continue with step 6.

Enters global configuration mode in a recursive Telnet session, which allows the output to be redirected away from the console port.

Step 6 

terminal monitor

Example:

Router(config)# terminal monitor

Enables logging output on the virtual terminal.

Step 7 

end

Example:

Router(config)# end

Exits to privileged EXEC mode.

Step 8 

debug voice aaa asnl

Example:

Router# debug voice aaa asnl

Displays debugging messages for gateway AAA ASNL.

Enter the no debug voice aaa asnl command when you are finished.

Step 9 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 10 

no terminal monitor

Example:

Router(config)# no terminal monitor

Disables logging on the virtual terminal.

Step 11 

end

Example:

Router(config)# end

Exits to privileged EXEC mode.

Configuration Examples for Accounting Server Connectivity Failure and Recovery Detection

This section provides configuration examples to match the identified configuration tasks in the previous section:

Configuring the GAS: Example

Loading the GAS: Example

Starting the GAS: Example

Verifying the GAS: Example

Configuring the GAS: Example

Figure 46 shows the topology used in this example.

Figure 46 Example Topology

In this example, the GAS is configured for two method lists: ml1 and ml2.

call application voice GAS tftp://192.255.254.253/app_GAS.2.0.0.0.tcl
call application voice GAS method-list ml1;ml2
call application voice GAS gas-active-timer-ml1 30
call application voice GAS detect-failure-responses-ml1 2
call application voice GAS recovery-responses-ml1 2
call application voice GAS probe-retry-timer-ml1 5
call application voice GAS report-accounting-failed-ml1 false
call application voice GAS probe-user-name-ml1 johndoe
call application voice GAS acct-inactivity-period-ml1 120
call application voice GAS send-accounting-on-ml1 true
call application voice GAS use-gas-debugs-ml1 true

call application voice GAS gas-active-timer-ml2 30
call application voice GAS detect-failure-responses-ml2 2
call application voice GAS recovery-responses-ml2 5
call application voice GAS probe-retry-timer-ml2 10
call application voice GAS report-accounting-failed-ml2 true
call application voice GAS acct-inactivity-period-ml2 90
call application voice GAS send-accounting-on-ml2 false
call application voice GAS use-gas-debugs-ml2 false

The ml1 method list is configured with the following parameter values:

Parameter Value
Description

gas-active-timer = 30

Generate a syslog message indicating that the GAS application is active every 30 minutes.

detect-failure-responses-ml1 = 2

After receiving two consecutive failed responses, the method list is declared unreachable.

recovery-responses-ml1 = 2

After receiving two consecutive success responses, the method list is declared reachable again.

probe-retry-timer-ml1 = 5

When the method list is in an unreachable state, send probe accounting records every 5 seconds.

report-accounting-failed-ml1 = false

The application script should not be notified when accounting fails before the method list is marked as unreachable.

probe-user-name-ml1 = johndoe

Use johndoe as the user name field in the probe accounting records.

acct-inactivity-period-ml1 = 120

When the method list is in a reachable state and 120 seconds of inactivity have passed after the last accounting record was sent to the method list, a probe accounting record is sent to determine connectivity to the method list.

send-accounting-on-ml1 = true

A message is sent when the method list transitions from unreachable to reachable. This behavior should be synchronized with the calling application script. If the application script tears down the existing calls when it is notified that the method list status transitioned from reachable to unreachable, this parameter should be set to true; otherwise, it should be set to false.

use-gas-debugs-ml1 = true

Debug output is controlled by the debug voip ivr commands and displayed to the terminal. If the use-gas-debugs parameter was set to false, only the value of the use-gas-debugs parameters for the ml1 and ml2 method lists would be displayed. The default value is true.


Loading the GAS: Example

In the following example, the GAS named GAS is loaded:

enable
call application voice load GAS

Starting the GAS: Example

In the following example, the GAS named GAS is started in instance session_1:

enable
call application session start session_1 GAS

Verifying the GAS: Example

In the following examples, the output is displayed for each command in the task.

Sample Output from the show running-config Command

In the following example, method lists ml1 and ml2 are defined, and the GAS named GAS is configured:

Router# show running-config

Current configuration :4419 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname as5300-2
!
logging buffered warnings
enable password cisco
!
resource-pool disable
clock timezone gmt 15 40
!
aaa new-model
!
aaa group server radius ml1
 server 10.8.159.105 auth-port 1645 acct-port 1646
aaa group server radius ml2
 server 10.9.57.101 auth-port 1715 acct-port 1716
!
aaa accounting update newinfo
aaa accounting connection default start-stop group radius
aaa accounting connection h323 start-stop group radius
aaa accounting connection ml1 start-stop group ml1
aaa accounting connection ml2 start-stop group ml2

aaa session-id common
ip subnet-zero
!
isdn switch-type primary-5ess
!
mta receive maximum-recipients 0
no memory check-interval
!
!
!
controller T1 0
 framing esf
 clock source line primary
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1
 framing esf
 clock source line secondary 1
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 2
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 3
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
gw-accounting aaa
 method ml1
!
interface Loopback1
 no ip address
 no ip route-cache
 no ip mroute-cache
!
interface Ethernet0
 ip address 10.8.156.2 255.255.0.0
!
!
interface Serial0:23
 no ip address
 dialer-group 1
 isdn switch-type primary-5ess
 isdn incoming-voice modem
 fair-queue 64 256 0
 no cdp enable
!
interface Serial1:23
 no ip address
 isdn switch-type primary-5ess
 no cdp enable
!
interface Serial2:23
 no ip address
 isdn switch-type primary-5ess
 no cdp enable
!
interface Serial3:23
 no ip address
 isdn switch-type primary-5ess
 no cdp enable
!
interface FastEthernet0
 ip address 172.19.141.84 255.255.0.0
 ip directed-broadcast
 no ip route-cache
 no ip mroute-cache
 duplex auto
 speed auto
!
ip default-gateway 10.8.0.1
ip classless
ip route 10.7.0.0 255.255.0.0 10.8.0.1
ip route 10.8.0.1 255.255.255.255 Ethernet0
ip route 10.9.0.0 255.255.0.0 10.8.0.1
ip route 192.255.254.253 255.255.255.255 10.8.0.1
ip route 192.255.254.254 255.255.255.255 10.8.0.1
no ip http server
!
access-list 101 permit ip any any
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
!
radius-server host 10.8.159.105 auth-port 1645 acct-port 1646
radius-server host 10.9.57.101 auth-port 1715 acct-port 1716
radius-server key cisco
radius-server authorization permit missing Service-Type
radius-server vsa send accounting
radius-server vsa send authentication
call rsvp-sync
!
call application voice GAS tftp://192.255.254.253/app_GAS.2.0.0.0.tcl
call application voice GAS method-list ml1;ml2
call application voice GAS gas-active-timer-ml1 5
call application voice GAS detect-failure-responses-ml1 2
call application voice GAS recovery-responses-ml1 2
call application voice GAS probe-retry-timer-ml1 5
call application voice GAS report-accounting-failed-ml1 false
call application voice GAS probe-user-name-ml1 johndoe
call application voice GAS acct-inactivity-period-ml1 120
call application voice GAS send-accounting-on-ml1 true
call application voice GAS use-gas-debugs-ml1 true
!
call application voice GAS gas-active-timer-ml2 5
call application voice GAS detect-failure-responses-ml2 2
call application voice GAS recovery-responses-ml2 5
call application voice GAS probe-retry-timer-ml2 10
call application voice GAS report-accounting-failed-ml2 true
call application voice GAS acct-inactivity-period-ml2 90
call application voice GAS send-accounting-on-ml2 false
call application voice GAS use-gas-debugs-ml2 false
!
call application voice calling_app tftp://192.255.254.253/app_session_rw.tcl
!
call application session start G1 GAS
!
voice-port 0:D
!
voice-port 1:D
!
voice-port 2:D
!
voice-port 3:D
!
!
mgcp profile default
!
dial-peer cor custom
!
!
dial-peer voice 1 pots
 application calling_app
 incoming called-number 25170
 port 0:D
!
dial-peer voice 1800877 voip
 destination-pattern 1800877....
 session target ipv4:10.8.156.3
!
alias exec osperr debug voip sett err
alias exec h225 debug cch323 h225
alias exec h245 debyg cch323 h245
alias exec ivr debyg voip ivr
alias exec ccapi debub voip ccapi in
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0
 password lab
line vty 1 4
!
end

Sample Output from the show voice accounting method Command

The following example displays the status history for the ml1 method list:

Router# show voice accounting method

Accounting Method List [ml1]
====================== 
Current Status:
---------------
unreachable                [21:52:39 gmt Dec 4 2002]
last record sent time      [23:14:59 gmt Dec 4 2002]
total probe sent out       [84]

Status History:
---------------
(2) unreachable            [21:52:39 gmt Dec 4 2002]
(1) reachable              [21:46:19 gmt Dec 4 2002]
                 SUCCESS                        FAILURE
Record  [Received   | Notified ] [Received   |  Notified  | Reported ]
Type    [from server| to client] [from server|  to client | to call  ]
------  [-----------|----------] [-----------|------------|----------]
START   [     0     |     0    ] [     0     |      0     |     0    ]
UPDATE  [     0     |     0    ] [     0     |      0     |     0    ]
STOP    [     0     |     0    ] [     84    |      84    |     0    ]
ACCT_ON [     0     |     0    ] [     0     |      0     |     0    ]
------  [-----------|----------] [-----------|------------|----------]
TOTAL   [     0     |     0    ] [     84    |      84    |     0    ]

Troubleshooting Enhanced Billing Support for SIP Gateways

To troubleshoot the Enhanced Billing Support for SIP Gateways feature, perform the following steps:

Make sure that you can make a voice call.

Use the debug ccsip all command to enable all SIP debugging capabilities, or use one of the following SIP debug commands:

debug ccsip calls

debug ccsip error

debug ccsip events

debug ccsip messages

In addition, debug ccsip events and debug ccsip all include new output specific to the Enhanced Billing Support for SIP Gateways feature. The example shows how the Proxy-Authorization header is broken down into a decoded user name and password.

CCSIP SPI: SIP Call Events tracing is enabled 
21:03:21: sippmh_parse_proxy_auth: Challenge is 'Basic'. 
21:03:21: sippmh_parse_proxy_auth: Base64 user-pass string is 
'MTIzNDU2Nzg5MDEyMzQ1Njou'.
21:03:21: sip_process_proxy_auth: Decoded user-pass string is '1234567890123456:.'.
21:03:21: sip_process_proxy_auth: Username is '1234567890123456'. 
21:03:21: sip_process_proxy_auth: Pass is '.'. 
21:03:21: sipSPIAddBillingInfoToCcb: sipCallId for billing records =
10872472-173611CC-81E9C73D-F836C2B6@172.18.192.19421:03:21: ****Adding to UAS Request 
table 

Troubleshooting Settlement

The following section is provided to assist in determining if your OSP network is set up correctly. The problems listed have been reported as the most common errors made when configuring settlement in a network. Each section describes a problem and a solution.

Settlement Database Not Set Up Properly

Problem

Calls are routed through a settlement server, but the originating gateway gets no response or a negative response.

Solution

Check with the settlement provider to make sure that the router is properly registered with that provider. Router registration with settlement provider is normally done outside of OSP.

Tcl IVR Script Not Called

Problem

Tcl IVR script is not used on the originating gateway or terminating gateway.

Solution

Configure a Tcl IVR script for the dial peer using the application application name command.


Note Tcl/IVR scripts are required for settlement, and classic IVR 1.0 does not support settlement.


Use the show call application voice summary to list all the available scripts on the router.

Default is classic SESSION application, which cannot do settlement.

The fax_hop_on.tcl script does not work with settlement.

The following example shows the available scripts on the router.

router# show call application voice summary
name                 description

session              Basic app to do DID, or supply dialtone.
fax_hop_on           Script to talk to a fax redialer
clid_authen          Authenticate with (ani, dnis)
clid_authen_collect  Authenticate with (ani, dnis), collect if that fails
clid_authen_npw      Authenticate with (ani, NULL)
clid_authen_col_npw  Authenticate with (ani, NULL), collect if that fails
clid_col_npw_3       Authenticate with (ani, NULL), and 3 tries collecting
clid_col_npw_npw     Authenticate with (ani, NULL) and 3 tries without pw
SESSION              Default system session application

No Destination Pattern Set

Problem

The originating gateway inbound POTS dial peer has no destination pattern set.

Solution

Because some PBX devices do not pass along the calling number in the setup message, the router uses the destination-pattern number or answer-address as an alternative, and a calling number is a required field for settlement.

No Session Target Settlement Set on Originating Gateway

Problem

The originating gateway outbound VoIP dial peer has no session target settlement.

The router could make successful calls, but not through a settlement server. The session target specification dictates how the router resolves the terminating gateway address for a particular called number.

Solution

Configure the session target settlement provider-number command.

No VoIP Inbound Dial Peer on Terminating Gateway

Problem

The terminating gateway has no VoIP inbound dial peer. Because the settlement token in the incoming setup message from the originating gateway cannot be validate, the terminating gateway rejects the call.

Solution

Create an inbound dial peer with the session target settlement command.

No Application Attribute on Terminating Gateway

Problem

The terminating gateway has an inbound dial peer configured, but with no application command. The default session application (SESSION) processes the call, but it does not support settlement.

Solution

The default session application (SESSION) does not support the settlement feature. Therefore, you must configure the application command in the inbound dial peer.

Terminating Gateway Not Synchronized with Settlement Server

Problem

The terminating gateway clock is not synchronized with the settlement server. The terminating gateway rejects the call because it is too soon or too late to use the settlement token in the incoming setup message.

Solution

Use the ntp or clock set command to synchronize the clocks between the terminating gateway and the settlement server.

Settlement Provider Not Running

Problem

The settlement provider on the originating gateway or terminating gateway is not running. No settlement transaction processing is allowed unless the provider is running.

Solution

Enable settlement using the no shutdown command in settlement configuration mode. Use the show settlement command to verify the provider status.

Router and Server Not Using SSL to Communicate

Problem

The router cannot use SSL to communicate with the server because the server URL should be "https," not "http."

Solution

Configure a secured URL using "https."

Problem

The router cannot use SSL to communicate with the server because the certificates of the server or router were not properly obtained.

Solution

Check the certificate enrollment process for both the server and the router.

Multiple Dial Peers Have Random Order

Problem

The originating gateway has multiple dial peers for the same called number, and settlement is never used. The order for rotary dial peers is random unless a dial peer preference is specified. The dial peer with lower preference is chosen first.

Solution

Define dial peer preference by using the preference command.

H.323 Setup Connection Timeout

Problem

The originating gateway cannot successfully set up a call with the first terminating gateway that is returned from the OSP server. The problem occurs when a gateway attempts to set up the call with the terminating gateways in the order they are received. If for some reason the H.323 call setup is not successful, there is a 15-second timeout by default before the next terminating gateway on the list is contacted.

Solution

The H.323 call setup timeout can be tuned using the h225 timeout command.

For example:

voice class h323 1 
 h225 timeout tcp etablish <value 0 to 30 seconds> 

 dial-peer voice 919 voip 
 application session 
 destination-pattern 919555....
 voice-class codec 1 
 voice-class h323 1 
 session target settlement 

Problem Isolation

To isolate problems with settlement, perform the following tasks:

Check the originating gateway and terminating gateway configuration for dial peers, settlement providers, and certificates.

Check the network between the originating gateway, terminating gateway, and the server. Ping each device to make sure that the machines are running.

Verify that IP calls can be made successfully. If so, the problem is specific to settlement.

Turn on debug voip ivr settlement on the originating gateway to see if the Tcl IVR script initiates a settlement request to the server.

Use the debug voip settlement network command on the originating gateway to capture the HTTP requests sent to the server and the response from the server. If the originating gateway gets no response from the server, contact the settlement provider.

Turn on debug voip settlement misc to see the list of TOWs returned from the server. If this list is incorrect, contact the settlement provider.

If the terminating gateway rejects the settlement token because it is too soon or too late to use it, synchronize the terminating gateway clock with the server.