V20 Update 10 Alpha: MCP, AI Server & More Admin Control

[telcocentricu1]

I have a question about the feature: "Users with multiple assigned DIDs can now choose which number to use when placing an outbound call from supported 3CX Apps". Users usually need to make outbound calls on behalf of queue assigned numbers (like the helpdesk number or similar), not the ones that are assigned to the user. Was this also considered?

Agreed 100%, we have had this feature requested for years and it is so close to show time. Just needs an outbound DID list rather than solely inbound. Most people are queue based like Centrovis mentioned.

 

[KyriacosS_3CX]

but it says the IP is already in the blacklist

It is possible that the specific IP was already received via the global blacklist, and so not visible for direct manipulation.

 

[businesstechconsultants]

It is possible that the specific IP was already received via the global blacklist, and so not visible for direct manipulation.

I did forget about 3cx having the global blacklist and yes this is turned on. That would be the explanation for the blacklist item.

 

[pcwizarduk]

Has anyone noticed in the alpha self hosted multi company the legacy sip truck providers have been removed

 

[Guillaume Bourgeois]

Hi !

I noticed a change that caught my attention. I’m seeing an object named 'ENLRange' with the properties 'From' and 'To' , in the payloads.

I don’t want to start any rumors, but does this mean 3CX is considering allowing extension numbers of different lengths within the same phone system?

Because if that’s the case, I have to admit I’d be impressed. For as long as I’ve worked with 3CX systems, extension numbers have always used a single fixed length. It’s been that way for so long that having to choose one extension length during installation isn’t really perceived as a limitation. It’s always seemed more like a deliberate engineering choice to keep the Dial Plan as reliable as possible.

So, am I reading too much into this ? Does ENLRange suggest that other changes or new capabilities are being considered?

Has anyone heard anything about this, or is anyone in the know? I’ll admit, it’s mostly just curiosity !

That being said, congratulations on the Alpha v10 update. All these improvements will make life much easier for phone system administrators by addressing many of the day-to-day challenges we deal with.

Hats off to the team.
You’re clearly the best at what you do.

 

[N_G]

@Guillaume Bourgeois - You are like the VoIP Mossad I am gonna have to say "No comment"

 

[Guillaume Bourgeois]

@Guillaume Bourgeois - You are like the VoIP Mossad I am gonna have to say "No comment"

Fair enough. I suddenly haven’t seen anything, heard anything, and definitely don’t know anything.
The “VoIP Mossad” seems to have suddenly « lost » all interest in this investigation. Move along, nothing to see here. hahaha !

​

 

[N_G]

@Guillaume Bourgeois We will try to hide stuff better next time

 

[Guillaume Bourgeois]

@Guillaume Bourgeois We will try to hide stuff better next time

Ohhh no !! lol !!!!
No, no, there’s no need. I’ve already fixed the problem. I added a reminder for myself on the board behind me. See for yourself, LOL!

 

[Charli]

Will the Upgrade to Debian 13 soon be released? Debian 12 is EOL since July. Or is 3CX using Debian LTS?

 

[Guillaume Bourgeois]

Will the Upgrade to Debian 13 soon be released? Debian 12 is EOL since July. Or is 3CX using Debian LTS?

Debian 12 hasn’t reached its end of life (EOL) yet.
It’s important not to confuse EOL with the end of regular support.



Debian 12’s lifecycle is divided into two main support phases:

Standard support: Debian 12 “Bookworm” was released on June 10, 2023 and received regular support from Debian’s Security and Release teams until July 11, 2026.

Long-Term Support (LTS): On July 12, 2026, security maintenance was handed over to the Debian LTS team. This transition is part of Debian’s normal lifecycle. There’s no separate “Debian 12 LTS” release and no operating system upgrade is required. Bookworm will continue receiving LTS security updates until June 30, 2028.

3CX uses the amd64 architecture, which is covered during the Debian 12 LTS phase.
The LTS phase has a more limited scope than standard support in terms of supported architectures and packages.

It’s also worth pointing out that 3CX uses its own repositories rather than Debian’s repositories directly.

So there’s no reason to consider Debian 12 unsupported from a security perspective at this point.
Upgrading to Debian 13 isn’t urgent at all.

Personally, I don’t see much benefit in moving to Debian 13 at this point. If you follow 3CX’s requirements, nothing other than the 3CX PBX should be installed on the same server anyway. So whether 3CX chooses to remain on Debian 12 or, hypothetically, decides one day to move to a closed, custom Linux image designed specifically for this purpose doesn’t really matter to me. (Just to be clear, I’m only using this as a hypothetical comparison. It’s not a claim, and it’s not based on any rumor)

As long as the underlying operating system remains secure, stable, and free of issues that could affect the PBX, I don’t see what practical difference it makes.


3CX will move to Debian 13 when there’s genuinely more to gain from upgrading than from staying on Debian 12.

 

[Charli]

@Guillaume Bourgeois Thank you for clearing up my confusion! I wasn't aware how the Debian lifecycle works, sorry ^^'

 

[N_G]

@Guillaume Bourgeois Great explanation Guillaume thank you for jumping in. Welcome back, good to have you back onboard