vicidial.org

Urgent – System not working after update

Hi guys,

Over the weekend I did “yum update”. So I am now on the latest version. GoAdmin ® 3.3-1406088000

After rebooting “Asterisk ( Telephony )” remained off and had to be manually started. This normally starts automatically.

We use Bria softphones. When an agent logs into a campaign it creates a call that they accept to login to the dialler. The problem we have today is when the agent accepts the call, Bria immediately ends the call.

I have no idea why or how to trouble shoot this.

Before the update everything was working fine.

I see I am now on:

Distro Name: CentOS release 5.11 (Final)

I used to be on GoAutoDial CE 3.3

Would that be the cause?

Can you post your Asterisk CLI on agent login?

I believe you posted this in the wrong sub-forum.

gardo wrote:Can you post your Asterisk CLI on agent login?

Hi Gardo, I think this is what you want?

Connected to Asterisk 1.8.23.0-1_centos5.go RPM by currently running on go (pid = 31096)
Verbosity is at least 4
[Oct 14 11:41:56] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:41:56] == Using SIP RTP CoS mark 5
[Oct 14 11:42:01] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:42:01] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:42:01] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:42:02] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:42:03] > Channel SIP/8005-00000005 was answered.
[Oct 14 11:42:03] -- Executing [8600051@default:1] MeetMe("SIP/8005-00000005", "8600051,F") in new stack
[Oct 14 11:42:03] == Parsing '/etc/asterisk/meetme.conf': [Oct 14 11:42:03] == Found
[Oct 14 11:42:03] == Parsing '/etc/asterisk/meetme-vicidial.conf': [Oct 14 11:42:03] == Found
[Oct 14 11:42:03] WARNING[18829]: app_meetme.c:1248 build_conf: Unable to open DAHDI pseudo device
[Oct 14 11:42:03] == Spawn extension (default, 8600051, 1) exited non-zero on 'SIP/8005-00000005'
[Oct 14 11:42:03] -- Executing [h@default:1] AGI("SIP/8005-00000005", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Oct 14 11:42:03] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:42:03] -- <SIP/8005-00000005>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[Oct 14 11:42:06] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:42:06] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:42:06] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:42:06] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:42:06] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:42:06] -- Executing [55558600051@default:1] MeetMeAdmin("Local/55558600051@default-00000003;2", "8600051,K") in new stack
[Oct 14 11:42:06] WARNING[19056]: app_meetme.c:4789 admin_exec: Conference number '8600051' not found!
[Oct 14 11:42:06] -- Executing [55558600051@default:2] Hangup("Local/55558600051@default-00000003;2", "") in new stack
[Oct 14 11:42:06] == Spawn extension (default, 55558600051, 2) exited non-zero on 'Local/55558600051@default-00000003;2'
[Oct 14 11:42:06] -- Executing [h@default:1] AGI("Local/55558600051@default-00000003;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Oct 14 11:42:06] -- <Local/55558600051@default-00000003;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[Oct 14 11:42:06] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:43:01] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:43:01] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:43:01] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:43:02] == Manager 'sendcron' logged off from 127.0.0.1
[Oct 14 11:43:06] == Manager 'sendcron' logged on from 127.0.0.1
[Oct 14 11:43:06] == Manager 'sendcron' logged off from 127.0.0.1

I notice the warnings and I see there may be a problem with DAHDI. I got this result:

[root@go ~]# dahdi_cfg
Notice: Configuration file is /etc/dahdi/system.conf
line 0: Unable to open master device '/dev/dahdi/ctl'

Don't know if that is relevant.

Do you use a hardware timing or an E1/T1 PRI card?

geoff3dmg wrote:Do you use a hardware timing or an E1/T1 PRI card?

Hi,

No I do not use any cards. It is a bog standard Del server without any telephony equipment.

I did the "1 click install" from the downloadable distro. I don't know what version my original installation distro was.

Ok I'd guess it's just a case of dahdi not being loaded. When you say you started asterisk manually, how did you do this?

I open "GoAdmin" and in the "Services" block it lists all the services. For some reason Asterisk is the only one that no longer boots automatically. So I select start and then Asterisk starts.

Ok I don't know enough about GoAutoDial to help you, sorry.

Same happened with mine once I updated via yum update, I downloaded the up to date Dahdi files and reinstalled, after a reboot it seems to work. I also have the problem with Asterisk not starting.

mrobinson wrote:Same happened with mine once I updated via yum update, I downloaded the up to date Dahdi files and reinstalled, after a reboot it seems to work. I also have the problem with Asterisk not starting.

Hi there,

Did you follow any particular instructions? I followed the ones written by Striker but I could not get it to work.

I just followed the instructions at http://www.striker24x7.blogspot.in/2013 ... dahdi.html and changed to download and install 2.10.0.1

Code: Select all

# wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-current.tar.gz
#tar -xvzf dahdi-linux-complete-current.tar.gz
#cd dahdi-linux-complete-2.10.0.1+2.10.0.1
#make clean
#make all
#make install
#make config

Then reboot. Are you using a VPS? When I tried using Digital Ocean in testing I was unable to install Dahdi.