QUESTION Using two Ethernet ports and subnets with PIAF.

[Slamby]

This is probably very simple, but I can't figure it out so need some quick help.

I have my PCs etc on one subnet (192.168.1.0), which use the main router for web, email, VPN etc (192.168.1.1).

I have my phones and PIAF box on another subnet (192.168.2.0) using a router dedicated to VoIP (192.168.2.1).

The new PIAF box has 2 LAN ports, and I need to access the box from the .1.0 subnet, so the PCs can use iSymphony, Asteridex etc.

How do I tell PIAF to only use eth0 (192.168.2.2), so that SIP trunk registrations use the VoIP router (192.168.2.1) only, and not go out on eth1 and use the main router?

 

[GomezAddams]

I'm not sure I understand, but I don't think you need to do anything. If your phones and asterisk box are on 192.168.2.0, the network stack on the asterisk box will know which interface to use to talk to the phones.

 

[jroper]

Hi

ow do I tell PIAF to only use eth0 (192.168.2.2), so that SIP trunk registrations use the VoIP router (192.168.2.1) only, and not go out on eth1 and use the main router?

Set the gateway to be be 192.168.2.1 on eth0, which should have the IP address in the 192.168.2.XXX, and no gateway should be set on eth1 which has an IP in the range 192.168.1.XXX

For the "Linux Conversational" this is easily done via Webmin.

Joe

 

[Slamby]

I'm not sure I understand, but I don't think you need to do anything. If your phones and asterisk box are on 192.168.2.0, the network stack on the asterisk box will know which interface to use to talk to the phones.

I might not have explained it very well. It's not the box talking to the phones that's the issue, it's which internet connection the box uses for SIP trunk registrations. With the two network ports connected on the asterisk box, it is on both the .1 .0 and .2.0 subnets, and can use the .1.1 gateway for SIP trunk registrations, which would cause issues, as everything has been set up for it to use the .2.1 router, with its associated static WAN IP etc.

Set the gateway to be be 192.168.2.1 on eth0, which should have the IP address in the 192.168.2.XXX, and no gateway should be set on eth1 which has an IP in the range 192.168.1.XXX

Thanks Joe, I'll set it up that way and do some testing.

 

[wa4zlw]

you can setup a static route to push traffic to your sip provider to go out the proper interface. that way you dont have to rely on the default gateway.

Leon