1) Welcome to the Party!
2) Some guidelines to help you on the site:
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
3) Two IPs for two campaigns is a problem. Two IPs for two Carriers, however is not so bad. But in either case this is a networking issue that is not related to Vicidial in any way. You may need to find a forum that support network routing in Linux at a deeper level. Ordinarily when you have a linux server you have a single "gateway" through which all traffic passes. If you have multiple gateways, you will need a rule to determine which traffic goes through which gateway. These rules are ordinarily based on the destination IP address. If you tell your system to send all traffic for xxx.xxx.xx.xxx through gateway1 and traffic for yyy.yyy.yyy.yyy through gateway2 (or perhaps "all other traffic" through gateway2), then the question is whether these two campaigns are using two different carriers at two different IP addresses. If so, excellent. If not ... then we have a problem. How will the networking router know one packet from another to route them differently?
4) If sip reload does not bring up the carrier, check the status of the carrier in "sip show peers". If that peers shows unreachable, consider setting "qualify=no". this will allow packets to be sent to the carrier even when it is down ... but beware: If the packets are still not able to get through, you will still not be able to make the call ... consider setting up a failover instead. Then the "unreachable" will activate the failover and you'll still be able to dial.
Posted: Tue Dec 25, 2012 2:04 am