22 posts / 0 new
Last post
jlindler
jlindler's picture
Joined: 2015/01/15
Points: 0

Ideas of what to check? The logon logo spins forever on logon on the TL Connect page, and then, you finally get the message, "Connection timeout, try again or contact your system administrator".

jlindler
jlindler's picture
Joined: 2015/01/15
Points: 0

Subsequent attempts will sometimes yield "Critical error occurred, error code 108".

agrunev
agrunev's picture
Joined: 2013/12/05
Points: 30

Hello,

Which Thirdlane Connect and Thirdlane PBX Version are you using? There was a similar issue in initial release, but it has been fixed. If possible, could you create an extension for me and email me the credentials to agrunevthirdlane.com, so I could take a look?

Thanks.

Andrey Grunev,
Software Engineer at Thirdlane

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 360

Jay,

You should consider upgrading to the most recent Thirdlane Connect. Please make sure licensing is in order.

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

jlindler
jlindler's picture
Joined: 2015/01/15
Points: 0

Hi Alex,

Yes, we are on the latest version of TL Connect. I will send Andrey an email with testing information.

jclappton
jclappton's picture
Joined: 2016/09/29
Points: 10

Does your tenant name contain capital letters?
I got the 108 error when I mistakenly used caps in my tenant names which doesn't work with the connect app.

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 360

Next release of Thirdlane platforms and Thirdlane Connect will handle mixed case tenants - mostly for backward compatibility as going forward we will not allow caps in tenant names.

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

biznet
biznet's picture
Joined: 2016/01/19
Points: 10

So, All our tenants have all caps in the tenant names, Wish I had known this when I first configured all of my 35 tenants. Also wish there was an "edit tenant name" possibility. As it now, one has to delete the tenant which includes all extensions and settings. This is not a good thing.

I guess my question is, will we have to change them eventually to small letters?

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 360

While renaming tenants would be a very useful feature, it won't be easy to implement, so we are debating on doing that.

As far as Thirdlane Connect support for the existing tenant names in uppercase or mixed - as I mentioned in the previous post, next release (due before the end of the month) will take care of that.

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

biznet
biznet's picture
Joined: 2016/01/19
Points: 10

Anxiously awaiting the new release that will allow for Mixed Case tenant names as I think that the thirdlane connect will be a great marketing tool and useful for new AND our old tenants.

I have instituted the policy of any new tenants will be small caps for future compatibility.

WRT a facility to change the tenant names within the Thirdlane GUI: the biggest problem for us will be having to physically visit the phones themselves (since they are mostly behind NAT devices at our customer sites) as the account names will be wrong in every one of them. Since our phone are all over the place, this will be a major big deal for some 250 of them we have so far. We supply the phones as part of our service, our customers do NOT currently have the admin password to configure the phones.

So, my request, would include for you guys to include some way of ignoring case in phone account names during registration. Worste case if we have to we can manually write down each tenant settings and manually remove and recreate the tenant as long as the phone account name is caps agnostic in the registration process.

Again, I mention that unless there is a compelling reason to NOT keep all caps tenant names backward compatible in future versions, please don't do it, or at least give us a 6 mth minimum warning with at least the above phone login request.

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 360

I am not sure if I understood exactly what is requested, so I repeat what we plan to do in the next release.

We will respect the case for any objects including registrations for the existing tenants (there will be no requirements for tenants to be lowercase) and we will support mixed case tenants in thirdlane connect. In the future GUI will not allow upper case letters in tenant names when creating tenants while old tenants could stay the way they were created - mixed or upper case or whatever. Would that be ok?

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

jlindler
jlindler's picture
Joined: 2015/01/15
Points: 0

I found that WebRTC has been turned off in preferences. I enabled it and now the error is "Connection timeout, try again or contact your system administrator"

jlindler
jlindler's picture
Joined: 2015/01/15
Points: 0

More information - Asterisk is using HTTP port 8088, and the system needed a firewall exemption for this port from localhost to localhost to logon. So, I can get in, but I have no audio.

eugene.voityuk
eugene.voityuk's picture
Joined: 2014/01/28
Points: 70

There must be no need to add additional firewall rules for 8088, except you are using non-standart iptables, in our distro by default there is a rule that accepts any traffic on localhost interface.

jlindler
jlindler's picture
Joined: 2015/01/15
Points: 0

Yes... that is rule one. I removed the rule I added, and things seem to be working seem in terms of the connection. What should I check as audio is not being passed?

biznet
biznet's picture
Joined: 2016/01/19
Points: 10

Alex,

What you suggest is perfect wrt case sensitivity. All existing tenants will forever be acceptable in all caps, to create tenants in the future mixed case will go away... this is acceptable, thanks for the clarification.

RJansen
RJansen's picture
Joined: 2017/11/29
Points: 0

We are on the thirdlane platform 8.2.1.1 (Multi tenant) and Thirdlane Connect 1.3.1
We have one tenant who want's to use the app however the tenant name stars with a capital E and gets the critical error 108 when he wants to login the connect app. Other tenants without the capital in the names can login without problems. Can you confirm that the capital letter in the username is not the problem with the mentioned software and connect release numbers?

jakeness
jakeness's picture
Joined: 2017/02/15
Points: 0

I can confirm that it's not a problem for me anymore - same version (current)
Although I haven't used caps in the tenant names since it was an issue but my previous built ones don't have a problem.
I've had a few times where I have to go into Webmin and disable Force change at next login for each user before I could get them to log in. Maybe try that.

RJansen
RJansen's picture
Joined: 2017/11/29
Points: 0

I tried the webmin suggestion, did't work. Still get the 108 error. I tried another tenant with a capital in the name and got the same error. Every other tenant without capital in the tenant name work without problems.
I noticed thirlane "fixed" the problem by making sure you can't start a new tenant with a capital in the name. It automaticly changes the capitals in small letters when you save the newly created tenant. So thats good for new tenants but somehow my tenants with a capital in the name wants to use the connect app.

@ thirdlane is there some way to make the tenant with the capitals in the name able to login or is the only solution to delete the entire tenant and create it again?

thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 360

I am not sure what may be wrong. If you could send us access info we'll take a look.

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

cleartalk
cleartalk's picture
Joined: 2010/05/25
Points: 0

@RJansen do you have SSH access to the PBX server?

If so check the file /etc/prosody/vhosts.cfg.lua and search for the tenant name.
If the tenant name is not in the file create a new file /etc/prosody/vhosts.static.lua and place the following vhost config ( or copy one from the vhost.cfg.lua ):

VirtualHost "TENANT.local"
Component "muc.TENANT.local" "muc"
modules_enabled = { "muc_focus"; "mam_muc"; "offline_gcm"; "muc_broadcast_settigns"; "muc_membership_query"; "muc_create"; "muc_custom_fields"; "muc_unique_name"; };
focus_media_bridge = "jitsi-videobridge.default.local"

After that edit the /etc/prosody/prosody.cfg.lua, change Include "vhosts.cfg.lua" to Include "vhosts.*.lua".
restart prosody service.

Then try to log on in Connect.

This worked for us till the update that fixed the capital in tenant name.

RJansen
RJansen's picture
Joined: 2017/11/29
Points: 0

The tenant name is in the file but thanks for the suggestion. I recreated the tenant when there is no capital in the tenant name everything works fine. Think this was the fastest way to help the tenant.