排除ISDN BRI鏈路上的第二次B通道呼叫故障

下載選項

  • PDF     (342.5 KB)
    在多種裝置上使用 Adobe Reader 檢視
  • ePub     (102.3 KB)
    在 iPhone、iPad、Android、Sony Reader 或 Windows Phone 上的各種應用程式中檢視
  • Mobi (Kindle)     (190.4 KB)
    在 Kindle 裝置或多部裝置的 Kindle 應用程式上檢視
已更新: 2005 年 10 月 17 日
文件 ID:22480

無偏見用語

本產品的文件集力求使用無偏見用語。針對本文件集的目的，無偏見係定義為未根據年齡、身心障礙、性別、種族身分、民族身分、性別傾向、社會經濟地位及交織性表示歧視的用語。由於本產品軟體使用者介面中硬式編碼的語言、根據 RFP 文件使用的語言，或引用第三方產品的語言，因此本文件中可能會出現例外狀況。深入瞭解思科如何使用包容性用語。

關於此翻譯

思科已使用電腦和人工技術翻譯本文件，讓全世界的使用者能夠以自己的語言理解支援內容。請注意，即使是最佳機器翻譯，也不如專業譯者翻譯的內容準確。Cisco Systems, Inc. 對這些翻譯的準確度概不負責，並建議一律查看原始英文文件（提供連結）。

簡介

多鏈路點對點協定(MPPP)使您能夠在ISDN BRI連線中同時啟用兩個B通道。MPPP在ISDN終端裝置之間提供128k(2 x 64kbps)頻寬。但是，在許多情況下，路由器只能連線一個B通道，而另一個B通道保持空閒。本文探討如何在此類情況下進行疑難排解。

注意：此過程主要用於連線一個BRI鏈路（即兩個B通道）。 如果使用MPPP捆綁兩個或多個BRI（即至少三個B通道），請參閱使用多個BRI介面配置多鏈路PPP。

必要條件

需求

檢驗路由器是否可以通過一個B通道相互連線。本文檔僅介紹與附加多鏈路通道相關的連線故障。如果無法通過一個通道進行連線，請參閱ISDN BRI故障排除流程圖。

除非第一個通道成功連線，否則不要繼續執行本文檔中的程式。

思科建議您瞭解以下主題：

  • 一般ISDN和按需撥號路由(DDR)配置概念。有關詳細資訊，請參閱思科學習連線上提供的基本ISDN和DDR配置的培訓演示。

  • 如何調試ISDN和PPP。您必須能夠確定路由器是否撥打、連線在ISDN層並協商PPP。

採用元件

本文中的資訊係根據以下軟體和硬體版本：

  • Cisco IOS®軟體版本12.1(2)和12.2(2)T

    Cisco在Cisco IOS®軟體版本12.1(2)中引入了dialer redial指令。 稍後，思科修改了該命令，以便在Cisco IOS軟體版本12.2(2)T中包括其他選項。有關此功能的詳細資訊，請參閱重撥增強功能。

  • 兩台連線到即時BRI電路的路由器。

本文中的資訊是根據特定實驗室環境內的裝置所建立。文中使用到的所有裝置皆從已清除（預設）的組態來啟動。如果您的網路正在作用，請確保您已瞭解任何指令可能造成的影響。

慣例

如需文件慣例的詳細資訊，請參閱思科技術提示慣例。

問題描述

路由器在BRI上啟用兩個B通道，以嘗試連線到ISDN對等體。到對等體的連線成功。但是，只有一個B通道成功連線。多鏈路PPP嘗試啟動額外的B通道，但呼叫持續失敗。

此圖說明成功呼叫的呼叫流程：

ppp_multilink_ts2.gif

您必須向電信公司提出的問題

