This post is at: ForumFeatures Wanted
8 posts / 0 new
Last post
netriplex
netriplex's picture
Joined: 2012/01/24
Points: 70

There are some things about the UI that could be improved that would help manageability on deployments with large numbers of extensions (in a single tenant).

1. Allow selectable page sizes. I am unsure where the 35 number came from but it would be better for this page size to be selectable. When trying to look through 3000 extensions, 35 is too small per page. It is also too small as the export extension option only exports the 35 exits displayed.
2. Allow extensions to be sorted based on the column headers. Again in large deployments, this helps make some things easier to find. Filters are helpful but sometimes do not capture the info you are after while a change in the sort would help much more.
3. Allow filtering by tags. Tags are nice to be able to set, except unless I go to the database and query manually, there is not much that I can do with them.
4. Expand what can be updated via mass update. After I import 100+ new extensions into TL for a new branch of a large company being added to the PBX, it would be nice to be able to be able to update the caller id fields (reg and emergency) on all of the extensions at once along with updating all of the tags associated with these extensions. Presently, I do this directly via MySQL as it is too tedious via the TL UI.

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

My comments below:

1. Allow selectable page sizes. I am unsure where the 35 number came from but it would be better for this page size to be selectable. When trying to look through 3000 extensions, 35 is too small per page. It is also too small as the export extension option only exports the 35 exits displayed.

--- You can set number of rows per page on Personal Preferences page. I will actually set the default to a higher number - would 100 be reasonable?

2. Allow extensions to be sorted based on the column headers. Again in large deployments, this helps make some things easier to find. Filters are helpful but sometimes do not capture the info you are after while a change in the sort would help much more.

--- I have no idea why and how we lost this functionality. It will be reenabled in the next release - for columns where it makes sense.

3. Allow filtering by tags. Tags are nice to be able to set, except unless I go to the database and query manually, there is not much that I can do with them.

--- Good idea, wait for the next release. Actually, our original intent was to use tags mostly for telephony (they are available in the dialplan), and not really for UI or general tagging. It is a general purpose feature, it can certainly be whatever you want it to be.

4. Expand what can be updated via mass update. After I import 100+ new extensions into TL for a new branch of a large company being added to the PBX, it would be nice to be able to be able to update the caller id fields (reg and emergency) on all of the extensions at once along with updating all of the tags associated with these extensions. Presently, I do this directly via MySQL as it is too tedious via the TL UI.

--- I agree, and I think it would actually not hurt to add similar mechanism for tenants and possibly other objects. That said - I will be waiting for a list of items based on real life use cases to appear here :)

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

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

RE: 4. One option I *really* need is the ability to mass change the web password for an user extension back to the default. Changing this extension by extension is very cumbersome given that we a significant number of room (read: extension) changes each summer. In some cases, it may be as many as 75% or 80% of the extensions in a single building. With the new features that are coming, I am sure that we will be expanding the use of the web interface. As it stands, we have held that feature back just because of the administrative headache of reseting web passwords in the upcoming year.

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

what do you mean by default? we could add an option to "regenerate" web passwords to make them random - and then you could send users a "welcome" email with all the info including web passwords.

would that work for your case?

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

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

Yes, the regenerate command would be exactly what we need if able to be run from the "Update Selected" menu!

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

will be available in the next release

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX

summitgroup
summitgroup's picture
Joined: 2013/10/24
Points: 0

Mass re-provision phones of type "x" would be great. If you make a template change, going to each Tenant to re-provision each phone to update the config file it downloads is a pain in the butt!

The other thing we get requests for is for Ring Groups, Queues and IVR's to be able to have "Virtual" extensions like in FreePBX so that you can transfer back to a Ring Group (ie. Department") to a Queue or to transfer someone back to the IVR Menu. (ie. Someone calls in, they land in the wrong area, you transfer back to the IVR).

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

1) In Phones Provisioning you can filter the list of phones, select and do "provision selected"
2) It is possible to use simple "go to" scripts (like tl-menu, tl-queue) for Hunt Lists, Queues, IVRs or any other objects that need addressing and create feature codes as virtual extensions. Would this help your use case?

Alex Epshteyn
Third Lane Technologies
Multi Tenant Asterisk PBX