使用modem dialout controller命令為傳出模擬呼叫配置T1或E1介面

下載選項

  • PDF     (294.6 KB)
    在多種裝置上使用 Adobe Reader 檢視
  • ePub     (93.1 KB)
    在 iPhone、iPad、Android、Sony Reader 或 Windows Phone 上的各種應用程式中檢視
  • Mobi (Kindle)     (100.8 KB)
    在 Kindle 裝置或多部裝置的 Kindle 應用程式上檢視
已更新: 2008 年 1 月 15 日
文件 ID:9499

無偏見用語

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

關於此翻譯

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

簡介

此示例配置說明如何使用modem dialout controller命令為傳出模擬呼叫配置T1或E1介面

開始之前

慣例

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

必要條件

本文件沒有特定先決條件。

採用元件

本檔案中的資訊是根據以下軟體和硬體版本。

  • Cisco IOS®軟體版本12.1(5)T

  • 具有兩個E1 PRI的Cisco AS5300

註：modem dialout controller命令是在Cisco IOS軟體版本12.1(T)中引入的。 建議在此實施中使用Cisco IOS軟體版本12.1(3)T或更高版本。modem dialout controller命令支援從IOS軟體版本12.1(5)T開始的多個介面。例如：

AS5300-3(config)#line 1 60
AS5300-3(config-line)#modem dialout controller t1 ?
	 <0-7>  List of controllers to dial out

AS5300-3(config-line)#modem dialout controller t1 0,1,3

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

概觀

當您希望傳出模擬呼叫使用特定的T1/E1線路時，請使用modem dialout controller命令。此命令是線上路配置模式下設定的，因此數據機將繫結到指定的T1/E1介面以用於任何出站模擬呼叫。然後，可以在與數據機對應的非同步（或組非同步）介面上配置必要的按需撥號路由(DDR)命令。

在此示例配置中，Cisco AS5300網路接入伺服器(NAS)有兩個主速率介面(PRI)，每個介面對映到不同的撥出號碼識別服務(DNIS)。 如果客戶端撥打8210，電信公司會將呼叫切換到E1 0，並且對8211的呼叫將切換到E1 1。此配置還使用數據機池來根據呼叫建立期間電信交換機傳送的被叫號碼(DNIS)消息分配數據機。這樣，對特定號碼的呼叫僅由屬於特定數據機池的數據機「應答」。由於每個T1/E1也繫結到特定的被叫號碼，因此我們已經將一組數據機有效地關聯到用於傳入呼叫的特定T1/E1。

為了演示撥出情況，客戶端向接入伺服器請求回撥。回撥在存取伺服器本機上設定，但也可以從RADIUS/TACACS+驗證、授權及計量(AAA)伺服器取得回撥屬性。對於特定號碼的來電，呼叫被切換到適當的T1並由數據機池成員應答。在協商回叫後，接入伺服器斷開呼叫，並在同一數據機上啟動回叫。然後使用modem dialout controller命令中指定的T1或E1介面進行撥出。在本示例中，撥號配置為與傳入呼叫位於相同的T1/E1上。

設定

本節提供用於設定本文件中所述功能的資訊。

注意：要查詢有關本文檔中使用的命令的其他資訊，請使用IOS命令查詢工具(僅限註冊客戶)。

網路圖表

本文檔使用下圖所示的網路設定。

modemdialoutcontroller.gif

組態

本文檔使用如下所示的配置。

訪問伺服器配置 
Current configuration:

!
version 12.1
service timestamps debug datetime msec
service timestamps log uptime msec
no service password-encryption
!
hostname lala
!
logging rate-limit console 10 except errors
!
username testuser callback-dialstring 6036 password 0 test

!-- Access server calls back testuser at phone number 6036 !-- The callback parameters can also be configured on a RADIUS/TACACS+ server.

!
spe 1/0 1/9
firmware location system:/ucode/mica_port_firmware
spe 2/0 2/23
firmware location system:/ucode/microcom_firmware
!
resource-pool disable
!
modem-pool ModemPool8210

