This post is at: ForumNews and Announcements
14 posts / 0 new
Last post
thirdlane
thirdlane's picture
Joined: 2007/02/07
Points: 320

We are pleased to announce the availability of Thirdlane Connect 1.0.7 powered by Thirdlane Business PBX and Thirdlane Multi Tenant PBX platform 8.0.1.2

Thirdlane Connect enables team communication using voice and video conferencing, private and group chat, integrations, screen and file sharing and works in modern browsers, on mobile devices, and Windows, Mac, and Linux desktops.

This is a follow up release that further enhances Thirdlane Connect and adds new features to simplify Thirdlane Connect deployment and operation to Thirdlane Multi Tenant and Thirdlane Business PBX platforms.

Note that Thirdlane Connect requires Asterisk 11, so if you are currently using Thirdlane with Asterisk 1.8, are current on your maintenance, and want to update, please follow the instructions in the initial Thirdlane Connect announcement.

New in this release:

  • Enhanced Domains and SSL certificates management, "Let's Encrypt" Certificate Authority integration
  • Support for wild card SSL Certificates
  • ICE (STUN and TURN) server management in Communications Manager, and use in Thirdlane Connect
  • Desktop versions of Thirdlane Connect can now be downloaded using Thirdlane Connect web application
  • New User Interface for Thirdlane Connect launch page, visual improvements to Thirdlane Connect for web, Windows, Mac, Linux and Android
  • Updates to Thirdlane Connect for Android at Google Play.
  • Various minor enhancements and bug fixes
awoodman
awoodman's picture
Joined: 2016/09/21
Points: 20

Hi Alex,

When will the repo's be updated to do a "yum update"? No updates showing for me... My Connect client for Android says "The version of your server (1.1.1) does not support your Thirdlane Connect version (1.0.7)...
Also where can we download the latest version of the Windows client?
https://www.thirdlane.com/product/download
doesn't have a link for the windows client anymore...

Alan.

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

Hi Alan,

In this release, we added a new RPM package, "thirdlane-connect-downloads", which contains Thirdlane Connect clients for Windows, Linux and OS X and is required by Thirdlane Connect 1.0.7. Once you update, open the web version of Thirdlane Connect, move to Settings -> Thirdlane Connect Downloads, click "Show download links" and select "Thirdlane Connect for Windows".

Regarding the repo's update - we are already investigating the problem.

Thanks,
Andrey.

Andrey Grunev,
Software Engineer at Thirdlane

awoodman
awoodman's picture
Joined: 2016/09/21
Points: 20

Thanks Andrey!!! Looking forward to the update!!!

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

Alan,

Repos were updated, so now it is:

yum clean all
yum update

and let us know if all is well

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

awoodman
awoodman's picture
Joined: 2016/09/21
Points: 20

Hi Alex,

Updated via repos...

I'm having issues getting the Android and Windows app to connect... Seems Prosody has an issue... I've emailed all the logs for you to review...

Please help to resolve this issue for me...

Regards,

Alan.

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

after updating asterisk11 and asterisk11-devel, asterisk won't start anymore.
/usr/sbin/safe_asterisk: line 170: 10799 Illegal instruction (core dumped) nice -n $PRIORITY "${ASTSBINDIR}/asterisk" -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}
/usr/sbin/safe_asterisk: line 170: 10807 Illegal instruction (core dumped) nice -n $PRIORITY "${ASTSBINDIR}/asterisk" -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}

matthewmalk248
matthewmalk248's picture
Joined: 2015/08/09
Points: 20

Getting this error when trying to log into thirdlane connect web version..

Connection error
Critical error occurred, error code 108

log "secure" shows I logged in successfully with my test extension 1001 on thirdlane tenant..

Successful login as thirdlane-1001 from 127.0.0.1

but prosody seems to be having trouble in uniserver.proxy.log..

2016-12-13 11:46:31.568401 -0500 trace Uniserver::Prosody::Async:59: Reconnecting Prosody...
2016-12-13 11:46:31.568767 -0500 info Uniserver::Prosody::Async:26: Trying to connect to localhost:5582...

and in uniserver log..

[
2016-12-13 11:43:37.181773 -0500 + 200,
2016-12-13 11:43:37.181773 -0500 + [],
2016-12-13 11:43:37.181773 -0500 + {
2016-12-13 11:43:37.181773 -0500 + Message => 'Peer 1001-thirdlane not found.',
2016-12-13 11:43:37.181773 -0500 + ActionID => '134',
2016-12-13 11:43:37.181773 -0500 + GOOD => 0,
2016-12-13 11:43:37.181773 -0500 + COMPLETED => 1,
2016-12-13 11:43:37.181773 -0500 + Response => 'Error'
2016-12-13 11:43:37.181773 -0500 + }
2016-12-13 11:43:37.181773 -0500 + ]

matthewmalk248
matthewmalk248's picture
Joined: 2015/08/09
Points: 20

UPDATE: I was able to resolve the Connection error by manually starting the Prosody service, it seems it's not starting when the server boots up

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

I would like to thank everyone for the feedback!

We are doing our best to test what we can before every release - but some problems only get discovered "in the wild" :).

Here are 2 more issues we found so far:

1) Communications Manager has a bug in checking tenant level limits for Connect enabled extensions and refuses to create user extension even when the limit has not been reached. Workaround - do not specify this limit for the new tenants and remove it from all tenants where it was specified

2) Specifying "Change on First Login" for user extensions (in Password Options tab on Tenant screen) results in users not being able to login into legacy User Portal or Thirdlane Connect. Please do not use this option until we find the solution

.

.

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

trinicom
trinicom's picture
Joined: 2008/12/11
Points: 0

the new version 8 looks awesome thanks again Alex and your team.

Found a bug in version 8 and 7.5 that when you make an IAX trunk, third lane is only writing part of the registration info to iax.conf.
the work around is you can manually add the 2nd part and it works, if you make changes in MTE it does not update the settings in iax,conf however it does not over write the manually settings that you put in.

basically
it writes this
register => testtrunk:password@myserver.com ; testtrunk

but does not write this part (you have to manually add it to iax,conf)

[mytesttrunk]
qualify=1000
nat=no
secret=password
host=myserver.com
username=testtrunk
context=from-outside
type=friend
disallow=all
allow=ulaw
allow=alaw

hope this gets addressed in a later update, we like our iax trunks.

Keith

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

I posted this in General Questions - reposting here.

Configuration is stored in the database - i believe it is only the registration that ends up in the file. For SIP we actually allow using the file based configuration as an option, perhaps we can do the same for IAX in the future.

Keith, were you able to make it work without modifying the files?

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

Dougster
Dougster's picture
Joined: 2017/02/15
Points: 10

Is there any plan for an IOS version of the Connect app. Can find some posting about beta testing a while ago. Android is great, but there are a lot of users out there with iphones.

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

Beta testing was probably about our Mobile Dialer, which is available in beta but is not in Apple Store. As far as the Thirdlane Connect for iPhone - while I don't have the exact date it will be our focus after the new release for all the other platforms next week.

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

Topic locked