配置多鏈路並對其進行故障排除時，請詢問被叫路由器的電話公司以下問題：

  1. 問題：我們需要撥打一個或兩個號碼才能同時連線到兩個遠端B通道？

    答案：

    一個數字：根據需要在本地路由器的物理或撥號器介面上配置單個撥號器字串或撥號器對映。如需詳細資訊，請參閱步驟4。繼續問題2。

    兩個數字：在本地路由器上，為每個遠端B通道ISDN號碼配置撥號器對映或撥號器字串。如需詳細資訊，請參閱步驟4。

  2. 問題：是否在尋線組中配置了B通道號？

    答案：

    是:對於只需要一個數字連線到兩個B通道的電路，這是預期設定。尋線組繫結兩個B通道號碼（因此呼叫方只需呼叫一個號碼）。 第一個B通道連線後，呼叫路由器再次撥打相同的號碼。位於最靠近被叫路由器的遠端端的交換機識別出第一B通道正忙，並將來電轉駁到第二B通道上，從而使捆綁成為可能。

    否:要求電信公司配置尋線組中的兩個B通道號碼，並在第一個號碼忙時，自動將呼叫轉到第二個號碼。如果電信公司未配置尋線組，請配置dialer redial或isdn fast-rolver delay命令，如故障排除一節的步驟5所述。

疑難排解

注意：使用此過程之前，請確認路由器是否使用一個B通道相互連線。如果無法通過一個通道進行連線，請參閱ISDN BRI故障排除流程圖。

  1. 開啟以下debug指令：debug dialer、debug isdn q931和debug ppp negotiation。

  2. 啟動發往遠端裝置的流量。確保有足夠的流量發起其他呼叫。

    提示：您可以使用延伸ping公用程式來改變資料包/封包大小和ping數量。有關如何使用延伸ping的詳細資訊，請參閱使用延伸ping和延伸traceroute命令。

  3. 檢查路由器是否嘗試第二次呼叫。調試如下所示：

    *Mar  1 01:30:55.295: BRI3/0 DDR: rotor dialout [priority]

!--- Use BRI 3/0 to dial out.

*Mar  1 01:30:55.295: BRI3/0 DDR: Dialing cause ip 
(s=10.1.1.1, d=172.22.53.201)

!--- DDR dialing cause is a ping to the remote router.

*Mar  1 01:30:55.295: BRI3/0 DDR: Attempting to dial 5558888

!--- Dial the remote number.

*Mar  1 01:30:55.295: ISDN BR3/0: TX ->  SETUP pd = 8  callref = 0x07
*Mar  1 01:30:55.299:         Bearer Capability i = 0x8890218F
*Mar  1 01:30:55.299:         Channel ID i = 0x83
*Mar  1 01:30:55.299:         Keypad Facility i = '5558888'

  4. 路由器是否嘗試第二次呼叫？

    • 是:請繼續執行步驟5。

    • 否:這意味著路由器未正確配置多鏈路PPP。配置以下命令：

      指令 說明
      ppp multilink 在物理介面和撥號程式介面（如果您使用撥號程式配置檔案）下配置ppp multilink命令（兩台路由器上）。

      附註：  如果新增此命令，則必須斷開所有現有連線，然後重新連線要應用的新多鏈路引數。在呼叫建立期間進行多鏈路協商。因此，對多鏈路的任何更改都不會在已完成LCP協商的連線上實現。
      dialer load-threshold 5 outbound 介面負載（從1到255），撥號器超出此範圍會向目的地發起另一個呼叫。頻寬的比率是255，其中255是可用頻寬的100%。在本例中，當鏈路上的出站負載為5/255或2%時，附加通道將啟動。根據您的需求更改此值。

      提示：使用者有時將dialer load-threshold 1命令配置為立即對每次呼叫使用所有B通道。此配置背後的理論是，如果所有B通道同時啟動，且每次呼叫使用整個ISDN管道，則呼叫的持續時間必須縮短，因為使用者資料需要較少的時間進行傳輸。

      雖然這個理論聽起來不錯，但實際上思科建議您不要將撥號器負載閾值設定為小於3。如果您將此值設定為小於3，多個ISDN通道將同時開啟，導致兩個通道之間發生爭用，並且任何通道都無法連線。
      dialer map ip address name name number 或dialer string number 為每個遠端B通道ISDN號碼配置撥號器對映（或撥號器字串）。兩條語句的IP地址和名稱必須相同，只有ISDN編號必須不同。範例： 
      dialer map ip 192.168.1.1 name asc001 13305551111
dialer map ip 192.168.1.1 name asc001 13305551112
      或 
      dialer string 13305551111
