Cisco to 3CX Migration / Flowroute - AudioCode SBC Queries

[amir_]

1. I'm curious to know if there are other current 3CX clients who migrated from Cisco IPT to 3CX. It takes 12 Cisco VMs to operate our medium sized business. We can do everything we currently are doing PLUS other great features with 3CX in one VM.

2. SBC
We currently have Flowroute SIP trunks terminating against Cisco CUBEs. I'm imagining the following PSTN call flow:
Calling Party >> PSTN >> Flowroute >> Audicode SBC >> 3CX VM >> Called Party

Is there anyone out there using Audiocodes SBCs to terminate Flowroute SIP Trunks

3. Cisco 8811 Phones - I'm curious to know if anyone has integrated these phones into 3CX?

TIA,

Amir

 

[cobaltit]

3CX doesn't support Audiocodes SBCs but if you work with Audiocodes that's all you care about, it doesn't really matter what SIP trunks are passing through it. Or you could just go direct which is supported by 3CX.

If the Cisco 8811 phones have SIP firmware then they can be made to work but there's no template and they won't be supported. Course if you are reducing from 12 VMs to one I imagine there's budget for new phones.

 

[eddv123]

Ive integrated 3CX with Audiocodes before and despite being un-supported by 3CX they do have a template for 3CX-PBX in the Audiocodes Wizard.

Obviously you have to know Audiocodes to make any amendments to this standard/template setup also and if not they do have a rather good set of paid courses if you need: https://www.audiocodes.com/services-support/audiocodes-academy

 

[asafayan]

Ive integrated 3CX with Audiocodes before and despite being un-supported by 3CX they do have a template for 3CX-PBX in the Audiocodes Wizard.

Obviously you have to know Audiocodes to make any amendments to this standard/template setup also and if not they do have a rather good set of paid courses if you need: https://www.audiocodes.com/services-support/audiocodes-academy

Hi,

Coming back to this as more of a design question - do you feel you need to terminate the telephony service provider SIP trunk against an SBC and then onto 3CX or can you simply terminate the TSP SIP trunk directly into 3CX?

 

[cobaltit]

100% of my deployments are SIP trunk directly into 3CX.

 

[eddv123]

Coming back to this as more of a design question - do you feel you need to terminate the telephony service provider SIP trunk against an SBC and then onto 3CX or can you simply terminate the TSP SIP trunk directly into 3CX?

You can do both - its up to you. To stay within the realms of 3CX support you would go directly as @cobaltit has done but the point of an SBC is it offers flexibility and extra functionality normally reserved for service providers) such as codec transcoding, lawful intercept,call quality MOS scoring etc )

What I must stress however is that if setting up anything via a "full" SBC (and I call it this to avoid confusion with 3CX's SBC) you must know that device as they are pretty complex - especially Audiocodes.

Ive attached a similar setup I did for an on-premise SBC with 3CX, but without the phones etc it could work just as well as an SBC in the cloud on a provider platform, I have also done something similar with Telcobridges FREE/PRO SBC also which in my opinion is a much better supported and manageable device: https://docs.telcobridges.com/tbwiki/FreeSBC:3CX

 

[amir_]

You can do both - its up to you. To stay within the realms of 3CX support you would go directly as @cobaltit has done but the point of an SBC is it offers flexibility and extra functionality normally reserved for service providers) such as codec transcoding, lawful intercept,call quality MOS scoring etc )

What I must stress however is that if setting up anything via a "full" SBC (and I call it this to avoid confusion with 3CX's SBC) you must know that device as they are pretty complex - especially Audiocodes.

Ive attached a similar setup I did for an on-premise SBC with 3CX, but without the phones etc it could work just as well as an SBC in the cloud on a provider platform, I have also done something similar with Telcobridges FREE/PRO SBC also which in my opinion is a much better supported and manageable device: https://docs.telcobridges.com/tbwiki/FreeSBC:3CX

Good advice. What I'm trying to reduce is the inherent complexity of our existing Cisco IPT environment - so we will NOT use a standalone SBC.

 

[eddv123]

Despite this last point (and quite sensible if you are unfamiliar) I would start looking and testing/learning about standalone SBC products.