Timezone + Callback function - messed up

[ayger]

Installation info:

Code: Select all

server : HP DL380 G5
version: ViciBox Redux v.4.0.3
astguiclient : VERSION: 2.6-394a BUILD: 130130-1207
Telephone card : Digium TE121 (T1/E1/J1)
Installation type : Single Server
Installation method : New install, dedicated box,
Asterisk version : Asterisk 1.4.44-vici
Installation medium : ViciBox.x86_64-4.0.3.iso
Other software installed : HP health agents only (disk raid monitoring, fan status)


Hi all,

Facts :

- Server time set to UTC and sync up with ntp server

Code: Select all

 hwclock ;date ; date -u;
Tue Mar 19 12:16:51 2013  -0.969221 seconds
Tue Mar 19 12:16:55 UTC 2013
Tue Mar 19 12:16:55 UTC 2013



- *system* timezone set to GMT+2 (Istanbul,Turkey)
- Timezone on php.ini set

Code: Select all

cat -n /etc/php5/apache2/php.ini |grep timezone
   997  ; Defines the default timezone used by the date functions
   999  date.timezone =Europe/Istanbul


- Timezone reported by phpinfo()

Code: Select all

date/time support   enabled
"Olson" Timezone Database Version   0.system
Timezone Database   internal
Default timezone   Europe/Istanbul

- Local Time on admin panel (upper left corner) displayed correctly
-Local Time on web interface on agents is displayed correctly
- Server setting on vicidial admin interface "Default Local GMT:-5:00"
- Phone settings on vicidial admin interface "Local GMT:+2:00"
- Agent's Desktops : Cloned image with identical software version (firefox/sip client), *identical* and locked settings (eg timezones etc etc)
- Campaign running : Only one (blended-incoming/outgoind)
- Database checks/repair : Already done, no corruption found.
- AST_VDauto_dial.pl output:

Code: Select all

 perl /usr/share/astguiclient/AST_VDauto_dial.pl --debugX
TIME DEBUG: ||0|   [b]GMT: 12:13[/b]
2013-03-19 [b]12:13:23[/b]|LOGGED INTO MYSQL SERVER ON 1 CONNECTION||
2013-03-19 [b]12:13:23[/b]|192.168.1.7: CALLING|
TIME DEBUG: 2.00|2.00|0|   [b]GMT: 10:13[/b]



I doubled checked that agents on "CAMPAIGN CALLBACK HOLD LISTINGS" are entering the right information and the desired callback time.

For example :
LEAD LIST CAMPAIGN ENTRY DATE CALLBACK DATE USER RECIPIENT STATUS GROUP
49204 996 {campaign name} 2013-02-19 18:31:03 2013-02-20 11:00:00 114 USERONLY LIVE users


Description of the problem;

On some agents i'm facing the following;

- Customer time is with -6 hours offset
- Callbacks on some agents are not displayed correctly. There's no "Live" but "Active Callback" link.


It seems that the timezone/clock information is totally messed up, or i've done something *totally* wrong.
Any suggestion would be highly appreciated.
Thank you,


PS: As you can probably see there's slight difference on reporting times on the above message due to copy/paste and seconds spent to format the provided information.More or less, you can understand the time difference.

[williamconley]

You provided lots of system information and configuration / setup info. But the errors are ... vague. I see no actual details of where this offset is observed. You should also post the underlying data. Customer time could be offset by 6 hours because the area code lookup failed or because you have a phone number from Hawaii (cell) being used by a client in Orlando ... Then there is "not displayed correctly" which leaves a lot to the imagination. A screen cap or code display would be nice. Once again, showing the data direct from the DB for this would not be a bad idea either. Please cite a single example and avoid subjective terms such as "the right" or "desired" while instead using the actual time entered and in what field on what form. (Technical details, right? )