!-- Modem pool for calls to a specific phone number

pool-range 1-40

!-- The range of the modems in the pool !-- Modems 1 through 40 are included in this pool

called-number 8210 max-conn 40

!-- Specifies the DNIS to be used for this modem pool !-- Incoming calls for phone number 8210 are assigned to this
 pool
!
modem-pool ModemPool8211
pool-range 41-60,61-84

!-- The range of the modems in the pool !-- Modems 41 through 84 are included in this pool

called-number 8211 max-conn 44

!-- Incoming calls for phone number 8211 are assigned to this pool

!
ip subnet-zero
no ip finger
!
isdn switch-type primary-net5
chat-script mod ABORT ERROR ABORT BUSY "" "AT" OK "ATDT \T" TIMEOUT 30 CONNECT \c

!-- Chat script for dialout

!
controller E1 0

!-- DNIS number for this E1 is 8210

clock source line primary
pri-group timeslots 1-31
!
controller E1 1

!-- DNIS number for this E1 is 8211

clock source line secondary 1
pri-group timeslots 1-31
!
controller E1 2
!
controller E1 3
!
!
interface Ethernet0
ip address 10.200.20.22 255.255.255.0
!
interface Serial0:15

!-- D-channel for E1 0 !-- DNIS number for this PRI is 8210

description PRI 8210
no ip address
encapsulation ppp
isdn switch-type primary-net5
isdn incoming-voice modem

!-- All incoming voice calls on this E1 are sent to the modems

!
interface Serial1:15

!-- D-channel for E1 1 !-- DNIS number for this PRI is 8211

description PRI 8211
no ip address
encapsulation ppp
isdn switch-type primary-net5
isdn incoming-voice modem

!-- All incoming voice calls on this E1 are sent to the modems

!
interface Group-Async1
ip unnumbered Ethernet0
encapsulation ppp
async mode interactive
peer default ip address pool dialup

!-- Assign IP address for incoming calls (with DNIS 8210) from pool dialup

ppp callback accept

!-- Permit PPP Callback

ppp authentication chap
group-range 1 40

!-- Interface includes modems 1 through 40 that are also in ModemPool8210

!
interface Group-Async2
ip unnumbered Ethernet0
encapsulation ppp
async mode interactive
peer default ip address pool dialup2

!-- Assign IP address for incoming calls (with DNIS 8211) from pool dialup2

ppp callback accept

!-- Here we accept the callback

ppp authentication chap
group-range 41 84

!-- Interface includes modems 41 through 84 that are also in ModemPool8211

!
ip local pool dialup 192.168.100.1 192.168.100.15
ip local pool dialup2 192.168.200.32 192.168.200.126

!-- Define the IP address ranges for the 2 pools

ip classless
no ip http server
!
line con 0
exec-timeout 0 0
transport input none
line 1 40

!-- Line configuration for modems 1-40 !-- These modems are in pool ModemPool8210

autoselect during-login
autoselect ppp
script callback mod

!-- Invoke chat script mod for the callback

login local
modem InOut

!-- Set the modems for dialin and dialout

modem dialout controller e1 0

!-- Outgoing call on these modems use e1 0

line 41 84

!-- Line configuration for modems 41-84 !-- These modems are in pool ModemPool8210

autoselect during-login
autoselect ppp
script callback mod

!-- Invoke chat script mod for the callback

login local
modem InOut
modem dialout controller e1 1

!-- Outgoing call on these modems use e1 1

line aux 0
line vty 0 4
!
end

驗證

目前沒有適用於此組態的驗證程序。

疑難排解

本節提供的資訊可用於對組態進行疑難排解。

疑難排解指令

Output Interpreter工具(僅供註冊客戶使用)支援某些show命令，這允許您檢視show命令輸出的分析。

