发信人: v10198(梦泪) 
整理人: firphoenix(2001-11-05 10:06:55), 站内信件
 | 
 
 
 cisco#show isdn status
 Global ISDN Switchtype = primary-net5
 ISDN Serial0:15 interface
         dsl 0, interface ISDN Switchtype = primary-net5
     Layer 1 Status:
         ACTIVE
     Layer 2 Status:
         TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
     Layer 3 Status:
         5 Active Layer 3 Call(s)
     Activated dsl 0 CCBs = 5
         CCB:callid=7D5, sapi=0, ces=0, B-chan=9, calltype=DATA
         CCB:callid=7D6, sapi=0, ces=0, B-chan=10, calltype=DATA
         CCB:callid=7DA, sapi=0, ces=0, B-chan=11, calltype=DATA
         CCB:callid=7DE, sapi=0, ces=0, B-chan=1, calltype=DATA
         CCB:callid=7DF, sapi=0, ces=0, B-chan=2, calltype=DATA
     The Free Channel Mask:  0xFFFF78FC
 ISDN Serial1:15 interface
         dsl 1, interface ISDN Switchtype = primary-net5
     Layer 1 Status:
         ACTIVE
     Layer 2 Status:
         TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
     Layer 3 Status:
         0 Active Layer 3 Call(s)
     Activated dsl 1 CCBs = 0
     The Free Channel Mask:  0xFFFF7FFF
     Total Allocated ISDN CCBs = 5
 
 debug isdn Q921
 
 Notice that E1 0 (whose D channel is Serial 0:15) has Layer 1 as ACTIVE and Layer 2 as MULTIPLE_FRAME_ESTABLISHED indicating that the 
 
 The debug isdn q921 command displays data link layer (Layer 2) access procedures that are occurring at the router on the D-channel. 
 
 Ensure you are configured to view debug messages by using the logging console or terminal monitor command.
 
 Note: In a production environment, verify that console logging is disabled by using the show logging command. If logging is enabled, the access server might intermittently stop working when the console port is overloaded with log messages. Enter the no logging console command to disable logging.
 
 Note: If debug isdn q921 is turned on and you do not receive any debug outputs, place a call or reset the controller to get debug outputs.
 
 Complete the following steps to ensure that the data link layer access procedures are occurring at the router on the D-channel:
 
 Verify that Layer 2 is stable by looking for messages in the debug output. If the line is bouncing up and down, output similar to the following will appear: 
 Mar 20 10:06:07.882: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0:15, TEI 0 changed to down
 Mar 20 10:06:09.882: %LINK-3-UPDOWN: Interface Serial0:15, changed state to down
 Mar 20 10:06:21.274: %DSX1-6-CLOCK_CHANGE: Controller 0 clock is now selected as clock source
 Mar 20 10:06:21.702: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0:15, TEI 0 changed to up
 Mar 20 10:06:22.494: %CONTROLLER-5-UPDOWN: Controller E1 0, changed state to up
 Mar 20 10:06:24.494: %LINK-3-UPDOWN: Interface Serial0:15, changed state to up
 
 debug isdn q931
 debug radius
 debug voip aaa
 
 Feb 17 16:39:03.793: ISDN Se3:15: RX <-  SETUP pd = 8  callref = 0x0072
 Feb 17 16:39:03.793:         Sending Complete
 Feb 17 16:39:03.793:         Bearer Capability i = 0x8090A3
 Feb 17 16:39:03.793:         Channel ID i = 0xA1838E
 Feb 17 16:39:03.793:         Progress Ind i = 0x8283 - Origination address is non-ISDN 
 Feb 17 16:39:03.793:         Calling Party Number i = 'A', 0x83, '07534442165', Plan:ISDN, Type:Subscriber(local)
 Feb 17 16:39:03.793:         Called Party Number i = 0xC1, '02085542609', Plan:ISDN, Type:Subscriber(local)
  --More--                           Feb 17 16:39:03.985: start_h323_accounting: 
 Feb 17 16:39:03.985:       calling num     : zzzz
 Feb 17 16:39:03.985:       called num      : xxxxxx
 Feb 17 16:39:03.985:       account num     : xxxxx
 Feb 17 16:39:03.985:       gateway id      : gdmz-p-gw2.unip.com.cn 
 Feb 17 16:39:03.985:       connection id   : 99780583 DDE900CB 0 1E2554 
 Feb 17 16:39:03.985:       incoming conn id: 99780583 DDE900CB 0 1E2554 
 Feb 17 16:39:03.985:       call origin     : answer 
 Feb 17 16:39:03.985:       call type       : Telephony 
 Feb 17 16:39:03.985:       setup time      : 16:39:03.975 UTC Sat Feb 17 2001 
 Feb 17 16:39:03.985:       nas_port        : ISDN 3:D:14 
 Feb 17 16:39:03.985:       subscriber_type_str : RegularLine 
 Feb 17 16:39:03.989: RADIUS: ustruct sharecount=3
 Feb 17 16:39:03.989: RADIUS: added cisco VSA 2 len 11 "ISDN 3:D:14"
 Feb 17 16:39:03.989: RADIUS: added cisco VSA 33 len 33 "h323-gw-id=gdmz-p-gw2.unip.com.cn"
 Feb 17 16:39:03.989: RADIUS: added cisco VSA 24 len 39 "h323-conf-id=99780583 DDE900CB 0 1E2554"
 Feb 17 16:39:03.989: RADIUS: added cisco VSA 1 len 48 "h323-incoming-conf-id=99780583 DDE900CB 0 1E2554"
 Feb 17 16:39:03.989: RADIUS: added cisco VSA 26 len 23 "h323-call-origin=answer"
 Feb 17 16:39:03.989: RADIUS: added cisco VSA 27 len 24 "h323-call-type=Telephony"
 Feb 17 16:39:03.989: RADIUS: added cisco VSA 25 len 48 "h323-setup-time=16:39:03.975 UTC Sat Feb 17 2001"
 Feb 17 16:39:03.989: update_h323_accounting: 
 Feb 17 16:39:03.989:       calling num     : zzzz
 Feb 17 16:39:03.989:       called num      : zxxxx
 Feb 17 16:39:03.989:       account num     : xxxx
 Feb 17 16:39:03.989: RADIUS: Initial Transmit ISDN 3:D:14 id 206 210.78.225.28:1813, Accounting-Request, len 381
 Feb 17 16:39:03.993:         Attribute 4 6 D35DE394
 Feb 17 16:39:03.993:         Attribute 26 19 00000009020D4953
 Feb 17 16:39:03.993:         Attribute 61 6 00000000
 Feb 17 16:39:03.993:         Attribute 1 13 30373533
 Feb 17 16:39:03.993:         Attribute 30 13 30323038
 Feb 17 16:39:03.993:         Attribute 31 13 30373533
 Feb 17 16:39:03.993:         Attribute 40 6 00000001
 Feb 17 16:39:03.993:         Attribute 6 6 00000001
 Feb 17 16:39:03.993:         Attribute 26 41 0000000921236833
 Feb 17 16:39:03.993:         Attribute 26 47 0000000918296833
 Feb 17 16:39:03.993:         Attribute 26 56 0000000901326833
 Feb 17 16:39:03.993:         Attribute 26 31 000000091A196833
 Feb 17 16:39:03.993:         Attribute 26 32 000000091B1A6833
 Feb 17 16:39:03.993:         Attribute 26 56 0000000919326833
 Feb 17 16:39:03.993:         Attribute 44 10 30303030
 Feb 17 16:39:03.993:         Attribute 41 6 00000000
 Feb 17 16:39:04.001: start_h323_accounting: 
 Feb 17 16:39:04.001:       calling num     : 07534442165 
 Feb 17 16:39:04.001:       called num      : 02085542609 
 Feb 17 16:39:04.001:       account num     : 07534442165 
 Feb 17 16:39:04.001:       gateway id      : gdmz-p-gw2.unip.com.cn 
 Feb 17 16:39:04.001:       connection id   : 99780583 DDE900CB 0 1E2554 
 Feb 17 16:39:04.001:       incoming conn id: 99780583 DDE900CB 0 1E2554 
 Feb 17 16:39:04.001:       call origin     : originate 
 Feb 17 16:39:04.001:       call type       : VoIP 
 Feb 17 16:39:04.001:       setup time      : 16:39:03.991 UTC Sat Feb 17 2001 
 Feb 17 16:39:04.001:       nas_port        :  
 Feb 17 16:39:04.001:       subscriber_type_str : RegularLine 
 Feb 17 16:39:04.005: RADIUS: ustruct sharecount=3
 Feb 17 16:39:04.005: RADIUS: added cisco VSA 33 len 33 "h323-gw-id=gdmz-p-gw2.unip.com.cn"
 Feb 17 16:39:04.005: RADIUS: added cisco VSA 24 len 39 "h323-conf-id=99780583 DDE900CB 0 1E2554"
 Feb 17 16:39:04.005: RADIUS: added cisco VSA 1 len 48 "h323-incoming-conf-id=99780583 DDE900CB 0 1E2554"
 Feb 17 16:39:04.005: RADIUS: added cisco VSA 26 len 26 "h323-call-origin=originate"
 Feb 17 16:39:04.005: RADIUS: added cisco VSA 27 len 19 "h323-call-type=VoIP"
  17 16:39:04.005: RADIUS: added cisco VSA 25 len 48 "h323-setup-time=16:39:03.991 UTC Sat Feb 17 2001"
 Feb 17 16:39:04.005: ISDN Se3:15: TX ->  CALL_PROC pd = 8  callref = 0x8072
 Feb 17 16:39:04.005:         Channel ID i = 0xA9838E
 Feb 17 16:39:04.009: RADIUS: Initial Transmit  id 207 210.78.225.28:1813, Accounting-Request, len 360
 Feb 17 16:39:04.009:         Attribute 4 6 D35DE394
 Feb 17 16:39:04.009:         Attribute 61 6 00000000
 Feb 17 16:39:04.009:         Attribute 1 13 30373533
 Feb 17 16:39:04.009:         Attribute 30 13 30323038
 Feb 17 16:39:04.009:         Attribute 31 13 30373533
 Feb 17 16:39:04.009:         Attribute 40 6 00000001
 Feb 17 16:39:04.009:         Attribute 6 6 00000001
 Feb 17 16:39:04.009:         Attribute 26 41 0000000921236833
 Feb 17 16:39:04.009:         Attribute 26 47 0000000918296833
 Feb 17 16:39:04.009:         Attribute 26 56 0000000901326833
 Feb 17 16:39:04.009:         Attribute 26 34 000000091A1C6833
 Feb 17 16:39:04.009:         Attribute 26 27 000000091B156833
 Feb 17 16:39:04.009:         Attribute 26 56 0000000919326833
 Feb 17 16:39:04.009:         Attribute 44 10 30303030
 Feb 17 16:39:04.009:         Attribute 41 6 00000000
 
 Feb 17 16:39:07.994: RADIUS: Retransmit id 206
 Feb 17 16:39:07.994: RADIUS: acct-delay-time for 40522524 (at 4052269B) now 4
 Feb 17 16:39:08.011: RADIUS: Retransmit id 207
 Feb 17 16:39:08.011: RADIUS: acct-delay-time for 40521E68 (at 40521FCA) now 4
 Feb 17 16:39:11.996: RADIUS: Retransmit id 208
 Feb 17 16:39:11.996: RADIUS: acct-delay-time for 40522524 (at 4052269B) now 8
 Feb 17 16:39:12.012: RADIUS: Retransmit id 209
 Feb 17 16:39:12.012: RADIUS: acct-delay-time for 40521E68 (at 40521FCA) now 8
 Feb 17 16:39:12.273: RADIUS: Received from id 210 210.78.225.28:1813, Accounting-response, len 20
 Feb 17 16:39:12.285: RADIUS: Received from id 211 210.78.225.28:1813, Accounting-response, len 20
 
 Feb 17 16:39:23.994: ISDN Se3:15: RX <-  DISCONNECT pd = 8  callref = 0x0072
 Feb 17 16:39:23.994:         Cause i = 0x82E6 - Recovery on  timer expiry
 Feb 17 16:39:23.994:         Progress Ind i = 0x8288 - In-band info or appropriate now available 
 Feb 17 16:39:26.775: stop_h323_accounting:
 Feb 17 16:39:26.775:       receive byte    : 0 
 Feb 17 16:39:26.775:       transmit byte   : 0 
 Feb 17 16:39:26.775:       receive pak     : 0 
 Feb 17 16:39:26.775:       transmit pak    : 0 
 Feb 17 16:39:26.775:       connect time    : 16:39:26.775 UTC Sat Feb 17 2001 
 Feb 17 16:39:26.775:       disconnect time : 16:39:26.775 UTC Sat Feb 17 2001 
 Feb 17 16:39:26.775:       disconnect cause: 22 
 Feb 17 16:39:26.775:       voice quality   : 0 
 
 
 
 
 
  | 
 
 
 |