Use 3CX alongside hosted PBX? (Auto-provisioning 3CX box, *not* phones via Cloud? )

[MolarBear]

Hi,

Recently downloaded 3CX and installed it onto a Raspberry Pi. Seems to to work great (with my phones attached but no SIP trunk added yet). We currently have a 'cloud' PBX (KCOM in Hull,UK which is based on BT VOIP) which we have a Yealink W52P connected to it and several handsets. On the Yealink base station page it shows the SIP log in details (server, proxy, username etc) to the hosted PBX. I asked KCOM to give me the password so I can just drop these into the 3CX SIP trunk page, however the technicians at KCOM tell me that cloud PBX system they are providing is not a 'sip trunk' and I cannot just copy the details (despite the phone having all the prefilled in sip trunk account details). I'm not sure if they know what they're on about? The company do provide a SIP trunk service but they claim that is completely separate. Would I be correct in thinking that the hosted PBX solution uses a SIP trunk to carry the VOIP data even though it's not called a SIP trunk per se?

They were unable to reset the password for the SIP trunk (it was only this piece of information I was missing), they advised me that the Yealink phones autoprovisioned via their hosted PBX and indeed even when I changed the password in the base station log in screen (and subsequently the phone was unable to register) they deleted it from their end and reprovisioned it without providing any passwords, they didn't even have the facility to view the device password.

My question is, is there a way for 3CX to acquire/auto-provision the password set by a hosted PBX? So the setup would be 2 'cloud pbx' licenses/sip trunks to be connected to the 3CX then I connect my phones to the 3CX box? I hope this makes sense!

Thanks!

 

[AWS2P]

few things are sure ,
SIP phones are usable on SIP systems so Yealink W52P is normally able to be provisionned by 3CX,you just need to factory reset phone , push the latest firmware supported by 3cx, then phones can be provisioned and used by 3CX.
https://www.3cx.com/sip-phones/yealink-dect-w52p/

SIP trunks need to be set on 3CX side and supported one providers, so if for now your solution is working with something using VOIP but not as a trunk, you need to purchase one trunk to a supported provider.

 

[leejor]

The people you've dealt with may genuinely not know what is going on, or they may simply towing the company line and not allowing you to register "just any device". In theory, you should be able to register a trunk on 3CX as an extension on their service. It may only handle one call, rather than many. However, many providers not only frown on this, they will discourage or forbid it, which may be the case here. During the initial registration, the device type is sent, which can be blocked, if it isn't a device they approve of. This may not be easily changed by the people you've been dealing with so it's easier to just say no.

Did they supply the phones you use? If they did, then they may insist on auto provisioning to keep trouble tickets to a minimum.

 

[JohnS_3CX]

Hi @MolarBear

The short answer is no, 3CX cannot auto-provision trunks this way. What your provider said makes sense. They run their own cloud PBX, and your phones register under it as extensions (under a private group of course that belongs to your account).

Your request is the equivalent of taking the details of a 3CX extension, and plugging them into a different PBX altogether and hoping that this 3rd party PBX will auto-provision just like a phone. But that is not the intended use around which this was built for, and they probably reject any unknown device using the credentials (based on MAC address I would expect).

They were correct to point out that a SIP Trunk is a completely separate service VS their existing hosted solution. If you wish to use 3CX as your PBX, you need to purchase a trunk from them, or better yet from one of our supported UK providers for best compatibility. https://www.3cx.com/partners/sip-trunks/uk/