注意：發出debug指令之前，請先參閱有關Debug指令的重要資訊。

  • debug isdn q931 — 顯示路由器和ISDN交換機之間的ISDN網路連線（第3層）的呼叫建立和斷開。

  • debug ppp negotiation — 在協商PPP元件(包括鏈路控制協定(LCP)、身份驗證和網路控制協定(NCP))時，顯示有關點對點協定(PPP)流量和交換的資訊。成功的PPP協商首先開啟LCP狀態，然後進行身份驗證，最後協商NCP（通常是IP控制協定 — IPCP）。

  • debug ppp authentication — 顯示PPP身份驗證協定消息，包括質詢身份驗證協定(CHAP)資料包交換和口令身份驗證協定(PAP)交換。

  • debug chat — 當非同步/普通舊式電話服務(POTS)撥號啟動時，監控聊天指令碼的執行。聊天指令碼是一組預期 — 傳送字串對，用於定義資料終端裝置(DTE)和資料通訊裝置(DCE)裝置之間的握手。

  • debug callback — 當路由器使用數據機和聊天指令碼在終端線路上回叫時，顯示回叫事件。

  • debug dialer — 顯示有關撥號器介面上接收的封包的偵錯資訊。

  • debug modem csm（未在此處顯示） — 顯示用於連線數據機呼叫的呼叫狀態機上的調試資訊。顯示內部數據機管理進程如何處理數據機呼叫。

調試輸出示例

以下是使用上述debug命令得到的輸出。

輸出顯示客戶端呼叫8210。然後呼叫被切換到E1 0，由數據機14(Async 14)接聽，數據機14是池ModemPool8210的成員。呼叫連線，協商PPP（和回叫），對客戶端進行身份驗證，AS5300斷開呼叫以準備回叫。然後，路由器使用同一數據機啟動回撥（非同步14）。 根據modem dialout controller命令，呼叫使用E1 0，並且執行撥出。

注意：為了便於列印，已包裝一些較長的調試行。沒有時間戳的開頭行來自上一行的末尾。

*Jan  1 05:00:43.018: ISDN Se0:15: RX <-  SETUP pd = 8  callref = 0x266A
!-- Incoming Call on E1 0
*Jan  1 05:00:43.018:         Sending Complete
*Jan  1 05:00:43.018:         Bearer Capability i = 0x9090A3
*Jan  1 05:00:43.018:         Channel ID i = 0xA18398
*Jan  1 05:00:43.022:         Progress Ind i = 0x8183 
- Origination address is non-ISDN
*Jan  1 05:00:43.022:         Calling Party Number i = 0xA1, '6036',Plan:ISDN, 
Type:National
*Jan  1 05:00:43.022:         Called Party Number i = 0x81, '210', Plan:ISDN, 
Type:Unknown

!-- The called number (DNIS) for the incoming call is (8)210

*Jan  1 05:00:43.022:         Locking Shift to Codeset 6
*Jan  1 05:00:43.022:         Codeset 6 IE 0x28  i = 'Analog', 0x20, '36'
*Jan  1 05:00:43.026: ISDN Se0:15: TX ->  CALL_PROC pd = 8  callref =0xA66A
*Jan  1 05:00:43.026:         Channel ID i = 0xA98398
*Jan  1 05:00:43.030: ISDN Se0:15: TX ->  ALERTING pd = 8  callref = 0xA66A
*Jan  1 05:00:43.082: ISDN Se0:15: TX ->  CONNECT pd = 8  callref = 0xA66A
*Jan  1 05:00:43.146: ISDN Se0:15: RX <-  CONNECT_ACK pd = 8  callref =0x266A
*Jan  1 05:00:43.146: ISDN Se0:15: CALL_PROGRESS: CALL_CONNECTED call id0x63, 
bchan 23, dsl 0
*Jan  1 05:00:45: %ISDN-6-CONNECT: Interface Serial0:23 is now 
connected to 6036

!-- Call is connected

*Jan  1 05:01:11.158: As14 LCP: I CONFREQ [Closed] id 1 len 50

!-- PPP negotiation begins. Note that the call is on !-- Async 14, which is a member of the pool ModemPool8210

