Guest

Preview Tool

Cisco Bug: CSCvj00057 - CMS guide doesn't state clearly that CMA doesn't support 443 for TURN.

Last Modified

Oct 04, 2018

Products (1)

  • Cisco Meeting Server

Known Affected Releases

2.2.12

Description (partial)

Symptom:
CMA doesn't fallback to 443 if 3478 is blocked on public IP of TURN server on FW.

Documentation doesn't clearly started this:

https://www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Deployment_Guide/Version-2-2/Cisco-Meeting-Server-2-2-Single-Split-Server-Deployment.pdf

Conditions:
Running TURN on Edge server using port 443.
TURN server is NAT'd to a Public IP via FW.
FW blocks port 3478 for the NAT'd Public IP.

WebRTC falls back to 443 for TURN allocation and relay.

CMA on Public internet doesn't fallback to 443 because Callbridge (CB) provides only 3478 ports for TURN.

CMA on internal network connects as they reach directly to CB on port 3478.
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.