Version 2.0.5: Time Synchronization Problem

[wizzbangca]

Testing a new installation and am running into a problem that no one else seems to have run into. I log into the dialer as a user, get to the web page that is shown why waiting for a call to come through and BAM! I get this:

There is a time synchronization problem with your system, please tell your system administrator

The client is approximately 5 seconds off in time from the server. Don't think the time sync is that sensitive, that wouldn't make much sense. NTPD is running on both the client and server, so can''t be that either. I searched through the web and no one has anything regarding this problem. I don't get why the message shows.

Any ideas?

[mflorell]

This is a result of the servers being off from each other, it has nothing to do with the agent workstation time.

How many servers do you have?

[wizzbangca]

Only 1 server.

[mflorell]

What is the output of this command in Linux:

screen -ls

[proxium]

I have the Time Synch problem as above and I don't have any communication between Asterisk server and astGUIclient/Vicidial server, is this a possible reason to stop communication?

Those are my detached screen on the Vicidial server:

neovicidial:/# screen -ls
There are screens on:
3413.ASTVDadapt (23.04.2009 10:49:02) (Detached)
3410.ASTVDremote (23.04.2009 10:49:02) (Detached)
3416.ASTVDautoFILL (23.04.2009 10:49:02) (Detached)
2294.ASTfastlog (23.04.2009 10:31:03) (Detached)
4 Sockets in /var/run/screen/S-root.

[mflorell]

Looks like none of the manager connected processes are running.

Try running the update script manually and see what happens:
/usr/share/astguiclient/AST_update.pl --debug

[proxium]

thx for answering me, this is the output:

neovicidial:~# perl /usr/share/astguiclient/AST_update.pl --debug
SHOW CHANNELS format: 1
LOOKING FOR Zap clients assigned to this server:
|SELECT extension FROM phones where protocol = 'Zap' and server_ip='192.168.1.150'|
LOOKING FOR IAX2 clients assigned to this server:
|SELECT extension FROM phones where protocol = 'IAX2' and server_ip='192.168.1.150'|
LOOKING FOR SIP clients assigned to this server:
|SELECT extension FROM phones where protocol = 'SIP' and server_ip='192.168.1.150'|
Zap Clients: |
IAX2 Clients: |
SIP Clients: |
unknown remote host: at /usr/share/astguiclient/AST_update.pl line 369

[proxium]

I runs SELECT extension FROM phones
WHERE protocol = 'SIP'
AND server_ip = '192.168.1.150'
in phpmyadmin and I get no result, so I try to take a look at this file "astguiclient.conf" and I found the VARserver_ip => 192.168.1.150 wich is the Vicidial IP, I change it's value to look like this

portion of /etc/astguiclient.conf
# The IP address of this machine
VARserver_ip => 192.168.1.114

# Database connection information
VARDB_server => 192.168.1.150
VARDB_database => asterisk
VARDB_user => root
VARDB_pass => root
VARDB_port => 3306


Now I've VARserver_ip that point on my Asterisk machine and VARDB_server that point on my astGUICLIENT/Vicidial and the most good news is the ability for me to see in ASTERISKCLI this message:
== Connect attempt from '192.168.1.150' unable to authenticate

It's the first time that my Vicidial try to communicate with Asterisk Server, I'll verify the access

[mflorell]

Check your manager.conf file in Asterisk and that it matches the settings in your servers table for manager connection info.

[proxium]

Yes alright, manager.conf contains the section [admin] and that's what I need to put in Manager User/Manager Secret in the agc configuration interface.

But now I have a message form the AsteriskCLI:
> Channel SIP/1111-0a436348 was never answered.

that appears when I login from Vicidial interface using 1111 phone user (my X-Lite) soft phone ring once and than I get in AsteriskCLI the message above and in Vicidial I get the alert message:
"There is a time synchronization problem with your system, please tell your system administrator"
and
"Noone is in your session: 8600051"

[mflorell]

You need to first make sure that all of the screens are running:

screen -ls

that should output ASTupdate, ASTsend and ASTlisten

If you don't see those then there is still a problem.

If you do see those then you need to check taht your SIP phone is registered.

[proxium]

this is the output:

neovicidial:~# screen -ls
There are screens on:
2440.ASTsend (23.04.2009 16:25:02) (Detached)
2446.ASTVDauto (23.04.2009 16:25:02) (Detached)
2437.ASTupdate (23.04.2009 16:25:02) (Detached)
2449.ASTVDremote (23.04.2009 16:25:02) (Detached)
2443.ASTlisten (23.04.2009 16:25:02) (Detached)
2339.ASTVDautoFILL (23.04.2009 16:24:04) (Detached)
2333.ASTVDadapt (23.04.2009 16:24:04) (Detached)
2337.ASTfastlog (23.04.2009 16:24:04) (Detached)
8 Sockets in /var/run/screen/S-root.

all is running, and my sip phone 1111 is registred because I see it in FOP (freepbx)

[mflorell]

So, you're using FreePBX...

That could cause all sorts of problems.

In the Asterisk CLI type "sip show peers" and post what the entry for that phone looks like.

[proxium]

sip show peers
Name/username Host Dyn Nat ACL Port Status
tofreepbx1/400 192.168.1.89 N 5060 OK (1 ms)
from-trunk (Unspecified) 5060 Unmonitored
2000/2000 (Unspecified) D N A 0 UNKNOWN
1111/1111 192.168.1.113 D N A 5060 OK (3 ms)
1000 (Unspecified) D N A 0 UNKNOWN
5 sip peers [Monitored: 2 online, 2 offline Unmonitored: 1 online, 0 offline]

I have a trunk on 192.168.1.89 to simulate a call between two AsteriskServer

[wizzbangca]

I'm glad this is helping people. Thank you all for your assistance. My outputs are as follows:

"screen -ls" shows:
5669.ASTVDadapt (Detached)
2044.ASTVDauto (Detached)
3005.asterisk (Detached)

Obviously missing some screens. After running "perl /usr/share/astguiclient/AST_update.pl --debug" I get:
Can't locate Net/Telnet.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/share/astguiclient/AST_update.pl line 236.
BEGIN failed--compilation aborted at /usr/share/astguiclient/AST_update.pl line 236.


Something isn't right somewhere, looking into that. I am also checking on the manager and user names and passwords between the confs and database as well.

[mflorell]

Did you install the Net::Telnet perl module on this system?

What instructions did you follow to install ViciDial?

[wizzbangca]

To solve the Net/Telnet.pim problem with "perl /usr/share/astguiclient/AST_update.pl --debug", run the following:

perl -MCPAN -e'shell' Cpan

then at the Cpan prompt, type:

install Net::Telnet

then type "quit" when done to get back to the linux CLI.

My new output for "perl /usr/share/astguiclient/AST_update.pl --debug" is:
SHOW CHANNELS format: 1

|0|SELECT count(*) FROM server_updater where server_ip = '10.48.10.8';|

|INSERT INTO server_updater set server_ip='10.48.10.8', last_update='2009-04-23 9:40:23';|
LOOKING FOR Zap clients assigned to this server:
|SELECT extension FROM phones where protocol = 'Zap' and server_ip='10.48.10.8'|
LOOKING FOR IAX2 clients assigned to this server:
|SELECT extension FROM phones where protocol = 'IAX2' and server_ip='10.48.10.8'|
LOOKING FOR SIP clients assigned to this server:
|SELECT extension FROM phones where protocol = 'SIP' and server_ip='10.48.10.8'|
Zap Clients: |
IAX2 Clients: |
SIP Clients: |
unknown remote host: at /usr/share/astguiclient/AST_update.pl line 408

From what I see, I have a little work to do.

[mflorell]

Check your servers setting for Telnet Host and change it to either 127.0.0.1 or the IP address of your server and see if that works.

What Linux distro are you using?

[wizzbangca]

Did you install the Net::Telnet perl module on this system?

What instructions did you follow to install ViciDial?

I followed your scratch install, but skipped areas that I believe were already done by trixbox. Obviously fonality doesn't install everything needed for perl. I will be going through the perl section to make sure all is installed. The problems in this thread aren't the only ones I have encountered. I have already read other attempts to integrate trixbox and vicidial, but they're so blasted old, they definitely don't work anymore. Most attempts are only half done as it is.

I'm going to be working to fix the issues I see so far.

[williamconley]

Trixbox. Ouch.

I integrate FreePBX, but never Trixbox.

I know of some people who insist on passing through trixbox, but so far i know of noone successfully running a vicidial call center on a trixbox.

