Guest

Preview Tool

Cisco Bug: CSCul29713 - TPC cannot connect to MCU 5310 with HTTPS Protocol

Last Modified

Mar 03, 2018

Products (1)

  • Cisco TelePresence Conductor

Known Affected Releases

XC2.2.x

Description (partial)

Symptom:

Title:
TPC showing alarm when adding MCU with HTTPS Protocol

Description :

While adding the Conference  Bridge in the conference pool, TPC through the Error Communication alarm.

When adding the Conference  Bridge in the conference pool with protocol as HTTPs and Port No. as 443, TPC can't communicate with conference bridge. If TPC using the HTTP protocol and port no. 80 the conference bridge can add without any alarm.

Expected behavior :

Protocol should be HTTP and the Port number should be 80 for adding the conference bridge 

Conditions:

Version details :

Cisco MCU 5310 -> 4.4.3
TPS Virtual -> 3.1.1
TPC -> XC2.2.1
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.