dialer string 13305551112

      附註：  如果電信公司通知您僅需要撥一個號碼，則您只需要一個撥號器對映或撥號器字串語句。

      有關多鏈路PPP配置選項的詳細資訊，請參閱適用於DDR的多鏈路PPP — 基本配置和驗證。

  5. 在物理或撥號器介面下配置以下命令之一：

    • dialer redial interval 5 attempts 3 — 撥號嘗試之間的間隔為五秒，最多嘗試三次。

      此間隔允許在重撥嘗試之前完全斷開舊呼叫。

    • isdn fast-rollover-delay 5 — 將翻轉延遲設定為5秒。

      提供此延遲，以便在嘗試新呼叫之前完全斷開舊呼叫。此命令在某些ISDN交換機上非常必要，因為新的呼叫嘗試可能會在舊呼叫完全斷開之前進行。這將導致第二次呼叫失敗。

輸出示例

本節提供成功呼叫和不成功呼叫的配置和調試輸出示例。使用本節作為參考，檢查您觀察到的調試是否與下面顯示的調試匹配：

ppp_multilink_ts1.gif 

interface BRI1/0
 ip address 192.168.1.111 255.255.255.0
 encapsulation ppp
 dialer map ip 192.168.1.1 name asc001 13305551111
 dialer map ip 192.168.1.1 name asc001 13305551112
 
!--- Notice that the dialer map statements are identical except for !--- the phone numbers to dial. !--- The numbers correspond to the ISDN numbers of the remote BRI. !--- This router will use the first dialer map, then the second dialer map. 

 dialer load-threshold 1 either

 !--- Set the load-threshold to the required value and direction dialer-group 1.

 isdn switch-type basic-ni
 isdn spid1 25255588880101 5558888
 isdn spid2 25255588890101 5558889 
 isdn fast-rollover-delay 5
 

 !--- Rollover delay is set to 5 seconds.

 ppp authentication chap pap callin
 ppp multilink

 !--- Enable multilink on the interface.

啟用debug isdn q931和debug ppp negotiation，然後對遠端終端IP地址發起ping。 

asc011#ping 192.168.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
Aug 24 16:30:35.651 est: ISDN BR1/0: TX -> SETUP pd = 8 callref = 0x3B
Aug 24 16:30:35.655 EST: Bearer Capability i = 0x8890218F
Aug 24 16:30:35.655 EST: Channel ID i = 0x83
Aug 24 16:30:35.659 EST: Keypad Facility i = '13305551111' 

!--- Calling out with the number specified in the first dialer map.

Aug 24 16:30:35.896 EST: ISDN BR1/0: RX <- CALL_PROC pd = 8 callref = 0xBB
Aug 24 16:30:35.896 EST: Channel ID i = 0x89
Aug 24 16:30:35.900 EST: Locking Shift to Codeset 5
Aug 24 16:30:35.900 EST: Codeset 5 IE 0x2A i = 0x80880B,'13305551111', 
  0x800109800114800114800114..
Aug 24 16:30:38.877 EST: ISDN BR1/0: RX <- ALERTING pd = 8 callref = 0xBB
Aug 24 16:30:38.881 EST: Signal i = 0x01 - Ring back tone on
Aug 24 16:30:38.929 EST: ISDN BR1/0: RX <- CONNECT pd = 8 callref =0xBB
Aug 24 16:30:38.929 EST: Signal i = 0x3F - Tones off
Aug 24 16:30:38.937 EST: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to up
Aug 24 16:30:38.941 EST: BR1/0:1 PPP: Treating connection as a callout
Aug 24 16:30:38.945 EST: BR1/0:1 PPP: Phase is ESTABLISHING, Active Open
  [0 sess , 0 load]
Aug 24 16:30:38.945 EST: BR1/0:1 PPP: No remote authentication for call-out
Aug 24 16:30:38.945 EST: BR1/0:1 LCP: O CONFREQ [Closed] id 5 len 23
Aug 24 16:30:38.945 EST: BR1/0:1 LCP: MagicNumber 0x55EE5FC7 (0x050655EE5FC7)
Aug 24 16:30:38.945 EST: BR1/0:1 LCP: MRRU 1524 (0x110405F4)
Aug 24 16:30:38.949 EST: BR1/0:1 LCP: EndpointDisc 1 Local 
  (0x130901617363303131)
