Access-control configured correctly but blocked the access

SCZ8.3.0 m1p2

After configuring a new access-control in the following way:

access-control

    realm-id                MB

    description               

    source-address             10.64.0.0/10

    destination-address           62.169.69.218

    application-protocol          SIP

    transport-protocol           ALL

    access                 permit

    average-rate-limit           0

    trust-level               low

    minimum-reserved-bandwidth       0

    invalid-signal-threshold        5

    maximum-signal-threshold        0

    untrusted-signal-threshold       0

    deny-period               30

    nat-trust-threshold           0

    max-endpoints-per-nat          0

    nat-invalid-message-threshold      0

    cac-failure-threshold          0

    untrust-cac-failure-threshold      0

    last-modified-by            admin@10.135.193.194

    last-modified-date           2024-03-27 11:42:31

With realm-config like this:

realm-config

    identifier               MB

    network-interfaces           M00:310

    mm-in-realm               enabled

    media-policy              TOS_SIP_audio

    access-control-trust-level       low

    invalid-signal-threshold        1

    untrusted-signal-threshold       20

    nat-invalid-message-threshold      5

    deny-period               60

    pai-strip                enabled

    restricted-latching           peer-ip

    restriction-mask            24

    accounting-enable            disabled

We noticed that traffic from the only two test-users with IPs 10.65.213.191 and 10.98.227.28 has got blocked (no answer from SBC).

Any idea of what could have caused SBC to start blocking this traffic?