Dialing Issue

[senate014]

Hello everyone, again!

Just a quick one. I'm setting up a GoautoDial box here in the UK.

I upload my Excel list to the Goautodial server which has phone numbers in the following format:

01423223489 (landline)
07879478983 (mobile)

So when i check the asterisk log (astierk -r command) I keep getting "Congestion" logs which is why I'm not getting any calls connecting.

I've loaded the excel files using the 44 UK country code. From looking at the asterisk -r debug the system is dialing 94401423223479 which my carrier wont like.

I tried uploading my Excel file with "PHONE CODE - Load Lead from File" but then i get the following error in my asterisk -r debug:

[Aug 10 00:43:38] NOTICE[10076]: chan_local.c:599 local_call: No such extension/context 9in_file01765604002@default while calling Local channel
[Aug 10 00:43:38] NOTICE[10076]: channel.c:3612 __ast_request_and_dial: Unable to call channel Local/9in_file01765604002@default


My dial plan is the following:

exten => _9X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9X.,2,Dial(SIP/${EXTEN:2}@SIP01,,tTo)
exten => _9X.,3,Hangup

Any body have any ideas what's going on?

Thanks again!

Andy

[williamconley]

a slight misunderstanding between you, asterisk, and the world regarding phone numbers and phone codes and dial prefixes.

But before we begin, we have this announcement to make you feel at home (everyone gets this until they comply, LOL):

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 and vicidial version with 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 "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. 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) Back to our regularly scheduled programming:

phone numbers in the UK have 10 digits. the zero is NOT part of the phone number. This can be evidenced by the fact that if *I* were to call 011441765604002, I would be connected with 1765604002 which is a valid number. But if I were to dial 0114401765604002, I would NOT be connected to 01765604002, the call would fail. I have to remove the "0" and add the "01144" because the "011" means "international!" and the "44" means "UK!". Thus the "0" is a code that within the UK means "this call is meant to be connected HERE, it is not international". In the US, this code is a "1".

So when you load the numbers, you should be loading 0 as the "dial code" and 1423223489 as the phone number. Unless you are not able to call this number "domestically" and have to dial an internation dial string in front of the number. In that case, you would load the entire international string as the dial code. If, for instance, you need to dial "01144" before "1765604002", then 01144 would be the dial code.

Exceptions for complicated people or programmers:

It is also possible to have the phone number "manipulated" during the call in just about any fashion you can imagine. For instance:

Lead information:

Dial Code: 0 (on the lead directly in each csv record, or "lead code override" during lead upload)
Phone Number: 1423223489

Campaign Information:

Dial Prefix: 9

Will result in: 901423223489

The "dial" line of the dialplan, with the "exten" changed to _90X. to be sure to ONLY catch those numbers starting with "90" from the above setup:

Code: Select all

exten => _90X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _90X.,2,Dial(SIP/01144${EXTEN:2}@SIP01,,tTo)
exten => _90X.,3,Hangup


This will remove the 9 and the 0, and add the country code.

All sorts of things can be done.

[senate014]

Hi William,

I really appreciate you replying and thanks for the beginners guide to the forum

To save me time working out how to post my full config and also writing down my hardware setup can you answer me this question.

I export the phone number data from a Sage ACT! database which has all the numbers starting with the leading "0".

Instead of having to figure out how to get excel to remove the leading 0 off every number, will GoAutoDial just dial the number using the dialing plan you listed below? I have a Trixbox Phone system that lets me dial 901423223879 with no issues, and doesn't put a leading 94401423223879?

All i need the Goautodial server to do is dial 901423223879.

When i upload the Excel data using the "Phone Code: Load From Lead File" option instead of UK - 44, I check the ASTERISK -R log and it's generating the following:

[Aug 10 00:43:38] NOTICE[10076]: chan_local.c:599 local_call: No such extension/context 9in_file01765604002@default while calling Local channel
[Aug 10 00:43:38] NOTICE[10076]: channel.c:3612 __ast_request_and_dial: Unable to call channel Local/9in_file01765604002@default

Why is it putting the "in_file" between the 9 and the 0?

Thanks again

Andy

[williamconley]

if you uploaded the phone numbers into vicidial with 01423223879 as a sample phone (which has the phone code included as part of the phone number), then you can set the campaign to "omit" the phone code field (which may have another digit in it, depending on how you uploaded). This way any entries in phone code will be ignored and no longer something we care about. That's a setting on the campaign. Omit Phone Code. Set to Yes.

Then put a 9 in the campaign "dial prefix".

Then the campaign will dial "901423223879" and that is what will be sent to the Dialplan Entry in the Carrier for your Vicidial server. Next we want that carrier dialplan entry to just pass that through without changing it because it's "correct" already, right?

