Page 1 of 1

Campaign VS Phone Outbound CallerID

PostPosted: Fri Apr 22, 2011 4:27 pm
by TroyD
Quick Question;
We are wanting to run a manual campaign, however we want to show the CID of the agents phone rather than having a general Campaign caller ID set. Since both are configurable, is it possible to run the campaign so that the agents phone's CID is sent rather than one CID for the whole campaign? Which one overrides the other or is it that only when placing a call using the phone does the phones CID get sent. There is also the option for placing a manual call from inside the agent screen, is this where the phones CallerID comes into play. We have a bunch of clients that we want to call, and we want to track which agent is the most effective on getting return calls therefore we have given a different number to each agent and want that number to be displayed to the clients that they call from inside a manual campaign.. Hope I made sense here..!!

PostPosted: Sat Apr 23, 2011 3:34 pm
by williamconley
I guess you could write an agi script or dialplan method that catches the meetme room from which the manual call emanates, finds the agent logged into it, gets the callerid from the phone and sets it. Probably not as elegant as changing it within the manual dial system in vicidial itself, but much easier to write. LOL

PostPosted: Sat Apr 23, 2011 4:12 pm
by mflorell
Using the agent phone as the CID on manual dial calls is only an option for 3-way calls currently. Although I'm sure this could be added as a programmable option at some point.

PostPosted: Mon Apr 25, 2011 7:07 am
by TroyD
mflorell wrote:Using the agent phone as the CID on manual dial calls is only an option for 3-way calls currently. Although I'm sure this could be added as a programmable option at some point.


How Much?? We would be willing to pay for this??

PostPosted: Mon Apr 25, 2011 10:10 am
by williamconley
Ordinarily it would be good to ask pricing in a PM, and it does not hurt if you can give an estimate of your budget for the project (consider it from Matt's perspective: If you say how much would you charge? vs "How much would you charge, we can have $200-$400 in the budget ...?" vs "we can have $50 in the budget" LOL)

PostPosted: Mon Apr 25, 2011 12:26 pm
by mflorell
Adding a campaign option to allow for sending of the agent's phone CID-number as the CID for manual dial calls within the vicidial agent interface would be 2 hours($400).

Thanks Matt

PostPosted: Mon Apr 25, 2011 6:02 pm
by TroyD
mflorell wrote:Adding a campaign option to allow for sending of the agent's phone CID-number as the CID for manual dial calls within the vicidial agent interface would be 2 hours($400).


Thank you for your input William. Matt, I will contact your office in the morning to arrange payment. Hopefully it will be useful for someone else as well as a welcomed addition for the vicidial community. Thanks again for your quick response and such a great product!

PostPosted: Mon Apr 25, 2011 6:06 pm
by williamconley
You can believe that lots of people will be happy to have that option. Some immediately, and some may never know it wasn't there all the time. LOL

But remember that MATT is "The Vicidial Group" who quoted your price, I'm just an independent technician. 8)

Re: Campaign VS Phone Outbound CallerID

PostPosted: Sat Nov 02, 2013 11:35 am
by yuvrajkc
Any update guys ?

Re: Campaign VS Phone Outbound CallerID

PostPosted: Sat Nov 02, 2013 5:47 pm
by williamconley
yuvrajkc wrote:Any update guys ?

Been a feature for quite some time. Read the manual 8-)

Re: Campaign VS Phone Outbound CallerID

PostPosted: Sat Feb 08, 2014 9:24 pm
by alt_solutions
Hi to all,

Please help me where to find the link here in the forum or in the manual. I search and tried to read also cant find how to set the Phone CallerID when agents are login to Campaign. I need to use the Phone Extensions caller ID instead of the Campaign. William said it is in the features already. Is it the group Alias?

Thanks,
alt

Re: Campaign VS Phone Outbound CallerID

PostPosted: Sat Feb 08, 2014 11:33 pm
by williamconley
The present version of vicidial will use the campaign caller id for outbound calls generated by the campaign if you have the proper dialplan entry in your carrier.

It will use the callerid from the phone (admin->phones) when dialing directly from a phone (without logging in to vicidial).

Re: Campaign VS Phone Outbound CallerID