Either seperate the boxes or switch to freepbx only (and keep your freepbx dial plan completely seperate from your vicidial dial plan so freepbx doesn't interfere).

If you have a need for SugarCRM / FreePBX ... you should consider getting a couple cheap P4s and using a three box solution. You'll find everything works better in the end.

Nothing against Trixbox, but honestly after you've learned what it does and how to use the software installed ... the "Trix" in the trixbox needs to go away so you can use the full power of your system without the trix overhead.

[proxium]

SELECT extension FROM phones where protocol = 'SIP' and server_ip='10.48.10.8'

this query normally return no record in your database, but you need to check the VARserver_ip in /etc/astguiclient.conf and replace with the IP of your Asterisk Server then try to update your "phones "table and assign the same value to "server_ip" field, wich is the server that contains all your phone extensions.

If this return valid value, then perl script will use Telnet module to register the phone in Asterisk side and start calling.

[proxium]

sip show peers
Name/username Host Dyn Nat ACL Port Status
tofreepbx1/400 192.168.1.89 N 5060 OK (1 ms)
from-trunk (Unspecified) 5060 Unmonitored
2000/2000 (Unspecified) D N A 0 UNKNOWN
1111/1111 192.168.1.113 D N A 5060 OK (3 ms)
1000 (Unspecified) D N A 0 UNKNOWN
5 sip peers [Monitored: 2 online, 2 offline Unmonitored: 1 online, 0 offline]

I have a trunk on 192.168.1.89 to simulate a call between two AsteriskServer

As shown here, I did register my phone in Asterisk through Vicidial but I have the time synch problem "wich is the main topic" and I receive the error "No one in your session: 8600051"

[wizzbangca]

Yeah, trixbox is more and more becoming an ouch. I plan on creating a freepbx box, but the updating part of freebpx is a bit of a deterrent. I like "yum update" to take care of most of everything. In the long run, not much a good script can't handle anyway. I may end up comparing the two side by side and seeing which floats my boat the most.

And yup, I'm turning the scratch install into a script. Managed to get almost everything but the conf file edits working. So far everything is contained within one script including the mysql statements.

I need to figure out a one server for all solution. Too much consulting money going out the window without that. My production system is 2 dual core xeon processors, 8 gig ram, 750gig hd (4 x 250 gig raid 5). That may be able to handle everything.

Managed to get past everything except one problem: when I log into the agc side of vicidial, my phone rings, I pick up, the phone hangs up right away. I then see "Noone is in your session: 8600051", something a lot of others have come across. Hopefully that will get solved.

Thanks for the help so far.

[wizzbangca]

SELECT extension FROM phones where protocol = 'SIP' and server_ip='10.48.10.8'

this query normally return no record in your database, but you need to check the VARserver_ip in /etc/astguiclient.conf and replace with the IP of your Asterisk Server then try to update your "phones "table and assign the same value to "server_ip" field, wich is the server that contains all your phone extensions.

If this return valid value, then perl script will use Telnet module to register the phone in Asterisk side and start calling.

10.48.10.8 is the vicidial/tribox server ip. I changed the server ip to 127.0.0.1 in the asterisk conf. After a restart from other installs from the sratch install i fooled myself into skipping, the phones were all automatically updated to 127.0.0.1. That could have also happened when the update script was run too.

[Op3r]

you do know the vicidial 2.0.5 can now configure asterisk (carriers and phones).

Plus running anything than vicidial for your system is going to be an expensive experience.

ditch the trixbox. Download vicidialnow or vicibox, this autoinstaller will install everything from linux to vicidial. it will definitely make your shift at work a whole lot easier.

[wizzbangca]

Op3r, can't disagree with you. In large centers, that's the way I am going. But gotta have an all in one solution.

Got the conference channel working, and the user to stay in the open call. Here's how:

Edit vicidial_extensions.conf:

Code: Select all

[default]
include => ext-local

; Extension 8600 + 8601 conference rooms
exten => 8600,1,Meetme,8600
exten => 8601,1,Meetme,8601

'; Extension 129
exten => 129,1,Playback,transfer|skip ; "Please hold while..."
exten => 129,2,Dial,sip/129|20|to ; Ring, 20 secs max
exten => 129,3,Voicemail,u129 ; Send to voicemail...

; # timeout invalid rules
exten => #,1,Playback(invalid) ; "Thanks for trying the demo"
exten => #,2,Hangup ; Hang them up.
exten => t,1,Goto(#,1) ; If they take too long, give up
exten => i,1,Playback(invalid) ; "That's not valid, try again"

; Give voicemail at extension 8500
exten => 8500,1,VoicemailMain?
exten => 8500,2,Goto(s,6)

; ASTERISK AGENTS LOGINS FOR QUEUES (NOT part of VICIDIAL)
; the following assumes phone agent login and exten are 3 digits and the same
; also assumes that 3-digit login is present in agents.conf and queueus.conf
;Agent Logout then stay onhook, DIAL 54 + 3-digit ID
exten => _54XXX,1,AgentCallbackLogin()
; the following are used to login and logout of Asterisk Queues from phone
;Agent Login then stay offhook on the phone, DIAL 55 + 3-digit ID
exten => _55XXX,1,AgentLogin(${EXTEN:1})
;Agent Login then stay onhook, phones will ring, DIAL 56 + 3-digit ID
exten => _56XXX,1,AgentCallbackLogin(${EXTEN:1}@default)

edit extensions_custom.conf:

Code: Select all

#include vicidial_extensions.conf

[custom-vicidial]

include => default

[from-internal-custom]
include => default

That's all I did. I found that at http://www.vicidial.org/VICIDIALwiki/ti ... %3AFreePBX. Now just waiting for the pri to be available to see what happens.

[wizzbangca]

Finally got the pri available. Not dialing out now. So, more work ahead. Why am I not surprised? Why am i also not surprised there is nothing coming up when I search for this problem?

Looking at some logs, here's what i see:
From vdautodial.2009-04-23 (over and over and over again in the log) when someone is logged in waiting for a call.

Code: Select all

2009-04-23 16:05:35|SERVER CALLS PER SECOND MAXIMUM SET TO: 20 |50||
2009-04-23 16:05:35|LIVE AGENTS LOGGED IN: 0   ACTIVE CALLS: 0|
2009-04-23 16:05:35| : agents:      dial_level: 0|
2009-04-23 16:05:35| : Calls to place: 0 (0 - 0) 0 |
2009-04-23 16:05:35|CAMPAIGN DIFFERENTIAL: 0   0   (0 - 0)|
2009-04-23 16:05:35|LOCAL TRUNK SHORTAGE: 0|0  (0 - 23)|
2009-04-23 16:05:35| : CALLING|
2009-04-23 16:05:35||     lagged call vla agent PAUSED 0E0|20090423160505|20090423160525|20090423160535||
2009-04-23 16:05:35||     lagged call vac agent DELETED 0E0|2009-04-23 16:03:35||


This is from hopper.2009-04-23

Code: Select all

2009-04-23 16:02:02||TESTCAMP|Added to hopper 0||
2009-04-23 16:02:03||TESTCAMP|50|2|24hours|||
2009-04-23 16:02:03||TESTCAMP|Added to hopper 0||
2009-04-23 16:03:02||TESTCAMP|50|2|24hours|||
2009-04-23 16:03:02||TESTCAMP|Added to hopper 0||
2009-04-23 16:03:03||TESTCAMP|50|2|24hours|||
2009-04-23 16:03:03||TESTCAMP|Added to hopper 0||
2009-04-23 16:04:03||TESTCAMP|50|2|24hours|||
2009-04-23 16:04:03||TESTCAMP|Added to hopper 0||
2009-04-23 16:04:03||TESTCAMP|50|2|24hours|||
2009-04-23 16:04:03||TESTCAMP|Added to hopper 0||
2009-04-23 16:05:01||TESTCAMP|50|2|24hours|||
2009-04-23 16:05:01||TESTCAMP|Added to hopper 0||
2009-04-23 16:05:02||TESTCAMP|50|2|24hours|||
2009-04-23 16:05:02||TESTCAMP|Added to hopper 0||
2009-04-23 16:06:02||TESTCAMP|50|2|24hours|||
2009-04-23 16:06:02||TESTCAMP|Added to hopper 0||
2009-04-23 16:06:03||TESTCAMP|50|2|24hours|||
2009-04-23 16:06:03||TESTCAMP|Added to hopper 0||
2009-04-23 16:07:02||TESTCAMP|50|2|24hours|||
2009-04-23 16:07:02||TESTCAMP|Added to hopper 0||
2009-04-23 16:07:02||TESTCAMP|50|2|24hours|||
2009-04-23 16:07:02||TESTCAMP|Added to hopper 0||


The hopper in the campaign shows there are 2 leads.
[/code]

[williamconley]

Op3r, can't disagree with you. In large centers, that's the way I am going. But gotta have an all in one solution.

I'm happy to work with you on the "all-in-one" with vici built in. But when i add vici, i keep vici / freepbx separate (they merely coexist). I was using freepbx to create trunks and extensions.

Now that vici does it by itself, that may not be necessary, but there will likely always be a lot of small customers who want an all-in-one. With FreePBX married to Vici ... this is quite possible (i have a lot of customer with this solution running right now, so I guess "possible" may be an understatement).

We are about to update our install for 2.0.5 and will likely release on sourceforge (not part of THIS project, but definitely dependent upon it in whole). Just have to find the time for a release! LOL

I expect we'll approach it from Vicibox and add freepbx to it, but we may do a full scratch install on gentoo with freepbx and add vici (which also works nicely). Or Both. Hm.

[Op3r]

Give me gentoo with vicidial please? We have a centos and debian flavored vicidial distro now. Adding gentoo will seriously enhance the rep of vicidial

[williamconley]

I don't know about seriously enhancing the rep, but I ended up in Gentoo at the direction of a SugarCRM guru who I asked (a LOOOONG time ago) what the best OS was for modifying the kernel and ease of installation. I ended up in Gentoo and installed my first vicidial according to the scratch install. It took some tweaks (almost all OS / file location related) but installed and ran quite easily. I've been using it ever since because most of my clients also want sugar and freepbx and they all fit easily into gentoo.

i initially posted on sourceforge to try to officially make it possible to port vicidial into gentoo with freepbx easily, but have NOT had time to keep it up. i'd like to be able to get back into that and bring people along for the ride. now that vicibox is SERIOUSLY going to make life easy for fresh installers, I may have to add methods to get freepbx/sugar into ubuntu vicibox as well, but i'd still like to have time to keep the installs up on SourceForge (hoping to get as much involvement in here as possible). Causes more motion (have you SEEN the quantity of upgrades in 2.0.5? whoa!)

[proxium]

So, you're using FreePBX...

That could cause all sorts of problems.

In the Asterisk CLI type "sip show peers" and post what the entry for that phone looks like.

We moves away from the topic, but it should be there a solution to stop the warning messages about time synchronisation and empty session on Vicidial.

[mflorell]

If everything is installed and working properly you should not get this issue. All screen sessions need to be running and communicating with Asterisk for this to happen.

[williamconley]

Also, you should understand that the FreePBX dial plan will interfere with Vicidial quite a bit, so they need to be kept completely seperate.

Unfortunately, with Trixbox there are more issues than just dial plan: it also has software running that manages to interfere, and/or their kernel and OS basic install does not seem to agree with Vicidial. To date, noone has made CentOS work well except the VicidialNOW folks who took the time to do it. It was NOT a quick solution. (You could always offer them a bounty to get your box running, they are apparently very good at CentOS).

The problem is that this software was designed for (and runs very well on ...) Slackware. CentOS/Fedora/Red hat is not supported. Several of us have succeeded in porting it to other OSs (in fact, the success in the Ubuntu area has apparently led to the release of Vicibox!)

In other words: it's not an "aside" that there's a problem with FreePBX/Trixbox ... that's your entire issue. If you want to run on CentOS: Lose the Trixbox and use VicidialNOW. Matt and everyone else are all happy to help, but an integration of a Trixbox / Vicidial today is unlikely (to put it mildly).

[wizzbangca]

I got vicidial to the point where I can log in, but vicidial will not dial. I'm at a complete loss now.

[williamconley]

Check the Asterisk CLI (using agi debug and/or sip debug if necessary) and the vicidial logs in /var/log/astguiclient.

See what IS happening.

But first: Do you have all your screens? (screen -list)

[wizzbangca]

List of screens:
2963.astshell (Detached)
3274.ASTVDauto (Detached)
3004.asterisk (Detached)
2986.ASTfastlog (Detached)
3271.ASTlisten (Detached)
3268.ASTsend (Detached)
3265.ASTupdate (Detached)
3277.ASTVDremote (Detached)
2983.ASTVDadapt (Detached)

As far as I know, these are all the required screens. I haven't been able to find a complete list of required screens.

agi debug: command not found
sip debug: command not found

If everyone says these commands exist, why are they not found? I have tried looking for where the commands reside, but forget that. No one seems to know, or is willing to divulge. Tried looking for how to install these commands/associated programs, and yet again no one seems to know or divulge.

I need something running today, I've been screwing with this for too long. Everything I try brings up more unsolvable problems than anything I have ever seen. Here's what I've done:

Trixbox with Vicidal integrated (this form post)

Vicidialnow trunked to trixbox:
No one wants to divulge how to do this step by step(road block #1)
Extensions are on trixbox, causing problems with vicidial agent logins. again, no info found for this. (road block #2)

Vicidial scratch install trunk to trixboxL
same results as vicidialnow trunk to trixbox.

[williamconley]

agi debug and sip debug occur within asterisk at the cli (and are reversed by agi no debug and sip no debug)

it is not "no one wants to divulge how" it is "no one has succeeded in doing it" and even "why would i assist someone in building a canal from california to wisconsin when it has already been demonstrated to be a bad idea"

i'm happy to help you with each roadblock as it occurs, as are others i'm sure, on the off chance that you will succeed (which would be great by the way, witness "VicidialNOW"). but you will likely find that this battle will only be won by a team such as the vicidialNOW team (they DID get that to run on CentOS) and you will most likely find that the team who gets this running will not do so for free (and you are presently experiencing why).

I remind you of the canal blurb above, if you want a crew to help you "dig" ... you can assume it will not be free. if you want us to tell you which direction to go ... "East", ask again later when you get to the next road and we'll help again.

It's not about "don't run it on trixbox or centos" it's about: This is a long hard road, others have tried, if you wish to do so as well, be warned. And you have been from the moment you mentioned it. Right?

[Op3r]

I was using Centos with vicidial since when the sourceforge mailing list was the only way to get help from. It was a long hard road. We have encountered problems after problems with it but we stuck by it (because it was so easy to use).

It came to the point that I was able to integrate vicidial with asterisk@home. It ran fine for 5 agents then crap hits the fan when we added another seat.

as will can tell you. It was not that easy. I can integrate trixbox easily now. But I STAY AWAY FROM IT. and if you want my help it wont be free.

VicidialNOW works with centos because demian biscocho made so much changes on it, that basically its not centos anymore. the kernel was touched so that the Preemption will be set on SERVER and not DESKTOP.

As we keep on telling you, stay away from it. Learn VICIDIAL on its own for the moment. Once you have the experience and confident enough to start using trixbox with vicidial then thats the time you do it.

There's nothing with trying vicidial with trixbox to work efficiently and problem free. I am waiting for someone to do it at last and have vicidial run as a module for trixbox. I remember the elastix guys was trying to run vicidial as a module for elastix and I havent heard anything from it since then.

Sorry for the long rant. But to make it short. STAY THE HELL AWAY FROM IT.

[proxium]

As mentionned here, it's a related topic to the Time Synchronisation problem in new Vicidial (2.0.5)

I've fixed that issue in system with the help of mflorrel after reading this topic: http://www.eflo.net/VICIDIALforum/viewtopic.php?p=29845&sid=89a2432ad0163f110a81c5fbf71ad15e

this issue of course is a Vicidial 2.0.5 new way to check to time synchronisation between WebServer, DataBase and AsteriskServer (If I'm wrong plz correct me ) and there is a table in the database used by the Vicidial called server_updater, the surprise is, when I've checked this table, it was empty, so I've executed this code in SQL:
insert into server_updater values('10.10.10.15','','');

You should change 10.10.10.15 with the addresse of your Asterisk Server and the message disappear.

You need to check those points:

Don't forget to check the Server_IP in Database and astguiclient.conf use /usr/share/astguiclient/ADMIN_update_server_ip.pl script

Make sure that all needed script are shown with the command screen -ls

try to use the same source for the time synchronisaton of your system

Put the same time zone in your Vicidial and Asterisk server (if they are separated)

[jkidd]

For anyone researching this, I got this error and it was because I'd made changes to the root cron file