|
Joined: Oct 2007
Posts: 27
Member
|
Member
Joined: Oct 2007
Posts: 27 |
Hi all,
I have an IPRC behind a firewall, with the DMZ server on the router set to the IP address of the IPRC card. I have Inter-Tel IP PhonePlus (IPP+)'s connecting to the card. As a secondary measure, I did forward the ports (5504, 5566, and 5567) to the card.
The internal phones work fine, because they can see the card without having to ever leave the network. However, phones outside of the firewall will not connect.
On the card setup, where there's a checkbox to note this card is behind a firewall/proxy, I check that, put in the public IP (as set in the router config), save it, log out, log back in, and it's blank again. So the card itself is not saving this public IP; I'm not sure if it's detecting something to cause it not to or not.
Do you guys see anything wrong with my setup?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jul 2005
Posts: 79
Member
|
Member
Joined: Jul 2005
Posts: 79 |
What is the firmware version of the card? The appropriate call control port should be 5004 not 5504. Also what version of Axxess are you running. I would recommend upgrading to the latest release of Axxess so that you can configure the IPRC card through DB Studio and no longer have to use the web interface. As of 9.1 Inter-tel added true NAT traversal support.
|
|
|
|
Joined: Oct 2007
Posts: 27
Member
|
Member
Joined: Oct 2007
Posts: 27 |
Axxess 5.2 Card is 1.2.2 production, 1.2.3 boot version
|
|
|
|
Joined: Oct 2007
Posts: 27
Member
|
Member
Joined: Oct 2007
Posts: 27 |
Forgot to mention with this, 5004 is forwarded as well. Still no dice 
|
|
|
|
Joined: Mar 2006
Posts: 1,596
Member
|
Member
Joined: Mar 2006
Posts: 1,596 |
I assume you are resetting the system after changing the IP settings...yes?
|
|
|
|
Joined: Oct 2007
Posts: 27
Member
|
Member
Joined: Oct 2007
Posts: 27 |
I've tried it both ways - changing the IP settings and leaving it, and changing the IP settings and resetting the card; neither way has worked. Is my setup, in theory, correct given my firmware?
|
|
|
|
Joined: Oct 2007
Posts: 27
Member
|
Member
Joined: Oct 2007
Posts: 27 |
any other suggestions? 
|
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
I somewhat concur with SayWhat. On the flip side there is no reason why what you are trying to do wont work. Can you get to the card via HTTP on it's NATd address?
|
|
|
|
Joined: Oct 2007
Posts: 27
Member
|
Member
Joined: Oct 2007
Posts: 27 |
Yes, I can access the card both internally and externally using its NATed IP address (via HTTP).
|
|
|
|
Joined: Jun 2007
Posts: 490
Member
|
Member
Joined: Jun 2007
Posts: 490 |
After re-reading the post given the rev of your system and your card, the chances of this working are close to zero. Sorry for the brain-fart on my part. The issue is that near and far end NAT is not supported in those software revs. Can you put your IPRC card outside the firwall completely? There are message transactions above L3 that ID source IP and port for the endpoint to communicate with the IPRC. Since there is no fixup per se for a proprietary protocol, the IPRC is always going to refer to itself as the only IP that it knows and that is its internal address in the given environment. If you cannot put the IPRC outside, an upgrade would be needed I think. Sorry for leading you astray for a bit but as I re-read and thought about it I cannot see how it could work with what you have.
|
|
|
Forums84
Topics94,528
Posts640,023
Members49,852
|
Most Online5,661 May 23rd, 2018
|
|
1 members (Toner),
195
guests, and
52
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|