After a bit of grief I was able to install Vicibox 8.1 ISO on a remote server. I'm really impressed with the amount of features, and I can clearly see how much is missing from GoAutoDial. I should have switched over a while ago, but live and learn. Anyways, my test server is as follows and I'm 100% focused on outbound calling in the USA. My PBX's handle inbound calls.

As you can clearly see a 9 is being added to the dial string for some odd reason. I have no idea what the other error/warnings are for, and figure I'll get to that later unless it's important. Hopefully somebody would be kind enough to shed some light on those parts.

The managers manual does a great job about explaining username:password authorization, but truth be told, I've never been able to get that to work with JustgoVoip, so I opted for IP authorization instead. Their customer service is VERY lacking!

This is what I changed to see if I could get auto/manual dialing working for a test campaign.

That last line has been driving me nuts for hours. It doesn't make sense to me why the 9 is added. I've tested a few variations of EXTEN (no number or 2), and tried different variations of _91XXXXXXXXXX (NXXNXXXXXX, XXXXXXXXXX, for example), as well as played around with the Dial Prefix section listed in the campaign menu (BLANK, X 9 or 1). The one time the outbound number showed up perfectly (12223334444) in the CLI I got that annoying local channel error message listed below.

Sip Show Registry shows active for the User/Phone, as well as JustGoVoip. I've also been pretty relentless about using Sip Reload and Dialplan Reload just to be on the safe after updating CARRIER and CAMPAIGN settings.

I really want to get away from using GAD. More than likely I'll be going with a different voip provider very soon, but before I do that, I'd love to know what I'm doing wrong because I cannot figure what is causing the issue with making outbound calls.

[Nov 17 19:35:08] ERROR[2063]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("vicibox81", "(null)", ...): Name or service not known

Where do you have "vicibox81" in your system? Wherever it is, the system can't resolve that name to an IP. Since this also appears to be the host name of your server, you may need to verify that this entry is in /etc/hosts or change the entry (wherever it is) to an IP or other valid domain or even localhost.

While it appears as though it *should* match, it's not for some reason. So:* Verify that the extensions-vicidial.conf actually reloads the new values when you make a change in a dialplan extension.* Make sure NONE of your dialplan extensions have a context in them (nothing with brackets [ ]) which would remove everything after that entry from the [default] context where they all must reside to work properly.* Do NOT leave the dial prefix blank. Use 9 or another single digit number until you have more than 10 carriers OR use X. But don't leave it blank. I strongly suggest you fall in line and use 9.* Use a matching 10 digit US NANPA dial pattern such as the one suggested by thephaseusa (_91NXXNXXXXXX is *the* standard for north america with dial prefix 9). This allows multiple simultaneous live carriers without interruption or interference with each other.

[Nov 17 19:35:08] ERROR[2063]: netsock2.c:305 ast_sockaddr_resolve: getaddrinfo("vicibox81", "(null)", ...): Name or service not known

Where do you have "vicibox81" in your system? Wherever it is, the system can't resolve that name to an IP. Since this also appears to be the host name of your server, you may need to verify that this entry is in /etc/hosts or change the entry (wherever it is) to an IP or other valid domain or even localhost.

While it appears as though it *should* match, it's not for some reason. So:* Verify that the extensions-vicidial.conf actually reloads the new values when you make a change in a dialplan extension.* Make sure NONE of your dialplan extensions have a context in them (nothing with brackets [ ]) which would remove everything after that entry from the [default] context where they all must reside to work properly.* Do NOT leave the dial prefix blank. Use 9 or another single digit number until you have more than 10 carriers OR use X. But don't leave it blank. I strongly suggest you fall in line and use 9.* Use a matching 10 digit US NANPA dial pattern such as the one suggested by thephaseusa (_91NXXNXXXXXX is *the* standard for north america with dial prefix 9). This allows multiple simultaneous live carriers without interruption or interference with each other.

Sorry for the late reply, it's been a busy week. JustGoVoip hasn't replied to me in about 1.5 weeks, so forget them. I was to able to get it working for some testing with Didlogic. My only issue with them is allowing CLI passthrough. They seem to be quite picky about that process. Caller ID always showed up for the DID regardless of changing it in the campaign settings. I've reached out them for feedback since I have a lot of numbers with a different provider and I'm eager to test out the geo-targeting feature of ViciDial.

For anybody else looking at this post going forward the following settings works great.

## hosts This file describes a number of hostname-to-address# mappings for the TCP/IP subsystem. It is mostly# used at boot time, when no name servers are running.# On small systems, this file can be used instead of a# "named" name server.# Syntax:# # IP-Address Full-Qualified-Hostname Short-Hostname#

I'm not exactly sure how to fix that part since I've been trying to figure out how to add another 3-4 providers to see how ViciDial works.

Should not be related to individual providers. Try adding one. The only configuration option specific to a provider related to dns is the "host=" entry in the sip configuration/context. As long as your DNSresolver can convert that to an ip (or you just provide an IP so no resolution is needed), then DNS should not fail for an individual provider.