Any chance for phpmyadmin & config edit included?

As a long time [email protected]/trixbox user the phpmyadmin and config edit included in trixbox are nice tools that keeps me from moving away trixbox completely.

Is there any howtos or plans to include these nice apps in a standard freepbx install?

Bart

phpmyadmin does not make sense to be included in FreePBX as a tarball. On an ISO it makes sense.

As far as config edit, there are much better tools such as editors that understand and color code asterisk dial plans and config files. If you are doing any significant custom dial plan work, you want to do it there. If you are editing files because our gui doesn’t handle some basic stuff - then keep those feature requests coming in because we should get to where there is no need to hand edit any files other than custom dialplan development.

Manually installing phpmyadmin is trivial though. If youve gone to the efforts of installing asterisk & freepbx from sources, dropping phpmyadmin on the box will be a breeze.

[quote=“p_lindheimer”]
If you are editing files because our gui doesn’t handle some basic stuff - then keep those feature requests coming in because we should get to where there is no need to hand edit any files other than custom dialplan development.[/quote]

To all extensions I want to send a sms-message (if busy or unavailabel)
I can’t do this in freePBX( or ?)

exten=>1000,1,Dial(SIP/1000&SIP/1206,30,r)
exten=>1000,n,Macro(send_sms_message,0032476378861,${CALLERID(num)},${TIMESTAMP})
exten=>1000,n,GotoIf($[${DIALSTATUS} = BUSY]?busy)
exten=>1000,n,VoiceMail(u${EXTEN}@default)
exten=>1000,n,Hangup()
exten=>1000,n(busy),VoiceMail(b${EXTEN}@default)
exten=>1000,n,Hangup()

[macro-send_sms_message]
exten=>s,1,NoOp(${ARG1})
exten=>s,n,System(/usr/bin/curl -s "http://localhost/sms/sms.php?number=${ARG1}&msg=At%20${ARG3}%20${ARG2}%20called.")

the above is fundamentally flawed, FreePBX does not invoke the dial() command directly it uses dialparties.agi to determine who to actually dial. (And it is a bit more complicated then that because it depends on what you are dialing, if their are follow-me contexts, etc.

You will want to look at macro-exten-vm and macro-vm adn modify what you do when BUSY or UNAVAILABLE is returned. The best way to do this is copy the entire contexts to extensions_custom.conf and then modify them there as that will override what is in the main file.

Keep in mind that if you override core contexts like these, you will want to carefully review and updates to ‘core’ to see if anything has changed and apply your changes. The best way to do that is to:

[list]Copy the contexts you will change into extensions_custom.conf (leave the originals)
Make your changes until it works
Make a patch file (diff -ubB [original] [modified] > [patchfile])
Save your patch file somewhere[/list:u]
Now when a new version of extensions.conf becomes available (could be any time there is a core update):
[list]Copy the contexts again just like before
run patch: patch
Check the changes to make sure everything is still ok[/list:u]
This lets you apply the patch file and incorporate changes that get made to the real code at the same time.