Caller ID Time is Not Correct

[karychen]

Does anyone here know how to set the time on the pap2 or is that something that VT has to do for you? Mine is Off by 1 hour, I live in the Central Time zone and it is off by 1 hour. Anyone with a clue how to change this please let me know, just PM me, or leave me the answer here thanks:cool:

[Brian188]

If you are provisioned, then VT will have to make the change for you.

If you have the Admin password you can set the time zone on the regional tab of the PAP2.

[RUSHnATL]

If you have the Admin password you can set the time zone on the regional tab of the PAP2.

I've got the admin password and I've set my time zone multiple times. It's fine for a little while, but after about an hour or two it appears to reset.

Do you think there's something on VT's servers that have it hard coded to my account? I'm using a server in the same time zone (eastern & New York server).

I had a problem with the CP Call Log showing Central time so put in a support ticket for that to get fixed, but now the caller ID is ahead an hour. I'd rather have it back the old way. So apparently there's a bigger flaw somewhere.

Hopefully somebody might know how to fix.

[Brian188]

I've got the admin password and I've set my time zone multiple times. It's fine for a little while, but after about an hour or two it appears to reset.

Do you think there's something on VT's servers that have it hard coded to my account? I'm using a server in the same time zone (eastern & New York server).

I had a problem with the CP Call Log showing Central time so put in a support ticket for that to get fixed, but now the caller ID is ahead an hour. I'd rather have it back the old way. So apparently there's a bigger flaw somewhere.

Hopefully somebody might know how to fix.

You need to turn provisioning off, or have VT make the change for you. Every 3600 secs. (1 hour) your adapter calls to VT's provisioning server and downloads all the settings. This will need to be disabled or it will just re-set all your changes. Under the provisioning tab of your PAP2 (Admin/advanced view required) set provisioning enable to "NO".

[W1IRH]

Seeing as how another Daylight Savings time adjustment is coming up in a couple of weeks, you should set the Daylight Saving Time Rule parameters. On Sipura/Linksys devices it is on the Regional tab.

An example of the string is:
Start=3/9/7/02:00:00;end=11/9/7/02:00:00;save=/+1

The rules are:
Configuration is defined by 3 fields. Each field is separated by semicolon as shown below. Optional values inside [ ] are assumed to be 0 if they are not specified. Midnight means 0:0:0 of the given date
Start = <start-time>; end=<end-time>; save = <save-time>
• <start-time> and <end-time> are of the form:
<month> /<day> / <weekday>[/HH:[mm[:ss]]]
• <save-time> is of form: [/[+|-]HH:[mm[:ss]]]
• <month> = 1,2,3,…,12 (for Jan, Feb, …, Dec)
• <day> = [+|-]1,2,3,…,31
• <weekday> = 1, 2, 3, …, 7 (for Mon, Tue, …,Sun), or 0 which has special meaning
• HH = hour (0-23)
• mm = minute (0-59)
• ss = second (0-59)
<start-time> and <end-time> specify the start and end-time date of daylight saving time.
<save-time> is the amount of hour/min/sec to add to the current time during daylight saving period.
The <save-time> value can be preceded by a negative (-) sign if subtraction is desired instead of addition.
If <weekday> is 0, it means the date to start or end daylight saving is at exactly the given date. In that case, the <day> value must not be negative.
If <weekday> is not zero, then the daylight saving starts or ends on the <weekday> on or after the given date
if <day> is positive, or on or before the given date
If <day> is 1, it means the <weekday> on or before the end-of-the-month (in other words the last occurrence of < weekday> in that month).

Have fun.

[sbradshaw]

Seeing as how another Daylight Savings time adjustment is coming up in a couple of weeks, you should set the Daylight Saving Time Rule parameters. On Sipura/Linksys devices it is on the Regional tab.

An example of the string is:
Start=3/9/7/02:00:00;end=11/9/7/02:00:00;save=/+1

The rules are:
Configuration is defined by 3 fields. Each field is separated by semicolon as shown below. Optional values inside [ ] are assumed to be 0 if they are not specified. Midnight means 0:0:0 of the given date
Start = <start-time>; end=<end-time>; save = <save-time>
• <start-time> and <end-time> are of the form:
<month> /<day> / <weekday>[/HH:[mm[:ss]]]
• <save-time> is of form: [/[+|-]HH:[mm[:ss]]]
• <month> = 1,2,3,…,12 (for Jan, Feb, …, Dec)
• <day> = [+|-]1,2,3,…,31
• <weekday> = 1, 2, 3, …, 7 (for Mon, Tue, …,Sun), or 0 which has special meaning
• HH = hour (0-23)
• mm = minute (0-59)
• ss = second (0-59)
<start-time> and <end-time> specify the start and end-time date of daylight saving time.
<save-time> is the amount of hour/min/sec to add to the current time during daylight saving period.
The <save-time> value can be preceded by a negative (-) sign if subtraction is desired instead of addition.
If <weekday> is 0, it means the date to start or end daylight saving is at exactly the given date. In that case, the <day> value must not be negative.
If <weekday> is not zero, then the daylight saving starts or ends on the <weekday> on or after the given date
if <day> is positive, or on or before the given date
If <day> is 1, it means the <weekday> on or before the end-of-the-month (in other words the last occurrence of < weekday> in that month).

Have fun.

Slight correction to your post. The correct Daylight Saving Time Rule string should be:

start=3/8/7/2:0:0;end=11/1/7/2:0:0;save=1

[W1IRH]

Slight correction to your post. The correct Daylight Saving Time Rule string should be:

start=3/8/7/2:0:0;end=11/1/7/2:0:0;save=1

Thanks for the correction. Looks like we both got the ending date wrong though. It ends on Sunday November 2 this year, not November 1.

start=3/8/7/2:0:0;end=11/2/7/2:0:0;save=1

[sbradshaw]

Thanks for the correction. Looks like we both got the ending date wrong though. It ends on Sunday November 2 this year, not November 1.

start=3/8/7/2:0:0;end=11/2/7/2:0:0;save=1

Actually, the one I provided is the correct one. The 1 does not exactly represent that actual day of the month when the rule applies (remember that the syntax was designed so that they rule could stay the same no matter what year you are in). 11/1/7 means that the first Sunday (7) that falls on or after the first day (1) of November (11) matches the rule. Make sense?

If you go with yours, then on a year when Sunday falls on November 1st, your rule will not work...as it will only match the Sunday (7) that falls on or after the second day (2) of November (11) -which would be Nov. 8th.

So the actual rule is:

start=3/8/7/2:0:0;end=11/1/7/2:0:0;save=1

Hope this helps. :)