- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Port Opening
Hello People,
I am new to Meraki, and need help on how to open ports.
We have physical telephones which are connected to 3CX. For that connection we have to install a so called Session Boarder Controller into our telephone setup. That SBC is a physical existing Raspberry Pi. That Pi needs Port 5090 to be open for TCP and UDP.
I am to use the Layer 3, Layer 7 or Port Fowarding Rules on the Firewall Dashboard?
Solved! Go to solution.
- Labels:
-
Firewall
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looking around the 3CX forum, it seems that the SBC only requires outbound access to the 3CX server on those ports.
Depending on your existing layer 3 firewall files in Meraki, it may simply work (as per the default) or you may need to create a specific rule with the source IP of your SBC, destination to the 3CX servers and allowing ports 5090 TCP & UDP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you need to open the port for communication from an external source to your internal network or from the internal network to the internal network?
If it is from the internal network to the internal network, you do not need to allow anything, since all internal communication is allowed by default.
Now, if it is from the external to the internal network, port forwarding solves the problem.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I need to open the port from an Internal to External and vice versa.
I am thinking that creating inbound and outbound rules specifying the ports and affected VLAN would suffice?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From internal to external you don't need to do anything.
From external to internal, port forwarding should resolve the issue.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I will try this too, and let you know the outcome.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looking around the 3CX forum, it seems that the SBC only requires outbound access to the 3CX server on those ports.
Depending on your existing layer 3 firewall files in Meraki, it may simply work (as per the default) or you may need to create a specific rule with the source IP of your SBC, destination to the 3CX servers and allowing ports 5090 TCP & UDP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you, I will try this, and provide feedback.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you, Brash. This worked
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All unsolicited inbound traffic is blocked by default and the L3 firewall is a stateful firewall the only way to open up specific ports inbound is by using port forwarding or NAT rules.
Please check the below documentation:
https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Port Forwarding and NAT Rules on the MX and suggest running the 3CX firewall checker once it’s all setup. v18 wasn’t ever an issue but v20 was a bit more challenging.
