Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: ralph on August 15, 2011, 04:31:02 PM
-
I just brought up SIP trunks on a 3300 through a Fortinet firewall.
Has anyone else been able to do this? I'd like to compare notes.
Ralph
-
If they are working it is a success should be just like most other firewalls. I would make sure to test the wide range of calling as I have seen some that appear to be working but things like conference calling or forward external don't work.
-
some that appear to be working but things like conference calling or forward external don't work. (http://some that appear to be working but things like conference calling or forward external don't work.)
Shoot! Didn't think of conf calls.
What I found in this case was we had to NAT 5060 to the PBX. Somehow, in the back of my mind, I think we shouldn't have to do that. Especially since the external IP address is received via DHCP.
Thanks brantn
Ralph
-
DHCP very bad. That is one thing I have noticed with many firewalls that claim to be SIP aware. The issue arrises when it transitions from public to private it does not keep the same port numbers and I would highly suggest to use Ingates line of products for SIP deployment. If you want to send me your SIP Peer Profile I might be able to make some suggestions on what to try but more then likely it is a known issue in most firewalls. NAT is a SIP killer.
-
Thanks for the offer. As soon as I can squeeze out some time I'll pull it and PM you with it.
Ralph