Aug 24 16:30:38.949 EST: ISDN BR1/0: TX -> CONNECT_ACK pd = 8 callref = 0x3B
...

!--- Output omitted.

...
Aug 24 16:30:39.009 EST: BR1/0:1 LCP: I CONFACK [ACKsent] id 5 Len 23
Aug 24 16:30:39.009 EST: BR1/0:1 LCP: MagicNumber 0x55EE5FC7(0x050655EE5FC7)
Aug 24 16:30:39.009 EST: BR1/0:1 LCP: MRRU 1524 (0x110405F4)
Aug 24 16:30:39.009 EST: BR1/0:1 LCP: EndpointDisc 1 Local 
  (0x130901617363303131)
Aug 24 16:30:39.013 EST: BR1/0:1 LCP: State is Open
Aug 24 16:30:39.013 EST: BR1/0:1 PPP:Phase is AUTHENTICATING, by the peer
  [0 sess, 0 load]
Aug 24 16:30:39.057 EST: BR1/0:1 CHAP: I CHALLENGE id 151 Len 27 from "asc001"
Aug 24 16:30:39.061 EST: BR1/0:1 CHAP: O RESPONSE id 151 Len 27 from "asc011"
Aug 24 16:30:39.109 EST: BR1/0:1 CHAP: I SUCCESS id 151 Len 4
 !--- Authentication is successful. 
Aug 24 16:30:39.109 EST: BR1/0:1 PPP: Phase is VIRTUALIZED [0 sess, 0 load]
Aug 24 16:30:39.113 EST: Vi1 PPP: Phase is DOWN, Setup [0 sess, 0 load]
Aug 24 16:30:39.121 EST: %LINK-3-UPDOWN: Interface Virtual-Access1,
changed state to up
Aug 24 16:30:39.121 EST: Vi1 PPP: Treating connection as a callout
Aug 24 16:30:39.121 EST: Vi1 PPP: Phase is ESTABLISHING, Active Open [0sess, 0load]
Aug 24 16:30:39.125 EST: Vi1 PPP: No remote authentication for call-out
Aug 24 16:30:39.125 EST: Vi1 LCP: O CONFREQ [Closed] id 1 Len 23
Aug 24 16:30:39.125 EST: Vi1 LCP: MagicNumber 0x55EE6079(0x050655EE6079)
Aug 24 16:30:39.125 EST: Vi1 LCP: MRRU 1524 (0x110405F4)
Aug 24 16:30:39.125 EST: Vi1 LCP: EndpointDisc 1 Local (0x130901617363303131)
Aug 24 16:30:39.129 EST: Vi1 PPP: Phase is UP [0 sess, 0 load]
Aug 24 16:30:39.129 EST: Vi1 IPCP: O CONFREQ [Closed] id 1 Len 10
Aug 24 16:30:39.129 EST: Vi1 IPCP: Address 192.168.1.111(0x0306C0A8016F)
Aug 24 16:30:39.137 EST: Vi1 IPCP: I CONFREQ [REQsent] id 1 Len 10
Aug 24 16:30:39.137 EST: Vi1 IPCP: Address 192.168.1.1 (0x0306C0A80101)
Aug 24 16:30:39.137 EST: Vi1 IPCP: O CONFACK [REQsent] id 1 Len 10
Aug 24 16:30:39.137 EST: Vi1 IPCP: Address 192.168.1.1 (0x0306C0A80101)
Aug 24 16:30:39.177 EST: Vi1 IPCP: I CONFACK [ACKsent] id 1 Len 10
Aug 24 16:30:39.177 EST: Vi1 IPCP: Address 192.168.1.111 (0x0306C0A8016F)
Aug 24 16:30:39.181 EST: Vi1 IPCP: State is Open
Aug 24 16:30:39.185 EST: BR1/0 IPCP: Install route to 192.168.1.1

!--- First call is successful. We will now initiate the additional call.

