INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

FreeSwitch - config assistance for a newbie

FreeSwitch - config assistance for a newbie

(OP)
Since I am a total newbie to FreeSwitch please be patient and 'gentle' with me....

With a new IT position I have 'inherited' 2 FreeSwitch installations.
* One installation environment is working (version 1.0.7)
* And one installation environment (version 1.5.14) is a new test environment that is not working.

I have tried to search the 428 page FreeSwitch documentation for an answer and got totally lost within it.
And I have tried to search the web for an answer, but did not find anything clearly spelled out.
And, lastly, I tried to investigate the working installation - duplicating settings as best I could to arrive at an answer, but could not get things working in the new test environment.

Now on to describe my problem....

I cannot get the new test environment to answer the inbound call and in the FreeSwitch log I find: Rejected by acl "domains". Falling back to Digest auth.

I have a dedicated SIP phone line which can successfully call into the new test environment.
And via FS_CLI I can see the call being received.
However the connection is never established and in the log I find: Rejected by acl "domains". Falling back to Digest auth.
NOTE - I have the incoming call's IP address already defined in the following files:
c:\freeswitch\debug\conf\autoload_configs\acl.conf.xml

CODE -->

<list name="domains" default="deny">
<!-- domain= is special it scans the domain from the directory to build the ACL -->
<node type="allow" domain="$${domain}"/>
<!-- use cidr= if you wish to allow ip ranges to this domains acl. -->
<node type="allow" cidr=<incoming call's IP address>/>
</list>

c:\freeswitch\debug\log\freeswitch.xml.fsxml

CODE -->

<list name="domains" default="deny">
<!-- use cidr= if you wish to allow ip ranges to this domains acl. -->
<node type="allow" cidr=<incoming call's IP address>/>
</list>

In both FreeSwitch environments I have a directory named: c:\freeswitch\Debug into which the previous individual installed all of the configuration parameters.
That path definition is defined in the c:\freeswitch\debug\log\freeswitch.xml.fsxml file, but nowhere else.
But if Freeswitch were not 'aware' of the \debug directory, it would not 'know' to 'look' into it for configuration info.

Questions regarding the new test environment:
1. Where/How is FreeSwitch configured to recognize this 'Debug' directory so that it will look for its configuration parameters there?
**** Maybe the non-working environment does not have that setting established and therefore is ignoring settings made there.

2. Within the Debug directory I have configured the new inbound IP address into the file: acl.conf.xml and have 'mirrored' the working environment in that regard.
**** But the 'Rejected' message in the log suggests that somehow that is not being recognized.

3. Are there other files which I have missed in trying to set this up?

Any assistance/advice/suggestions you might have would be GREATLY appreciated.

Thanks
JRB-Bldr

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close