Hello Liviu, I am already running the last version of OpenSIPS. opensips -V version: opensips 3.4.3 (x86_64/linux) deb https://apt.opensips.org bookworm 3.4-releases
In my example, the "iat" PASSporT value is correct. The only issue lies with the Date header field. Le mar. 20 févr. 2024 à 14:55, Liviu Chircu <[email protected]> a écrit : > Hi James, > > Make sure you're running a recent OpenSIPS build, I recall this bug was > caught a few months ago > <https://github.com/OpenSIPS/opensips/commit/75a168a9f43>. > > Best regards, > > Liviu Chircuwww.twitter.com/liviuchircu | www.opensips-solutions.com > OpenSIPS Summit 2024 Valencia, May 14-17 | www.opensips.org/events > > On 20.02.2024 15:03, James Seer wrote: > > Hello, > > I have a question regarding Date Header Verification in our setup: > > Server Timezone: Central European Time > Configuration: > require_date_hdr: false > verify_date_freshness : 300 seconds > SIP INVITE Date Header: Tue, 20 Feb 2024 00:26:05 GMT > Server time: 2024-02-20T00:26:06 CET > Identity header payload "iat" value: 1708385165 > > Despite the Date header being in the future, OpenSIPS proceeded with > verification. While I can see there's an existing error code (-6: Date > header value is older than local policy for freshness), it only addresses > cases where the header is "older" than the local policy. > > This could be easily handled in script code, but shouldn't opensips > trigger a distinct failure with a new error code, considering the > discrepancy between the Date header and server time ? (More than 300 > seconds of difference) > > Thank you > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
