ACL problem

[noci]

I have a gateway XYZ,
created from a copy of the external profile. It has the ACL XYZACL.

When receiving a call through this gateway the log shows:

90306b46-9424-48f2-85a0-b42b52a89ef8 2019-08-28 22:02:35.944298 [DEBUG] switch_core_state_machine.c:585 (sofia/XYZ/abc@127.0.0.1) Running State Change CS_NEW (Cur 3 Tot 3)
90306b46-9424-48f2-85a0-b42b52a89ef8 2019-08-28 22:02:35.944298 [DEBUG] sofia.c:10242 sofia/XYZ/abc@127.0.0.1 receiving invite from D.E.F.G:5060 version: 1.10.0 -release-11-7a921c608b 64bit
2019-08-28 22:02:35.944298 [DEBUG] sofia.c:10336 verifying acl "XYZACL" for ip/port D.E.F.G:0.
2019-08-28 22:02:35.944298 [WARNING] sofia.c:10449 IP D.E.F.G Rejected by acl "XYZACL"
90306b46-9424-48f2-85a0-b42b52a89ef8 2019-08-28 22:02:35.944298 [DEBUG] switch_core_state_machine.c:604 (sofia/XYZ/abc@127.0.0.1) State NEW
90306b46-9424-48f2-85a0-b42b52a89ef8 2019-08-28 22:02:35.944298 [NOTICE] sofia.c:2424 Hangup sofia/XYZ/abc@127.0.0.1 [CS_NEW] [CALL_REJECTED]

The D.E.F.G address actualy is mentionin the ACL
XYZACL is default deny
allow P.Q.R.S/32
allow D.E.F.G/32
allow K.L.M.N/32
(because there are 3 optional remote addresses).

Adding 127.0.0.1/32 to the ACL didn't help
Why does this fail?

Neither restarting the server after various changes did make a difference.

 

[noci]

I have a gateway XYZ,
created from a copy of the external profile. It has the ACL XYZACL.

Found the issue....
ACL in the profile was XYZACL, the ACL was actualy named: XyzACL


So the error wasn't XYZACL rejected .....
but instead: XYZACL not found.