1) Welcome to the Party!
2) Newbie help/suggestions:
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) Try to ping the carrier from the vicidial server
- Code: Select all
ping sip.tintoring.xxx -c 2
If you can ping it: then your carrier is likely ignoring your packets. You'll need to modify your account with them to allow your Vicidial server's IP address to make calls through their system. If you cannot ping it, try to ping a normal website
- Code: Select all
ping http://www.irs.gov -c 2
If you cannot, your networking is not set up. Look at the proper use of yast to configure your networking in OpenSuSE
If you can, then your carrier may not be allowing communications at all. And once again, you'll need to modify your account with them to allow your Vicidial server's IP address to make calls through their system.
Often you must log in to the carrier's web site/account system to allow your vicidial server's IP address to communicate with their systems at all.
It's also possible that your own firewall is blocking the traffic. Consider turning off your firewall for a few minutes to test this
- Code: Select all
yast firewall
There is a button in here to stop the firewall (and to restart it, of course).
It is also possible that you are using a private network (10.x.x.x or 192.168.x.x) which requires (for some carriers) that your external IP be placed in /etc/asterisk/sip.conf as "externip=x.x.x.x" (a "reload" must be issued in asterisk after making this change.
Happy Hunting!