*Jan  1 05:01:11.158: As14 LCP:    ACCM 0x00000000 (0x020600000000)
*Jan  1 05:01:11.158: As14 LCP:    MagicNumber 0x75D617D5 (0x050675D617D5)
*Jan  1 05:01:11.158: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:11.158: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:11.158: As14 LCP:    Callback 6  (0x0D0306)
*Jan  1 05:01:11.158: As14 LCP:    MRRU 1614 (0x1104064E)
*Jan  1 05:01:11.158: As14 LCP:    EndpointDisc 1 Local
*Jan  1 05:01:11.158: As14 LCP:     (0x13170177DE54DA55A24ADD8043063898)
*Jan  1 05:01:11.158: As14 LCP:     (0x1C049700000000)
*Jan  1 05:01:11.158: As14 LCP: Lower layer not up, Fast Starting
*Jan  1 05:01:11.158: As14 PPP: Treating connection as a dedicated line
*Jan  1 05:01:11.158: As14 PPP: Phase is ESTABLISHING, Active Open 
[0 sess,1 load]
*Jan  1 05:01:11.158: As14 LCP: O CONFREQ [Closed] id 1 len 25
*Jan  1 05:01:11.158: As14 LCP:    ACCM 0x000A0000 (0x0206000A0000)
*Jan  1 05:01:11.158: As14 LCP:    AuthProto CHAP (0x0305C22305)
*Jan  1 05:01:11.158: As14 LCP:    MagicNumber 0x118F14E6 (0x0506118F14E6)
*Jan  1 05:01:11.158: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:11.158: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:11.158: As14 LCP: O CONFREJ [REQsent] id 1 len 31
*Jan  1 05:01:11.158: As14 LCP:    MRRU 1614 (0x1104064E)
*Jan  1 05:01:11.158: As14 LCP:    EndpointDisc 1 Local
*Jan  1 05:01:11.158: As14 LCP:     (0x13170177DE54DA55A24ADD8043063898)
*Jan  1 05:01:11.162: As14 LCP:     (0x1C049700000000)
*Jan  1 05:01:13: %LINK-3-UPDOWN: Interface Async14, changed state to up

!-- Interface Async 14 is up

*Jan  1 05:01:11.302: As14 LCP: I CONFACK [REQsent] id 1 len 25
*Jan  1 05:01:11.302: As14 LCP:    ACCM 0x000A0000 (0x0206000A0000)
*Jan  1 05:01:11.302: As14 LCP:    AuthProto CHAP (0x0305C22305)
*Jan  1 05:01:11.302: As14 LCP:    MagicNumber 0x118F14E6 (0x0506118F14E6)
*Jan  1 05:01:11.302: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:11.302: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:11.302: As14 LCP: I CONFREQ [ACKrcvd] id 2 len 23
*Jan  1 05:01:11.302: As14 LCP:    ACCM 0x00000000 (0x020600000000)
*Jan  1 05:01:11.302: As14 LCP:    MagicNumber 0x75D617D5 (0x050675D617D5)
*Jan  1 05:01:11.302: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:11.302: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:11.302: As14 LCP:    Callback 6  (0x0D0306)
*Jan  1 05:01:11.302: As14 LCP: O CONFACK [ACKrcvd] id 2 len 23
*Jan  1 05:01:11.302: As14 LCP:    ACCM 0x00000000 (0x020600000000)
*Jan  1 05:01:11.302: As14 LCP:    MagicNumber 0x75D617D5 (0x050675D617D5)
*Jan  1 05:01:11.302: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:11.302: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:11.302: As14 LCP:    Callback 6  (0x0D0306)

!-- Callback is negotiated

*Jan  1 05:01:11.302: As14 LCP: State is Open
*Jan  1 05:01:11.302: As14 PPP: Phase is AUTHENTICATING, by this end 
[0 sess, 1 load]
*Jan  1 05:01:11.302: As14 CHAP: O CHALLENGE id 1 len 25 from "lala"
*Jan  1 05:01:11.446: As14 LCP: I IDENTIFY [Open] id 3 len 18 magic 
0x75D617D5 MSRASV5.00
*Jan  1 05:01:11.462: As14 LCP: I IDENTIFY [Open] id 4 len 28 magic 
0x75D617D5 MSRAS-1-TESTPC-W2K
*Jan  1 05:01:11.462: As14 CHAP: I RESPONSE id 1 len 29 from "testuser"
*Jan  1 05:01:11.462: As14 CHAP: O SUCCESS id 1 len 4

