No live video from federated entities - Security Center 5.9 - 5.12

Solution

1. On both systems, make sure the following ports are open on the public address of the server and are redirected for firewall and NAT purposes:
   • Connection to remote Security Center Directory: TCP 5500^a
   • Communication with Media Router: TCP 554
   • Live and playback video stream requests: TCP 560 and TCP 960^b

   ^a Use TCP 4502 for systems upgraded from Security Center 5.3 or earlier.

   ^b TCP port 960 applies to new installations of Security Center 5.8 and later. In Security Center 5.6 and 5.7, TCP port 5004 was used instead of TCP port 960. Therefore, any system upgraded to 5.9 through 5.6 or 5.7 continues to use TCP port 5004, unless manually changed in the redirector's properties inConfig Tool.

2. Based on where the Security Desk workstation you are logging on from is located, make sure your network is set up correctly. For more information see the following topics in the All About Security Center Federation™ document:
   • Scenario 1: Security Desk on Federation™ host network with access to federated system
   • Scenario 2: Security Desk on Federation™ host network without access to federated system
   • Scenario 3: Security Desk on Federation™ host network and systems using public IP addresses and NAT
   • Scenario 4: Security Desk on network of federated system
   • Scenario 5: Security Desk outside the corporate network