Users.conf, sip.conf, extensions.conf oh my!

Ok, so my brain is fried… I cant for the life of me figure out how these three talk to eachother or how the context is passed around. Can someone explain it?

My users can make calls to hard phones defined in the users.conf, they can get into VM, but one can not call a sip phone. It does not register their dynamic address and connect one to the user.

Suggestions? Should I be writing the extention into sip.conf as a [context]? Is that truly a context? Is context = default global?

my brain… it hurts us…

:stuck_out_tongue:

Thanks ya all. If you need examples of what asterisk now has spat out, I would be glad to paste them up. I have also manually added users in sip.conf in accordance to the exaples in the wiki outline.

(NoOb) :open_mouth: :stuck_out_tongue:

ok… so no where in the documentation is it mentioned that the usernames for all accounts created with the gui are in reality the extension names…

When I came to this realization, I nearly fell over… it feels so obvious, but I overlooked it.

Sorry :unamused:

But how DOES everything fit together? There really isnt much documentation on how the users.conf works…

Therefore the GUI is not a really good place to start playing Asterisk. users.conf is trying to do too many things that other config files traditionally do. Combined with scandalous lack of documentation, it can easily confuse veterans.

Do without users.conf and GUI. This will ease the learning curve.

I was wondering if using GUI in 1.4.4 made only me feel like I was “The Class Dunce”.

I figured a version with GUI would be a breeze to pick up, HUHN !!!

I am a novice to Asterisk but have worked in PBX’s and Class 5 Switching offices all my life. (25 +) the issues I have run into have made me realize that although I have a copy of O’Reilly FOT not all things are covered in the book and having forums such as this are an absolute necessity…

Learn on asterisk-1.2

If you want to jump straight into the GUI, users.conf holds all the info for individual extensions. They are generally then accessible through the [default] context.

If you are really keen, I suggest opening all the config files in an editor (like kate on KDE). Make your changes and see which files get updated.