Skip to main content

Web UI not reading certain values?

Posted by devand_cloud on Mon, 12/30/2013

Hey guys,

We run a Thirdlane MTE PBX on Asterisk 1.8.23.1 with PBX Manager 6.1.1.12

We have noticed that the web UI is not displaying certain values (ie. Outbound Caller ID, Call Forwarding, essentially anything that asterisk would need to dip into the mysql database for). You can save them, and the changes stick, but the fields just show up blank.

Any idea why this might be happening?

Thanks!


Submitted by eeman on Wed, 01/01/2014 Permalink

thirdlane 6.1.1.12 did not store data in a MySQL database. It stored those particular settings into the ASTDB. you need to make sure thirdlane has a connection to your AMI and its able to execute a database show command.

Submitted by devand_cloud on Thu, 01/02/2014 Permalink

Okay, so I'm a little unsure how to do that. I may be way off in left field here, but I've gone into the CLI and invoked 'manager show connected', which says there are 0 users connected. I'm guessing this _may_ be because the system is not making any changes when I'm polling the user list?

That said, I have double-checked that the password in (System Settings >> General Settings) matches the secret value under the 'manager' context within manager.conf

Any advice on how to proceed?

Submitted by devand_cloud on Wed, 01/08/2014 Permalink

Just wondering if anyone might happen to have some insight on this one. Being that the holiday season has now come to a close and people are starting to utilize their phones / web portals again, I would really (really) like to have this sorted out asap. And I'm kind of sitting dead in the water at the moment, unsure how would be best to proceed.

Any advice on this would be greatly appreciated.

Thanks!

Submitted by devand_cloud on Fri, 01/10/2014 Permalink

Is there anyone out there at all that could help shed some light on this matter?

According to Erik's comment, all I really need to know at this point is how to get into the AMI and verify that thirdlane is able to execute a few commands.

Getting pretty desperate for some help here. Anyone?

Submitted by thirdlane on Sat, 01/18/2014 Permalink

Was this system updated from Asterisk 1.6 (or early version of 1.8) to 1.8.23? If so, there may be some incompatibility issues that were introduced by Asterisk. Are you running the latest version of Thirdlane 6.X?

You should consider migrating to Thirdlane Communications Manager 7.1 and definitely use it for any new installations.

Submitted by rfrantik on Tue, 01/21/2014 Permalink

devand:

question: Is the system working properly? You mention that the values seem to "stick" even though you can't see them. I'm just wondering why you would jump to the conclusion that this is a database problem when things are working?

We've been seeing some odd things with the 6.1.1.12 interface since a recent Google Chrome update (Version 32.0.1700.76 m) seems to be causing the issue. We are specifically having trouble with long drop down list and it doesn't let you scroll down. We are working around the issue with Firefox.

So I'm wondering what operating system you are using on your desktop? What browser (w/version number) you are using to access 6.1.1.12? On which specific screens are you having trouble seeing data? I think there are a couple of place for outbound caller ID and CFWD, mine all seem to work OK.

Thanks

Submitted by devand_cloud on Wed, 01/22/2014 Permalink

==// @rfrantik:

I have tried using Chrome ver. 32.0.1700.77 on OS X, Safari ver. 7.0.1 (9537.73.11), also on OS X, Chrome ver. 32.0.1700.76 m on Windows 8 and Firefox ver. 26.0 also on Windows 8.

I had already tried using Safari on OS X when I initially discovered the issue, but just tested the other 2 to be sure.

I had doubts that it would be initially, as we had reports from end-users.

Do you know how I might go about verifying that the PBX manager is able to execute the 'database show' command in the AMI as per eeman's suggestion above?

==// @thirdlane / Alex:

The system was initially installed with Asterisk 1.8.20.1, and then updated to 1.8.23.1, but that happened back on October 11 and 12, 2013. Everything had been working fine for months up until recently.

Unfortunately, although upgrading our system to 7.1 may in fact resolve this issue, we are not in a position to do so quite at this point.

Any other ideas?

Submitted by thirdlane on Fri, 01/24/2014 Permalink

It is very likely that the problem is with astdb. What is wrong specifically is hard to tell without more information, but i've seen astdb getting corrupted before. Can you do "database show ..." to see if the values are there? What confuses me is that you said that it was working and then stopped as i dont remember recent changes in Asterisk that would break astdb access ( there were quite a few but in earlier versions)

if you give me easy access to the box :) i would look at this