Modifying the Caller ID Name

[green125]

Hello all,

We recently started working with a new carrier and they pointed out to us that the caller ID name we are sending with our calls looks something like this: "V3151411020024906880". Digging around, it looks like this is the caller_code. We would like to change this to be the same as the caller ID number, or at least something that looks more natural.

I didn't find any settings for this, so I tried altering the code in AST_VDauto_dial.pl that inserts into the vicidial_manager table. So instead of inserting something like Callerid: "V3151411020024906880" <19876543210> into cmd_line_f, I changed it to insert something like Callerid: "19876543210" <19876543210>. When I tested this, none of the calls placed appeared in the vicidial_log table and the leads in vicidial_list did not get updated. It seems like vicidial might be using the caller ID name to keep track of the call between processes.

Is there any way to have something else appear as the caller ID name sent to the carrier?


ViciBox v.8.0.1 | Version: 2.14-683a | BUILD: 180809-1547 | SVN Version: 3017 | DB Schema Version: 1552 | Asterisk 11.25.3-vici | Cluster Setup

[carpenox]

you need to purchase a DID(direct inward dial) number to use as your caller ID display....you should read the sticky notes that say "read me before posting" that tell you to read the managers manual before posting, not saying not to post, but its just good information to learn. It will ACTUALLY help and answer a lot of the questions you are about to ask :-p

welcome to the forum

-Nox

[green125]

Thanks for the quick and friendly response. We have a number of DIDs we are currently using and that part all seems to work. Our concern is if a local carrier doesn't display the name that's registered with the DID for whatever reason, they might just show the name that is being sent along with the call. Right now that is the caller_code.

We actually had a call today with vicidial support where we asked this question. We were told that the best workaround is to use an OpenSIPS server. I will look into that and see what I find.