Windows版Jabber呼叫流分析过程
目录
简介
本文档介绍用于分析Windows版Cisco Jabber中的呼叫流的过程。
先决条件
要求
Cisco建议您了解Windows 9.x版的Cisco Jabber。
使用的组件
本文档中的信息基于Windows版Cisco Jabber 9.x。
本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始（默认）配置。如果您使用的是真实网络，请确保您已经了解所有命令的潜在影响。
分析Windows版Cisco Jabber中的呼叫流
要确定呼叫在Windows版Cisco Jabber中的开始和结束时间，请在记事本++中打开csf-unified.log文件，然后搜索CALL_EVENT。要查找呼叫的第一行，请在CALL_EVENT语句后找到Initial:
2013-02-24 18:22:07,362 INFO [0x000009e4][control\CallControlManagerImpl.cpp(2021)]
[csf.ecc.evt] [ecc::CallControlManagerImpl::notifyCallEventObservers] -
CALL_EVENT: evCreated,
0x005B1818, Initial, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_NONE, CalledPartyNumber: ,
CallingPartyNumber: ,
CallInstance: -1, Status: , GCID: , IsConference: 0, IsCallSelected: 0, CapabilitySet:
Jabber日志术语
在Jabber呼叫流程中注意以下关键字：
呼叫状态
- 初始 — 呼叫处于设置中，Jabber确定呼叫是否呼入/呼出，并预拨呼叫/被叫电话号码。
- 摘机 — Jabber电话摘机。
- 拨号 — 拨打被叫电话号码号码。
- 继续 — 数字将传送到Cisco Unified Communications Manager(CUCM)并进行处理。
- RingOut — 拨打号码并将振铃发送到远程端。
- 已连接 — 远程端已应答，且已建立连接。
- 挂机 — Jabber电话挂机。
CC_CALL_TYPE — 这将在初始化后从“NONE”更改为“OUTGOING”或“INCOMING”，具体取决于呼叫是发送还是接收。
呼叫ID — 呼叫状态之前的十六进制数字(0x005B1818)是Jabber呼叫ID，它在每次呼叫的持续时间内保持一致。当下一个呼叫发生时，该呼叫将递增。
CSF-UNIFIED.LOG
如果使用记事本++，则可以使用在当前文档中查找全部选项，该选项显示整个呼叫流。如下所示（为便于查看，时间戳和信息方括号被删除）：
CALL_EVENT: evCreated, 0x005B1818, Initial, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_NONE,
CalledPartyNumber: , CallingPartyNumber: , CallInstance: -1, Status: ,
GCID: , IsConference: 0,
IsCallSelected: 0, CapabilitySet:
CALL_EVENT: evInfoChanged, 0x005B1818, Initial, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: , CallingPartyNumber: , CallInstance: 1, Status: ,
GCID: , IsConference: 0,
IsCallSelected: 0, CapabilitySet: canOriginateCall,canDialVoicemail
CALL_EVENT: evInfoChanged, 0x005B1818, Initial, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: 1001, CallingPartyNumber: 1000, CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet: canOriginateCall,canDialVoicemail
CALL_EVENT: evStateChanged, 0x005B1818, OffHook, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: 1001, CallingPartyNumber: 1000, CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet: canEndCall,canSendDigit
CALL_EVENT: evStateChanged, 0x005B1818, Dialing, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: 1001, CallingPartyNumber: 1000, CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet: canEndCall,canSendDigit
CALL_EVENT: evStateChanged, 0x005B1818, Proceed, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: 1001, CallingPartyNumber: 1000, CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet: canEndCall
CALL_EVENT: evStateChanged, 0x005B1818, RingOut, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: 1001, CallingPartyNumber: 1000, CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet: canEndCall,canDirectTransfer
CALL_EVENT: evCallStarted, 0x005B1818, Connected, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: 1001, CallingPartyNumber: 1000, CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet: canHold,canEndCall,canSendDigit,canCallPark,
canDirectTransfer,
canJoinAcrossLine
CALL_EVENT: evStateChanged, 0x005B1818, OnHook, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: 1001, CallingPartyNumber: 1000, CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet:
CALL_EVENT: evDestroyed, 0x005B1818, OnHook, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_OUTGOING,
CalledPartyNumber: , CallingPartyNumber: , CallInstance: 1, Status: ,
GCID: , IsConference:
0, IsCallSelected: 0, CapabilitySet:
当Jabber首次摘机或拨号时，将显示输出，以及主叫方和被叫方号码。对于呼入呼叫，将显示类似的呼叫流模式。但是，CC_CALL_TYPE不同：
2013-02-24 18:22:07,130 INFO [0x00000ec0] [control\CallControlManagerImpl.cpp(2001)]
[csf.ecc.evt][ecc::CallControlManagerImpl::notifyCallEventObservers] -
CALL_EVENT: evCreated, 0x10003, Initial,
CC_ATTR_NORMAL, CC_CALL_TYPE_INCOMING, CalledPartyNumber: 1001,
CallingPartyNumber: 1000,
CallInstance: 1, Status: , GCID: , IsConference: 0, IsCallSelected: 0, CapabilitySet:
Office集成（在Jabber日志中点击呼叫）
对于通过Microsoft Office Integration发出的呼叫，在呼叫流程前添加了一条额外线路。如果搜索“开始语音呼叫使用”，它提供日志中执行“单击以呼叫”功能的每个点。例如，来自Microsoft Outlook的联系人(右键单击和呼叫)的呼叫如下所示：
2013-02-24 18:42:18,912 INFO [0x000009e0] [\ExtensionProviderFunctionsImpl.cpp(235)]
[cuc-extension-provider] [StartVoiceCallImpl2] - Starting voice call with 1001
几毫秒后，同样的“Initial”关键字开始：
2013-02-24 18:42:18,915 INFO [0x0000053c] [control\CallControlManagerImpl.cpp(2021)]
[csf.ecc.evt][ecc::CallControlManagerImpl::notifyCallEventObservers] -
CALL_EVENT: evCreated, 0x00EF3BA0,Initial, CC_ATTR_NOT_DEFINED, CC_CALL_TYPE_NONE,
CalledPartyNumber: , CallingPartyNumber: ,
CallInstance: -1, Status: , GCID: , IsConference: 0, IsCallSelected: 0, CapabilitySet:
注意Click to Call函数中的[cuc-extension-provider]部分。如果您在Jabber日志中搜索此项，它还会提供从Microsoft Office Integration传送的任何结果。
反馈