!-- CHAP authentication is successful

*Jan  1 05:01:11.462: As14 MCB: User testuser  Callback Number - Server 6036

!-- Number to be used for callback, configured locally in the username !-- command. The callback information can be off loaded to an AAA server.

*Jan  1 05:01:11.462: Async14 PPP: O MCB Request(1) id 1 len 7
*Jan  1 05:01:11.462: Async14 MCB: O  1  1  0  7  3  3  0
*Jan  1 05:01:11.462: As14 MCB: O Request Id 1 Callback Type 
Server-Num delay 0
*Jan  1 05:01:11.462: As14 PPP: Phase is CBCP [0 sess, 1 load]
*Jan  1 05:01:11.606: Async14 PPP: I MCB Response(2) id 1 len 7
*Jan  1 05:01:11.606: Async14 MCB: I  2  1  0  7  3  3  C
*Jan  1 05:01:11.606: As14 MCB: Received response
*Jan  1 05:01:11.606: As14 MCB: Response CBK-Server-Num 3 3 12
*Jan  1 05:01:11.606: Async14 PPP: O MCB Ack(3) id 2 len 7
*Jan  1 05:01:11.606: Async14 MCB: O  3  2  0  7  3  3  C
*Jan  1 05:01:11.606: As14 MCB: O Ack Id 2 Callback Type Server-Num delay 12
*Jan  1 05:01:11.606: As14 MCB: Negotiated MCB with peer
*Jan  1 05:01:11.734: As14 LCP: I TERMREQ [Open] id 5 len 16 
(0x75D617D5003CCD7400000000)
*Jan  1 05:01:11.734: As14 LCP: O TERMACK [Open] id 5 len 4
*Jan  1 05:01:11.734: As14 MCB: Peer terminating the link
*Jan  1 05:01:11.734: As14 MCB: Link terminated by peer, Callback Needed
*Jan  1 05:01:11.734: As14 MCB: Initiate Callback for testuser at 6036 
using Async
*Jan  1 05:01:11.734: As14 MCB: Async-callback in progress
*Jan  1 05:01:11.734: As14 PPP: Phase is TERMINATING [0 sess, 1 load]
*Jan  1 05:01:11.734: TTY14 Callback PPP process creation
*Jan  1 05:01:11.734: TTY14: Callback script exists 
- no script creation necessary
*Jan  1 05:01:11.734: TTY14 Callback process initiated, user: 
testuser dialstring 6036
*Jan  1 05:01:14: %ISDN-6-DISCONNECT: Interface Serial0:23  disconnected 
from 6036, call lasted 29 seconds

!-- Call is disconnected

*Jan  1 05:01:12.386: ISDN Se0:15: TX ->  DISCONNECT pd = 8  
callref = 0xA66A
*Jan  1 05:01:12.386:         Cause i = 0x809F - Normal, unspecified
*Jan  1 05:01:12.450: ISDN Se0:15: RX <-  RELEASE pd = 8  callref = 0x266A
*Jan  1 05:01:12.450: ISDN Se0:15: TX ->  RELEASE_COMP pd = 8  
callref = 0xA66A
*Jan  1 05:01:13.734: As14 LCP: TIMEout: State TERMsent
*Jan  1 05:01:13.734: As14 LCP: State is Closed
*Jan  1 05:01:13.734: As14 PPP: Phase is DOWN [0 sess, 1 load]
*Jan  1 05:01:13.734: As14 PPP: Phase is ESTABLISHING, Passive Open 
[0 sess, 1 load]
*Jan  1 05:01:13.734: As14 LCP: State is Listen
*Jan  1 05:01:16: %LINK-5-CHANGED: Interface Async14, changed state to reset
*Jan  1 05:01:14.734: As14 LCP: State is Closed
*Jan  1 05:01:14.734: As14 PPP: Phase is DOWN [0 sess, 1 load]
*Jan  1 05:01:17.734: As14 IPCP: Remove route to 192.168.100.13
*Jan  1 05:01:17.734: TTY14 Callback forced wait = 4 seconds
*Jan  1 05:01:21: %LINK-3-UPDOWN: Interface Async14, changed state to down
*Jan  1 05:01:19.734: As14 LCP: State is Closed
*Jan  1 05:01:21.766: CHAT14: Matched chat script mod to string mod
*Jan  1 05:01:21.766: CHAT14: Asserting DTR
*Jan  1 05:01:21.766: CHAT14: Chat script mod started