PostPosted: Sun Feb 09, 2014 12:45 am
by alt_solutions
Hi William,

Thanks for the quick reply.

I need Agents who are logged in to campaign to use their phone callerID because they have their own DID numbers. Im using ISDN 30 channels so that in inbound calls it will be redirected to their own respective inbound closer group. (Note: Manual DIal Campaign)

For example:
Agent1 -> Outbound CallerID 11111111
Agent2 -> Outbound CallerID 22222222
Agent3 -> Outbound CallerID 33333333

I got the idea of Group Alias and will set to each Agent outbound CID when they select their assigned Group Alias (CID number). My problem is I have Multiple DID number that they have to Click and Select Scroll Down Group Alias every-time they do Manual Dialing. Is there a way to set it to the extensions.conf to override phone CID instead using the Campaign CID?

Thanks,
alt

Re: Campaign VS Phone Outbound CallerID

PostPosted: Sun Feb 09, 2014 12:51 am
by williamconley
Campaign setting available in Detail view:

Manual Dial CID - This defines whether an agent making manual dial calls will have the campaign callerID settings used, or their agent phone callerID settings used. Default is CAMPAIGN. If the Use Custom CID campaign option is enabled or the list Campaign CID Override setting is used, this setting will be ignored.

Re: Campaign VS Phone Outbound CallerID

PostPosted: Sun Feb 09, 2014 1:10 am
by alt_solutions
Hi William,

Thanks for the quick response again.. lols

It is really in the manual. wew! this thread left hanging the last time ive checked. Now its clear to me.. hahaha.

Thanks I've tested and working already!

Regards,
alt

Re: Campaign VS Phone Outbound CallerID

PostPosted: Mon Jun 02, 2014 2:00 am
by ryanakron
So I'm a little late to the game here, but one really simple solution is to set the caller ID using the variable ${CHANNEL} in your dialplan.

So for example:
exten => _1NXXNXXXXXX,1,Set(CALLERID(num)=${CHANNEL})
exten => _1NXXNXXXXXX,2,AGI(agi://127.0.0.1:4577/call_log)
exten => _1NXXNXXXXXX,3,Dial(SIP/RSQUARED/${EXTEN:0},,tTor)
exten => _1NXXNXXXXXX,4,Hangup

Making a call from a phone with extension 300 would give a caller ID similar to "SIP/300-00000006"
So let's make the assumption that we will only use 3-digit phone extensions, then we can change the CID to just the extension:

Change: exten => _1NXXNXXXXXX,1,Set(CALLERID(num)=${CHANNEL})
To: exten => _1NXXNXXXXXX,1,Set(CALLERID(num)=${CHANNEL:4:3})

Re: Campaign VS Phone Outbound CallerID

PostPosted: Tue Jun 10, 2014 2:02 am
by williamconley
ryanakron wrote:So I'm a little late to the game here, but one really simple solution is to set the caller ID using the variable ${CHANNEL} in your dialplan.

So for example:
exten => _1NXXNXXXXXX,1,Set(CALLERID(num)=${CHANNEL})
exten => _1NXXNXXXXXX,2,AGI(agi://127.0.0.1:4577/call_log)
exten => _1NXXNXXXXXX,3,Dial(SIP/RSQUARED/${EXTEN:0},,tTor)
exten => _1NXXNXXXXXX,4,Hangup

Making a call from a phone with extension 300 would give a caller ID similar to "SIP/300-00000006"
So let's make the assumption that we will only use 3-digit phone extensions, then we can change the CID to just the extension:

Change: exten => _1NXXNXXXXXX,1,Set(CALLERID(num)=${CHANNEL})
To: exten => _1NXXNXXXXXX,1,Set(CALLERID(num)=${CHANNEL:4:3})

However, the question was for a logged in user making a manual dial call from within the campaign (not from the phone, but from the screen ... which means the phone is in a conference room). This generates the call from the conference room and not from the actual phone.

With the latest version of Vicidial, the calls from the phone (not in a conference room, direct calling) will already have the callerid which is set in the phone record in Admin->Phones without any need to modify any carrier settings.

The challenge I see for this user was that he is using a PRI which may have special needs for passing the CID information. But hopefully that didn't require extra coding. 8-)