Bug V20, Edit Trunk

[rdsmvp]

I think I found a bug. When logged in to the webclient, I click on the Admin gear icon. Then I click on ´Voice & Chat' and there I can see the 'WebMeeting bridge' and my trunk (Nexmo). Clicking on the three dots on the right and selecting 'Edit Trunk', sends me back to the 'Team' screen, showing my name/extension. So I cannot edit the trunk info at all. The user in question (my account) is a system owner and was actually the account I logged in to perform the upgrade to V20 (that was successful). Any ideas? I am on the latest V20 available as of today. Used Edge and Firefox (on Linux), same exact results.

 

[Charles_3CX]

Hi, When using an unsupported trunk that does not have a template, this issue will occur, and you will need to delete the trunk and recreate it using a generic template to rectify this.

 

[rdsmvp]

Understood. THanks!

 

[SWE-phones]

@Charles_3CX Will deleting the trunk not have serious downstream effects?

I just upgraded from v18 to v20 and I'm seeing the same "goes to the Team screen" behavior. Our system has 1 trunk defined and it's set as Route 0/1 on a BUNCH (hundreds) of outbound rules. If I delete the trunk, will those rules get bricked until I can edit each one and put the new trunk in?

Also, if I have to recreate the trunk from scratch (or a template), it sure would be nice to be able to look at the old one to get all the settings. I can look at the XML to retrieve the settings from the "unsupported" but otherwise functional trunk but it'd also be super cool if the software could just display the "unsupported" trunk, perhaps with a warning that tells us how to fix it. I mean, I'm making and receiving calls on it, so it's not so unsupported that it's unusable, so why can't its configuration be viewed even in a read-only capacity?



Noticed as I type this - on the outbound rules list page - https://{our instance}.3cx.us/#/office/outbound-rules - the trunk shows up in the column "Route 1" (of 1-5) but when you pick a rule and edit it - https://{our instance}/#/office/outbound-rules/edit/7 -, it shows up as Route 0 (of 0-4) - you've got a "where do we start counting" display bug.