So:

Code: Select all

exten => _90XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _90XXXXXXXXXX,2,Dial(SIP/${EXTEN}@SIP01,,tTo)
exten => _90XXXXXXXXXX,3,Hangup

Note that the Dial Pattern is now quite specific to this situation. It will only be activated by dialing a 12 digit extension starting with 90 and will pass that extension straight through without any changes to SIP01 (whoever that is).

This is good because it will allow for future expansion without collision with this dial pattern. The new patterns will be able to be active without disabling this one. So future number uploads can be handled properly without shutting this campaign down.

I will suggest, however, that you will need to bypass your Trixbox server when you go into production. There is not a Trixbox server built that can keep up with a Vicidial server at full production.

Not to mention that Trixbox is discontinued anyway. LOL

PS: We also convert from ACT! SQL version to SugarCRM CE for clients trying to get away from that legacy system.

[senate014]

if you uploaded the phone numbers into vicidial with 01423223879 as a sample phone (which has the phone code included as part of the phone number), then you can set the campaign to "omit" the phone code field (which may have another digit in it, depending on how you uploaded). This way any entries in phone code will be ignored and no longer something we care about. That's a setting on the campaign. Omit Phone Code. Set to Yes.

Then put a 9 in the campaign "dial prefix".

Then the campaign will dial "901423223879" and that is what will be sent to the Dialplan Entry in the Carrier for your Vicidial server. Next we want that carrier dialplan entry to just pass that through without changing it because it's "correct" already, right?

So:

Code: Select all

exten => _90XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _90XXXXXXXXXX,2,Dial(SIP/${EXTEN}@SIP01,,tTo)
exten => _90XXXXXXXXXX,3,Hangup

Note that the Dial Pattern is now quite specific to this situation. It will only be activated by dialing a 12 digit extension starting with 90 and will pass that extension straight through without any changes to SIP01 (whoever that is).

This is good because it will allow for future expansion without collision with this dial pattern. The new patterns will be able to be active without disabling this one. So future number uploads can be handled properly without shutting this campaign down.

I will suggest, however, that you will need to bypass your Trixbox server when you go into production. There is not a Trixbox server built that can keep up with a Vicidial server at full production.

Not to mention that Trixbox is discontinued anyway. LOL

PS: We also convert from ACT! SQL version to SugarCRM CE for clients trying to get away from that legacy system.

Hi William,

Again, thanks for all your help, it worked a treat!!

One other question if that's ok?

I've been doing some testing on the 4000 leads list I've uploaded and which is now dialing out correctly. When a call is established and passed through to me, the person at the other end is saying "Hello, Hello... Hello". This makes me think there is a delay in passing the call through to me as the agent when the dialed number picks up the phone at the other end. Is there anyway of reducing the delay or making the call connect instantly to the agent?

Thanks again!

Andy

[williamconley]

put your own phone number in the queue. you'll find out about the delay if there is one quite easily.

vicidial's delay is minimal, but dependent upon your system's power as well.

if you have a virtual system or a large lag time to the VOIP provider ... vicidial can't control those at all.

did you post details about your system? i don't think i see them ... too bad.

[senate014]

put your own phone number in the queue. you'll find out about the delay if there is one quite easily.

vicidial's delay is minimal, but dependent upon your system's power as well.

if you have a virtual system or a large lag time to the VOIP provider ... vicidial can't control those at all.

did you post details about your system? i don't think i see them ... too bad.

Hi William,

Thanks for getting back to me so quick.

The system is the following spec:

HP DL385 G1
16GB
2x Dual Core AMD CPU's
HP MSA30 U320 SCSI Storage Array W 14x 146GB 15K U320 Hard Drives
VMware ESXi 4.1

The Goautodial server is a virtual machine configured with 2x CPU's and 4GB RAM.

The ESXi 4.1 Server is under 20% average CPU load, minimal disk I/O usage and using 14GB out of the 16GB installed memory.

Thanks again!

Andy

[williamconley]

Vicidial does not run virtual. get it on a physical machine.

also (per my previous post ...) you did not post the Vicidial version with build or the installation .iso. These are quite handy when asking any question on the forum. Version with build is actually a requirement (of the site owner, and it's free so let's not argue with him, right? LOL).

vicidial's "engine" relies on hi-res perl timing. the CPAN hi-res perl timing module has proven resilient to porting into a virtual environment.

works great for testing and even for single users. but for production, put it on a physical box. get yourself a nice core2quad and you'll enjoy the vicidial experience much more. use the VMware version for "practice & development".