This is continuing the issue I posted regarding the Thirdlane Connect utility on a fresh install in the wrong forum.
I verified with our team. We did add the EPEL repo to the installation. EPEL repo was needed to install cloud-init utilities into the installation to allow it to properly run on Openstack/Amazon EC2. Outside of that installation, no changes to the default installation have been made.
As posted in my previous message, installed version of Thirdlane and Thirdlane Connect are:
Installed Packages
thirdlane-connect-mt.noarch 1.0.6-7.el6 installed
Installed Packages
pbxmw-mt.noarch 8.0.1.1-19.el6 installed
We are about to attempt to install a single tenant demo version to determine if the same issue exists with single tenant or if this issue is exclusive to Multitenant.
Only other potential cause of the issue I can think of is a setting that needs to be manually configured somewhere for the external IP and/or additional firewall ports to be opened (we mirrored the stock IPTables configuration on our firewall).
External IP may be an issue though if there is a setting for it somewhere. In Amazon/Openstack the virtual machine itself is assigned a private ip address and a public floating ip address is translated by the virtualization layer that the local VM is unaware of. Asterisk handles this issue with the externip configuration directive in sip.conf and that part works without any issue. I am wondering if a similar setting of some type needs to exist for the Thirdlane Connect product? Are their logs anywhere for thirdlane connect that can be reviewed?
OK, after spending hours on this trying to determine what would be causing this issue, I have found the "bug".
Essentially, Thirdlane Connect does not work with Tenant names containing CAPITAL letters. Once I discovered this, when I went back to try to login to thirdlane connect, I noticed after hitting login, the username would briefly change to all lowercase letters before displaying the error message. Obviously, the error message is extremely unhelpful and does not really provide any hint/clue whatsoever as to the problem.
I have reproduced this several things in different ways.
New install:
1. I created another fresh install of MTE, successfully logged into Thirdlane Connect with an extension in the default thirdlane tenant.
2. Added a new tenant called Capital_tena that cloned the settings of the thirdlane tenant.
3. Created an extension in the new tenant with all default settings except name and ensured thirdlane connect was enabled.
4. Attempted to log into Thirdlane Connect using the new extension's web credentials and received the error previously posted about version mismatch.
Old Install:
1. Went back and verified that I could connect to Thirdlane Connect in default thirdlane tenant using a new extension created in that tenant. It was successful.
2. Added another new tenant to the system new_tenantlc that cloned the settings of the existing tenant that was created that used CAPITAL letters to ensure no other settings in that tenant could have been the cause of the problem.
3. Created a new extension in new_tenantlc with default settings.
4. Successfully logged into Thirdlane Connect with the new tenant that had all lowercase letters for the tenant name.
5. Verified the login for the extension in the tenant that used capital letters, still failed which it did still fail.
Recommended Fix:
Allow Thirdlane Connect to work with logins/tenant names that contain CAPITAL letters.
Alternative Solution:
Prevent tenants from being created that use CAPITAL letters.