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!
  • Students Click Here

*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.

Students Click Here


Elastix Help on Context

Elastix Help on Context

Elastix Help on Context


A customer has an Elastix version 2.4 (That It was already installed when I checked it), They have two context for extensions, one context that allows extensions to make external calls without entering PIN's and another contexts that ask for PIN's for allowing make external calls.
When I edited the file "extensions.conf", I saw that the contexts were created manually into this file.
My doubt, context must be created into the file "extension_custom.conf"?, because when the file "extensions.conf" is modified and If The Elastix is restarted or reloaded Dialplan all the modification make in the file "extensions.conf" are lost becasuse this file is overwrited?, Or Is There a way to configure Elastix for not losing the changes make manually in the file "extensions.conf" when Elastix restsrt or When the dialplan is reloaded? If there's a way? I think this Elastix have it because changes make in the file "extensions.conf" aren't lost (I don't know how')
Please, Any Ideas?

RE: Elastix Help on Context

I believe you are correct. I don't personally use freepbx gui on any of my systems (which I think is what elastix uses) but I recall when playing with it early on in trixbox distro that you couldn't make any changes to the actual extensions.conf file because of what you are describing. The system would overwrite the whole file when any changes were made in the gui. That is the reason for the extension_custom.conf. You should see something at the top of the auto-generated extensions.conf file that "includes" the custom file. That makes it seem to the system that they are the same file when you do a dialplan reload from the asterisk command line.

Long story short. Put the contexts in the extensions_custom.conf and they should survive changes properly.

Let me know if you have questions and I can probably help.


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!

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