dhostetter

I had the exact same issue and through much trial and error I discovered that you either need to:

A) Give one IPRC card an external address and connect to a network outside the firewall and move any phones to be located outside the firewall (i.e. offsite) to that IPRC card

or

B) Upgrade to PBX software 9.1 which allows IPRC cards to work through a firewall provided all the correct ports are opened

I could never figure out why - with all the correct ports open - IPRC cards in PBX's < 9.1 will not work through a firewall, but it is so. Perhaps some ports are dynamic.

dhostetter

The IP phone side router/firewall doesn't need any special configuration. The IP phones work through a standard NAT service. Mine at home goes through a D-Link 614 and I didn't do anything specific to that router.

ITEngineer

There are many "well it depends here" but lets start with this. The correct ports to open are TCP 5566, UDP 5567, UDP 5004, UDP 5005. From here it depends on version of endpoint software and version of system. Is this a 5000 or Axxess? Is it running in ITP mode or SIP mode? If you are a new version of Axxess or 5000 you can turn on Automatic Nat Traversal. But to start with open the correct ports listed above.

SilentJ619

Your problem is with your ports. Since you already have connectivity and are experiencing one way audio, what version your at shouldn't matter. IT Enginners above post is correct in asking what type/version of system because in the Axxess version 8.x to 9.x they restrict the IPRC Card (not IP devices) from routing through any NAT. There logic was to prevent latency.

Basically your missing a range of UDP ports for 5004

Here is the list....if your using a 5000 IP PBX 5004 is changed to 6004, but same principals apply.

*****Audio Recieve Port*****
*****UDP: 5004 -5070*****

Terminal Call Control
TCP:5566

General Purpose
UDP:5567

Call Control
TCP:5570


....The IP phone dynamicaly picks any one of the UDP port 5004 -5070 and sends audio down that port. If you want to verifiy this before you make the change in your firewall, use Etherreal or any other protocol capture device and run it while you make a couple of one way audio IP calls. Stop the capture device and find your voice transmisions, they might be labeled as RTP , or do a sort by IP to find the device. A protocol capture will break down each data packet into it 7 layer OSI functions. Look at layer 4 to see the destination and source port. I bet you find the device trying to send audio on a port other then 5004.

Hope this helps, I have a hard time explaining all the crap in my head.

RBGNorcal

Thanks for all the helpful info; we're now up and running. Sure enough, the Inter-Tel rep who sold us the phones left us with incomplete settings. So the problem is now fixed, no thanks to Inter-Tel! God, these IP phones have been a nightmare, but now I see light at the end of the tunnel!

Thanks again -

Justin

SilentJ619

Glad to see your up and running. Your not the first person to complain about the Inter-Tel dealers not coming through with the help you needed. I run into this problem every day, It just makes me look like a hero when I come in and clean up the mess they created. As you can see the fix's for most of the Inter-Tel problems are very simple, if the supporting vendors would just read the installation manual and check the knowledge base posts there wouldn't be a need for this forum at all.

Good Luck

RBGNorcal

that we bought the system directly from Inter-Tel here in Sacramento - not even a third-party vendor, and basically we paid a lot of money for them to ship us a box of phones with NO setup info! Oh, the fun life of being the IT scapegoat - we don't care what you have to do, just make it work! Anyway, thanks again for the help, it is truly appreciated! Hopefully the next time someone runs across this problem they will find this post and be saved!

JasonDyer

Just a quick posting. I received an Inter-tel IP Phone from my company. The IT manager gave me a few ports to open to the phone as we are having the same issue where I can hear the other party and they cannot hear me. I was given a whole bunch of ports to try. I ended up openning

TCP: 1-80
TCP: 4000-4500
UDP: 2000-2500
TCP & UPD: 5000 - 5600

Not yet tested as I am not at home, BUT, a couple ports mentioned in the post were not amongst the list, however, they do fall within the ranges I opened. Will keep posted, but I am optimistic!

ITEngineer

Not all of these ports need to be opened. There are a few that you list that are optional ie port 80. Most people don't open these ports for security reasons. The ports listed in the above thread are correct and the ports that need to be open. Opening addtional ports beyond what is needed is asking for security issues, IMHO.

__________________
Life is a highway....