Aug 24 16:30:39.754 EST: ISDN BR1/0: TX -> SETUP pd = 8 callref = 0x3C
Aug 24 16:30:39.754 EST: Bearer Capability i = 0x8890218F
Aug 24 16:30:39.758 EST: Channel ID i = 0x83
Aug 24 16:30:39.762 EST: Keypad Facility i = '13305551111' 

!--- We once again dial out with the first dialer map (the expected behavior). !--- This call fails and router rolls over to use the second dialer map.

Aug 24 16:30:39.995 EST: ISDN BR1/0: RX <- CALL_PROC pd = 8 callref = 0xBC
Aug 24 16:30:39.995 EST: Channel ID i = 0x8A
Aug 24 16:30:39.999 EST: Locking Shift to Codeset 5
Aug 24 16:30:39.999 EST: Codeset 5 IE 0x2A i = 
  0x80880B,'13305551111',0x800109800114800114800114
Aug 24 16:30:40.111 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1,
  changed state to up
Aug 24 16:30:40.131 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface
  Virtual-Access1, changed state to up
Aug 24 16:30:41.209 EST: BR1/0:1 LCP: I ECHOREQ [Open] id 1 Len 12 magic 0x8EFDDF16
Aug 24 16:30:41.209 EST: BR1/0:1 LCP: O ECHOREP [Open] id 1 Len 12 magic 0x55EE5FC7
Aug 24 16:30:42.779 EST: ISDN BR1/0: RX <- DISCONNECT pd = 8 callref = 0xBC
Aug 24 16:30:42.783 EST: Cause i = 0x8291 - User busy
Aug 24 16:30:42.783 EST: Signal i = 0x04 - Busy tone on

!--- The call fails. The remote switch sends a message that the B-channel is busy. !--- Upon receipt of this disconnect, the router dials the second dialer map. !--- If you do not receive this Disconnect within a certain timeframe, the router !--- does not attempt another call. The dialer redial or isdn fast-rollover !--- commands can fix this issue.

Aug 24 16:30:42.795 EST: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to
  13305551111 asc001
Aug 24 16:30:42.807 EST: ISDN BR1/0: TX -> RELEASE pd = 8 callref = 0x3C
Aug 24 16:30:42.831 EST: ISDN BR1/0: TX -> SETUP pd = 8 callref = 0x3D
Aug 24 16:30:42.835 EST: Bearer Capability i = 0x8890218F
Aug 24 16:30:42.835 EST: Channel ID i = 0x83
Aug 24 16:30:42.839 EST: Keypad Facility i = '13305551112'

!--- Dial with the second dialer map.

Aug 24 16:30:42.927 EST: ISDN BR1/0: RX <- RELEASE_COMP pd = 8 callref = 0xBC
Aug 24 16:30:42.931 EST: Signal i = 0x3F - Tones off
Aug 24 16:30:43.096 EST: ISDN BR1/0: RX <- CALL_PROC pd = 8 callref = 0xBD
Aug 24 16:30:43.096 EST: Channel ID i = 0x8A
Aug 24 16:30:43.100 EST: Locking Shift to Codeset 5 asc011#
Aug 24 16:30:43.100 EST: Codeset 5 IE 0x2A i = 0x80880B, '13305551112'
  ,0x800109800114800114800114
Aug 24 16:30:46.329 EST: ISDN BR1/0: RX <- ALERTING pd = 8 callref = 0xBD
Aug 24 16:30:46.329 EST: Signal i = 0x01 - Ring back tone on
Aug 24 16:30:46.361 EST: ISDN BR1/0: RX <- CONNECT pd = 8 callref = 0xBD
Aug 24 16:30:46.361 EST: Signal i = 0x3F - Tones off
Aug 24 16:30:46.373 EST: %LINK-3-UPDOWN: Interface BRI1/0:2, changed state to up
Aug 24 16:30:46.373 EST: BR1/0:2 PPP: Treating connection as a callout
...

!--- Output omitted.

...
Aug 24 16:30:46.445 EST: BR1/0:2 LCP: State is Open
Aug 24 16:30:46.445 EST: BR1/0:2 PPP: Phase is AUTHENTICATING, by the peer 
  [0 sess, 1 load]
