Thirdlane.com logo

Ulaw codec not an option when adding users

Posted by cbbs70a on Thu, 05/08/2008
Forums
Thirdlane platform General Questions

Hello;
I am evaluating Thirdlane's PBX manager for Asterisk and I see that when adding a SIP/User extension, the available codecs do not show ulaw. How does one add options that are available? Also, it does not allow me to specify any context that I would like to use. Why should I have to pick a context of theirs? This does not make sense.
Thanks
FSD

Submitted by thirdlane on Thu, 05/08/2008 Permalink

This is strange. Which codecs do you see?

Which version of PBX Manager are you running?

Submitted by cbbs70a on Fri, 05/09/2008 Permalink

Hello;

I am using command-line Asterisk and am looking at Thirdlanes PBX manager as a tool for my customers. I have already written 2500+ lines of configuration. It seems like a good product so far, but since I already have a configuration, I would like to not have to rewrite all of it to use the GUI. So my question is this, I already have default contexts written, but the PBX manager already has set names for default contexts also, such as 'local-extensions', etc which I don't want. Can I change this? In general, are these default settings configurable or do I have to go with the options that Thirdlanes software wants to use? Are development tools/docs available so I can configure the software the way I want and add options and tools that I want?

Thanks

FSD

Submitted by eeman on Sat, 05/10/2008 Permalink

Some things are static, such as from-inside, from-inside-redir and local-extensions. They are deeply imbedded into hundreds of macros. Other aspects are entirely open to customization. I have not found a single GUI out there that allows for as much customization as PBX manager. A context name is just a context name, I wouldn't get too hung up on not having a specific context name if the same features exist within a different name. The end users never see them. The scripts section is the section where you can add options and tools. If you want to modify the way a specific system script works, clone a copy and make your modifications, then call your macro instead of the packaged one.

No GUI is going to give you the flexibility that purely command-line editing is going to give you. But, being faced with the same dilemma as the rest of us, there comes a need for some of the simpler tasks to be turned over to an end user. It comes down to finding a management interface that gets you the ability to offload simpler tasks to end users without completely binding your hands and feet. No GUI will ever be as flexible as editing a file. One is always bound to a framework while the other is a completely blank canvas. There will always be some compromise when selecting a graphical interface. PBX Manager accomplishes much of this without locking you out or overwriting your changes on the next save. Unlike freepbx and a few others, it is done in a way that continues to allow asterisk to mark packets with the proper QoS tags for your network equipment to prioritize on.