V20: Timeline for Restoration of V18 Features

[zebis]

Hello 3CX Team and happy 2025!!

Now that v18 is EOS, is there an estimated timeline for the restoration of the below v18 features not yet available in V20? Please excuse me if the timeline has already been posted. We have 3rd party systems in place to address all of these so this is not mission critical. The reason I'm asking is the expectation management will help for budgets and planning. Thank you!

V18 Features Not Yet Present in V20:

• Ability to set extension forwarding target as an internal string for forwarding to targets such as conference rooms (<conf>*<room>), shared parking spaces (spx), etc.
• IVR of type DTMF Input
• SIP Trunk: Setting outbound parameters
• SIP Trunk: Setting inbound parameters
• Resource monitors on dashboard to show items such as CPU, memory, and storage status
• Ability to export inbound call flow (even though, in v20, these are now configured at endpoint)
• Ability to import inbound call flow
• Call reporting with at least the features of v18 such as extension range and granular per report scheduling
• Granular user role customization
• Ability to stage updates / upgrades before applying to production environments. V18 supported this nicely with advanced backup capability providing granular control of license and FQDN inclusion. For V18 staging, the backup would be restored to a licensed staging environment to which lab equipment could be registered, etc. This is not yet supported in V20.
• Recording search by time range in addition to date range
• Status on dashboard showing number of up extensions
• Extension export to include SIP credentials
• Bulk-send Welcome / password-reset e-mails.
• Welcome e-mail variable support: Password reset e-mails which, in v20, have replaced Welcome e-mails do not support variables from Welcome e-mails such as %%VMNUMBER%%
• Ability to block tunneled connections, app, and webclient for specified extensions
• Ability to set extension passwords via system owner account
• From phone tab, ability to sort phones by column headings
• Webclient: Ability to receive calls without requiring browser notification permission

 

[Evolute IT]

Lol, much of this is not coming back. Get over it. Others are just UI stuff that are knit picking honestly.

 

[NicholasP_3CX]

Ability to set extension forwarding target as an internal string for forwarding to targets such as conference rooms (<conf>*<room>), shared parking spaces (spx), etc.

You can select a shared parking as a forwarding destination, as well as the conference server, but not a conference "room"

IVR of type DTMF Input

A script is available to do this in the PBX Integrations "store"



Its very simple to define the destinations.

• SIP Trunk: Setting outbound parameters
• SIP Trunk: Setting inbound parameters

This is available in the templates. You can define your settings in the template and import your provider template.

Resource monitors on dashboard to show items such as CPU, memory, and storage status

No.

• Ability to export inbound call flow (even though, in v20, these are now configured at endpoint)

Go to Reports > Inbound Rules > export CSV

• Ability to import inbound call flow

Update 5

• Call reporting with at least the features of v18 such as extension range and granular per report scheduling

Almost there: https://www.3cx.com/blog/releases/improved-reporting/

• Granular user role customization

Ability to stage updates / upgrades before applying to production environments. V18 supported this nicely with advanced backup capability providing granular control of license and FQDN inclusion. For V18 staging, the backup would be restored to a licensed staging environment to which lab equipment could be registered, etc. This is not yet supported in V20.

This caused other issues with the provisioning folder being replicated between different PBXs.

• Recording search by time range in addition to date range

We now send the recording information to your CRM so you can get alot of data from there as well.

• Status on dashboard showing number of up extensions

I can see a use for this if IP Phones which are constantly registered are in use. However, with web clients and mobile apps you might have certain devices which are unregistered without a need for it to be reported.

• Extension export to include SIP credentials

Not really necessary for phones to be provisioned. Once you import the user with the phone details (MAC and template) this will send an RPS request upon import of the user. Reset the phone and it will pick up its provisioning information. What youre requesting is ony useful for manually configured phones. Which you would get the information from the PBX to register the phone anyway.

• Bulk-send Welcome / password-reset e-mails.

Also, you do not need to intervene to reset a password for the users. They can just request the email themselves by clicking on Forgot password and entering their email.

Welcome e-mail variable support: Password reset e-mails which, in v20, have replaced Welcome e-mails do not support variables from Welcome e-mails such as %%VMNUMBER%%

• Ability to block tunneled connections, app, and webclient for specified extensions

I will give you this one.

• Ability to set extension passwords via system owner account

Experience has shown that admins are the main culprit for putting weak passwords and compromising the security mechanisms of 3CX. This is why we cant have nice things in this world. Blame your peers for this one, not us.

• From phone tab, ability to sort phones by column headings

I will give you this arguement as well.

• Webclient: Ability to receive calls without requiring browser notification permission

This is due to the way the web client receives the calls now, via push notifications and permission is required in order to activate the extension on the web client.

 

[Alphabetic]

This the 1st stick beating of 2025?

 

[zebis]

Hello NicholasP,

Thank you so much for taking the time for the detailed and timely reply; this is extremely helpful and much appreciated!

Have a great day and happy 2025!!

 

[zebis]

Hello again NicholasP,

All of the points you outlined manage our expectations well and I have a question regarding your reply of the Welcome E-mail / password reset e-mail item. Your screen shot shows the Welcome e-mail template, however, I was under the impression the only way to send a Welcome e-mail was by enabling automatic sending triggered by extension creation. Is there a way to manually send a Welcome e-mail or, for V20, is the only extension e-mail that can be manually sent the password reset e-mail? If the password reset e-mail is the only extension e-mail that can be sent manually, are there plans to support Welcome e-mail variables in the Password reset e-mail template?

Thank you!

 

[mastermindjf]

Hi.
What about give a user access to report and recording without access the users configurations?
Any solution?

 

[NicholasP_3CX]

Hello again NicholasP,

All of the points you outlined manage our expectations well and I have a question regarding your reply of the Welcome E-mail / password reset e-mail item. Your screen shot shows the Welcome e-mail template, however, I was under the impression the only way to send a Welcome e-mail was by enabling automatic sending triggered by extension creation. Is there a way to manually send a Welcome e-mail or, for V20, is the only extension e-mail that can be manually sent the password reset e-mail? If the password reset e-mail is the only extension e-mail that can be sent manually, are there plans to support Welcome e-mail variables in the Password reset e-mail template?

Thank you!

Resetting a user will resend the welcome email to them.

 

[zebis]

Hello NicholasP,

Thank you for the info and clarification. Just to make sure I'm on the right page, am I correct in understanding, in V20, Welcome E-mails can only be sent in combination with credential resets?

Nicholas, I appreciate your time on these replies. Even though I wish some of the answers were different, you've been helpful to explain which V18 features are not planned for restoration in V20, timelines for those that are being restored, and protocols for features that have already been restored but are accessed differently than v18.

Thank you for your time and detailed replies.