11 posts / 0 new
Last post
CarstenR
CarstenR's picture
Joined: 2008/06/05
Points: 20

Hello,

We upgraded to the newest 10.1.1 version yesterday and noticed quite a few changes. I have some questions/issues, hopefully we can try to work through them.

Connect worked before the upgrade and now it is no longer able to register to the PBX. On Windows 10, it is connecting to the messaging server, but is saying "no connection with telephony server. Calls via PBX are disabled.

The updated android app gives me a sign in error: Critical error occurred, error code 23 now. This was working before the upgrade as well.

Using the launcher via the configuration manager gives me the following error: An error occurred during signing in. The error code: USER_DATA_LOADING_FAILED.

I've verified the Network Topology and am able to register a SIP phone via UDP, but not TCP. All options are set in Network Topology, TCP, UDP, TLS.

With the SIP phone, when I make an outbound call it connects, but then drop about 8-10 seconds after the call is established. Also was not happening before the upgrade. Only have tested outbound at this time for this.

It appears there is now a proxy involved in the middle, so I am no longer seeing any registration attempts to asterisk, so troubleshooting any sort of connection issues is going to be problematic. With the addition of this, what tools do you have in place, or suggest to assist in troubleshooting these things that we used to be able to from the asterisk CLI?

Thanks in advance.

volodya
volodya's picture
Joined: 2017/01/05
Points: 260

Hello Carsten,

If possible I would like to check your system. Please send credentials to support@thirdlane.com.

volodya
volodya's picture
Joined: 2017/01/05
Points: 260

If anyone will be getting errors "23" or "USER_DATA_LOADING_FAILED" please make sure that you are running the latest version of the platform.

chrisc@accentse...
chrisc@accentservices.com's picture
Joined: 2018/05/07
Points: 10

The outbound call dropping has affected us as well on a lab system we have to test the new build. We will not be upgrading our production systems until this is resolved. Good luck, so far it's been a challenge for us.

Chris Cameron

CarstenR
CarstenR's picture
Joined: 2008/06/05
Points: 20

I've been working with support on it and I think I may have found the issue. Waiting for response as they verify.

chrisc@accentse...
chrisc@accentservices.com's picture
Joined: 2018/05/07
Points: 10

We've been told the same thing this morning.

Chris Cameron

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

Did you get it resolved? If so was it specific to your install?

CarstenR
CarstenR's picture
Joined: 2008/06/05
Points: 20

It looks like I found the issue and they are working on the fix. Until that's been addressed, I can't test any further. I don't think it's specific to my install. There have been some significant changes to the back end.

I wouldn't suggest updating if you are using any sort of SIP trunks that change the host via the contact URI until this is resolved. I will update once everything has been patched and tested.

katie
katie's picture
Joined: 2019/02/15
Points: 0

We noticed there are updates in the repository. Does this correct the outbound call issue?

CarstenR
CarstenR's picture
Joined: 2008/06/05
Points: 20

Katie,

Support made updates to the Kamailio configuration and we are now able to successfully make outbound calls.

volodya
volodya's picture
Joined: 2017/01/05
Points: 260

We adjusted configuration to provide interoperability with the carriers that Carsten and some other customers encountered. We will be rolling out the an update with this and few other changes shortly. Please wait for the annoncement that will be posted on the forum here: https://www.thirdlane.com/forum/news-and-announcements