I have been able to successfully install the ISO version of Multi-Tenant (with Asterisk 1.8) and it seems to work just fine. However when I try to install with my preferred method of building Asterisk 1.8 (using 1.8.5) and installing the Webmin module, it initially appears fine, but a simple test of calling one extension from another extension will fail saying the extension is not found in the context from-inside-tenantname.
I have spent many, many hours working on this issue from different angles, trying to ensure Asterisk is properly compiled, all dependencies are installed, etc.
I can copy all the /etc/asterisk files from an ISO-installed version to the Webmin-installed version and it seems to work fine. On the surface it would seem something is missing from the Webmin version. I have tried the same thing on Asterisk 1.6 and 1.4 as well with identical results.
Any thoughts? The current version of the administrator manual seems to not be updated as it still refers to Asterisk 1.4.
Of course. From a fresh load
Of course.
From a fresh load of CentOS 5.6 (32 bit):
- updated entire system with yum
- turned off SELinux
- installed dependencies (gcc gcc-c++ make wget subversion libxml2-devel ncurses-devel openssl-devel vim-enhanced kernel-devel-`uname -r` nano iptables unixODBC-devel libdbi-dbd-mysql mysql-connector-odbc) with yum
- downloaded source tarballs of Asterisk 1.8.5.0 and Dahdi (Complete 2.4.1.2+2.4.1) from asterisk.org site
- installed Dahdi (make, make install, make config)
- installed Asterisk (configure, make, make install, make samples) - all default settings
- installed Webmin from RPM (1.5.5.0-1)
- installed Thirdlane MT GUI (6.1.1.11) in Webmin by uploading file
(of course some minor steps omitted such as restarts and NTP)
When doing this, the Thirdlane GUI installs fine and seems to behave as normal (we have been using an older version of Thirdlane MT for over five years so we're pretty good at that).
- I create a new tenant (copied everything from Thirdlane tenant except we use a 12 character phone password)
- I create two SIP extensions in that tenant with all defaults
- Configured two Cisco SPA phones for each extension - registers successfully
- Call from either extension to the other results in fast busy signals and one line in the CLI that said the extension dialed was not in the context from-inside-tenantname
Interesting wrinkle - I have another machine where I loaded the Thirdlane MT ISO (and configured the same tenant and two extensions). If I copy the entire contents of /etc/asterisk from the ISO machine to this one (save for an edit of asterisk.conf because I'm not running as the user asterisk), it seems to work just fine.
Leads me to believe the Asterisk install is fine, but rather perhaps some scripts or something may have been missed in the WBM.GZ file for the Thirdlane GUI.
so from CLI do a 'dialplan
so from CLI do a 'dialplan show' and hte context it claims it isnt in.
in 1.8 if you have an #include statement to a nonexistent file it quits and doesnt process any more of the config file.
Erik, Your comment about the
Erik,
Your comment about the #include statement was the problem. Extensions.conf called many files, and most of them were present, however the following ones were not:
user_scripts.include
huntlists.include
user_extensions.include
Once I TOUCHed those files (to create empty files with those names), the dialplan filled out entirely and it is seems to be working correctly now. As these are specific to Thirdlane, I would suggest updating the installation script for the Webmin module to ensure these files exist. That will make a much better "out of the box" experience - especially for someone new to Thirdlane who doesn't already know how well it works.
Thank you for your help.
Josh
#include files
This is fixed in the next release. We keep chasing all the non backward compatible things in Asterisk - sorry for the inconvenience.
its unclear the order of steps you took when you built everything and installed the webmin module.. can you elaborate.