!-- Callback chatscript mod is started

*Jan  1 05:01:21.766: CHAT14: Sending string: ATZ
*Jan  1 05:01:21.766: CHAT14: Expecting string: OK
*Jan  1 05:01:21.814: CHAT14: Completed match for expect: OK
*Jan  1 05:01:21.814: CHAT14: Sending string: ATDT \T<6036>

!-- Dial 6036 per the callback configuration

*Jan  1 05:01:21.814: CHAT14: Expecting string: CONNECT
*Jan  1 05:01:21.902: ISDN Se0:15: TX ->  SETUP pd = 8  callref = 0x0008

!-- The outgoing call uses E1 0 as per the modem dialout controller !-- command for modem 14.

*Jan  1 05:01:21.902:         Bearer Capability i = 0x8090A3
*Jan  1 05:01:21.902:         Channel ID i = 0xA9839F
*Jan  1 05:01:21.902:         Progress Ind i = 0x8183 
- Origination address is non-ISDN
*Jan  1 05:01:21.902:         Calling Party Number i = 0x80, '6036',
Plan:Unknown, Type:Unknown
*Jan  1 05:01:21.902:         Called Party Number i = 0x80, '6036',
Plan:Unknown, Type:Unknown
*Jan  1 05:01:21.946: ISDN Se0:15: RX <-  CALL_PROC pd = 8  
callref = 0x8008
*Jan  1 05:01:21.946:         Channel ID i = 0xA9839F
*Jan  1 05:01:21.974: ISDN Se0:15: RX <-  ALERTING pd = 8  callref = 0x8008
*Jan  1 05:01:28.958: ISDN Se0:15: RX <-  CONNECT pd = 8  callref = 0x8008
*Jan  1 05:01:28.962:         Progress Ind i = 0x8182 
- Destination address is non-ISDN
*Jan  1 05:01:28.962:         Connected Number i = 0xA136303336
*Jan  1 05:01:28.962:         Locking Shift to Codeset 6
*Jan  1 05:01:28.962:         Codeset 6 IE 0x28  i = 'Analog', 0x20, '36'
*Jan  1 05:01:31: %ISDN-6-CONNECT: 
Interface Serial0:30 is now connected to 6036
*Jan  1 05:01:28.966: ISDN Se0:15: TX ->  CONNECT_ACK pd = 8  
callref =0x0008
*Jan  1 05:01:41.562: CHAT14: Completed match for expect: CONNECT
*Jan  1 05:01:41.566: CHAT14: Sending string: \c
*Jan  1 05:01:41.566: CHAT14: Chat script mod finished, status = Success
*Jan  1 05:01:41.598: TTY14: Callback starting PPP directly with 
Invalid auth info
*Jan  1 05:01:41.642: As14 LCP: I CONFREQ [Closed] id 0 len 47

!-- PPP negotiation begins

