vicidial.org

how we can make manual calls from the agent screen go out with CID Group caller id

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) What is your setting for "Manual Dial CID" on the campaign?

1. Thanks

2. ViciBox_v10.x86_64-10.0.0 from .iso | Vicidial 2.14-830a | Build 210920-2159 | Asterisk 13.38.2-vici | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation |Intel Xeon

3. Manual Dial CID is set to Campaign and CID group is also configured.

Your system is using code that is over a year old, and we have fixed several CID issues in the last year. I would suggest upgrading your system to the latest svn/trunk revision and testing this again.

I have upgraded my server . Still I am unable to use CID group for manual Dial.

Server Details :

ViciBox_v10.x86_64-10.0.1 from .iso | Vicidial 2.14-867a | Build 221017-0822 | Asterisk 13.38.2-vici | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation |Intel Xeon

@mflorell @williamconley

Check the dialplan you set in the carrier entry for the manual dial prefix set in the campaign detail view.
Perhaps there's a line in there setting the Caller ID number, overwriting what the CID Group is setting.
I'm using CID group of types AREACODE and NONE on several campaigns and systems and manual calls work as expected using the Caller ID from the group.

As for manual dialing, CID group of types "AREACODE" uses different Caller ID from the group as expected, while CID group of types "STATE" does not use the Caller ID from the group as expected.

So does state work on auto dial, just not on manual?

Help states:

If the STATE type is used, then the STATE value should match the state field for a lead, and if no match is found, the dialer will use the campaign CID as a default

Have you verified the state field of the lead matches the state set on the caller ID?

If everything is set up and it's still not working, create a ticket in bug tracker with as much information as possible, if I get a minute, I'll take a look as I'm potentially looking to use that option in the next couple weeks for a new project, if there is a bug there I'll find it and fix it or perhaps one of the team at Vici will beat me to it.

Yes Right. State is working smoothly for auto dial but it is not working for manual dial.

I too was able to reproduce this issue when I ran a quick test.
I've logged it on Mantis: http://www.vicidial.org/VICIDIALmantis/view.php?id=1388