auto dial problems

[peacy]

Hi,

I'm having some problems with automatic dialling on my server. Hope somebody can help me... (I've been banging my head against the wall for quite a few days now)

The setup:
- AMD X2 5600+, 2 Gb RAM, 1Tb disk, etc.
- Digium TE120P card connected to an E1 PRI with 8 channels active
- OS: CentOS 5
- Asterisk: 1.4.6
- Zaptel: 1.4.3
- Libpri: 1.4.0
- astguiclient: VERSION: 2.0.95 BUILD: 70402-1157
- Agents using Grandstream SIP phones

The problem:
When I set the campaign to manul dial everything works fine.
When I set it to auto with a ratio of one calls are not transferred to the agents, but being dropped (or hung up).
I can see from the logs that the dialling starts properly when I resume the agent. The called number rings properly, but when the called is answered it is not transferred to the conference, but hung up. (Or at least you hear a busy tone when you answer the phone.)

I have followed the scratch install guide and in fact installed 2 working systems. One using POTS lines and another one using ISD BRI lines.

The FASTagiout file reveals the problem, which is:
2007-07-20 21:27:51|TEST_VDfastAGI|VD_hangup|VD hangup: no VDAC record found: 1184963229.41129 S0707202127098600051

Hope somebody can enlighten me why this is happening.

Cheers,
Zoltan

[peacy]

Hi,

I just thought I'll add some more info.

The load on the server is non-existent as this is only a test setup. (i'm using only 1 agent and a couple of leads)

I started comparing my ISDN BRI (working) and my ISDN PRI (non-working) box.

From the asterisk console this is what I see on the working box:
- Dial sent properly
- other side answers
- extension 8365, call_log called
- extension 8365, VDAD_transfer called
- answered called passed onto the meeting room

This is what happens on the non-working box:
- Dial sent properly
- other side answers
- extension 8365, call_log called
- extension 8365, VDAD_transfer called
- extension 8365, VDAD_transfer called
- extension 8365, VDAD_transfer called
- extension 8365, Hangup called

So for some reason the VDAD_transfer script cannot transfer the call to an available agent.

I'll continue my investigation, but if anybody can give me some pointer I'd be really happy.

Cheers,
Zoltan

PS: I hope that from now on I can post my logs (I'm new to the forum, which means no URLs in the post - which apparently also applies to 'agi://....' )

[peacy]

Hi,

Well, the problem is solved!

The main difference between the two servers was that the non-working one was installed using rpms (from atrpms) and the working one was compiled by myself.

The rpm install of asterisk starts up asterisk as a non-privileged user (asterisk).

When astguiclient is installed, the log directory (/var/log/astguiclient) is created with drw-rw-rw- permissions, so the agi scripts couldn't write to it.
Since logging was to FILE, the agi-VDADtransfer.agi script just died because it couldn't write to the log directory!

I checked install.pl and the log directory is created with 0666 mask. I think that the mask should be changed to 0777. (I might report this as an enhancement.)

Cheers,
Zoltan

[anandkumargupta]

Thanks,

I am getting the another problem but did the same mistake . let me check your comment is going to help me.

Anand

[masaboor]

Hi

I got the same problem and tried to change the file permission .But even now its not working.can u help me out

[mflorell]

If you have more than one server involved (even if it's just Apache/PHP/MySQL) they all need to be ntpd time synchronized ot the same timing source or things will not work right.