Hi, I setup freeswitch with fusionpbx in a multi tenant evironment. Works fine. But currently I can not call "cross domain". So user 1 in domain A can not reach user 2 in domain B. When calling my log show the following: 2018-03-14 12:37:39.580028 [NOTICE] switch_channel.c:1104 New Channel sofia/internal/1@domain-A [19bbf41c-277c-11e8-81fa-4dba4b7d93a7] 2018-03-14 12:37:39.580028 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/1@domain-A) Running State Change CS_NEW (Cur 1 Tot 84) 2018-03-14 12:37:39.580028 [DEBUG] sofia.c:9873 sofia/internal/1@domain-A receiving invite from 1.2.3.4:54948 version: 1.6.19 64bit 2018-03-14 12:37:39.580028 [DEBUG] sofia.c:10044 IP 1.2.3.4 Rejected by acl "domains". Falling back to Digest auth. 2018-03-14 12:37:39.580028 [WARNING] sofia_reg.c:1792 SIP auth challenge (INVITE) on sofia profile 'internal' for [2@domain-B] from ip 1.2.3.4 2018-03-14 12:37:39.580028 [DEBUG] switch_core_state_machine.c:603 (sofia/internal/1@domain-A) State NEW 2018-03-14 12:37:39.580028 [DEBUG] sofia.c:2334 detaching session 19bbf41c-277c-11e8-81fa-4dba4b7d93a7 2018-03-14 12:37:39.619980 [DEBUG] sofia.c:2442 Re-attaching to session 19bbf41c-277c-11e8-81fa-4dba4b7d93a7 2018-03-14 12:37:39.619980 [DEBUG] sofia.c:9873 sofia/internal/1@domain-A receiving invite from 1.2.3.4:54948 version: 1.6.19 64bit 2018-03-14 12:37:39.619980 [DEBUG] sofia.c:10044 IP 1.2.3.4 Rejected by acl "domains". Falling back to Digest auth. 2018-03-14 12:37:39.639961 [DEBUG] freeswitch_lua.cpp:365 DBH handle 0x7fdb641160c0 Connected. 2018-03-14 12:37:39.639961 [DEBUG] freeswitch_lua.cpp:382 DBH handle 0x7fdb641160c0 released. 2018-03-14 12:37:39.639961 [WARNING] sofia_reg.c:2906 Can't find user [12@telequest.qcall.cloud] from 1.2.3.4 You must define a domain called 'telequest.qcall.cloud' in your directory and add a user with the id="12" attribute and you must configure your device to use the proper domain in it's authentication credentials. 2018-03-14 12:37:39.639961 [WARNING] sofia_reg.c:1737 SIP auth failure (INVITE) on sofia profile 'internal' for [2@domain-B] from ip 1.2.3.4 Is there a special setting or configuration I missed? Is it a ACL issue? Thanks in advance, Thorsten