本文档介绍Cisco Conductor与Cisco Unified Communications Manager(CUCM)之间的HTTPS集成时遇到的问题。
Conductor与CUCM之间的HTTPS集成用于临时会议失败。出现此问题时,有两种主要症状:
以下各节将进一步详细解释这两种症状。
在以下两种情况中都会观察到此症状:
这些图像显示了这两种场景的注册状态:
此注册失败的根本原因是用于HTTPS/传输层安全(TLS)的库。 TLS握手失败,加密警报,因为库不支持HTTPS/TLS的IP地址格式的统一资源标识符(URI)。
在高级别上,TLS握手的发生类似于:
当对上述症状应用解决方法时,会发现此症状,导致临时会议的创建失败:
此症状的根本原因是Conductor,当URI使用FQDN构建时,Conductor无法处理conference.create Application Program Interface(API)调用。
然后,Conductor将记录此事件:
Event="An API request could not be processed." Command="conference.create"
Conference_name="001035060001" Detail="<Fault 201:
'Request received to a non ad-hoc IP address'>
为了使HTTPS集成和临时会议创建在CUCM和Conductor之间正常运行,需要修复Cisco Bug ID CSCut22572。此修复应允许将HTTPS目标地址配置为FQDN。
Cisco Bug ID CSCut10254中描述的功能增强功能将允许使用IP地址配置HTTPS目标地址,无论是手动/覆盖配置还是SIP中继。
SIP中继服务状态有时可能显示为无服务或关闭。当出现以下情况时,会发生这种情况:
示例如下:
这的根本原因是Conductor,它不回复从CUCM发送的SIP选项消息。SIP URI基于目标地址(本例中为FQDN)构建,Conductor需要IP地址表示法:
2015-03-27T18:00:23+01:00 conductorcucm b2bua[28262]: UTCTime="2015-03-27 17:00:23,269"
Module="network.sip" Level="DEBUG": Action="Received" Local-ip="10.48.36.195"
Local-port="5061" Src-ip="10.48.36.128" Src-port="40523"
Msg-Hash="17750686918648045057"
SIPMSG:
|OPTIONS sip:condcucmadhoc.vngtp.lab:5061 SIP/2.0
Via: SIP/2.0/TLS 10.48.36.128:5061;branch=z9hG4bK1539977cd7264
Call-ID: c0a17300-51518ca7-15313-8024300a@10.48.36.128
CSeq: 101 OPTIONS
Contact: <sip:10.48.36.128:5061;transport=tls>
From: <sip:10.48.36.128>;tag=1335522536
To: <sip:condcucmadhoc.vngtp.lab>
Max-Forwards: 0
User-Agent: Cisco-CUCM10.5
Date: Fri, 27 Mar 2015 17:00:23 GMT
Content-Length: 0
2015-03-27T18:00:23+01:00 conductorcucm b2bua[28262]: UTCTime="2015-03-27 17:00:23,322"
Module="developer.applicationmanager.search" Level="INFO"
CodeLocation="ppcmains/ivy/search/SearchFsmState_Idle.cpp(82)"
Method="SearchFsmState_Idle::handleRequest" Thread="0x7feea9888700":
AppId="59" LegId="ASide[1]" CurState="SearchFsmState_Idle"
Detail="Received search" searchContext="mTarget : sip:condcucmadhoc.vngtp.lab
mRouteSet:
"
2015-03-27T18:00:23+01:00 conductorcucm b2bua[28262]: UTCTime="2015-03-27 17:00:23,325"
Module="developer.applicationmanager.search" Level="INFO"
CodeLocation="ppcmains/ivy/search/SearchFsmState_Idle.cpp(96)"
Method="SearchFsmState_Idle::performSearch" Thread="0x7feea9888700":
AppId="59" LegId="BSide[1]" CurState="SearchFsmState_Idle"
Detail="Initiating search" searchContext="mTarget : sip:condcucmadhoc.vngtp.lab
mRouteSet:
"
2015-03-27T18:00:23+01:00 conductorcucm b2bua[28262]: UTCTime="2015-03-27 17:00:23,344"
Module="developer.modulefactory.threadeddispatcher" Level="ERROR"
CodeLocation="ppcmains/ivy/threadeddispatcher/ThreadedDispatcher.cpp(106)"
Method="ThreadedDispatcher::run" Thread="0x7feea9888700": Detail="Caught
std::exception" what="DefaultRouteHeaderStrategy::manipulateOutgoingRouteSet:
Policy routing configured, but no outgoing route found."
即使Conductor可以解析对等FQDN,也会发生这种情况:
版本 | 发布日期 | 备注 |
---|---|---|
1.0 |
29-Apr-2015 |
初始版本 |