WebEx : ??????? (CMR)

排除故障网真呼叫失败对混合的CMR由于"500内部服务器错误”从WebEx

2016 年 10 月 27 日 - 机器翻译
其他版本: PDFpdf | 英语 (2016 年 4 月 21 日) | 反馈

简介

本文描述遇到的问题,当思科协作会议室(CMR)时混合的电话会议失效与从思科WebEx Cloud的一个500内部服务器错误

贡献用Alok Jaiswal和Ishan Sambhi, Cisco TAC工程师。

问题

这是使用示例在本文描述的拓扑:

当您做呼叫对思科WebEx侧由在前提设备时,您接收一次延迟的提供邀请从思科高速公路核心的消息到思科高速公路边缘由于在Cisco Unified Communications Manager (CUCM)和高速公路核心之间的一延迟的提供会话初始化协议(SIP)中继:

2015-07-06T12:30:03+10:00 vcse tvcs: UTCTime="2015-07-06 02:30:03,027"
Module="network.sip" Level="DEBUG":  Action="Received"  Local-ip="172.28.21.110"
Local-port="7011"  Src-ip="172.28.21.104"  Src-port="25048"
Msg-Hash="3314200182494138210"
SIPMSG:
|INVITE sip:34IBJumtlZRvmrI5t7WQjMhA@company.webex.com SIP/2.0
Via: SIP/2.0/TLS 172.28.21.104:5061;egress-zone=TraversalClientB2B;branch=z9hG4b
Kae647bb81b403d0562281463002ad68a379858.bdfb90811a812d6a11d607f3e17095a1;
proxy-call-id=fdbf1c60-62e1-4204-884a-00fe8664ee66;rport
Via: SIP/2.0/TCP 172.28.21.100:5560;branch=z9hG4bK11c80762b0b051;received=
172.28.21.100;ingress-zone=CUCMNeighborZoneB2B
Call-ID: e7672380-5991e82c-e0ca3-64151cac@172.28.21.100
CSeq: 101 INVITE
Remote-Party-ID: "7221.company.com.au" <sip:172.28.21.100>;party=calling;
screen=yes;privacy=off
Contact: <sip:172.28.21.100:5560;transport=tcp>;video;audio;isFocus;
sip.cisco.multistream;x-cisco-tip;+multiple-codecs-in-ans
From: "7221.company.com.au" <sip:172.28.21.100>;tag=2950560~
3fb53c10-0c98-891d-d84f-6fa87e4135c3-22671423
To: <sip:34IBJumtlZRvmrI5t7WQjMhA@kytec.webex.com>
Max-Forwards: 15
Record-Route: <sip:proxy-call-id=fdbf1c60-62e1-4204-884a-00fe8664ee66@
172.28.21.104:5061;transport=tls;lr>
Record-Route: <sip:proxy-call-id=fdbf1c60-62e1-4204-884a-00fe8664ee66@
172.28.21.104:5060;transport=tcp;lr>
Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY
User-Agent: Cisco-CUCM10.5
Expires: 180
Date: Mon, 06 Jul 2015 02:30:04 GMT
Supported: timer,resource-priority,replaces,X-cisco-srtp-fallback,
X-cisco-original-called
Session-Expires: 1800
Min-SE: 1800
Allow-Events: presence
X-TAATag: 4a936c0c-69a7-4fd8-a070-82b7c3ecb3ce
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Cisco-Guid: 3882296192-0000065536-0000007914-1679105196
Content-Length: 0

在相关搜索规则匹配后,呼叫被发送对WebEx侧:

2015-07-06T12:30:03+10:00 vcse tvcs: UTCTime="2015-07-06 02:30:03,033"
Module="network.search" Level="DEBUG":   Detail="Considering search rule
'Route WebEx calls to WebEx' towards target 'WebEx DNS Zone' at priority
'150' with alias '34IBJumtlZRvmrI5t7WQjMhA@company.webex.com'"

这是传送对WebEx侧作为一次延迟的提供的邀请信息:

2015-07-06T12:30:03+10:00 vcse tvcs: UTCTime="2015-07-06 02:30:03,758"
Module="network.sip" Level="DEBUG":  Action="Sent"  Local-ip="172.28.252.1"
Local-port="25129"  Dst-ip="Webex IP address"  Dst-port="5061"
Msg-Hash="2892679945940486042"
SIPMSG:
|INVITE sip:34IBJumtlZRvmrI5t7WQjMhA@company.webex.com SIP/2.0
Via: SIP/2.0/TLS 58.162.48.4:5061;egress-zone=DNSZoneB2B;branch=z9hG4bK6f09b6c9d2
5bf7f92fa25e6f9a336a0b52417.3f21ed7645b445bb8e55e174caa5935c;proxy-call-id=b8fb1
c34-d048-472b-8b41-81c96abb19d1;rport
Via: SIP/2.0/TLS 172.28.21.104:5061;egress-zone=TraversalClientB2B;branch=z9hG4bK
ae647bb81b403d0562281463002ad68a379858.bdfb90811a812d6a11d607f3e17095a1;
proxy-call-id=fdbf1c60-62e1-4204-884a-00fe8664ee66;received=172.28.21.104;rport=
25048;ingress-zone=TraversalServerB2B
Via: SIP/2.0/TCP 172.28.21.100:5560;branch=z9hG4bK11c80762b0b051;received=
172.28.21.100;ingress-zone=CUCMNeighborZoneB2B
Call-ID: e7672380-5991e82c-e0ca3-64151cac@172.28.21.100
CSeq: 101 INVITE
Remote-Party-ID: "7221.company.com.au" <sip:172.28.21.100>;party=calling;screen=
yes;privacy=off
Contact: <sip:172.28.21.100:5560;transport=tcp>;video;audio;isFocus;
sip.cisco.multistream;x-cisco-tip;+multiple-codecs-in-ans
From: "7221.company.com.au" <sip:172.28.21.100>;tag=2950560~
3fb53c10-0c98-891d-d84f-6fa87e4135c3-22671423
To: <sip:34IBJumtlZRvmrI5t7WQjMhA@company.webex.com>
Max-Forwards: 14
Record-Route: <sip:proxy-call-id=b8fb1c34-d048-472b-8b41-81c96abb19d1
@58.162.48.4:5061;transport=tls;lr>
Record-Route: <sip:proxy-call-id=b8fb1c34-d048-472b-8b41-81c96abb19d1
@172.28.21.110:7011;transport=tls;lr>
Record-Route: <sip:proxy-call-id=fdbf1c60-62e1-4204-884a-00fe8664ee66
@172.28.21.104:5061;transport=tls;lr>
Record-Route: <sip:proxy-call-id=fdbf1c60-62e1-4204-884a-00fe8664ee66
@172.28.21.104:5060;transport=tcp;lr>
Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY
User-Agent: Cisco-CUCM10.5
Expires: 180
Date: Mon, 06 Jul 2015 02:30:04 GMT
Supported: timer,resource-priority,replaces,X-cisco-srtp-fallback,
X-cisco-original-called
Session-Expires: 1800
Min-SE: 1800
Allow-Events: presence
X-TAATag: 4a936c0c-69a7-4fd8-a070-82b7c3ecb3ce
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Cisco-Guid: 3882296192-0000065536-0000007914-1679105196
Content-Length: 0

WebEx侧响应对此邀请与500内部服务器错误的消息:

2015-07-06T12:30:04+10:00 vcse tvcs: UTCTime="2015-07-06 02:30:04,887"
Module="network.sip" Level="DEBUG":  Action="Received"  Local-ip="172.28.252.1"
Local-port="25129"  Src-ip="Webex IP address"  Src-port="5061"
Msg-Hash="9729181486250604161"
SIPMSG:
|SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TLS 58.162.48.4:5061;branch=z9hG4bK6f09b6c9d25bf7f92fa25e6f9a336a0b
52417.3f21ed7645b445bb8e55e174caa5935c;rport=25129;egress-zone=DNSZoneB2B;
proxy-call-id=b8fb1c34-d048-472b-8b41-81c96abb19d1
Via: SIP/2.0/TLS 172.28.21.104:5061;branch=z9hG4bKae647bb81b403d0562281463002ad6
8a379858.bdfb90811a812d6a11d607f3e17095a1;rport=25048;egress-zone=
TraversalClientB2B;proxy-call-id=fdbf1c60-62e1-4204-884a-00fe8664ee66;received=
172.28.21.104;ingress-zone=TraversalServerB2B
Via: SIP/2.0/TCP 172.28.21.100:5560;branch=z9hG4bK11c80762b0b051;received=
172.28.21.100;ingress-zone=CUCMNeighborZoneB2B
Call-ID: e7672380-5991e82c-e0ca3-64151cac@172.28.21.100
CSeq: 101 INVITE
From: "7221.company.com.au" <sip:172.28.21.100>;tag=2950560~
3fb53c10-0c98-891d-d84f-6fa87e4135c3-22671423
To: "CiscoWebEx" <sip:34IBJumtlZRvmrI5t7WQjMhA@company.webex.com>;
tag=38659d409ccec3f7
Server: TANDBERG/4352 (X8.5.2-b2bua-1.0)
P-Asserted-Identity: "CiscoWebEx" <sip:webex.com>
Warning: 399 114.29.213.174:5071 "Invalid content in far end 200 OK"
Content-Length: 0

解决方案

此问题发生由于在只允许它与早提供SIP一起使用的WebEx Cloud的一个需求。对此问题的解决方案将有在CUCM和高速公路核心之间的一早期的提供SIP中继。

早提供在从CUCM的一SIP中继可以达到通过这些方法之一:

  • 启用在SIP中继的媒介终接点要求的设置。

  • 修改语音的早期的提供支持和SIP中继配置文件的视频呼叫字段。

启用媒介终接点要求的设置

为了启用在SIP中继的媒介终接点要求的设置,导航到从CUCM页的设备>中继和选择相关中继。

在设备信息信息部分,请检查媒介终接点要求的复选框,如显示此处:

注意:思科不建议您使在SIP中继的MTP为了解决此问题。此方法强制CUCM调用呼叫的附加资源,并且那些资源必须支持视频编码解码器;否则,视频在呼叫失效。

修改及早提供语音的支持,并且视频呼叫SIP配置文件的字段

在您通过此方法前启用早提供,您必须首先验证在SIP中继配置的SIP配置文件。为了验证SIP配置文件,导航到设备>中继,选择中继到EXPC/VCS C,移动到下面页和验证信息在SIP配置文件字段:

一旦验证SIP配置文件,请导航对设备>设备设置> SIP配置文件并且选择相关配置文件。在中继特定配置窗口,请配置语音和视频呼叫的早期的提供支持如显示此处:

从属在您的环境,部署变化。然而,思科推荐在部分跟随和最佳实践描述关联与他们的部署类型。

配置在单个Unified CM系统的早提供

在此方案中,思科网真导体和会议桥连接给Cisco Unified CallManager (CM),并且Unified CM建立中继到思科高速公路。网真终端注册对Unified CM。

在此方案中,必须为早提供配置这些中继:

  • UnifiedCMtoCiscoExpressway-C

  • UnifiedCMtotheTelePresenceConductor

配置在多团星系统(网真导体的早提供连接对CUCM SME)

此方案介入一个或更多统一的CM会话管理版本(SME)集群与连接分支统一的CM集群。网真导体和会议桥连接对Unified CM SME。Unified CM SME建立中继到思科高速公路C。

在此方案中,必须为早提供配置这些中继:

  • UnifiedCMSMEtoCiscoExpressway-C

  • UnifiedCMSMEtotheTelePresenceConductor

注意:在有三个或多个集群的多团星系统中,一个人统一CM集群是专用的Unified CM SME,终端从未注册对Unified CM SME。终端总是注册对分支统一的CM集群。

配置在多团星系统(连接的网真导体的早提供生叶集群)

此方案介入一个或更多Unified CM SME集群与连接分支统一的CM集群。网真导体和会议桥连接对分支集群。单个中继连接Unified CM SME到思科高速公路C。

在此方案中,必须为早提供配置这些中继:

  • UnifiedCMSMEtoCiscoExpressway-C

  • LeafUnifiedCMclusterstotheTelePresenceConductor

  • LeafUnifiedCMclusterstotheUnifiedCMSME

注意:WebEx Cloud需求有早提供SIP在CMR混合配置指南描述。



Document ID: 119247