Time sync problem again i know :)

[mark_flynn]

just need a quick point in the right direction.

i have managed to get goautodial 2.1 into a amazon ec2 environment with asterisk 1.4 and dahdi current version installed i have also patched the dahdi_dummy to use hi-res timers and dahdi_test -v returns with 99.99 to 99.87 i can dial into a conference room and my sip phone also registers with vicidial but when i login to agent gui there is no activity in the asterisk cli ie meetme request etc i can also dial other extensions with no problems and dial other routes on dialplan but then i get the time sync error popup on agent gui.

any ideas? i mean i feel its very close to working

[mark_flynn]

also William.

this is Mark Flynn from LBM (emails regarding cluster setup)

whats your skype addy?

[williamconley]

1) Poundteam Incorporated does allow direct contact off this board for anyone other than paying clients (AFTER they are paying clients ...). If you want direct support, we are very happy to help ... if you don't mind paying for it! Otherwise, this board is free and will allow all your answers and questions to be visible to the group AND allow others to answer as well.

2) If you intend to use Vicidial (GoAutoDial is an installer, as is Vicibox, but Vicidial is the product being installed ...) on an EC2 system, you'll be among many who have tried ... to date there have been none who succeeded (although a few have claimed success, those have failed to actually materialize ...).

3) If you "must" move forward (Please report your results!): you'll first need to see if all your screens are running:

Code: Select all

screen -list

[DavidAEsquivel]

Hi Mark,

I have battled with this issue for months on several different version of Vici. I my case, it turned out that the issue had nothing whatsoever to do with timing or bad memory or bad kernels or any of the million other guesses as to what the problem might be.

It was so much simpler that I was stunned and quite frankly a bit upset that the error message was so unrelated to the actual problem. If you change the IP Address on the server from the default but fail to properly run the update_server_ip script without error. It will cause this error every single time on pretty much every version of Vici that I have tried.

David

[striker]

hi David

what server model you are using?
which method of vicidial installations you are following?