Page 1 of 1

calls not syncing

PostPosted: Fri Apr 04, 2008 5:00 am
by Op3r
I am currently having this kind of horror in one of my setup. The calls that comes to the agent are not synchornised meaning even though they are not in call on the agent screen but they are still getting a call.

The load is not high and even the memory is not high.

I tried to use x100p on the server but its not being detected right so I went back to ztummy.


furthermore I keep on getting this on agiout

2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi|WWWWWWWW VDAD XFER REMOTE WAIT: |0||SIP/vd1-0a186870|89059553643|1207303211.1270|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi||SELECT count(*) FROM vicidial_auto_calls where status = 'LIVE' and campaign_id = '' and call_time < "" and lead_id != '';|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi|WWWWWWWW VDAD XFER REMOTE WAIT: |0||SIP/vd1-0a186870|89059553643|1207303211.1270|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi||SELECT count(*) FROM vicidial_auto_calls where status = 'LIVE' and campaign_id = '' and call_time < "" and lead_id != '';|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi|WWWWWWWW VDAD XFER REMOTE WAIT: |0||SIP/vd1-0a186870|89059553643|1207303211.1270|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi||SELECT count(*) FROM vicidial_auto_calls where status = 'LIVE' and campaign_id = '' and call_time < "" and lead_id != '';|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi|WWWWWWWW VDAD XFER REMOTE WAIT: |0||SIP/vd1-0a186870|89059553643|1207303211.1270|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi||SELECT count(*) FROM vicidial_auto_calls where status = 'LIVE' and campaign_id = '' and call_time < "" and lead_id != '';|
2008-04-04 14:00:13|agi-VDAD_LB_transfer.agi|WWWWWWWW VDAD XFER REMOTE WAIT: |0||SIP/vd1-0a186870|89059553643|1207303211.1270|


Im using 2.0.3 and asterisk 1.2.24

PostPosted: Fri Apr 04, 2008 3:23 pm
by mflorell
Check for the 'o' flag in your Dial command in your dialplan.

PostPosted: Fri Apr 04, 2008 3:55 pm
by Op3r
But I have it

exten => _XXXXXX.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _XXXXXX.,n,Dial(SIP/kamote/${EXTEN:},,60,tTo)
exten => _XXXXXX.,n,Hangup()


:(

and furthermore because the gateway have answer() which I send the calls to on the dial plan do you think its safe to use the sip-silence for 8368?

PostPosted: Fri Apr 04, 2008 7:22 pm
by mflorell
What is the Linux distro for this? Is process preemption enabled in the kernel?

PostPosted: Sat Apr 05, 2008 2:02 am
by Op3r
Im using centos.

I had never encountered this error on my installs before and even after. Only this setup that I have.

I was thinking along the lines of a hardware defect or something. I am using core2duo.

Ok I will check if process preemption on the kernel is enabled.