The IKE log is explicitly failing at Quick Mode with "no matching selector config," even though the crypto proposals line up perfectly. That means the tunnel's traffic-selector (the local/remote subnets) doesn't match the policy on one side. In this case the peer is offering 8.19.99.1/24 (and expecting 8.18.99.1/24 on our side), but our IPSec policy likely only permits, for example, 8.19.99.0/24 ↔ 8.18.99.0/24. By adding the actual /24 network (e.g. 8.19.99.0/24) or the specific /24 selector that the peer is initiating as a permitted initiator, the Quick Mode selectors will align and the tunnel will establish.