Setting Outbound Caller ID

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Setting Outbound Caller ID

Postby katsover » Fri Jan 24, 2020 2:01 am

I have a question:

Let say, if a "Customer A" calls number 1234567 using his/her personal mobile phone.
then the telecommunication company of that 1234567 was configured to redirect the call to a sip phone 0501234, which is being registered to Vicidial server.

Does the Customer will still see "1234567" as caller id on his mobile phone?

Then if an agent from the vicidial server (0501234) do outbound calls to "Customer A" Phone, then its phone will receive "0501234" as caller ID?

Is it possible that the phone will still receive 1234567 as callerID? If yes, is it something to do within vicidial or dial plan?
Posts: 2
Joined: Wed Jan 08, 2020 11:40 pm

Re: Setting Outbound Caller ID

Postby williamconley » Wed Jan 29, 2020 4:45 pm

1) Welcome to the Party! 8-)

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, 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

... the telecommunication company of that 1234567 was configured to redirect the call to ...

The answer is in your question. Calls are never actually "forwarded" as a rule. A new call is generated which connects the old channel to the new channel (there are some notable exceptions, but the methodology in those exceptions function the same as if it were not an exception, so for today's answer ... doesn't matter! lol). When the forwarding/fresh call occurs, the "configuration" and decisionmaking process happens at the moment of forward. You at this end of the call have zero control over that decision. If the telco in question is configured to generate the new call with the original caller ID, they will. If they are configured to generate with some other caller ID, that's what will be seen. And there's absolutely nothing you can do from your end to manage this as it's not your equipment generating the new call.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!) # 352-269-0000 # +44(203) 769-2294
Posts: 19549
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Return to Support

Who is online

Users browsing this forum: No registered users and 57 guests