[Freeswitch-users] User processed in wrong context

TTT lists at telium.io
Mon Nov 21 19:49:50 UTC 2022

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 at lists.freeswitch.org] On Behalf Of Brian West
Sent: Monday, November 21, 2022 1:39 PM
To: FreeSWITCH Users Help <freeswitch-users at 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 at telium.io <mailto:lists at 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=" <> "/>





From: FreeSWITCH-users [mailto:freeswitch-users-bounces at lists.freeswitch.org <mailto:freeswitch-users-bounces at lists.freeswitch.org> ] On Behalf Of TTT
Sent: Sunday, November 20, 2022 6:07 PM
To: 'FreeSWITCH Users Help' <freeswitch-users at lists.freeswitch.org <mailto:freeswitch-users at 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 at freeswitch.com <mailto:sales at freeswitch.com> 

Official FreeSWITCH Sites

FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org <mailto:FreeSWITCH-users at lists.freeswitch.org> 




Brian West | Co-founder and Developer

Need Commercial support? email sales at freeswitch.com <mailto:sales at 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 at freeswitch.com <mailto:brian at freeswitch.com> 

Mobile: 918-424-9378

Website:  <https://www.freeswitch.com/> https://www.FreeSWITCH.com

 <https://www.facebook.com/freeswitch>  <https://twitter.com/freeswitch> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20221121/c6fd71ac/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 344 bytes
Desc: not available
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20221121/c6fd71ac/attachment-0001.jpg>

More information about the FreeSWITCH-users mailing list