time synchronization problem / Zaptel

[Zahid]

Hardware -Intel(R) Xeon(R) CPU 5120 @ 1.86GHz /12 GB
Distro Name GoAutoDial CE 2.0
Kernel Version 2.6.18-194.8.1.el5.goPAE (SMP)
Asterisk 1.4.27.1-1

After a server reboot I am facing time synchronization problem, when my agents try to login on vicidial application they received following error & there is no call back received on softphone as well.

“There is a time synchronization problem with your system, please tell your system administrator”
“Noone is in your session: 8600051”
I have noticed my zaptel drivers are not loading; I try to load but received following errors,
[root@go /]#
[root@go /]# lsmod | grep zaptel
[root@go /]#
[root@go /]# lsmod | grep ztdummy
[root@go /]#
[root@go /]# modprobe zaptel
FATAL: Module zaptel not found.
[root@go /]#
[root@go /]# modprobe ztdummy
FATAL: Module ztdummy not found.
[root@go /]#
[root@go /]#

Please advise, thanks.

[williamconley]

does your phone register?

is your system using zaptel or dahdi?

what version and build is your Vicidial?

[gardo]

Looks like you have upgraded your kernel.

Hardware -Intel(R) Xeon(R) CPU 5120 @ 1.86GHz /12 GB
Distro Name GoAutoDial CE 2.0
Kernel Version 2.6.18-194.8.1.el5.goPAE (SMP)
Asterisk 1.4.27.1-1

You need to recompile and reinstall DAHDI.

# cd /usr/src/dahdi
# make
# make install

[williamconley]

gardo, would it be possible to build in a "kernel version checker" that would do that automatically if the kernel were updated? (or perhaps even just a warning somewhere in a log?)

i mean for GoAuto3.0

[Zahid]

I was using Zaptel, now i install a fresh copy of GoAutoDial CE 2.0 but still zaptel is not working, now i have try vicidialnow-ce-1.3 and it works.

Would you please guide me how i can back up my dialer including configs, DB & recording so that i case of any disaster I can rebuild and restore my configurations and logs for reporting purposes. Thank you,

[williamconley]

perhaps you could explain how you knew zaptel wasn't working (perhaps it was asterisk 1.4 and had dahdi instead of zaptel?) were you able to dial into a conference/meetme room?

there is a backup script in /usr/share/astguiclient, and a user manual for Vicidial at eflo.net (free, but there is a MUCH more robust paid version that will save you quite a bit of time).

[Zahid]

Hi William, when i run lsmod | grep zaptel & lsmod | grep ztdummy it doesn't retrun me any process, previously it does, that's how i come to know that the zaptel is not working.

[williamconley]

on the other hand, what if dahdi is installed instead of zaptel?

the question is: what is not working that makes you believe zaptel is your problem?

can you register a phone? then can you dial into a conference room?

[Zahid]

May be dahdi was there & i just only look for zaptel; i was able to register the phones but when i dial any conference number it doesn’t respond & if i try to login agents through vici-application i received the following error & there is no call back received on softphone as well. I check all the timing related issues, like hardware & OS time should be same, server & phone using the same time settings etc.

Error - “There is a time synchronization problem with your system, please tell your system administrator”

So you mean with fresh GoAutoDial CE 2.0 installation dahdi is the default timing interface?

[DhwaniTechnologies]

I am posting my views on this topics, if some of my comments are incorrect please correct me.

To start with, I have done a successful installation of Goautodial with Sangoma PRI cards. That server has been running for over 6 months now without an issue.

You are definitely using Dahdi and not Zaptel unless you made some serious changes in the system (unlikely).

The error you are facing is most likely not because of the drivers anyway. I have seen that error multiple times on SIP based installations of Goautodial.

You need to first check your memory utilization, make sure that too much memory is not being utilized unnecessarily for caching/paging. More details on this are available in the Stickies on this forum.

Secondly, you need to make sure that your server and agent system time are synchronized. Watch out for the time that's ticking on the top of your agent screen. If this goes out of sync for more than a few seconds, the server will think that the agent screen is not responding and therefore give you that error.

Also, check your server time zone. If you are in another country and using a non-US timezone, make sure your agents are also using the same timezone.

I hope this helps.

[williamconley]

ordinarily time sync errors result from loss of contact between the agent's web browser and the server.

if the agent's internet connection to the server is bad, and the agent is using a soft phone ... then vicidial may not be able to call that agent on their soft phone.

can you show us the Asterisk CLI output from an attempt to dial a conference room? and from an agent attempting to log in?

Code: Select all

asterisk -R
set verbose 20

JUST the relevant lines please (not 3000 lines of code ... just the ones that result from a dial attempt or login attempt ...)

also (a basic piece of info):

Code: Select all

screen -list

please post the output from this at the regular command line (if you do not have at least 7 screens, you have not been successful in your installation ... you may wish to try again and/or try vicibox redux to see if your results are better.

[gardo]

That's in our roadmap. We were able to do it for the Sangoma Wanpipe drivers to automatically recompile when the kernel version changes. We'll have it available for DAHDI on the next release.

gardo, would it be possible to build in a "kernel version checker" that would do that automatically if the kernel were updated? (or perhaps even just a warning somewhere in a log?)

i mean for GoAuto3.0 Cool

DAHDI is the default not Zaptel on GoAutoDial.

May be dahdi was there & i just only look for zaptel; i was able to register the phones but when i dial any conference number it doesn’t respond & if i try to login agents through vici-application i received the following error & there is no call back received on softphone as well. I check all the timing related issues, like hardware & OS time should be same, server & phone using the same time settings etc.

Error - “There is a time synchronization problem with your system, please tell your system administrator”

So you mean with fresh GoAutoDial CE 2.0 installation dahdi is the default timing interface?

[Zahid]

Dear All, thank you for your help but i installed a fresh copy of vicidialnow-ce-1.3 and it works great for me.

[williamconley]

As long as it works!

Remember you CAN upgrade the 2.0.5 vicidial in that install to SVN or to 2.2.1 (for the pretty agent screen).