排除VTR和VTRI的呼叫建立問題

已更新: 2023 年 1 月 31 日

文件 ID:220179

無偏見用語

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

關於此翻譯

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

簡介

本文描述如何在應用伺服器(AS)中使用驗證轉換和路由(VTR)工具對常見呼叫設定問題進行故障排除。

背景資訊

BroadWorks Application Server有兩個嵌入式工具，可用於解決呼叫建立問題：VTR和驗證轉換和路由邀請(VTRI)。這兩個工具的用途相同，不同之處在於輸入命令：

VTR將呼叫者詳細資訊（如使用者ID或電話號碼）以及目標號碼作為輸入，
VTRI將SIP INVITE消息作為輸入。

注意:VTR和VTRI命令也可在網路伺服器(NS)中使用，但輸出結構與AS不同。本文檔重點介紹AS VTR(I)，在使用NS VTR(I)時不能用作參考。

Application Server VTR Administration Guide中提供AS VTR的完整命令參考。

必要條件

需求

思科建議您瞭解以下內容：

作業階段啟始通訊協定(SIP)訊號傳送。
應用伺服器的呼叫處理機制，以及可用的服務及其配置。

採用元件

本文檔中的資訊基於BroadWorks AS版本R24。但是，其他軟體版本的行為是類似的。

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

VTR(I)工具的用法

VTR分析可以從命令列介面(CLI)和Web介面觸發。

從CLI運行VTR(I)工具

若要從Web GUI運行VTR，請使用以下步驟：

步驟1.使用bwadmin憑據登入BroadWorks CLI。

步驟2.啟動BroadWorks CLI並導航到AS_CLI/ASDiagnostic/Diag:

AS_CLI> cd ASDiagnostic/Diag

步驟3.若要使用VTRI，請在新行中運行vtri命令，後跟SIP INVITE和句點字元。例如：

AS_CLI/ASDiagnostic/Diag> vtri
Enter a SIP message. When complete, enter a single period (.) on a line to start verifying the translation.
INVITE sip:2012@mleus.lab SIP/2.0
Via: SIP/2.0/UDP 10.61.205.219:58300;rport;branch=z9hG4bKPjgINPvPUvoBT57iTOBPsgCfEqE5GX1aj7
Max-Forwards: 70
From: "Marek Leus" 
     
     
       ;tag=6fU.VlLrWc6WI3JU8jWKS.25yeoWEhpc To: sip:2012@mleus.lab Contact: "Marek Leus" 
      
        Call-ID: dTUVBWON9UjmftpGCOoJzhLfbajBm11C CSeq: 6492 INVITE Route: 
       
         Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, norefersub User-Agent: Telephone 1.6 Content-Type: application/sdp Content-Length: 480 v=0 o=- 3883737105 3883737105 IN IP4 10.61.205.219 s=pjmedia b=AS:117 t=0 0 a=X-nat:0 m=audio 4012 RTP/AVP 96 9 8 0 101 102 c=IN IP4 10.61.205.219 b=TIAS:96000 a=rtcp:4013 IN IP4 10.61.205.219 a=sendrecv a=rtpmap:96 opus/48000/2 a=fmtp:96 useinbandfec=1 a=rtpmap:9 G722/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/48000 a=fmtp:101 0-16 a=rtpmap:102 telephone-event/8000 a=fmtp:102 0-16 a=ssrc:2039250127 cname:43ec7f3b5b951d53 .

步驟4.若要使用VTR，請運行vtr命令，後跟呼叫者和目標的詳細資訊。例如：

# Command reference:
AS_CLI/ASDiagnostic/Diag> h vtr
This command is used to perform a test call and see the routing results. Please
be careful when performing test calls, it may have an impact on existing real
calls or cause user migration.

Parameters description:
origType   : The type of origination used to trigger the VTR request.
linePort   : The lineport of the originating user.
bwphone    : The originating BroadWorks user phone number.
pstnphone  : The originating PSTN user phone number.
userId     : The originating BroadWorks user Id.
url        : The originating url.
destination: The called user, number or URI.
option     : Additional vtr options.
contact    : The contact URL to use for the test call.
diversion  : The diversion URL to use for the test call.