*Jan  1 05:01:41.646: As14 LCP:    ACCM 0x00000000 (0x020600000000)
*Jan  1 05:01:41.646: As14 LCP:    MagicNumber 0x143F35CB (0x0506143F35CB)
*Jan  1 05:01:41.646: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:41.646: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:41.646: As14 LCP:    MRRU 1614 (0x1104064E)
*Jan  1 05:01:41.646: As14 LCP:    EndpointDisc 1 Local
*Jan  1 05:01:41.646: As14 LCP:     (0x13170177DE54DA55A24ADD8043063898)
*Jan  1 05:01:41.646: As14 LCP:     (0x1C049700000000)
*Jan  1 05:01:41.646: As14 LCP: Lower layer not up, Fast Starting
*Jan  1 05:01:41.646: As14 PPP: Treating connection as a callout
*Jan  1 05:01:41.646: As14 PPP: Phase is ESTABLISHING, Active Open 
[0 sess,1 load]
*Jan  1 05:01:41.646: As14 LCP: O CONFREQ [Closed] id 2 len 25
*Jan  1 05:01:41.646: As14 LCP:    ACCM 0x000A0000 (0x0206000A0000)
*Jan  1 05:01:41.646: As14 LCP:    AuthProto CHAP (0x0305C22305)
*Jan  1 05:01:41.646: As14 LCP:    MagicNumber 0x118F8C01 (0x0506118F8C01)
*Jan  1 05:01:41.646: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:41.646: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:41.646: As14 LCP: O CONFREJ [REQsent] id 0 len 31
*Jan  1 05:01:41.646: As14 LCP:    MRRU 1614 (0x1104064E)
*Jan  1 05:01:41.646: As14 LCP:    EndpointDisc 1 Local
*Jan  1 05:01:41.646: As14 LCP:     (0x13170177DE54DA55A24ADD8043063898)
*Jan  1 05:01:41.646: As14 LCP:     (0x1C049700000000)
*Jan  1 05:01:43: %LINK-3-UPDOWN: Interface Async14, changed state to up
*Jan  1 05:01:41.810: As14 LCP: I CONFACK [REQsent] id 2 len 25
*Jan  1 05:01:41.810: As14 LCP:    ACCM 0x000A0000 (0x0206000A0000)
*Jan  1 05:01:41.810: As14 LCP:    AuthProto CHAP (0x0305C22305)
*Jan  1 05:01:41.810: As14 LCP:    MagicNumber 0x118F8C01 (0x0506118F8C01)
*Jan  1 05:01:41.810: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:41.810: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:41.842: As14 LCP: I CONFREQ [ACKrcvd] id 1 len 20
*Jan  1 05:01:41.842: As14 LCP:    ACCM 0x00000000 (0x020600000000)
*Jan  1 05:01:41.842: As14 LCP:    MagicNumber 0x143F35CB (0x0506143F35CB)
*Jan  1 05:01:41.842: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:41.842: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:41.842: As14 LCP: O CONFACK [ACKrcvd] id 1 len 20
*Jan  1 05:01:41.842: As14 LCP:    ACCM 0x00000000 (0x020600000000)
*Jan  1 05:01:41.842: As14 LCP:    MagicNumber 0x143F35CB (0x0506143F35CB)
*Jan  1 05:01:41.842: As14 LCP:    PFC (0x0702)
*Jan  1 05:01:41.842: As14 LCP:    ACFC (0x0802)
*Jan  1 05:01:41.842: As14 LCP: State is Open
*Jan  1 05:01:41.842: As14 PPP: Phase is AUTHENTICATING, by this end 
[0 sess, 1 load]
*Jan  1 05:01:41.842: As14 CHAP: O CHALLENGE id 2 len 25 from "lala"
*Jan  1 05:01:42.002: As14 LCP: I IDENTIFY [Open] id 2 len 18 magic 
0x143F35CB MSRASV5.00
*Jan  1 05:01:42.018: As14 LCP: I IDENTIFY [Open] id 3 len 28 magic 
0x143F35CB MSRAS-1-TESTPC-W2K
*Jan  1 05:01:42.034: As14 CHAP: I RESPONSE id 2 len 29 from "testuser"
*Jan  1 05:01:42.034: As14 CHAP: O SUCCESS id 2 len 4

!-- PPP negotiation is successful

