incorrect call time

[macmaglaque]

Hi Guys,

Any ideas why my customer time is incorrect?

I'm located in the Philippines and all of my settings are set to +8

When I'm calling a number in the US, I get a different time. How can I correct this?

https://www.dropbox.com/s/5expzjbynx9a9ck/customer%20time.PNG?dl=0

Time difference is just exactly from my time (PHT) minus the GMT.

[williamconley]

------------
1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Client time is an important feature. It's also listed in the Vicidial Manager's Manual (free version in the store at EFLO.net is very useful, as mentioned above). As a short summary, you must ensure that the dial code is correct and that the local time/gmt settings for the list are correct as well as the time settings during upload. The system has many time settings to allow it to calculate the time of the client properly. Which are discussed in the manual, of course.

[macmaglaque]

Hi William,

This is for manual dial and not an uploaded list. Dial code used is 1


Vicidial 2.14-614a BUILD: 170430-1001 | Asterisk 1.8.23.0 | AWS Server Virtual Machine Single Core | No Digium | Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz

[williamconley]

Doesn't change my answer. You're looking at the client time which is determined the same way to display on the screen as it is for autodialing. If the client's time is wrong in the DB, it's wrong in the DB for both purposes.

[macmaglaque]

Okay William will check the manual.

Thank you!


Vicidial 2.14-614a BUILD: 170430-1001 | Asterisk 1.8.23.0 | AWS Server Virtual Machine Single Core | No Digium | Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz

[williamconley]

You can also look directly at a lead record in the DB and check the GMT field. There is a script that runs at 1AM and 7AM to validate this value on all leads. So you can modify a lead record and run that script to see if your mods were successful. Hint: the goal here isn't to manually set the GMT, but put the appropriate information in the lead record, such as Dial Code, Area Code, and Postal Code, to allow the script to correctly identify the Time Zone.

This is mostly managed during upload of leads, but there are also settings in the list modify and a few other places.

[macmaglaque]

Hi Everyone,

Here's my actual problem. Whenever I call toll free numbers such as 800, 888 etc., gmt_offset_now is set to +0 only. How can I correct this?

https://www.dropbox.com/s/2vzbhrgacm0lx5p/gmt_offset.PNG?dl=0

Regards,

[mflorell]

You can manually add entries to the vicidial_phone_codes for toll free numbers.

Here's the db schema of that table:

CREATE TABLE vicidial_phone_codes (
country_code SMALLINT(5) UNSIGNED,
country CHAR(3),
areacode CHAR(3),
state VARCHAR(4),
GMT_offset VARCHAR(6),
DST enum('Y','N'),
DST_range VARCHAR(8),
geographic_description VARCHAR(100),
tz_code VARCHAR(4) default ''
) ENGINE=MyISAM;

[macmaglaque]

thanks Matt!

Last 2 questions please.

First, how can I change the link for the recordings from http to https? I blocked access to http so that my users will only https by default. (no http to https allowed)
Lastly, why does the call records of my agents in the real time reports doesn't reset to 0? Instead, it adds the calls from the previous days. I already followed the instructions to point the voicemail server to my server's ip and run the vars script and wait till for my set gmt time but still the same.

[mflorell]

To have https links on audio recordings, you'll have to add the "--HTTPS" flag to the crontab entries for the audio processing scripts.

As for the call counters, make sure the Timeclock End of Day is set to a time when you voicemail server is up and running, because that's when the ADMIN_keepalive_ALL.pl script will run those queries.

[macmaglaque]

Hi Guys,

I'm still getting the wrong customer time using manual dial. When I uploaded the same number on the dialer, it showed the correct time.

I'm using 510 California number.

Regards,

[williamconley]

Hi Guys,

I'm still getting the wrong customer time using manual dial. When I uploaded the same number on the dialer, it showed the correct time.

I'm using 510 California number.

Regards,

You might have uncovered a bug (or an incomplete feature?). I just tried two manual dials in a row and one failed. Arizona, time was correct, but that was a lead that was already in the system. But the one in CA was GMT and was not an existing lead. It appears that newly created leads are not checked against the area codes table during dialout.