Obi 202 NTP not working. Wrong Date and Time

<< < (2/2)

SteveInWA:
WTH.  In all the years I've been on this forum, I have never heard of that parameter even mentioned.

So, the question is, which ITSP are you using on those SP slots?  It would help others who may run into this.

Good job figuring it out.

ubergoober:
I don't think this is going to be a widespread problem. 

I run FusionPBX/Freeswitch on an odroid which does not have a hardware clock.  Re-syncing Freeswitch with the system clock corrected the date/time shown in SIP messages, but disabling X_ProcessDateHeader will provide insulation against future trouble.  Incidentally, even though the sofia stack was sending SIP messages with incorrect dates, my CDR records reflect correct dates and times.

T

ProfTech:
Quote from: SteveInWA on December 18, 2019, 10:04:15 pm

WTH.  In all the years I've been on this forum, I have never heard of that parameter even mentioned.


The parameter has always been there. And I think it is "checked" by default. If you don't put in an NTP server or can't reach one you can use the time stamp sent by the ITSP. I suppose there might be a case where you might use it if you wanted your phones to display a different time zone than the one you're actually in.

ubergoober:
In my opinion, this feature is OK as a backup strategy where NTP isn't accessible.  But to make it the default, and might I say rather invisible choice is a mistake.  NTP is reliable and available in most environments. 

T

Navigation

[0] Message Index

[*] Previous page