Routing SIP data through second NIC with dry t1

[Polareious]

Greetings everyone! For the past week I've been jamming my head on the table trying to figure out I have a client whom has an edgemarc dry T1 router that plugs into interface eth1 and his broadband comcast on eth0 (Utilizing a cisco RV016 redundant bandwidth connections w/comcast). I can ping the sip providers IP and still connect to the web gui/register phones but in the CLI the carrier is unreachable. I have looked up routing and tried multiple things but it seems to just break the connection even more (to the point I cannot ping the carriers IP anymore). This is on a goautodial 2.1 new install, yesterday I picked up his new server hardware and will be installing vicibox instead and replacing the goautodial =) regardless though I see myself running into this problem again.. either way any help would be much appreciated. Today I have a meeting with the carriers lead tech to see if I can square this issue away -_- it doens't matter to me which of the two I can get working today! (I will have the new vicibox ready for this evening to attempt the dual nic connection) In a little I will post all the information and settings on the box.

[williamconley]

you sound like you are trying to do too many things at once.

perhaps you should concentrate on getting just the "net" working on that vicidial server before you attempt everything else. baby steps. and bring each step here and we will help you walk through it.

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

[Polareious]

CentOS 5.8 final/goautodial 2.1/Linux HLA 2.6.18-308.16.1.e15PAE i686/Asterisk 1.4.39.1-vici RPM/Standalone server/only updated via yum no additional software

POS Dell DUAL core 4G ram 1Tb HDD - this is a test dialer to show the system works. Once it is I have a rack server I'm already in process of putting ViciServer 4 on

[Polareious]

Perhaps I should clarify..

I have 2 nics

1st is broadband and the IP which agents connect to and register phones
2nd is the dry T1 that is demarked by an Edgemarc 'edge master' device. This provides an IP address to the second nic in which I can ping the carriers IP and they see us as well, but I cannot for the life of me figure out how to route all sip traffic through eth1 only :/ I did try the externip=xxx.xxx.xxx.xxx but it is not working. I noticed the other day the carrier created a IP schema of 10.1.10.1 with a different gateway then what the broadband IP schema is. Today they will be changing the schema to match what is currently in the office so as to perhaps clarify the situation -- from every forum I've read related it is stated that the gateways must be the same! I'm in a bit of a jubilee

[williamconley]

1) Single most important piece of information still missing: vicidial version with build.

2) Routing traffic in the way you mentioned is easy IF your 1st network card is a local network shared with those agents. In this situation: You will need to change your gateway to the gateway for the 2nd nic. The gateway determines how the internet is reached. If you are using the gateway of the 1st nic, that is where all your traffic will go ... but if you are using the gateway for the 2nd nic then the only traffic that will go to the first nic is that of the local traffic for your agents, but no internet traffic will be sent to nic 1.

[Polareious]

Thank you for your words of wisdom William, it is always a pleasure reading up after you work I ended up having to place the internet connection onto eth1 and the dry T1 trunk onto eth0, then pointed the default gateway to the eth1 (which contained the internet) and BAM connection/calls/clarity