Piaf box with two NIC's and two feeds

[edisoninfo]

I'm installing a new Piaf box and the cable company is bringing in two separate feeds. One for the internet access and one strictly for the sip trunks from them. I've not installed one like this before. Is it as simple as connecting one of the server nic's to the Sip Trunk feed and the other nic to the internal network feed? I would like to keep the phones and computers separate to avoid any bandwidth issues, but then again, I need the computers to access the Piaf box and phones. The computers need to access the piaf box for configuration, softphones, etc. and in a few locations, the computers will be plugged into the second port on the back of the phone.

I won't know until they are installed but I believe the sip trunk feed will also be able to access the internet.

I would like to keep the voice traffic separate but if I tie them together, does that spoil that attempt?

 

[MrBostn]

Sounds like you need a Dual wan router

A dual wan router is what you need. Then you setup internal vlans to separate the two services.

Is the cable co installing two cable modems?

I'm installing a new Piaf box and the cable company is bringing in two separate feeds. One for the internet access and one strictly for the sip trunks from them. I've not installed one like this before. Is it as simple as connecting one of the server nic's to the Sip Trunk feed and the other nic to the internal network feed? I would like to keep the phones and computers separate to avoid any bandwidth issues, but then again, I need the computers to access the Piaf box and phones. The computers need to access the piaf box for configuration, softphones, etc. and in a few locations, the computers will be plugged into the second port on the back of the phone.

I won't know until they are installed but I believe the sip trunk feed will also be able to access the internet.

I would like to keep the voice traffic separate but if I tie them together, does that spoil that attempt?

 

[ddorminey]

It is that simple. connect one ethernet port on your server to the 'sip trunk' connection and nothing else (well, with a firewall in between, but you already knew that... right?).

Then let the rest of your devices connect to the other ethernet port on the server. This doesn't allow for separation of voice and data networks internally but will keep your users from maxing out the pipe that your SIP trunk lives on.

---Devin

 

[edisoninfo]

A dual wan router is what you need. Then you setup internal vlans to separate the two services.

Is the cable co installing two cable modems?

Yes, they are supplying two cable modems. Using a solid set of IPtables rules I could connect one NIC in the piaf server directly to the Sip modem and connect the other NIC to the internal lan. I just ordered a Cisco SA520-K9 router that has a spare port to be used as a dual wan or dmz or internal lan port. Very versatile port! It also supports vlans and does intra-vlan routing. So, I'm going to head in that direction first I think.

 

[jroper]

Hi

Isn't this as simple as connecting it all together with the two internet connections on the same IP address range, set you PC's to have a gateway of one, and set your PBX to have a gateway of the other.

Joe

 

[RonRussell]

We have installed several similar setups from CLECS and what we did is: The carrier provides an enet port for the SIP trunk and another enet port for the internet. The SIP trunk port connects directly to your LAN switch and has a private ip address assigned (ex: 192.168.168.100). The internet port connects to the public side of your firewall with a public ip address (ex: 173.49.56.4). Your PBX is on your LAN with an ip address in the same subnet as the carriers SIP trunk port (ex: 192.168.168.1) and registers to the carrier. In our case the carrier specified a public ip address for the SIP trunk and we just assigned the private address and had them configure it on their port. Then we created a static route on the PBX (ex:route add -host 173.49.56.4 gw 192.168.168.100).

 

[blanchae]

Add the following line to both /etc/asterisk/iax_general_custom.conf and
/etc/asterisk/sip_general_custom.conf:

bindaddr=<IP Address>

where <IP Address> is your assigned network address for your VoIP NIC. This will force Asterisk to only use that NIC for VoIP.

This will avoid a routing problem where VoIP traffic returns through the Data NIC. The problem is a phone registers to the VoIP NIC's IP address but the response returns from the Data NIC's IP address. The phone basically ignores the response because it is coming from the wrong IP address.

 

[edisoninfo]

I tried the bindaddr= line but the phones would not register. I have eth0 = 192.168.75.10 which is going to plug into the sip trunk feed from the cable company. I have eth1 = 192.168.1.250 which plugs into the LAN. If I set bindaddr= the eth0 IP, the phones can not register since SIP is not paying any attention to it. Is there a way to bind the "sip trunks" to one nic and the "sip phones" or all sip or whatever to the lan nic?

Best to just leave the bindaddr= line out?

The box needs internet access obviously. I won't know if I can get to the 'net via the sip trunk feed until they install it. I presume I can but if not, then I need the default gw to point to the lan gateway. I presume this will mess up the trunk lines?