Mike, Anthony, thanks for the advice. I set accept-blind-auth in my external profile and FS does not challenge the invite any more. Did I understand right that without accept-blind-auth FS challenged incoming Invite because of the presence of Proxy-Authorization header in the Invite? Do I understand right that if I place accept-blind-auth inside <gateway></gateway> it will work for that gateway only? Thank and regards, Nikolay. _____ From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris Sent: Friday, January 15, 2010 1:22 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] sip trunk question: why call throughexternalprofile is challenged? This now rings a bell, also, if you create a gateway on that profile who's gateway name matches the realm on the incoming auth header, I think that also was working. Mike On Jan 14, 2010, at 5:01 PM, Anthony Minessale wrote: try setting param accept-blind-auth to true in your sofia profile config internal.xml iirc it was made just for sipX who feels the need to send auth headers even when nobody asked for them. so even when auth-calls is false we will still try to parse the auth if one is sent. On Thu, Jan 14, 2010 at 11:21 AM, Michael Jerris <mike@jerris.com> wrote: if you look in the sample configs for the words blind and auth you will find all these settings, also you can setup acls for ip auth to not challenge. Mike On Jan 14, 2010, at 3:26 AM, Nikolay Kondratyev wrote: Mike, thanks for the reply. Mmm. looks like I need more detailed instructions where to dig. Is there a way to turn off "challenging" completely? I thought that <param name="auth-calls" value="false"/> should do it, but alas. By the way should this parameter be visible in either "sofia status profile external" or "sofia status gateway sipx4.lab.nstel.ru <http://sipx4.lab.nstel.ru/> " ? I don't see it. I attached traces of failed and successful calls.