-
3
- #1
Hi all,
Many of you saw the thread I started on SIP trunk ghost calls. I had intended to build a firewall from a Raspberry Pi and place it in front of my BCM50, but the project turned out to be more complex than I thought in trying to program iptables firewall software. Since my project involved adding a second Ethernet port to the Pi I had to create a network bridge which seriously changed the way packets flow through the firewall. It sort of worked, but not nearly good enough. I shelved that idea for the time being and came up with another solution that has shielded my BCM50 from the SIP scanners, but also allows my SIP trunks to work behind NAT without having to use port forwarding. Attached is a Word document I wrote that details the process I went through.
Brian Cox
Georgia Telephone
Many of you saw the thread I started on SIP trunk ghost calls. I had intended to build a firewall from a Raspberry Pi and place it in front of my BCM50, but the project turned out to be more complex than I thought in trying to program iptables firewall software. Since my project involved adding a second Ethernet port to the Pi I had to create a network bridge which seriously changed the way packets flow through the firewall. It sort of worked, but not nearly good enough. I shelved that idea for the time being and came up with another solution that has shielded my BCM50 from the SIP scanners, but also allows my SIP trunks to work behind NAT without having to use port forwarding. Attached is a Word document I wrote that details the process I went through.
Brian Cox
Georgia Telephone