Musarano Posted July 16, 2019 Report Share Posted July 16, 2019 Hi ! I been trying to setup the TimeZone for Puerto Rico (NDST) but i always get 1 hour ahead when checking the call logs. I tried setting at the domain and as the system sections, but still i havent been able to do so. Also, the Server where Vodia-PBX is running on, is been set as Puerto Rico Zone ( The servers are in Miami, soon in a second place too ), and most of the my customers are in Puerto Rico. Sorry if i been posting quite a bunch of Posts, but i will like to run Vodia-PBX/SS as best possible that can be ! Love the product !! -Thank You -M Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 16, 2019 Report Share Posted July 16, 2019 I think "Atlantic Time Zone (No DST)" should be your time zone. There is no daylight savings in Puerto Rico right? Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 Hi. Yes, that is correct. I also tried several others like eastern etc, but no luck so far.. Hope this helps. -M Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 16, 2019 Report Share Posted July 16, 2019 Well - did you try "Atlantic Time Zone (No DST)" and did it solve the problem? Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 Yes, it was from the beginning with that setting... but i havent been able to achieve the correct time. It always one hour ahead.. Of coase this is only changing in it under domain and as global configuration. -M Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 16, 2019 Report Share Posted July 16, 2019 So maybe your problem is not so much the PBX itself - it might be the VoIP phone. You can check if the PBX has the time right by leaving a dummy mailbox message and then listen to it - maybe pressing "4" to hear the time when it was received. If that time is correct, the PBX itself has the time correct. If the time on the VoIP phone is incorrect, then this might be a problem with the timezone for that specific vendor and model. Unfortunately there is absolutely no standard for the different VoIP phones and we are trying to keep up. If the the VoIP phone gets it wrong let us know what model and vendor you are using and we'll take a look if it can be corrected. Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 I think im not been clear, sorry. The problem is not at the phones, instead, at the Calls Log at VODIA-PBX, which is reporting the calls with one hour ahead of time, with the proper time set or selected. Im using VODIA as SSwitch.. no phones are registered to it. example: 7/16/2019 1:15:07 PM <sip:+18891335878@localhost> <sip:00241315083233@localhost> 02:04 farendpbx 1:16:45 PM "CallerCallerCaller" <sip:+1xxxxxxxxxx@localhost> "Customer" <sip:+1xxxxxxxxxx@localhost> 00:07 ITSP 1:14:56 PM "CallerCallerCaller" <sip:+1xxxxxxxxxx@localhost> "Customer" <sip:+1xxxxxxxxxx@localhost> 01:00 ITSP 1:13:28 PM "CallerCallerCaller" <sip:+1xxxxxxxxxx@localhost> "Customer" <sip:+1xxxxxxxxxx@localhost> 01:21 ITSP 1:13:33 PM "CallerCallerCaller" <sip:+1xxxxxxxxxx@localhost> "Customer" <sip:+1xxxxxxxxxx@localhost> 00:48 ITSP 1:04:57 PM "CallerCallerCaller" <sip:+1xxxxxxxxxx@localhost> "Customer" <sip:+1xxxxxxxxxx@localhost> 07:54 ITSP 1:09:58 PM "CallerCallerCaller" <sip:+1xxxxxxxxxx@localhost> "Customer" <sip:+1xxxxxxxxxx@localhost> 00:21 ITSP 1:08:09 PM "CallerCallerCaller" <sip:+1xxxxxxxxxx@localhost> "Customer" <sip:+1xxxxxxxxxx@localhost> 00:53 ITSP 1:05:48 PM "CallerCallerCaller" <sip:0757@localhost> <sip:18773@localhost> ITSP 1:03:38 PM <sip:+18891335878@localhost> <sip:00341315083233@localhost> 02:04 farendpbx The time should be 12:nn:nn as calls been currently dialed, but registered wrongly. I will be setting back the time to Atlantic to retry testing. Thank You -M Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 Didnt work either... Still showing time 1 hour ahead. Assuming i dont need to restart the service.. -M Quote Link to comment Share on other sites More sharing options...
Support Posted July 16, 2019 Report Share Posted July 16, 2019 Do you have an NTP server settings done here: /reg_ports.htm on the PBX? Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 Checking... Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 Noup, dont seems to have that file on >vodia networks\vodia pbx\> Quote Link to comment Share on other sites More sharing options...
Support Posted July 16, 2019 Report Share Posted July 16, 2019 Not sure what you are referring to, but we're talking about this: Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 Oh ! im sorry, i thought that was reffering to the path on hard disk That section is emtpy. but i can go ahead and try time.windows.com ? -Thank You Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 In fact, i dont have the second option NTP server on that configuration page. Hope this helps ! Quote Link to comment Share on other sites More sharing options...
Support Posted July 16, 2019 Report Share Posted July 16, 2019 Edit the NTP port and you'll get it. Make sure that NTP port is open on your firewall. Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 Huh! funny, somehow and suddenly, NTP server section, appeared from no where after i try entering and deleting some data in that field of NTP Port Now, its gone again, but i saw ntp.vodia.com there.. but again, it got hidden. Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 14 minutes ago, Support said: Edit the NTP port and you'll get it. Make sure that NTP port is open on your firewall. Just did. Still no changes. 123 TCP opened in FW. Quote Link to comment Share on other sites More sharing options...
Support Posted July 16, 2019 Report Share Posted July 16, 2019 You need to re-provision the phones after that point. Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 I am not using phones.. im using the GUI to check this out, Looking at the Inbound/outbound calls that are listed on Vodia Status+Call Logs or Vodia Status+Call Logs Show wrong time of the call event. Phones behind the far-end PBX are working normally with correct time locally. (There is no physical phones connected to Vodia) The problem is the listing on GUI. Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 16, 2019 Author Report Share Posted July 16, 2019 I found out that blanking the NTP Port and clicking outside, it brings on the NTP server field. I wrote there time.windows.com from ntp.vodia.com, but it seems that it will require to restart the VodiaPBX Server, since several other Item field got a green arrow at the side.. -M Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 17, 2019 Author Report Share Posted July 17, 2019 I managed to try everything safe i could. But still Vodia showing wrong time (1 hour ahead) I even setted up with NTP server: pr.pool.ntp.org + port 123. Windows update and sync time fine. But still no luck showing any different time under Call Logs in Vodia GUI. Will erasing the whole calls history fix this? Thank You -M Quote Link to comment Share on other sites More sharing options...
Support Posted July 17, 2019 Report Share Posted July 17, 2019 The call logs that has been written until this point will not change (as far as we know). Have you restarted the PBX to make sure the settings take effect? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 17, 2019 Report Share Posted July 17, 2019 Chiming in... The call log timezone depends on the browser - the PBX sends it in GMT and then the browsers job is to show this in the local time zone. It is actually easy and browsers are good in calculating the local time. Quote Link to comment Share on other sites More sharing options...
Musarano Posted July 17, 2019 Author Report Share Posted July 17, 2019 Thank You Both! Yes, you were correct, testing and testing, it ended up using (UTC-04:00) Georgetown, La Paz, Manaus, San Juan And now, things seen accordingly ! Great! Thank You! -M Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.