someting is adding numbers to my inbound saved drop calls

[ucko123]

Hey very fresh here and that community helped me a lot so far and thank you for that. But now I came to problem I don't know how to deal with so iam asking for your help to point me in right direction.

Code: Select all

[Mar  5 22:43:47]     -- Executing [31305209@default:1] AGI("SIP/202-0000dfbe", "agi://127.0.0.1:4577/call_log") in new stack
[Mar  5 22:43:47]     -- <SIP/202-0000dfbe>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Mar  5 22:43:47]     -- Executing [31305209@default:2] Set("SIP/202-0000dfbe", "CALLERID(num)=106326141") in new stack
[Mar  5 22:43:47]     -- Executing [31305209@default:3] Dial("SIP/202-0000dfbe", "SIP/0031305209@t2") in new stack
[Mar  5 22:43:47]   == Using SIP RTP CoS mark 5
[Mar  5 22:43:47]     -- Called SIP/0031305209@t2
[Mar  5 22:43:47]     -- SIP/t2-0000dfbf is ringing

that is my normal call from Zoiper or from any outbound campaign. In short all my leads are without leading 0 and in process of calling I end up with two 0 more and because I didn't find the reason when setting up system so my VOIP provider just cut one 0 on all outgoing calls.

Now we expand from outbound campaigns and I setup inbound campaign too. Everything is working and calls are coming in too. I also setup Drop List to catch anyone who give up waiting on agent or get timeout in 6min of waiting...
And all this leads get two 0 in front so when I want to call them back from inbound campaign I get this:

Code: Select all

[Mar  5 21:52:27]     -- Executing [10031305209@default:1] AGI("Local/10031305209@default-000103ef;2", "agi://127.0.0.1:4577/call_log") in new stack
[Mar  5 21:52:27]     -- AGI Script Executing Application: (EXEC) Options: (Set(_CAMPCUST=INCALL))
[Mar  5 21:52:27]     -- <Local/10031305209@default-000103ef;2>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Mar  5 21:52:27]     -- Executing [10031305209@default:2] Set("Local/10031305209@default-000103ef;2", "CALLERID(num)=106326141") in new stack
[Mar  5 21:52:27]     -- Executing [10031305209@default:3] Dial("Local/10031305209@default-000103ef;2", "SIP/0010031305209@t2") in new stack
[Mar  5 21:52:27]   == Using SIP RTP CoS mark 5
[Mar  5 21:52:27]     -- Called SIP/0010031305209@t2

As you see it adds up 1 to number

Now to questions

1. How I prevent to get those two 0 in front of leads numbers gathered from Drop List function?
2. What is adding up this 1 in front of numbers

Additional info for no.3 question: we have pool from VOIP from 140 to 149
All outbound campaigns calling with 141
Inbound DID is linked to 149

3. Can CID be different for Inbound campaign when calling out like 145?

Thx in advance for all your answers

[blackbird2306]

1. Please post your dialplan. There seems to be a wrong line in your dial command in dialplan.
2. There is a campaign setting "Dial Prefix"

2. What is adding up this 1 in front of numbers

[ucko123]

1.
exten => _X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _X.,2,Set(CALLERID(num)=XXXXXX141)
exten => _X.,3,Dial(SIP/00${EXTEN}@t2)
exten => _X.,4,Hangup
I guess that 00$ is adding 2nd 0 I don't want but that is removed by VOIPprovider. So If I write 0$ then VOIP can cancel their remove one 0 from our numbers?
Is that 00$ why iam getting double 0 on incalls too or its that on provider side?

2. Dial Prefix in campaign is set to x

[blackbird2306]

Yes that's exactly the point. The entry "SIP/00${EXTEN}" is responsible for the double zero called in front. You can strip the first "0" if you want and then your voip provider can stop the manipulation:

exten => _X.,3,Dial(SIP/0${EXTEN}@t2)

[ucko123]

Ok if I understand correctly "exten => _X.,3,Dial(SIP/00${EXTEN}@t2)" is adding zeros for outcalls and also for incalls? If that's the case then solution is I stop adding 0 at all and rather say VOIP provider to add one 0 for me instead removing it like it is now. Do I think in right direction?

[williamconley]

Never use "_X." as a part of your dialplan. Any carrier will require at least seven digits. Use "_XXXXXXX." otherwise you'll have a collision with internal Vicidial functions, many of which are four digits.

[ucko123]

Quick update
It was my VOIP provider who was sending me calls with two 0 added in front. They cut it off and now my drop calls list is populated with right numbers.

Ok if I understand correctly "exten => _X.,3,Dial(SIP/00${EXTEN}@t2)" is adding zeros for outcalls and also for incalls? If that's the case then solution is I stop adding 0 at all and rather say VOIP provider to add one 0 for me instead removing it like it is now. Do I think in right direction?

Ty for

Never use "_X." as a part of your dialplan. Any carrier will require at least seven digits. Use "_XXXXXXX." otherwise you'll have a collision with internal Vicidial functions, many of which are four digits.

