New system, v18 vs v20

[VincentDalvani]

I need a PBX in the Atlanta office for 5 staff members one sip trunk provides them with 11 local numbers.

I need a PBX in the London office for 41 staff members two sip trunks provide them with 49 local numbers and 12 numbers across Europe.

I need to bridge these two PBX's so both offices can call the other office via extension.

Both offices will have an IVR with sales accounts shipping and support options.

The IVR will feed into a ring all call queue, it will send all staff a voicemail as an attachment if nobody answers.

The system is fairly basic.

The question is as this will be a new implementation is v18 or v20 better to start with, and why.

What features would I gain from v20?

What would I loose from not choosing v18?

When will v18 be end of life?

 

[SweetAction]

The question is as this will be a new implementation is v18 or v20 better to start with, and why.

I think you could do v20 without issue here. You indicate you need IVR and Voicemail, as well as Bridges and SIP trunks. All that is in v20.

What features would I gain from v20?

Not having to upgrade later

What would I loose from not choosing v18?

Possibly some feature that isn't in v20 yet, like scheduled reports. But you didn't indicate a need for any of that.

 

[TheodorosG_3CX]

Adding to the response from @SweetAction at some point V18 will not be supported and currently V20 has the features you request. More features are going to be added though in next updates, so the best option is to start with V20 and always be up to date.

 

[Alphabetic]

You could use one PBX with an SBC at the other site and utilise departments for office hours.

 

[AWS2P]

V20 presence for bridges is not ready at this point but bridges are working