*Jan  1 05:01:42.034: As14 PPP: Phase is UP [0 sess, 1 load]
*Jan  1 05:01:42.034: As14 IPCP: O CONFREQ [Closed] id 1 len 10

!-- IPCP parameters are now negotiated

*Jan  1 05:01:42.034: As14 IPCP:    Address 10.200.20.22 (0x03060AC81416)
*Jan  1 05:01:42.194: As14 CCP: I CONFREQ [Not negotiated] id 4 len 10
*Jan  1 05:01:42.194: As14 CCP:    MS-PPC supported bits 0x00000001 
(0x120600000001)
*Jan  1 05:01:42.194: As14 LCP: O PROTREJ [Open] id 3 len 16 protocol CCP 
(0x80FD0104000A120600000001)
*Jan  1 05:01:42.210: As14 IPCP: I CONFREQ [REQsent] id 5 len 40
*Jan  1 05:01:42.210: As14 IPCP:    CompressType VJ 15 slots CompressSlotID
(0x0206002D0F01)
*Jan  1 05:01:42.210: As14 IPCP:    Address 0.0.0.0 (0x030600000000)
*Jan  1 05:01:42.210: As14 IPCP:    PrimaryDNS 0.0.0.0 (0x810600000000)
*Jan  1 05:01:42.210: As14 IPCP:    PrimaryWINS 0.0.0.0 (0x820600000000)
*Jan  1 05:01:42.210: As14 IPCP:    SecondaryDNS 0.0.0.0 (0x830600000000)
*Jan  1 05:01:42.210: As14 IPCP:    SecondaryWINS 0.0.0.0 (0x840600000000)
*Jan  1 05:01:42.210: As14 IPCP: O CONFREJ [REQsent] id 5 len 34
*Jan  1 05:01:42.210: As14 IPCP:    CompressType VJ 15 slots CompressSlotID
(0x0206002D0F01)
*Jan  1 05:01:42.210: As14 IPCP:    PrimaryDNS 0.0.0.0 (0x810600000000)
*Jan  1 05:01:42.210: As14 IPCP:    PrimaryWINS 0.0.0.0 (0x820600000000)
*Jan  1 05:01:42.210: As14 IPCP:    SecondaryDNS 0.0.0.0 (0x830600000000)
*Jan  1 05:01:42.210: As14 IPCP:    SecondaryWINS 0.0.0.0 (0x840600000000)
*Jan  1 05:01:42.214: As14 IPCP: I CONFACK [REQsent] id 1 len 10
*Jan  1 05:01:42.214: As14 IPCP:    Address 10.200.20.22 (0x03060AC81416)
*Jan  1 05:01:42.386: As14 IPCP: I CONFREQ [ACKrcvd] id 6 len 10
*Jan  1 05:01:42.386: As14 IPCP:    Address 0.0.0.0 (0x030600000000)
*Jan  1 05:01:42.386: As14 IPCP: O CONFNAK [ACKrcvd] id 6 len 10
*Jan  1 05:01:42.386: As14 IPCP:    Address 192.168.100.13 (0x0306C0A8640D)
*Jan  1 05:01:42.546: As14 IPCP: I CONFREQ [ACKrcvd] id 7 len 10
*Jan  1 05:01:42.546: As14 IPCP:    Address 192.168.100.13 (0x0306C0A8640D)
*Jan  1 05:01:42.546: As14 IPCP: O CONFACK [ACKrcvd] id 7 len 10
*Jan  1 05:01:42.546: As14 IPCP:    Address 192.168.100.13 (0x0306C0A8640D)
*Jan  1 05:01:42.546: As14 IPCP: State is Open
*Jan  1 05:01:42.550: As14 IPCP: Install route to 192.168.100.13
*Jan  1 05:01:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async14, 
changed state to up

!-- Callback connection is up, PPP negotiation is complete !-- and a route is installed.

相關資訊

修訂記錄

修訂 發佈日期 意見
1.0
15-Jan-2008
初始版本

這份文件是否有所幫助？

Feedback意見

讓思科協助您

本文件適用於這些產品