Ill try it tonight when call center is unactive.

So only thing that left to do is:

Additional info for no.3 question: we have pool from VOIP from 140 to 149
All outbound campaigns calling with 141
Inbound DID is linked to 149

3. Can CID be different for Inbound campaign when calling out like 145?

Thx in advance for all your answers

[blackbird2306]

I don't understand your 3rd question. Give us more information what the problem is.

[ucko123]

That's my dial plan

exten => _X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _X.,2,Set(CALLERID(num)=106326141)
exten => _X.,3,Dial(SIP/00${EXTEN}@t2)
exten => _X.,4,Hangup

So all calls we do in outbound campaigns translates into 059084141 and that's the number customers see...

Now for inbound campaign DID is used 106326149

So my question is if there is an option that I use 106326145 for outgoing calls in same inbound campaign?
Incalls 149 and outcalls 145? I hope that make more sense

[blackbird2306]

First of all does your voip provider allow CLI/ANI (caller id) delivery or do they change it in some way? Because in dialplan you are setting your caller id manually to "106326141" (Set(CALLERID(num)=106326141)), but talking of customers see "059084141". This doesn't match.
Usually setting caller id should not be part of dialplan (in some cases certainly ok), there are campaign settings for doing this instead.

[ucko123]

They do translation from dial plan 106326141 to 059084141 what customers see
Also in DID I used 106326149 but customer have to dial in 059084149 to get us inbound

Now I would like to have 059084145 showing to customers if I call them back if they hung up phone sick of waiting - dropped calls
So again inbound/blended campaign for incall 149 for outcall 145
Is that possible?

[blackbird2306]

Sure this is possible, but another question. How does this translation happen? Do they translate the caller id depending on your sent callerid or on your used trunk/pool.

sent caller id 106326141 --> will be translated to 059084141
sent caller id 106326145 --> would be translated to 059084145

or e.g.
exten => _X.,3,Dial(SIP/00${EXTEN}@t2) --> translated to 059084141
exten => _X.,3,Dial(SIP/00${EXTEN}@t4) --> translated to e.g. 059084145

[ucko123]

Translation happens on their side (VOIP provider) I operate only with 10632614X in Vici system

[blackbird2306]

If I understood it correctly, then translation depends on your sent caller id.

1. Change your dialplan (delete CALLERID(num)=106326141 and update priority 1,2,3):
exten => _XXXXXXX.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _XXXXXXX.,2,Dial(SIP/00${EXTEN}@t2)
exten => _XXXXXXX.,3,Hangup

Make sure diaplan is reloaded in asterisk!

2. Now you are able to change the caller id dynamically in campaign settings according to you wishes

3. Change in outbound campaign settings "Campaign CallerID" --> "106326141" --> translated from voip provider to 059084141

4. Change in inbound campaign settings "Campaign CallerID" --> "106326145" --> translated from voip provider to 059084145

5. Make sure that outbound and inbound campaign settings "Manual Dial CID" is set to "CAMPAIGN"

6. If you make calls directly through softphone then go into phone settings and set Outbound CallerID --> e.g. "106326141"

[ucko123]

That makes sense Ill try it tonight when callcenter will close and ill post it back if its ok

Thanks so far

[ucko123]

This indeed was solution to my problem now I finally have fully automatic inbound/outbound campaign

Thx again

PS: I couldn't wait till night as I felt that this will work

If I understood it correctly, then translation depends on your sent caller id.

1. Change your dialplan (delete CALLERID(num)=106326141 and update priority 1,2,3):
exten => _XXXXXXX.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _XXXXXXX.,2,Dial(SIP/00${EXTEN}@t2)
exten => _XXXXXXX.,3,Hangup

Make sure diaplan is reloaded in asterisk!

2. Now you are able to change the caller id dynamically in campaign settings according to you wishes

3. Change in outbound campaign settings "Campaign CallerID" --> "106326141" --> translated from voip provider to 059084141

4. Change in inbound campaign settings "Campaign CallerID" --> "106326145" --> translated from voip provider to 059084145

5. Make sure that outbound and inbound campaign settings "Manual Dial CID" is set to "CAMPAIGN"

6. If you make calls directly through softphone then go into phone settings and set Outbound CallerID --> e.g. "106326141"

[williamconley]

Also check this out if you think this may become an issue again (this is from "Modify a DID Record"):

Clean CID Number -This field allows you to specify a number of digits to restrict the incoming caller ID number to by putting an R in front of the number of digits, for example to restrict to the right 10 digits you would enter in R10. You can also use this feature to remove only a leading digit or digits by putting an L in front of the specific digits that you want to remove, for example to remove a 1 as the first digit you would enter in L1. Default is empty. If more than one rule is specified make sure you separate them with a space and the R will run before the L.

So if they were sending you a 12 digit number starting with 00, you could use this to strip off the 00 and keep the 10 digit number. Useful if they do this again in the future.