======================================================================
vtr
    
     
     
       , Choice = {linePort, bwphone, pstnphone, userId, url} 
      
        , String {1 to 80 characters} 
       
         , String {1 to 17 characters} 
        
          , String {1 to 17 characters} 
         
           , String {2 to 161 characters} 
          
            , String {2 to 161 characters} 
           
             , String {1 to 161 characters} [

從Web GUI運行VTR(I)工具

若要從Web GUI運行VTR，請使用以下步驟：

步驟1.導航到https://<AS_FQDN>/Login頁，然後登入到AS Web介面。

步驟2.導覽至System > Utilities > Verify Translation and Routing。

步驟3. 若要使用VTRI，請按一下SIP Message單選按鈕，然後將SIP INVITE消息貼上到輸入欄位中。然後，按一下執行VTR請求連結：

Verify Translation and Routing

步驟4. 要使用VTR，請按一下Parameters單選按鈕並填充所有必填欄位。然後點選執行VTR請求連結：

Verify Translation and Routing Parameters

VTR(I)輸出細分

VTR和VTRI結果的格式類似。它由八個部分組成：

引數或SIP INVITE（僅存在於VTR中；在VTRI中不需要，因為它適用於實際SIP消息）。
建立者資訊。
始發呼叫資訊。
原始轉換結果。
正在終止呼叫資訊。
治療資訊
時間戳。
結果。

註：本文檔中的所有VTR輸出均基於vtr userId <user_id> <destination_number>命令輸出，除非另有說明。

引數或SIP邀請

VTR結果的第一部分是SIP INVITE，或用於模擬呼叫的引數。如果您明確提供SIP INVITE（換句話說，如果您使用VTRI），則此部分不可見。

當源設定為URL或線路/埠時，生成SIP INVITE。例如：

AS_CLI/ASDiagnostic/Diag> vtr linePort 5403362011@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following SIP INVITE to run VTRI command with Lineport
 -------------------------------------------------------
INVITE sip:2012@10.48.93.126 SIP/2.0
Via:SIP/2.0/UDP 127.0.0.1:5061;branch=vtr-unique-via-branch-26
From:"VTR Calling Name"
     
     
       ;tag=26 To:"VTR Called Name" 
      
        Call-ID:26 CSeq:26 INVITE Contact: 
       
         Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REGISTER,UPDATE Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv

如果來源設定為使用者ID或電話（bwphone和pstnphone），則會顯示引數。例如：

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 16
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2012@10.48.93.126:5060
dialedDigits (initial) 2012
deviceEnpoint          5403362011@mleus.lab

建立者資訊

本節顯示有關始發方（呼叫方）的資訊。如果呼叫者是本地BroadWorks使用者，則會顯示有關該使用者的詳細資訊。例如：

=====================================================
===========     ORIGINATOR INFO   ===================
=====================================================
[Orig-Id]	VTR Short form trigger.
[Orig-Id]	No Endpoint.
[Orig-Id]	Originating user type: BroadWorks
[Orig-Id]	User Info
[Orig-Id]	User Id                      = ngnuserB1@mleus.lab
[Orig-Id]	User Uid                     = 110439218
[Orig-Id]	Group Id                     = ngngroupB1
[Orig-Id]	Service Provider Id          = ngnentB1
[Orig-Id]	Reseller Id                  = null
[Orig-Id]	ASCII First Name             = Marek
[Orig-Id]	ASCII Last Name              = Leus
[Orig-Id]	Unicode First Name           = Marek
[Orig-Id]	Unicode Last Name            = Leus
[Orig-Id]	Country Code                 = 1
[Orig-Id]	User Type                    = User
[Orig-Id]	Trunk User Type              = BroadWorks Regular User
[Orig-Id]	(0) Address type             = main
[Orig-Id]	(0) dn                       = +15403362011
[Orig-Id]	(0) extension                = 2011
[Orig-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Orig-Id]	beingRemoved                 = false
[Orig-Id]	configurable CLID            = 5403362010
[Orig-Id]	synchronizationASRSentToNS   = false

始發呼叫資訊

在此部分中，按順序列出呼叫呼叫方端上的事件進展。如果呼叫方是Cisco BroadWorks使用者，則這是執行所分配服務的位置。例如：

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	Resuming event processing after TranslationServiceOrigInstance
[Orig/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
(...)
# Output omitted for clarity
(...)
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/ReleaseWithCauseHandler]	Post Processing RWC for Call.

原始轉換結果

本節提供有關從Cisco BroadWorks網路伺服器請求轉換的資訊。如果需要網路轉換，則顯示有關使用的撥號方案策略的資訊。它還顯示為此目的交換的SIP消息。例如：

=====================================================
===========  ORIGINATING TRANSLATION RESULT =========
=====================================================
[Orig-Xlation/DialPlanPolicy]	--Dial Plan Policy Information--
[Orig-Xlation/DialPlanPolicy]	requiresAccessCodeForPublicCalls = false
[Orig-Xlation/DialPlanPolicy]	allowE164PublicCalls             = false
[Orig-Xlation/DialPlanPolicy]	privateDigitMap                  =
[Orig-Xlation/DialPlanPolicy]	publicDigitMap                   = ([2-9]11|[0-1][2-9]11|0[#T]|00|01[2-9]xx.[#T]|*xx|011x.[#T]|[0-1]xxxxxxx[#T]|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxxxx[#T]|101xxxx.[#T]|11|[2-9][#T])
[Orig-Xlation/DialPlanPolicy]	preferE164FormatForCallbackSvcs  = false

[Orig-Xlation/NetworkUsagePolicy]	Network Usage Policy is - do not force all calls to network -
[Orig-Xlation/NetworkServerINVITE]	Sending INVITE event to network server for Translation Service Originating Side client
[Orig-Xlation/NetworkServerINVITE]	Endpoint Id: callhalf-60487:0
    udp 1128 SIP Bytes OUT to 10.48.93.128:5060
    INVITE sip:2014@10.48.93.128;user=phone;transport=udp SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564-
    From:"Marek Leus"
     
     
       ;tag=1152157837-1674811757564- To: 
      
        Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Contact: 
       
         P-Asserted-Identity:"Marek Leus" 
        
          Privacy:none X-BroadWorks-Correlation-Info:be8fde53-9ba5-4fc4-a788-ee426ed1fe90 Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY Supported: Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [Orig-Xlation/NS-RESPONSE] Got Network Server response for Translation Service Originating Side client udp 394 SIP Bytes IN from 10.48.93.128:49109 SIP/2.0 404 Not found Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564- From:"Marek Leus" 
         
           ;tag=1152157837-1674811757564- To: 
          
            ;tag=1006595920-1674811749882 Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Content-Length:0 [Orig-Xlation/TranslationManager] Translation Client: Translation Service Originating Side call Id is callhalf-60487:0 [Orig-Xlation/TranslationManager] === TranslationResult === [Orig-Xlation/TranslationManager] callType Network [Orig-Xlation/TranslationManager] address 2014 [Orig-Xlation/TranslationManager] addressType main [Orig-Xlation/TranslationManager] isServiceCode false [Orig-Xlation/TranslationManager] sc8Translated false [Orig-Xlation/TranslationManager] sc100Translated false [Orig-Xlation/TranslationManager] oacTranslated false [Orig-Xlation/TranslationManager] carrierPrefixTranslated false [Orig-Xlation/TranslationManager] intraSP false [Orig-Xlation/TranslationManager] alias false [Orig-Xlation/TranslationManager] preExtEmergencyRtgAK null [Orig-Xlation/TranslationManager] === Carrier Info === [Orig-Xlation/TranslationManager] ;csel=noind

終止呼叫資訊

如果呼叫具有有效的目的地，則會顯示有關其身份和終止服務匯流排上的事件的資訊。類似於始發呼叫資訊部分，這是執行目標使用者所分配服務的位置。它還顯示傳送到目的地的SIP INVITE。例如：

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term/CallManagerServiceBus]	CallManagerId is callhalf-60459
[Term/CallManagerServiceBus]	 === Routing TerminationEvent on the Call Manager bus ===

[Term/Term-Id]	Terminating user type: BroadWorks
[Term/Term-Id]	User Info
[Term/Term-Id]	User Id                      = ngnuserB2@mleus.lab
[Term/Term-Id]	User Uid                     = 156778964
[Term/Term-Id]	Group Id                     = ngngroupB1
[Term/Term-Id]	Service Provider Id          = ngnentB1
[Term/Term-Id]	Reseller Id                  = null
[Term/Term-Id]	ASCII First Name             = John
[Term/Term-Id]	ASCII Last Name              = Doe
[Term/Term-Id]	Unicode First Name           = John
[Term/Term-Id]	Unicode Last Name            = Doe
[Term/Term-Id]	Country Code                 = 1
[Term/Term-Id]	User Type                    = User
[Term/Term-Id]	Trunk User Type              = BroadWorks Regular User
[Term/Term-Id]	(0) Address type             = main
[Term/Term-Id]	(0) dn                       = +15403362012
[Term/Term-Id]	(0) extension                = 2012
[Term/Term-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Term/Term-Id]	beingRemoved                 = false
[Term/Term-Id]	configurable CLID            = 5403362010
[Term/Term-Id]	synchronizationASRSentToNS   = false

[Term/CallServiceBus]	CallId is callhalf-60459:0
[Term/CallServiceBus]	 === Routing InvitationEvent on the Terminating Call bus ===

[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	NumberPortabilityQueryServiceTermInstance has processed the event...continue
(...)
# Output omitted for clarity
(...)
[Term/CallManagerServiceBus]	RingTimeoutServiceInstance has processed the event...continue
[Term/SipINVITE]	 Outgoing resulting INVITE for Endpoint Id: callhalf-60459:0
    udp 1195 SIP Bytes OUT to 10.61.71.93:62388
    INVITE sip:5403362012@10.61.71.93:62388;transport=UDP;rinstance=c71abb15b3ff5d4a SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.61.71.93V62388-0-960978525-1694279432-1674811718841-
    From:"Marek Leus"
     
     
       ;tag=1694279432-1674811718841- To:"John Doe" 
      
        Call-ID:BW102838841270123-1135433227@10.48.93.126 CSeq:960978525 INVITE Contact: 
       
         Supported:100rel Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE Call-Info: 
        
          ;appearance-index=1 Recv-Info:x-broadworks-client-session-info Accept:application/media_control+xml,application/sdp,multipart/mixed Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv

治療資訊

此部分僅適用於未成功的呼叫。文中給出了呼叫失敗的詳細原因。還列出了如果呼叫因該原因而失敗，媒體伺服器播放的通告/音調。例如：

=====================================================
===========  TREATMENT INFORMATION          =========
=====================================================
[Treatment/TreatmentsService]	Treatment service processing RWC. Release Cause is FORBIDDEN
[Treatment/TreatmentsService]	defaultAnnouncement isTrtCallFailure.wav
[Treatment/TreatmentsService]	defaultTone is reorder-pcmu.wav

[Treatment/TreatmentsService]	Configurable Treatment NOT used but specific audio treatment files have been provided
[Treatment/TreatmentsService]	audioAnnouncement(s):
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/silence10s.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav

時間戳

呼叫時間戳可用於將VTRI中的事件與XSLogs相關聯。

結果

測試呼叫的最終結果，可能的值為：

允許 — 呼叫可以成功擴展到遠端方。傳出INVITE顯示在「終止呼叫資訊」部分。
已阻止 — 由於某些策略或異常情況，呼叫設定被阻止。原因既可以位於起始端，也可以位於終止端（取決於原因）。
已重定向 — 已重定向呼叫，且無條件。重新導向目標會在報告中識別和顯示。
超時 — 由於某種原因，導致測試呼叫無法正確終止，並且已達到10秒的內部時間限制。可以利用手頭的資訊，但是沒有顯示最終結果。
媒體 — 媒體元件在內部啟動（通常為互動式語音響應[IVR]）以播放特定通知或收集數字。在此情況下，測試呼叫停止，但報告顯示截至此時的事件。

網路拓撲和呼叫流程

為簡單起見，本文檔中使用了一個基本呼叫方案：

軟體電話應用程式直接註冊到AS。
所有使用者都位於同一個組中。
既未使用呼叫前轉，也未使用重定向功能。

呼叫方案

本文檔介紹使用分機2011的使用者按順序撥號的三個場景：

擴展2012，將其分配給已註冊裝置。
分機2012，被分配給一個註冊裝置，但是選擇性呼叫接受服務被配置為拒絕來自2011的呼叫如本螢幕截圖所示：
副檔名2014，未分配給任何使用者。

場景1：呼叫成功

在這種情況下，一個本地使用者按分機撥打另一個本地使用者。讓我們瀏覽此呼叫的VTR輸出以瞭解更多相關資訊：

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 12
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2012@10.48.93.126:5060
dialedDigits (initial) 2012
deviceEnpoint          5403362011@mleus.lab

在VTR結果的第一部分中，可以看到AS如何將引數從vtr命令對映到SIP URL:

來電者：5403362011@mleus.lab
目標：2012@10.48.93.126:5060

=====================================================
===========     ORIGINATOR INFO   ===================
=====================================================
[Orig-Id]	VTR Short form trigger.
[Orig-Id]	No Endpoint.
[Orig-Id]	Originating user type: BroadWorks
[Orig-Id]	User Info
[Orig-Id]	User Id                      = ngnuserB1@mleus.lab
[Orig-Id]	User Uid                     = 110439218
[Orig-Id]	Group Id                     = ngngroupB1
[Orig-Id]	Service Provider Id          = ngnentB1
[Orig-Id]	Reseller Id                  = null
[Orig-Id]	ASCII First Name             = Marek
[Orig-Id]	ASCII Last Name              = Leus
[Orig-Id]	Unicode First Name           = Marek
[Orig-Id]	Unicode Last Name            = Leus
[Orig-Id]	Country Code                 = 1
[Orig-Id]	User Type                    = User
[Orig-Id]	Trunk User Type              = BroadWorks Regular User
[Orig-Id]	(0) Address type             = main
[Orig-Id]	(0) dn                       = +15403362011
[Orig-Id]	(0) extension                = 2011
[Orig-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Orig-Id]	beingRemoved                 = false
[Orig-Id]	configurable CLID            = 5403362010
[Orig-Id]	synchronizationASRSentToNS   = false

然後，由於呼叫者是本地使用者，因此將列印有關使用者的所有詳細資訊。在本節中，您可以瞭解使用者的名字(Marek)和姓氏(Leus)，他們的分機號(2011)是什麼，全號(+15403362011)是什麼，以及他們屬於哪個企業/組(ngnentB1/nggroupB1)。

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60455:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60455:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	Resuming event processing after TranslationServiceOrigInstance
[Orig/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ReturnCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LNDServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LocationControlServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validating origination. Using call type Group
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validation returned disposition Allow - OCP call type: Group

[Orig/CallServiceBus]	ACRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	NPAnnouncementServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFAlwaysFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCFFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DNDFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CPCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ClassmarkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VAOCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ExecutiveAssistantOrigServiceInstance has processed the event...continue
[Orig/VTR_FINAL]	Triggering report.

由於它是一個沒有啟用服務的簡單使用者，因此Originating Call Information部分中的資訊不多。AS會逐個檢查一個服務，並最終轉到VTR的下一部分。它還將此呼叫定義為組呼叫。如果要將此VTR分析與XSLogs相關聯，則可以從此部分提取呼叫半ID(callhalf-60455)，然後使用它在日誌檔案中查詢此呼叫。例如：

bwadmin@as1.mleus.lab$ less XSLog2023.01.27-00.00.00.txt | grep callhalf-60455
2023.01.27 10:28:38:819 CET | Info       | Sip | BCCT Worker #1 | 3104778 | +15403362011 | callhalf-60455
	$ new CHSS > +15403362011 >  > callhalf-60455
2023.01.27 10:28:38:819 CET | FieldDebug | StateReplication | BCCT Worker #1 | 3104779 | +15403362011 | callhalf-60455
2023.01.27 10:28:38:821 CET | Info       | CallP | Call Half Input Adapter 5 | 3104780 | Call Manager | +15403362011 | ngngroupB1 | callhalf-60455

下一節是源轉換結果：

=====================================================
===========  ORIGINATING TRANSLATION RESULT =========
=====================================================
[Orig-Xlation/DialPlanPolicy]	--Dial Plan Policy Information--
[Orig-Xlation/DialPlanPolicy]	requiresAccessCodeForPublicCalls = false
[Orig-Xlation/DialPlanPolicy]	allowE164PublicCalls             = false
[Orig-Xlation/DialPlanPolicy]	privateDigitMap                  =
[Orig-Xlation/DialPlanPolicy]	publicDigitMap                   = ([2-9]11|[0-1][2-9]11|0[#T]|00|01[2-9]xx.[#T]|*xx|011x.[#T]|[0-1]xxxxxxx[#T]|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxxxx[#T]|101xxxx.[#T]|11|[2-9][#T])
[Orig-Xlation/DialPlanPolicy]	preferE164FormatForCallbackSvcs  = false

[Orig-Xlation/NetworkUsagePolicy]	Network Usage Policy is - do not force all calls to network -
[Orig-Xlation/TranslationManager]	Translation Client: Translation Service Originating Side call Id is callhalf-60455:0
[Orig-Xlation/TranslationManager]	  === TranslationResult ===
[Orig-Xlation/TranslationManager]	callType             Group
[Orig-Xlation/TranslationManager]	address             2012
[Orig-Xlation/TranslationManager]	destination uid      156778964
[Orig-Xlation/TranslationManager]	destination user Id  ngnuserB2@mleus.lab
[Orig-Xlation/TranslationManager]	addressType          main
[Orig-Xlation/TranslationManager]	originalAddress      2012
[Orig-Xlation/TranslationManager]	dgcAlternateAddress  2012
[Orig-Xlation/TranslationManager]	isServiceCode           false
[Orig-Xlation/TranslationManager]	sc8Translated           false
[Orig-Xlation/TranslationManager]	sc100Translated         false
[Orig-Xlation/TranslationManager]	oacTranslated           false
[Orig-Xlation/TranslationManager]	carrierPrefixTranslated false
[Orig-Xlation/TranslationManager]	intraSP                 false
[Orig-Xlation/TranslationManager]	alias                   false
[Orig-Xlation/TranslationManager]	preExtEmergencyRtgAK null

從此部分，您可以瞭解為給定呼叫應用了什麼撥號計畫。對於此呼叫，輸出會通知它是組內的呼叫，並定向至使用者ngnuserB2@mleus.lab。下一節將介紹此使用者的詳細資訊：

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term/CallManagerServiceBus]	CallManagerId is callhalf-60459
[Term/CallManagerServiceBus]	 === Routing TerminationEvent on the Call Manager bus ===

[Term/Term-Id]	Terminating user type: BroadWorks
[Term/Term-Id]	User Info
[Term/Term-Id]	User Id                      = ngnuserB2@mleus.lab
[Term/Term-Id]	User Uid                     = 156778964
[Term/Term-Id]	Group Id                     = ngngroupB1
[Term/Term-Id]	Service Provider Id          = ngnentB1
[Term/Term-Id]	Reseller Id                  = null
[Term/Term-Id]	ASCII First Name             = John
[Term/Term-Id]	ASCII Last Name              = Doe
[Term/Term-Id]	Unicode First Name           = John
[Term/Term-Id]	Unicode Last Name            = Doe
[Term/Term-Id]	Country Code                 = 1
[Term/Term-Id]	User Type                    = User
[Term/Term-Id]	Trunk User Type              = BroadWorks Regular User
[Term/Term-Id]	(0) Address type             = main
[Term/Term-Id]	(0) dn                       = +15403362012
[Term/Term-Id]	(0) extension                = 2012
[Term/Term-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Term/Term-Id]	beingRemoved                 = false
[Term/Term-Id]	configurable CLID            = 5403362010
[Term/Term-Id]	synchronizationASRSentToNS   = false

通過此部分，您可以瞭解呼叫者與以前相同的呼叫目標詳細資訊：名字和姓氏(John Doe)、分機(2012)、全號碼(+15403362012)，以及企業/組(ngnentB1/nggroupB1)。

[Term/CallServiceBus]	CallId is callhalf-60459:0
[Term/CallServiceBus]	 === Routing InvitationEvent on the Terminating Call bus ===

[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	NumberPortabilityQueryServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	CMServiceInstance has processed the event...continue
[Term/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Term/CallServiceBus]	OCPTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	ICPServiceInstance has processed the event...continue
[Term/CallServiceBus]	ACRServiceInstance has processed the event...continue
[Term/CallServiceBus/SCRServiceInstance]	Criteria Set(s) evaluated but not triggered:
[Term/CallServiceBus/SCRServiceInstance]
[Term/CallServiceBus/SCRServiceInstance]	Criteria Set:
[Term/CallServiceBus/SCRServiceInstance]	description: Reject_all
[Term/CallServiceBus/SCRServiceInstance]	active: false
[Term/CallServiceBus/SCRServiceInstance]	blackListFlag: false
[Term/CallServiceBus/SCRServiceInstance]	ScheduleCriteria
[Term/CallServiceBus/SCRServiceInstance]	- No Schedule associated
[Term/CallServiceBus/SCRServiceInstance]	- inScheduleRightNow: true
[Term/CallServiceBus/SCRServiceInstance]	CallingPartyAddressCriteria
[Term/CallServiceBus/SCRServiceInstance]	Any Address
[Term/CallServiceBus/SCRServiceInstance]	CallToCriteria
[Term/CallServiceBus/SCRServiceInstance]	CallTo matches ANY

[Term/CallServiceBus]	SCRServiceInstance has processed the event...continue
[Term/CallServiceBus]	PTTTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	LNRServiceInstance has processed the event...continue
[Term/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Term/CallServiceBus]	GroupNightForwardingServiceInstance has processed the event...continue
[Term/CallServiceBus]	FaxMessagingServiceInstance has processed the event...continue
[Term/CallServiceBus]	SCFServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFAlwaysTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	DNDServiceInstance has processed the event...continue
[Term/CallServiceBus]	PersonalAssistantServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallWaitingTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	PreAlertingAnnouncementServiceInstance has processed the event...continue
[Term/CallServiceBus]	AnswerTimerServiceInstance has processed the event...continue
[Term/CallServiceBus]	VMServiceInstance has processed the event...continue
[Term/CallServiceBus]	RedirectionServiceInstance has processed the event...continue
[Term/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
[Term/CallServiceBus]	ExecutiveTermServiceInstance has processed the event...continue
[Term/CallServiceBus]	ExecutiveAssistantTermServiceInstance has processed the event...continue

在此部分中，還將檢查所有服務。只有一項服務分配給此使用者（選擇性呼叫接受），但唯一的條件集(Reject_2011)處於非活動狀態。因此，它不會被觸發，並且VTR分析將移到「終止呼叫資訊」部分的下一個階段，該階段顯示分析的最終結果。

[Term/CallManagerServiceBus]	CallManagerId is callhalf-60459
[Term/CallManagerServiceBus]	 === Routing InvitationEvent on the Call Manager bus ===

[Term/CallManagerServiceBus]	AccessRoutingServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	VAOServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	TSDServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	SCAPServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	CallCenterAgentServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	FlashServiceInstance has processed the event...continue
[Term/CallManagerServiceBus]	RingTimeoutServiceInstance has processed the event...continue
[Term/SipINVITE]	 Outgoing resulting INVITE for Endpoint Id: callhalf-60459:0
    udp 1195 SIP Bytes OUT to 10.61.71.93:62388
    INVITE sip:5403362012@10.61.71.93:62388;transport=UDP;rinstance=c71abb15b3ff5d4a SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.61.71.93V62388-0-960978525-1694279432-1674811718841-
    From:"Marek Leus"
     
     
       ;tag=1694279432-1674811718841- To:"John Doe" 
      
        Call-ID:BW102838841270123-1135433227@10.48.93.126 CSeq:960978525 INVITE Contact: 
       
         Supported:100rel Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE Call-Info: 
        
          ;appearance-index=1 Recv-Info:x-broadworks-client-session-info Accept:application/media_control+xml,application/sdp,multipart/mixed Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv

在此部分中，您可以看到如果最終目的地是真正的呼叫，則將擴展到最終目的地的INVITE消息。還可以提取可用於在日誌檔案中跟蹤此呼叫的callhalf ID(callhalf-60459):

bwadmin@as1.mleus.lab$ less XSLog2023.01.27-00.00.00.txt | grep callhalf-60459
2023.01.27 10:28:38:827 CET | Info       | Sip | Call Half Input Adapter 5 | 3104796 | +15403362012 | callhalf-60459 | 5ff0de06-90a9-4bb6-892a-610d7441ed69
	$ new CHSS > +15403362012 > callhalf-60455:0 > callhalf-60459
2023.01.27 10:28:38:827 CET | FieldDebug | StateReplication | Call Half Input Adapter 5 | 3104797 | +15403362012 | callhalf-60459 | 5ff0de06-90a9-4bb6-892a-610d7441ed69
2023.01.27 10:28:38:827 CET | Info       | CallP | Call Half Input Adapter 0 | 3104798 | Call Manager | +15403362012 | ngngroupB1 | callhalf-60459 | 5ff0de06-90a9-4bb6-892a-610d7441ed69

最後兩節顯示此分析的最終結果和時間戳：

=====================================================
===========           TIMESTAMPS            =========
=====================================================
[Timestamps]	Start time = 2023.01.27 10:28:38:819 CET
[Timestamps]	End time   = 2023.01.27 10:28:38:846 CET

=====================================================
===========   RESULT: ALLOWED         ===============
=====================================================

案例2：選擇性呼叫接受服務拒絕的呼叫

在此場景中，一個本地使用者通過分機再次撥打另一個本地使用者；但是，這次將選擇性呼叫接受配置為拒絕此呼叫。讓我們瀏覽此呼叫的VTR輸出以瞭解更多相關資訊：

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2012
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 16
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2012@10.48.93.126:5060
dialedDigits (initial) 2012
deviceEnpoint          5403362011@mleus.lab

I在VTR結果的第一部分，可以看到AS如何將vtr命令的引數對映到SIP URL:

來電者：5403362011@mleus.lab
目標：2012@10.48.93.126:5060

由於它與第一個場景中的呼叫者完全相同，因此此場景的「建立者資訊」部分也完全相同。因此，為了清楚起始Call Information部分會跳過此部分，並繼續對其進行分析：

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	Resuming event processing after TranslationServiceOrigInstance
[Orig/CallServiceBus]	SecurityClassificationServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ReturnCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LNDServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LocationControlServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validating origination. Using call type Group
[Orig/CallServiceBus/OCPOriginatorServiceInstance]	Validation returned disposition Allow - OCP call type: Group

[Orig/CallServiceBus]	ACRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	NPAnnouncementServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFAlwaysFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCFFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DNDFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CPCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ClassmarkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VAOCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/CallServiceBus]	SCRFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	ExecutiveAssistantOrigServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallId is callhalf-60507:0
[Orig/CallServiceBus]	 === Routing ReleaseWithCauseEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has processed the event...continue
[Orig/CallServiceBus]	CallTransferRecallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallParkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	Treatments Service would have started the announcement (see Treatment Section for more details).
[Orig/CallServiceBus/TreatmentsServiceInstance]	Letting event continue to release test call resources properly

[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFBusyFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNoAnswerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNotReachableFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DirectedCallPickupServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DPUBIServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	MusicOnHoldServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/ReleaseWithCauseHandler]	Post Processing RWC for Call.

此部分顯示AS知道目標號碼，並將呼叫定義為組呼叫。但是，您還可以確定是否有問題。首先，涉及「始發呼叫匯流排上的Routing ReleaseWithCauseEvent」語句和TreatmentServiceInstance。同樣，此部分以ReleaseWithCauseHandler結尾。

下一節是Originating Translation Result，它與場景1中的部分完全相同，因為呼叫被定向到同一使用者。因此，為了清楚起見，省略了它。差異顯示在「終止呼叫資訊」部分：

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term/CallManagerServiceBus]	CallManagerId is callhalf-60511
[Term/CallManagerServiceBus]	 === Routing TerminationEvent on the Call Manager bus ===

[Term/Term-Id]	Terminating user type: BroadWorks
[Term/Term-Id]	User Info
[Term/Term-Id]	User Id                      = ngnuserB2@mleus.lab
[Term/Term-Id]	User Uid                     = 156778964
[Term/Term-Id]	Group Id                     = ngngroupB1
[Term/Term-Id]	Service Provider Id          = ngnentB1
[Term/Term-Id]	Reseller Id                  = null
[Term/Term-Id]	ASCII First Name             = John
[Term/Term-Id]	ASCII Last Name              = Doe
[Term/Term-Id]	Unicode First Name           = John
[Term/Term-Id]	Unicode Last Name            = Doe
[Term/Term-Id]	Country Code                 = 1
[Term/Term-Id]	User Type                    = User
[Term/Term-Id]	Trunk User Type              = BroadWorks Regular User
[Term/Term-Id]	(0) Address type             = main
[Term/Term-Id]	(0) dn                       = +15403362012
[Term/Term-Id]	(0) extension                = 2012
[Term/Term-Id]	activeAsComponentID          = [vnf=null,vnfc=1]
[Term/Term-Id]	beingRemoved                 = false
[Term/Term-Id]	configurable CLID            = 5403362010
[Term/Term-Id]	synchronizationASRSentToNS   = false

[Term/CallServiceBus]	CallId is callhalf-60511:0
[Term/CallServiceBus]	 === Routing InvitationEvent on the Terminating Call bus ===

[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	NumberPortabilityQueryServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	CMServiceInstance has processed the event...continue
[Term/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Term/CallServiceBus]	OCPTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	ICPServiceInstance has processed the event...continue
[Term/CallServiceBus]	ACRServiceInstance has processed the event...continue
[Term/CallServiceBus/SCAServiceInstance]	Criteria Set evaluated and triggered:
[Term/CallServiceBus/SCAServiceInstance]
[Term/CallServiceBus/SCAServiceInstance]	Criteria Set:
[Term/CallServiceBus/SCAServiceInstance]	description: Reject_2011
[Term/CallServiceBus/SCAServiceInstance]	active: true
[Term/CallServiceBus/SCAServiceInstance]	blackListFlag: true
[Term/CallServiceBus/SCAServiceInstance]	ScheduleCriteria
[Term/CallServiceBus/SCAServiceInstance]	- No Schedule associated
[Term/CallServiceBus/SCAServiceInstance]	- inScheduleRightNow: true
[Term/CallServiceBus/SCAServiceInstance]	CallingPartyAddressCriteria
[Term/CallServiceBus/SCAServiceInstance]	+15403362011
[Term/CallServiceBus/SCAServiceInstance]	CallToCriteria
[Term/CallServiceBus/SCAServiceInstance]	CallTo matches ANY

[Term/CallServiceBus]	SCAServiceInstance has CONSUMED the event.
[Term/CallServiceBus]	CallId is callhalf-60511:0
[Term/CallServiceBus]	 === Routing ReleaseWithCauseEvent on the Terminating Call bus ===
[Term/CallServiceBus]	TranslationServiceTermInstance has processed the event...continue
[Term/CallServiceBus]	CMServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallParkServiceInstance has processed the event...continue
[Term/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Term/CallServiceBus]	OCPTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	PTTTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	LNRServiceInstance has processed the event...continue
[Term/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Term/CallServiceBus]	PersonalAssistantServiceInstance has processed the event...continue
[Term/CallServiceBus]	CallWaitingTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFBusyTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	AnswerTimerServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFNotReachableTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	CFNoAnswerTerminatorServiceInstance has processed the event...continue
[Term/CallServiceBus]	VMServiceInstance has processed the event...continue
[Term/CallServiceBus]	DirectedCallPickupServiceInstance has processed the event...continue
[Term/CallServiceBus]	DPUBIServiceInstance has processed the event...continue
[Term/CallServiceBus]	RedirectionServiceInstance has processed the event...continue
[Term/CallServiceBus]	MusicOnHoldServiceInstance has processed the event...continue

您可以看到，這一次Reject_2011標準集處於活動狀態。因此，選擇性呼叫接受服務被觸發。因此，在終止呼叫匯流排上引發ReleaseWithCauseEvent。AS檢查其餘的服務並轉到Treatment Information部分：

=====================================================
===========  TREATMENT INFORMATION          =========
=====================================================
[Treatment/TreatmentsService]	Treatment service processing RWC. Release Cause is FORBIDDEN
[Treatment/TreatmentsService]	defaultAnnouncement isTrtCallFailure.wav
[Treatment/TreatmentsService]	defaultTone is reorder-pcmu.wav

[Treatment/TreatmentsService]	Configurable Treatment NOT used but specific audio treatment files have been provided
[Treatment/TreatmentsService]	audioAnnouncement(s):
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/silence10s.wav
[Treatment/TreatmentsService]	https://10.48.93.126/media/en/TrtSelectCallReject.wav

通過本節內容，您可以瞭解呼叫失敗（已禁止）的原因以及要播放TrtSelectCallReject.wav通告。

最後兩節顯示此分析的最終結果和時間戳：

=====================================================
===========           TIMESTAMPS            =========
=====================================================
[Timestamps]	Start time = 2023.01.27 10:31:29:425 CET
[Timestamps]	End time   = 2023.01.27 10:31:29:466 CET

=====================================================
===========   RESULT: BLOCKED         ===============
=====================================================

場景3：呼叫未分配的號碼

在這種情況下，一個本地使用者撥打另一個未分配的副檔名。讓我們瀏覽此呼叫的VTR輸出以瞭解更多相關資訊：

AS_CLI/ASDiagnostic/Diag> vtr userId ngnuserB1@mleus.lab 2014
VTR Result:
 --------------------------------------------------------
Using following parameters to run short form VTR command
 -------------------------------------------------------
VtrOriginationEvent
vtrKey                 14
origUserId             ngnuserB1@mleus.lab
origUserUid            110439218
requestURI equivalent  2014@10.48.93.126:5060
dialedDigits (initial) 2014
deviceEnpoint          5403362011@mleus.lab

在VTR結果的第一部分中，可以看到AS如何將vtr命令的引數對映到SIP URL:

來電者：5403362011@mleus.lab
目標：2014@10.48.93.126:5060

=====================================================
===========  ORIGINATING CALL INFO   ================
=====================================================
[Orig/CallServiceBus]	CallId is callhalf-60487:0
[Orig/CallServiceBus]	 === Routing InvitationEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has CONSUMED the event.
[Orig/CallServiceBus]	CallId is callhalf-60487:0
[Orig/CallServiceBus]	 === Routing ReleaseWithCauseEvent on the Originating Call bus ===

[Orig/CallServiceBus]	TranslationServiceOrigInstance has processed the event...continue
[Orig/CallServiceBus]	CallTransferRecallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	GETSServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EnhancedCallLogsServiceInstance has processed the event...continue
[Orig/CallServiceBus]	OCPOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallCenterAgentCallServiceInstance has processed the event...continue
[Orig/CallServiceBus]	PTTOriginatorServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CallParkServiceInstance has processed the event...continue
[Orig/CallServiceBus]	LegacyACBServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AutomaticCallbackServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	TreatmentsServiceInstance has processed the event...continue
[Orig/CallServiceBus/TreatmentsServiceInstance]	Treatments Service would have started the announcement (see Treatment Section for more details).
[Orig/CallServiceBus/TreatmentsServiceInstance]	Letting event continue to release test call resources properly

[Orig/CallServiceBus]	CallWaitingFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFBusyFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNoAnswerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	VMServiceInstance has processed the event...continue
[Orig/CallServiceBus]	CFNotReachableFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DirectedCallPickupServiceInstance has processed the event...continue
[Orig/CallServiceBus]	DPUBIServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AnswerTimerFACServiceInstance has processed the event...continue
[Orig/CallServiceBus]	MusicOnHoldServiceInstance has processed the event...continue
[Orig/CallServiceBus]	AoCServiceInstance has processed the event...continue
[Orig/CallServiceBus]	EmergencyCallTimerServiceInstance has processed the event...continue
[Orig/ReleaseWithCauseHandler]	Post Processing RWC for Call.

從本節中，您已經可以知道出現了問題。首先，有一個「始發呼叫匯流排上的路由發佈WithCauseEvent」語句，而不是「始發呼叫匯流排上的路由邀請事件」語句。然後，會涉及TreatmentServiceInstance語句。最後，該節以ReleaseWithCauseHandler語句結尾。

=====================================================
===========  ORIGINATING TRANSLATION RESULT =========
=====================================================
[Orig-Xlation/DialPlanPolicy]	--Dial Plan Policy Information--
[Orig-Xlation/DialPlanPolicy]	requiresAccessCodeForPublicCalls = false
[Orig-Xlation/DialPlanPolicy]	allowE164PublicCalls             = false
[Orig-Xlation/DialPlanPolicy]	privateDigitMap                  =
[Orig-Xlation/DialPlanPolicy]	publicDigitMap                   = ([2-9]11|[0-1][2-9]11|0[#T]|00|01[2-9]xx.[#T]|*xx|011x.[#T]|[0-1]xxxxxxx[#T]|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxxxx[#T]|101xxxx.[#T]|11|[2-9][#T])
[Orig-Xlation/DialPlanPolicy]	preferE164FormatForCallbackSvcs  = false

[Orig-Xlation/NetworkUsagePolicy]	Network Usage Policy is - do not force all calls to network -
[Orig-Xlation/NetworkServerINVITE]	Sending INVITE event to network server for Translation Service Originating Side client
[Orig-Xlation/NetworkServerINVITE]	Endpoint Id: callhalf-60487:0
    udp 1128 SIP Bytes OUT to 10.48.93.128:5060
    INVITE sip:2014@10.48.93.128;user=phone;transport=udp SIP/2.0
    Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564-
    From:"Marek Leus"
     
     
       ;tag=1152157837-1674811757564- To: 
      
        Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Contact: 
       
         P-Asserted-Identity:"Marek Leus" 
        
          Privacy:none X-BroadWorks-Correlation-Info:be8fde53-9ba5-4fc4-a788-ee426ed1fe90 Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY Supported: Max-Forwards:10 Content-Type:application/sdp Content-Length:410 v=0 o=- 123 123 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 16428 RTP/AVP 0 2 4 8 18 96 97 98 100 101 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:4 G723/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729a/8000 a=rtpmap:96 G726-40/8000 a=rtpmap:97 G726-24/8000 a=rtpmap:98 G726-16/8000 a=rtpmap:100 NSE/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 a=sendrecv [Orig-Xlation/NS-RESPONSE] Got Network Server response for Translation Service Originating Side client udp 394 SIP Bytes IN from 10.48.93.128:49109 SIP/2.0 404 Not found Via:SIP/2.0/UDP 10.48.93.126;branch=z9hG4bKBroadWorks.-iom24c-10.48.93.128V5060-0-960997887-1152157837-1674811757564- From:"Marek Leus" 
         
           ;tag=1152157837-1674811757564- To: 
          
            ;tag=1006595920-1674811749882 Call-ID:BW1029175642701231892598132@10.48.93.126 CSeq:960997887 INVITE Content-Length:0 [Orig-Xlation/TranslationManager] Translation Client: Translation Service Originating Side call Id is callhalf-60487:0 [Orig-Xlation/TranslationManager] === TranslationResult === [Orig-Xlation/TranslationManager] callType Network [Orig-Xlation/TranslationManager] address 2014 [Orig-Xlation/TranslationManager] addressType main [Orig-Xlation/TranslationManager] isServiceCode false [Orig-Xlation/TranslationManager] sc8Translated false [Orig-Xlation/TranslationManager] sc100Translated false [Orig-Xlation/TranslationManager] oacTranslated false [Orig-Xlation/TranslationManager] carrierPrefixTranslated false [Orig-Xlation/TranslationManager] intraSP false [Orig-Xlation/TranslationManager] alias false [Orig-Xlation/TranslationManager] preExtEmergencyRtgAK null [Orig-Xlation/TranslationManager] === Carrier Info === [Orig-Xlation/TranslationManager] ;csel=noind

「始發轉換結果」部分可以深入瞭解呼叫失敗的原因。從輸出中可明顯看出，AS嘗試使用NS解析2014編號，但它返回404 Not Found錯誤響應。

由於呼叫無法擴展至其目標，因此「終止呼叫資訊」部分非常簡短：

=====================================================
===========  TERMINATING CALL INFO   ================
=====================================================
[Term]	Terminating call processing information has not been populated

相反，會顯示「處理資訊」部分，其中包含有關如何處理失敗呼叫的資訊：

=====================================================
===========  TREATMENT INFORMATION          =========
=====================================================
[Treatment/TreatmentsService]	Treatment service processing RWC. Release Cause is USER_NOT_FOUND
[Treatment/TreatmentsService]	defaultAnnouncement isTrtUnknownUser.wav
[Treatment/TreatmentsService]	defaultTone is reorder-pcmu.wav

[Treatment/TreatmentsService]	Treatment playing default announcement https://10.48.93.126/media/en/TrtUnknownUser.wav

本節提供呼叫失敗的原因(USER_NOT_FOUND)，並通知要播放TrtUnknownUser.wav通知和/或重新排序 — pcmu.wav音。它還指明了與媒體伺服器對話時用於指示其播放正確公告的路徑。

最後兩節顯示此分析的最終結果和時間戳：

=====================================================
===========           TIMESTAMPS            =========
=====================================================
[Timestamps]	Start time = 2023.01.27 10:29:17:525 CET
[Timestamps]	End time   = 2023.01.27 10:29:17:669 CET

=====================================================
===========   RESULT: BLOCKED         ===============
=====================================================

修訂記錄

修訂	發佈日期	意見
1.0	31-Jan-2023	初始版本

由思科工程師貢獻

Marek Leus
技術諮詢工程師

這份文件是否有所幫助？

意見

讓思科協助您

開啟支援問題單
(需有思科服務合約)

排除VTR和VTRI的呼叫建立問題

無偏見用語

關於此翻譯

目錄

簡介

背景資訊

必要條件

需求

採用元件

VTR(I)工具的用法

從CLI運行VTR(I)工具

從Web GUI運行VTR(I)工具

VTR(I)輸出細分

引數或SIP邀請

建立者資訊

始發呼叫資訊

原始轉換結果

終止呼叫資訊

治療資訊

時間戳

結果

網路拓撲和呼叫流程

呼叫方案

場景1：呼叫成功

案例2：選擇性呼叫接受服務拒絕的呼叫

場景3：呼叫未分配的號碼

修訂記錄

由思科工程師貢獻

這份文件是否有所幫助？

讓思科協助您