All of this happens before it hits the dialplan. The call is being received on a sip profile configured to require authentication and there is not matching user to authenticate against. If your scenario never requires authentication, then don't configure it on your sip profile settings.

On Mar 9, 2015, at 10:08 AM, rentmycoder rentmycoder <rentmycoder@gmail.com> wrote:

I try to recive incoming calls from a gateway using FS without external profile.... I would like to use just one profile, and route incoming calls based on DID-s and context, just like in asterisk... But FS always logs:

sofia.c:8834 sofia/internal/13245678@1.2.3.4 <mailto:13245678@1.2.3.4> receiving invite from 1.2.3.4:5060 <http://1.2.3.4:5060/> version: 1.4.14 sofia.c:9001 IP 1.2.3.4 Rejected by acl "domains". Falling back to Digest auth.

sofia_reg.c:2827 Can't find user [2000@192.168.101.44 <mailto:2000@192.168.101.44>] from 1.2.3.4 You must define a domain called '192.168.101.44' in your directory and add a user with the id="2000" attribute and you must configure your device to use the proper domain in it's authentication credentials.

I do not need any users at all...

I just need to recive calls from a gateway and route them to specific context/extension in XML dialplan...

How to do thet? What is the context parameter of the gateway is used for, if not for that purpuse?