Inbound call group auto selection

[Shlosera]

I was not able to find that feature in the docs and the Internet so that I decided to ask here.

If the campaign has set a inbound group, when the agent logs in that campaign will be asked on next screen to choose an inbound group. If the agent choose the group he/she will be able to receive inbound call however if the group is not chosen the inbound calls won't reach the agent.

My question is if it is possible the inbound group of the campaign to be assigned automatically when the agent chooses the campaign? This is important because sometimes the agents are not choosing the inbound groups and and the campaigns works mostly as a outbound one and all missed calls are put on hold.

Thanks in advance.

[mflorell]

Yes, that is a feature that you have to activate per agent.

[Shlosera]

If you are talking about Agent Choose Ingroups: 0 or 1 it is not working for me. It is possible to force the inbound group for the agent if only check the specific Inbound Groups in the user interface.
My goal is to force to the agent the inbound group of the campaign that he is logging in. Is this possible?
After number of test I was really not able to find option like this.

[mflorell]

You have to select the in-groups for each agent in the User Modify screen.

[Shlosera]

Unfortunately it is not working for me because every time when the agent logs in a different campaign with different allowed in-group it must be changed in the User Modify screen.
So, I can understand that there is no feature like this that I need.

[mflorell]

In more recent versions of the code, you can select all of the in-groups for the user and the agent will only be logged into the ones that are allowed for the campaign they are logged into.

[Shlosera]

I already tried this suggestion but it is not working with version of goautodial-ce-3.3-1392354000/vicidial-2.7.401a-130508.2256.2.go
Probably I have to upgrade in order to use it.

[mflorell]

You would need to upgrade, the version you are using is over 2 years old.

[Shlosera]

Thanks a lot.

[pratik]

We are facing same issue.

We are using vicidial 2.11 version.

Can you please suggest.

[williamconley]

We are facing same issue.

We are using vicidial 2.11 version.

Can you please suggest.

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 (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... 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 "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. 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) I suggest you read the Vicidial Manager's Manual to discover how the inbound calls work. I don't think you have the "same issue" as anyone else on this particular thread. You should probably create a new thread and clearly state your situation/problem/configuration settings (in addition to the above). But first: Start at the Vicidial Manager's Manual and complete the entire inbound section to see if this resolves your issue.