この製品のドキュメントセットは、偏向のない言語を使用するように配慮されています。このドキュメントセットでの偏向のない言語とは、年齢、障害、性別、人種的アイデンティティ、民族的アイデンティティ、性的指向、社会経済的地位、およびインターセクショナリティに基づく差別を意味しない言語として定義されています。製品ソフトウェアのユーザインターフェイスにハードコードされている言語、RFP のドキュメントに基づいて使用されている言語、または参照されているサードパーティ製品で使用されている言語によりドキュメントに例外が存在する場合があります。シスコのインクルーシブ ランゲージの取り組みの詳細は、こちらをご覧ください。
シスコは世界中のユーザにそれぞれの言語でサポート コンテンツを提供するために、機械と人による翻訳を組み合わせて、本ドキュメントを翻訳しています。ただし、最高度の機械翻訳であっても、専門家による翻訳のような正確性は確保されません。シスコは、これら翻訳の正確性について法的責任を負いません。原典である英語版(リンクからアクセス可能)もあわせて参照することを推奨します。
このドキュメントでは、Application Server(AS)のVerify Translation and Routing(VTR)ツールを使用して、一般的なコールセットアップの問題をトラブルシューティングする方法について説明します。
.
BroadWorks Application Serverには、コールセットアップの問題のトラブルシューティングに使用できる組み込みツールが2つあります。VTRとVerify Translation and Routing INVITE(VTRI)です。これら2つのツールの目的は同じで、コマンド入力の違いによって異なります。
注意:ネットワークサーバ(NS)でもVTRおよびVTRIコマンドを使用できますが、出力構造はASとは異なります。このドキュメントではAS VTR(I)に焦点を当てており、NS VTR(I)での作業中にリファレンスとして使用することはできません。
AS VTRの完全なコマンドリファレンスについては、『Application Server VTR Administration Guide』を参照してください。
次の項目に関する知識があることが推奨されます。
このドキュメントの情報は、BroadWorks ASバージョンR24に基づくものです。 ただし、他のソフトウェアバージョンの動作も同様です。
このドキュメントの情報は、特定のラボ環境にあるデバイスに基づいて作成されました。このドキュメントで使用するすべてのデバイスは、初期(デフォルト)設定の状態から起動しています。本稼働中のネットワークでは、各コマンドによって起こる可能性がある影響を十分確認してください。
VTR分析は、コマンドラインインターフェイス(CLI)とWebインターフェイスの両方からトリガーできます。
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を実行するには、次の手順を使用します。
ステップ 1:https://<AS_FQDN>/Loginページに移動し、AS Webインターフェイスにログインします。
ステップ 2:[System] > [Utilities] > [Verify Translation and Routing] に移動します。
ステップ 3: VTRIを使用するには、[SIP Message] オプションボタンをクリックし、SIP INVITEメッセージを入力フィールドに貼り付けます。次に、[Execute VTR request] リンクをクリックします。
ステップ 4: VTRを使用するには、[Parameters] オプションボタンをクリックし、すべての必須フィールドに値を入力します。次に、[Execute VTR request] リンクをクリックします。
VTRとVTRIの結果の形式は類似しています。8つのセクションで構成されています。
注:特に明記されていない限り、このドキュメントのすべてのVTR出力は、vtr userId <user_id> <destination_number>コマンドの出力に基づいています。
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 Network Serverから要求された変換に関する情報を提供します。ネットワーク変換が必要な場合は、使用されているダイヤルプランポリシーに関する情報が表示されます。この目的のために交換された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
コールに有効な宛先がある場合は、そのIDと終端側のサービスバス上のイベントに関する情報が表示されます。発信呼情報セクションと同様に、宛先ユーザに割り当てられたサービスが実行される場所です。また、宛先に送信された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と関連付けることができます。
テストコールの最終結果です。可能な値は次のとおりです。
簡単にするために、このドキュメントでは基本的なコールシナリオを使用します。
このドキュメントでは、内線番号2011のユーザが次の3つのシナリオを順番に説明します。
このシナリオでは、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にマッピングする方法を確認できます。
=====================================================
=========== 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/ngngroupB1)を確認できます。
=====================================================
=========== 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と関連付ける場合は、このセクションからcallhalf 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:
=====================================================
=========== 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/ngngroupB1))を学習します。
[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
このセクションの次の部分では、すべてのサービスがチェックされます。このユーザに割り当てられているサービスは1つだけですが(選択的コール受け入れ)、基準セット(Reject_2011)のみが非アクティブです。したがって、VTR分析はトリガーされず、分析の最終結果を示す[Terminating Call Info]セクションの次のステージに移動します。
[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
最後の2つのセクションでは、この分析の最終結果とタイムスタンプを示します。
=====================================================
=========== 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 ===============
=====================================================
このシナリオでは、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 16
origUserId ngnuserB1@mleus.lab
origUserUid 110439218
requestURI equivalent 2012@10.48.93.126:5060
dialedDigits (initial) 2012
deviceEnpoint 5403362011@mleus.lab
IVTR結果の最初のセクションでは、ASがvtrコマンドからSIP URLにパラメータをマッピングする方法を確認できます。
最初のシナリオと発信者がまったく同じであるため、このシナリオの[Originator Information]セクションもまったく同じです。したがって、分かりやすくするために省略され、分析は引き続き[Originating 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 on the Originating Call bus」ステートメントがあり、TreatmentServiceInstanceが関係しています。同様に、セクションはReleaseWithCauseHandlerで終了します。
次のセクションはOriginating Translation Resultです。これは、コールが同じユーザに送信されるため、シナリオ1のセクションと同じです。したがって、明確にするために省略されます。この違いは、[Terminating Call Info]セクションに表示されます。
=====================================================
=========== 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
このセクションから、コール失敗の理由(FORBIDDEN)とTrtSelectCallReject.wavアナウンスが再生される理由を確認できます。
最後の2つのセクションでは、この分析の最終結果とタイムスタンプを示します。
=====================================================
=========== 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 ===============
=====================================================
このシナリオでは、1人のローカルユーザが、割り当てられていない別の内線番号をダイヤルします。このコールの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にパラメータをマッピングする方法を確認できます。
最初のシナリオと発信者がまったく同じであるため、このシナリオの[Originator Information]セクションもまったく同じです。したがって、分かりやすくするために省略され、分析は引き続き[Originating Call Information]セクションに進みます。
=====================================================
=========== 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.
このセクションから、何か問題があることがすでにわかります。最初に、「Routing InvitationEvent on the Originating Call bus」ステートメントの代わりに、「Routing ReleaseWithCauseEvent on the Originating Call bus」ステートメントがあります。次に、関連する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
[Originating Translation Result]セクションには、コールが成功しない理由に関する情報が表示されます。ASがNSで2014番号を解決しようとしていることは出力から明らかですが、404 Not Foundエラー応答が返されます。
コールを宛先まで拡張できないため、[Terminating Call Info]セクションは非常に短くなります。
=====================================================
=========== TERMINATING CALL INFO ================
=====================================================
[Term] Terminating call processing information has not been populated
代わりに、失敗したコールの処理方法に関する情報を含む[Treatment Information]セクションがあります。
=====================================================
=========== 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アナウンスまたはreorder-pcmu.wavトーンが再生されることを通知します。また、メディアサーバとの対話で使用されるパスを指定して、適切なアナウンスを再生するように指示します。
最後の2つのセクションでは、この分析の最終結果とタイムスタンプを示します。
=====================================================
=========== 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 |
初版 |