Solved

Using a Polycom VSX-7000 Behind a Cisco PIX Firewall

Posted on 2007-11-29
7
7,663 Views
Last Modified: 2011-01-14
I am trying to use a Polycom VSX-7000 Video conferencing system behind a PIX fiewall.  I have set all features in both the PIX and the VSX to recommended settings but I can't complete a connection.  I can tracert from the VSX to the remote site but a call will not complete - the Polycom just rings and the other site does not answer.
 We are using a PIX 506E, with vers. 6.3(5) software.  The Polycom is using ver. 8.5.3 and we are not using Gatekeeper.  
I listed the changes made to our PIX as recommended by Polycom.  When discussing the problem with Polycom they believe it's a PIX problem.  I can't seem to find what we need to change to make this work.  Has anyone setup a PIX to handle a Polycom Video Conferencing system?

PIX Changes --
  Opened outbound ports - TCP 1720
                                           TCP 3230 - 3235
                                           TCP 3603
                                           TCP 389
                                           UDP 3230 - 3253
  Opened inside interface (all IP) to video device.
  Entered a static NAT to translate inside/outside addresses.
  Tried with both fixup h323 h225 1720 and with no fixup h323 h225 1720 - same results.
The Polycom has an inside LAN adddress and has NAT turned off in the software settings.  We assume this is correct since the PIX is handling the NAT.                                      
0
Comment
Question by:uescjp
  • 2
  • 2
  • 2
  • +1
7 Comments
 
LVL 28

Expert Comment

by:batry_boy
ID: 20378843
Have you tried taking the PIX out of the equation and making a connection when the traffic is not going through the PIX?  This would mean giving the Polycom unit a public IP address for a certain amount of time while you test.

I think I would verify that the Polycom connection without the traffic going through the firewall.  Might save a lot of time troubleshooting the issue.
0
 

Author Comment

by:uescjp
ID: 20381234
Yes.  We have done that and the Polycom works fine if we do not try to go through the PIX.
0
 
LVL 6

Accepted Solution

by:
foobar_666uk earned 250 total points
ID: 20571492
Can you post your Pix Config so I can help?

If you have "fixup h323" commands on, this will interfere with your port forwarding as it will try and do clever packet inspection. So use "no fixup h323"

There is a great guide to VC (Polycom) through a Cisco PIX 501 firewall here on my companies website:
http://www.firstconnections.co.uk/support/viewkb.asp?id=26

If you are still have problems, please let me know!
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 6

Expert Comment

by:foobar_666uk
ID: 20797539
Have my comments helped at all? I have setup the Polycom VSX behind PIX Firewall many many times, so I am sure I can help...
0
 
LVL 1

Expert Comment

by:tlcsupport
ID: 21863561
Do you have an inspection class defined? Try removing any 'inspect' statements related to H323.

e.g.
policy-map global_policy
  class inspection_default
   no inspect h323 h225
   no inspect h323 ras

I think this achieves the same as using the "no fixup" command.
0
 
LVL 1

Assisted Solution

by:tlcsupport
tlcsupport earned 250 total points
ID: 21986810
Also make sure your Polycom suites are configured to use fixed ports. (Admin / ip / firewall I think) If they are, they will use ports 3230 - 3253. If they aren't, they will use random ports (1024-65535) and probably won't make it through your firewall.

You can rule out firewall ACLs by either opening up all IP (for testing only, of course) or by using a laptop and wireshark to inspect the traffic (I'd only recommend the latter if you've done this before and know what you're doing).

Worth noting - If you use the inspect h323 command, you only need open ports 1720 and 1731 as the PIX automatically opens and closes ports required for the audio and video RTP data by sniffing (inspecting) the control traffic. However, I've found that the inspect H323 command caused a lot of problems with Polycom 7000e suites.
0
 

Author Closing Comment

by:uescjp
ID: 31411787
Sorry our firewall was upgraded to an ASA making this question unneeded.  Mostly our fault for not replying, but thanks for the help and effort.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When I upgraded my ASA 8.2 to 8.3, I realized that my nonat statement was failing!   The log showed the following error:     %ASA-5-305013: Asymmetric NAT rules matched for forward and reverse flows It was caused by the config upgrade, because t…
Have you experienced traffic destined through a Cisco ASA firewall disappears and you do not know if the traffic stops in the firewall or somewhere else? The solution is the capture feature. This feature was released in 6.2(1) and works in all firew…
Both in life and business – not all partnerships are created equal. As the demand for cloud services increases, so do the number of self-proclaimed cloud partners. Asking the right questions up front in the partnership, will enable both parties …
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question