vicidial.org

Good evening,
i have to change the callerid for one only campaign, so i go in the details of this campaign and set the fiel "campaign caller id" with the new number.
When i try to do a call (manual or predictive) it doesn't work. How i can solve?

I send the call to my provider via sip trunk.

Thank you

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) Your question:

When i try to do a call (manual or predictive) it doesn't work

The only possible answer to "it doesn't work" is "then fix it". lol. But I digress ...

Was it working before you changed the CallerID?

If you change the CallerID back, does it resume working? (if so, for the sake of argument, post something similar to the CallerID, not the real one but close)

(if not ...):
Check the Admin Log at the bottom of the campaign to see what else you may have changed inadvertently, and change that back, too.

If all else fails: Don't just say "it doesn't work", post an Asterisk CLI example of an attempted call (not 3000 lines of unrelated code: just from the moment before the attempt until the attempt has failed, showing the entire attempt, preferably with NO other calls on the system to interfere with the output). Then we may be able to give you help on How to fix it.

Right!!

First of all thank you for reply.

Asterisk 1.4.44-vici built by abuild @ build16 on a x86_64 running Linux on 2012-08-29 02:51:25 UTC
ViciBox Server v.4.0
Vicidial VERSION: 2.8-403a
BUILD: 130510-1350
© 2013 ViciDial Group

With the old number it works, i can do manual or predictive calls.
With the new number this is what i see

[Jan 28 10:38:06] -- Called 393272421889@80.90.90.254
[Jan 28 10:38:06] -- Got SIP response 603 "Declined" back from 80.90.90.254
[Jan 28 10:38:06] -- SIP/80.90.90.254-000000c4 is busy
[Jan 28 10:38:06] == Everyone is busy/congested at this time (1:1/0/0)
[Jan 28 10:38:06] -- Executing [477393272421889@default:2] Goto("Local/8600051@default-5e73,1", "s-BUSY|1") in new stack
[Jan 28 10:38:06] -- Goto (default,s-BUSY,1)
[Jan 28 10:38:06] -- Executing [s-BUSY@default:1] Playback("Local/8600051@default-5e73,1", "busy") in new stack
[Jan 28 10:38:06] -- <Local/8600051@default-5e73,1> Playing 'busy' (language 'en')
[Jan 28 10:38:09] == Auto fallthrough, channel 'Local/8600051@default-5e73,1' status is 'BUSY'
[Jan 28 10:38:09] == Spawn extension (default, 8600051, 1) exited non-zero on 'Local/8600051@default-5e73,2'
[Jan 28 10:38:09] -- Executing [h@default:1] DeadAGI("Local/8600051@default-5e73,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[Jan 28 10:38:09] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[Jan 28 10:38:09] -- Executing [h@default:1] DeadAGI("Local/8600051@default-5e73,1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----21-----BUSY----------") in new stack

Have you ever watched HeeHaw? If it hurts to raise your arm, don't raise your arm.

If your carrier rejects your call based on the caller ID being "XXXX", don't make a call using caller ID "XXXX".

On a side note: This *usually* only happens to those who seriously annoy a real telephone company. What is happening here is that you are purchasing your minutes from an "Aggregate Seller". They are in turn purchasing from a larger aggregate seller, and that one from another, until eventually the call reaches a real telephone company (with PSTN switching). That big telco has real customers. They complain. They are connected to other major carriers, who also complain, and these major telcos share the complaint data for the purpose of red-flagging "bad actors" (ie: perhaps guys like you? Or someone who previously used this Caller ID).

Once they get a red flag, the question is "to what" do they attach this flag? They can't just cut off the major aggregate because one of their subcustomers (7 levels removed) is a bad guy. So they shut off that CallerID's ability to make calls (sometimes they just remove the passage of the DTMF tones, if the calls being generated are Press One calls!).

Now, you can't make a call. You contact your carrier who contacts theirs and so on up the line. Then you get a visit from someone with a badge. Because they've been looking for whoever is making calls with that caller ID. This way, you come to them.

Use another number. Stop doing whatever you were doing, because you're NOT getting under the radar. You're getting attention you really don't want.

If you weren't doing anything, change numbers anyway, that one's burned. If you have $20k worth of stationery with this number on it and haven't done anything wrong, call your carrier, begin the "why are you rejecting these calls" conversation, and hope for the best.

Finally i solve "my" problem.
My provider forget to add the number in his whitelist.

Thank you all

LOL: If your Carrier has a whitelist, that's a cool thing. Good postback!

davide.filippi wrote:Finally i solve "my" problem.
My provider forget to add the number in his whitelist.

Thank you all

Actually like that idea. Good way to prevent fraud for those who don't lock down their servers maybe?