Aug 24 16:30:46.489 EST: BR1/0:2 CHAP: I CHALLENGE id 31 Len 27 from "asc001"
Aug 24 16:30:46.493 EST: BR1/0:2 CHAP: O RESPONSE id 31 Len 27 from "asc011"
Aug 24 16:30:46.542 EST: BR1/0:2 CHAP: I SUCCESS id 31 Len 4
Aug 24 16:30:46.542 EST: BR1/0:2 PPP: Phase is VIRTUALIZED [0 sess, 1 load]
Aug 24 16:30:46.546 EST: BR1/0:2 MLP: asc001, multilink up
Aug 24 16:30:47.343 EST: BR1/0:1 LCP: I ECHOREP [Open] id 1 Len 12 magic 
  0x8EFDDF16
Aug 24 16:30:47.343 EST: BR1/0:1 LCP: Received id 1, sent id 1, line up
Aug 24 16:30:47.343 EST: BR1/0:2 LCP: I ECHOREP [Open] id 1 Len 12 magic 
  0x8EFDFC22
Aug 24 16:30:47.347 EST: BR1/0:2 LCP: Received id 1, sent id 1, line up
Aug 24 16:30:47.543 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:2,
  changed state to up

!--- The 2 B-channel Call connects.

asc011#

使用show isdn active命令檢查連線。記下每個出站呼叫的被叫號碼。 

--------------------------------------------------------------------------------
ISDN ACTIVE CALLS
--------------------------------------------------------------------------------
Call   Calling   Called  Remote  Seconds  Seconds   Seconds  Charges
Type    Number   Number  Name     Used    Left      Idle     Units/Currency
--------------------------------------------------------------------------------
Out         +3305551111 asc001         55 Unavail    0         0
Out         +3305551112 asc001         48 Unavail    0         0
-------------------------------------------------------------------------------

此示例顯示FAILED呼叫。某些無關的輸出被省略。


asc008#ping 192.168.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
Aug 21 09:33:17.627 EST: BR1/0 DDR: Dialing cause ip (s=192.168.1.108,d=192.168.1.1)
Aug 21 09:33:17.627 EST: BR1/0 DDR: Attempting to dial 13305551111
Aug 21 09:33:17.635 EST: ISDN BR1/0: TX -> SETUP pd = 8 callref = 0x0C
Aug 21 09:33:17.639 EST: Bearer Capability i = 0x8890
Aug 21 09:33:17.639 EST: Channel ID i = 0x83
Aug 21 09:33:17.639 EST: Keypad Facility i = '13305551111'

!--- Calling out with the number specified in the first dialer map.

Aug 21 09:33:18.184 EST: ISDN BR1/0: RX <- CALL_PROC pd = 8 callref = 0x8C
Aug 21 09:33:18.184 EST: Channel ID i = 0x89.
Aug 21 09:33:20.532 EST: ISDN BR1/0: RX <- ALERTING pd = 8 callref =0x8C
Aug 21 09:33:20.536 EST: Signal i = 0x01 - Ring back tone on
Aug 21 09:33:20.564 EST: ISDN BR1/0: RX <- CONNECT pd = 8 callref =0x8C
Aug 21 09:33:20.568 EST: Signal i = 0x3F - Tones off
Aug 21 09:33:20.572 EST: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to up
Aug 21 09:33:20.576 EST: BR1/0:1 PPP: Treating connection as a callout
Aug 21 09:33:20.580 EST: BR1/0:1 PPP: Phase is ESTABLISHING, Active Open
  [0 sess, 1 load]
...

! --Output omitted.

...
Aug 21 09:33:20.660 EST: BR1/0:1 LCP: State is Open
Aug 21 09:33:20.660 EST: BR1/0:1 PPP: Phase is AUTHENTICATING, by the peer 
  [0 sess, 1 load]
Aug 21 09:33:20.720 EST: BR1/0:1 CHAP: I CHALLENGE id 127 Len 27 from "asc001"
Aug 21 09:33:20.720 EST: BR1/0:1 CHAP: O RESPONSE id 127 Len 27 from "asc008"
Aug 21 09:33:20.784 EST: BR1/0:1 CHAP: I SUCCESS id 127 Len 4

!--- Authentication is successful.

