Cisco MCU5310 external call in issue

Question

Scenario: Currently I have a Cisco MCU5310 sitting on internal network using only Port A with internal IP address settings but I could not call in from external network. There is no NAT settings option like normal Cisco C40/C60.
q1. if I would like to make a mix of VC sessions with internal and external parties, do I need to use Port A for internal network connection and Port B for external network connection?
q2. Or rather I can use only Port A for both external and internal VC session just like a normal Cisco C40/C60 but would need the IT firewall team to do the NAT routing of the traffic from external to internal vice versa for the MCU to work connecting both internal and external VC parties?
q3. What would be the firewall ports that are required to be opened and the settings needed to set in the Cisco MCU5310 in this case?

Answer 1

Jason -
It's possible for external and internal endpoints to call into the MCU at the same time with only one IP assigned to the MCU, but it depends if you have your network routing setup to allow both internal and external traffic to reach that one IP.  We did this with our MCU some years ago, we used a single IP on the MCU and was open on the firewall to allow incoming external endpoints to connect directly into conferences, while at the same time internal endpoints were doing the same.  You can either open up the IP of the MCU completely or just the required ports needed on your firewall.
conferencing_products_conferenceme_ports_used_kb_3
Ideal, if you don't have a VCS, you'd use the second port (video firewall) on the MCU, and of course the preferred method is the use of a VCS.  In either case, it just depends on what you have and how you're capable of deploying it within your environment, such as having the video firewall option key on the MCU or using a VCS.