I found the following in my vars.xml: <!-- Internal SIP Profile --> <X-PRE-PROCESS cmd="set" data="internal_auth_calls=true"/> So I think auth is still enabled. And I confirmed my voip client does register successfully before placing the call to 5000. From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of TTT Sent: Monday, November 21, 2022 2:50 PM To: 'FreeSWITCH Users Help' <freeswitch-users@lists.freeswitch.org> Subject: Re: [Freeswitch-users] User processed in wrong context I’m afraid I don’t understand your answer…how did I disable auth on internal? I’m working from the basic installation (RPM on CentOS8) with vanilla config (RPM for CentOS8)) and all I’ve done is update some addresses. From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian West Sent: Monday, November 21, 2022 1:39 PM To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org <mailto:freeswitch-users@lists.freeswitch.org> > Subject: Re: [Freeswitch-users] User processed in wrong context You've disabled auth on internal which puts you into public... can you elaborate? On Mon, Nov 21, 2022 at 12:02 PM TTT <lists@telium.io <mailto:lists@telium.io> > wrote: Based on a old posting I found, I suspect this may be acl related. I added the cidr below, could that be the cause? If so, can someone explain how that affects context selection? <list name="domains" default="deny"> <node type="allow" domain="$${domain}"/> <node type="allow" cidr="172.31.254.0/24 <http://172.31.254.0/24> "/> </list> From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org <mailto:freeswitch-users-bounces@lists.freeswitch.org> ] On Behalf Of TTT Sent: Sunday, November 20, 2022 6:07 PM To: 'FreeSWITCH Users Help' <freeswitch-users@lists.freeswitch.org <mailto:freeswitch-users@lists.freeswitch.org> > Subject: [Freeswitch-users] User processed in wrong context I have installed basic FreeSWITCH with the vanilla config. So far so good. My client app can authenticate fine as user 1019. The list_users command shows the 1019 id as in the "default" context. I then try to dial 5000 (which should be the IVR demo), but instead the call is processed as an outside_call (true) so I cannot reach the ivr. I see this interesting line on the console: 2022-11-20 17:00:58.066297 98.20% [INFO] mod_dialplan_xml.c:639 Processing testuser<1019>->5000 in context public Why is user 1019 being processed in the public context? The user's configuration shows it in the default context. So shouldn't it be processed in context 'default' (internal calls), not 'public'? Since my phone client connects to port 5060 (I can’t actually change it) it SHOULD be treated as internal. Unless, mod_dialplan_xml uses some other criteria to select the context for the user. _________________________________________________________________________ The FreeSWITCH project is sponsored by SignalWire https://signalwire.com Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. Build your next product on our scalable cloud platform. Join our online community to chat in real time https://signalwire.community Professional FreeSWITCH Services sales@freeswitch.com <mailto:sales@freeswitch.com> https://freeswitch.com Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com -- Brian West | Co-founder and Developer Need Commercial support? email sales@freeswitch.com <mailto:sales@freeswitch.com> FreeSWITCH Solutions | <https://maps.google.com/?q=17345+Civic+Drive+%232531+Brookfield,+WI+53045&entry=gmail&source=g> 17345 Civic Drive #2531 Brookfield, WI 53045 Email: brian@freeswitch.com <mailto:brian@freeswitch.com> Mobile: 918-424-9378 Website: <https://www.freeswitch.com/> https://www.FreeSWITCH.com <https://www.facebook.com/freeswitch> <https://twitter.com/freeswitch>