Aug 21 09:33:20.784 EST: BR1/0:1 PPP: Phase is VIRTUALIZED [0 sess, 1 load]
Aug 21 09:33:20.784 EST: Vi1 PPP: Phase is DOWN, Setup [0 sess, 1 load]
Aug 21 09:33:20.792 EST: %LINK-3-UPDOWN: Interface Virtual-Access1,
  changed state to up
...

!--- Output omitted.

...
Aug 21 09:33:20.864 EST: Vi1 IPCP: Address 192.168.1.108(0x0306C0A8016C)
Aug 21 09:33:20.864 EST: Vi1 IPCP: State is Open
Aug 21 09:33:20.868 EST: Vi1 DDR: dialer protocol up
Aug 21 09:33:20.868 EST: BR1/0 IPCP: Install route to 192.168.1.1
Aug 21 09:33:21.089 EST: BR1/0 DDR: Attempting to dial 13305551111
Aug 21 09:33:21.093 EST: ISDN BR1/0: TX -> SETUP pd = 8 callref = 0x0D
Aug 21 09:33:21.097 EST: Bearer Capability i = 0x8890
Aug 21 09:33:21.097 EST: Channel ID i = 0x83
Aug 21 09:33:21.101 EST: Keypad Facility i = '13305551111'

!--- The second call is dialed out with the first dialer map. !--- The first B-channel on the remote BRI is in use. You must receive a !--- Disconnect(cause code:busy).

Aug 21 09:33:21.581 EST: ISDN BR1/0: RX <- CALL_PROC pd = 8 callref =0x8D
Aug 21 09:33:21.581 EST: Channel ID i = 0x8A
Aug 21 09:33:21.786 EST: %LINEPROTO-5-UPDOWN: Line protocol on 
  InterfaceBRI1/0:1, changed state to up
Aug 21 09:33:21.802 EST: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
  Virtual -Access1, changed state to up
Aug 21 09:33:23.577 EST: ISDN BR1/0: RX <- PROGRESS pd = 8 callref = 0x8D
Aug 21 09:33:23.577 EST: Cause i = 0x8491 - User busy
Aug 21 09:33:23.581 EST: Progress Ind i = 0x8488 - In-band info or appropriate
  now available

!--- In this case, the "Rx <- PROGRESS" is returned, the CALLED !--- router does not even try to call out on the second number because the router !--- assumes the call is in progress. You must receive a DISCONNECT for the router !--- to dial the second number.

Aug 21 09:33:26.578 EST: %ISDN-6-CONNECT: Interface BRI1/0:1 is now 
  connected to 13305551111 asc001
Aug 21 09:33:51.091 EST: BRI1/0: wait for isdn carrier timeout, call  nbid=0x8010
Aug 21 09:33:51.091 EST: BR1/0 DDR: Attempting to dial 13305551112
Aug 21 09:33:51.099 EST: ISDN BR1/0: TX -> DISCONNECT pd = 8 callref = 0x0D
Aug 21 09:33:51.103 EST: Cause i = 0x8090 - Normal call clearing
Aug 21 09:33:51.147 EST: ISDN BR1/0: RX <- RELEASE pd = 8 callref = 0x8D
Aug 21 09:33:51.155 EST: ISDN BR1/0: TX -> RELEASE_COMP pd = 8 callref = 0x0Di

!--- No CONNECT follows the PROGRESS, and so the ISDN carrier times out. !--- Interestingly the ISDN dialer calls out, but the IOS !--- disconnects the same (due to the expiry of certain dialer timers).

使用show isdn active命令檢查連線。請注意，只有一個連線處於活動狀態。

--------------------------------------------------------------------------------
ISDN ACTIVE CALLS
--------------------------------------------------------------------------------
Call     Calling    Called    Remote    Seconds    Seconds  Seconds    Charges
Type     Number     Number     Name       Used      Left       Idle 
Units/Currency
--------------------------------------------------------------------------------
Out             +3305551111  asc001       25       Unavail      0         0
--------------------------------------------------------------------------------

相關資訊

修訂記錄

修訂 發佈日期 意見
1.0
17-Oct-2005
初始版本

這份文件是否有所幫助？

Feedback意見

讓思科協助您

本文件適用於這些產品