From 21e03349ddbd7d39d4b382e33a8d639ddfefd01f Mon Sep 17 00:00:00 2001
From: FusionPBX <markjcrane@gmail.com>
Date: Wed, 17 Feb 2021 22:12:24 -0700
Subject: [PATCH] Chang the tls-verify-date so that it defaults to false.

---
 resources/templates/conf/sip_profiles/internal-ipv6.xml.noload | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/resources/templates/conf/sip_profiles/internal-ipv6.xml.noload b/resources/templates/conf/sip_profiles/internal-ipv6.xml.noload
index 1129d7a80b..c9fcf7b73e 100644
--- a/resources/templates/conf/sip_profiles/internal-ipv6.xml.noload
+++ b/resources/templates/conf/sip_profiles/internal-ipv6.xml.noload
@@ -60,7 +60,7 @@
 		<!-- Optionally set the passphrase password used by openSSL to encrypt/decrypt TLS private key files -->
 		<param name="tls-passphrase" value=""/>
 		<!-- Verify the date on TLS certificates -->
-		<param name="tls-verify-date" value="true"/>
+		<param name="tls-verify-date" value="false"/>
 		<!-- TLS verify policy, when registering/inviting gateways with other servers (outbound) or handling inbound registration/invite requests how should we verify their certificate -->
 		<!-- set to 'in' to only verify incoming connections, 'out' to only verify outgoing connections, 'all' to verify all connections, also 'in_subjects', 'out_subjects' and 'all_subjects' for subject validation. Multiple policies can be split with a '|' pipe -->
 		<param name="tls-verify-policy" value="all|subjects_all" enabled="false"/>