Using a carrier only for outbound

[GuJack20]

Hello

This is my first post so hello to all of you.

Here is my problem. We have never user vicidial or goautodial before. Until now we had softphones of the agents configured with the same carrier and the agents were dialing manually.
I have installed goautodial and i'm experimenting with it. I have also updated with yum update and now i have GoAdmin ® 3.0-1370664000

I have a problem figuring out how to configure the carrier for inbound, so i was thinking to let only one agent with the old configuration (without the server) so he can get inbound calls until i finish configuring the inbound in Goautolive.

Is there any way to make the carrier be used only for outbound? Now the server receives the inbounds (i can see them in the asterisk CLI) but the calls get disconnected and even the agents that are using the old config doesn't get the chance to respond.
Before this the inbound calls were going to each agent randomly and they had the chance to respond.

I hope i have explained well

Thanks

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

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) Inbound call routing is determined at the Carrier's control center, whatever that may be. If you do not want your calls to go to Vicidial, you must modify that behavior at the Carrier as Vicidial can only control calls that arrive. It may be possible to remove your "Registration String" from the Admin->Carrier setting to avoid inbound calls, if the registration links to an account designed to send the calls. Then have an agent register instead and that agent will get the calls. The drawback with that is a single agent will be registered at one moment, not "all" or "random" even if it appears that way and you'll lose calls. I have a nice long discussion on that topic when I do training.

4) Your best bet, however, would be to read the Vicidial Manager's Manual on how to set up an Ingroup. The call will arrive at the server (likely because of that registration string). Then the call will be sent to the [trunkinbound] context (because of context=trunkinbound in the account entry for the carrier) which transfers control of the inbound call to the Vicidial scripts. This pushes the call to the "Inbound->Show DIDs" control. The DID at which it lands will ordinarily be configured to send the call to an Ingroup. The Ingroup will have multiple agents logged in. The Ingroup will then choose an AVAILABLE agent and pass the call to them. If no agents are available, hold music is engaged. This is how the system is built to run by design and is, of course, in the manual. Which is why I say you should read it and configure accordingly.

5) You should seriously consider switching to "Vicibox" instead of "Goautodial" as it has more recent code. In both cases, the software installed is Vicidial, although this fact may be somewhat obfuscated by the Goautodial logos and screens. The reality of the matter is that all those extra screens do nothing for you as it pertains to configuring your dialer to route calls. But they are distracting. I advise people regularly to install VMware or any other virtualization technology and install a "Test" Vicidial server which will be perfect for a single phone call and configuration practice. All options are available, anything can be done ... but only for one agent. LOL. Perfect, however, for the ability to test Vicibox and Goautodial against one another. Remember that Vicibox is supported by The Vicidial Group and everyone on the Vicidial forums, whereas Goautodial is supported by fewer technicians (we, of course, support any installation of Vicidial ... on the forums and at the office). Not to say Goautodial is not worthy, but I only recommend it for those who MUST have CentOS or the pretty Agent Screen (for sales purposes). Otherwise the drawback of older code (limitation of the Pretty Agent screen, which is never up to date) and smaller support group is an overriding factor for most. There are, of course, lots of users for both systems.

Happy Hunting!

[gardo]

Just configure your carrier as you would normally do. Inbound or outbound doesn't really matter when it comes with setting up the carrier. As long as you have the correct "context" entry in the account details.

Here's an example entry:

[goautodial]
disallow=all
allow=g729
allow=gsm
allow=ulaw
type=friend
secret=password
username=username
host=dal.justgovoip.com
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=very
nat=yes

Take note of the "context=trunkinbound". This means that Vicidial can use this trunk for inbound. Once you have configured your carrier, you need to define your phone numbers (DIDs/TFNs) to be accepted by the system.

Post your Asterisk CLI here when receiving calls. We can see where you might have missed your inbound configuration.

You can check how to configure your inbound campaigns in our Wiki page (specifically the HOWTOs page): http://goautodial.org/projects/goautodialce/wiki/HowTos3.