On Thu, Dec 3, 2009 at 10:29 AM, David Laperle
<dlaperle@rsslex.com> wrote:
Hi guys,
i have a weird problem with my dialplans. For the moment, i have only 2 «usable» extensions. They were working #1 yesterday, but this morning i realize i forgot to compile mod_python, so i go back into my source folder and modify the modules.conf to uncomment mod_python, did a make and make install (i did a backup of my conf folder before)! The make and make install worked flawlessly. Then i put back my bkp of conf directory.
I restarted the freeswitch service, created my python test dialplan and entered into cli to see what's gonna happen! To my surprise, the call didn't processed to the extension i was dialing.
i tried all the other extensions i had, they were all not working!!!!
After that i realized that the .xml in freeswitch/dialplan/default/ weren't imported into configuration at startup ...
I have read all the documentation about difference between public and default dialplan and i understand them correctly, in public if i include all default folder, it's working again (i can reach all my extensions in default.
My extensions are in the correct user_context ... i did nothing since yesterday other than a make && make install after enabling python ...
Any other user have an idea why the default/*.xml aren't processed automatically? What could i have done wrong so they are no longer processed?
double-check for the existence of conf/dialplan/default.xml - I've seen on rare occasion where that file simple goes away for no apparent reason. Since I never change that file - and I recommend that you never change it either ;) - you can go to your FS source directory and issue "make samples" and it will re-create any missing default config files without overwriting you existing config files.
-MC