Configuration Issue with Third-Party SIP for Unifi Talk Phones via SBC 3CX

[VincentM]

Hello everyone,

I’m encountering an issue while trying to configure Unifi Talk phones (UTP-Touch) on a 3CX infrastructure, with a hosted PBX and a local SBC running on a Raspberry Pi 5 (192.168.50.x). The connection between the PBX, the SBC, and the Bouygues Telecom SIP trunk is functioning correctly, but I’m struggling to register the phones through the Unifi Talk interface.

Context​

I’m aware that Unifi Talk phones are not officially supported by 3CX. However, our infrastructure solely relies on Ubiquiti equipment. The Unifi Talk interface offers basic fields for Third-Party SIP configuration, but I’m unsure about the exact variable names expected by 3CX for a generic, unregistered phone via SBC. Ubiquiti provides IPSP templates for other providers, which might give a hint about the required fields.

Available Fields in Unifi Talk:​

• Provider Name
• Destination Countries
• Handle All Outgoing Calls By Default
• Phone Numbers
• IP Address Range
• Add Custom Field

Current Technical Information:​

• Extension Number
• Hostname/Registrar: XXXX.3cx.cloud
• SBC: Raspberry Pi 5 (192.168.50.x)
• Outbound Proxy Port
• Authentication ID
• Password

Possible Field Names We've Considered:​

• username
• realm
• password
• extension
• proxy

Does anyone have more accurate information about which field names are most reliable, or could point us towards a solution? Any help would be greatly appreciated.

I’m looking for a 3CX template to help identify the necessary fields to register these phones and any suggestions to configure this solution optimally. This is a test phase before a broader deployment within our company, and it could also benefit other 3CX users. If this works out, I am willing to write a detailed procedure for the community.

Thank you for your help!
Vincent Moreau

 

[nm2016]

@VincentM Were you ever able to figure this out? I am trying to do the same thing right now and am completely stuck.

 

[VincentM]

@nm2016 hello, no I didn't really make progress on the subject... excest that I understand that the 3CX PBX comes in duplicate with UniFi. You must remove this intermediary and add the SIP trunk directly to UniFi Talk. I'm starting to look at VOIP.MS which are pre-configured in third parties.

 

[nm2016]

@nm2016 hello, no I didn't really make progress on the subject... excest that I understand that the 3CX PBX comes in duplicate with UniFi. You must remove this intermediary and add the SIP trunk directly to UniFi Talk. I'm starting to look at VOIP.MS which are pre-configured in third parties.

That's exactly what I did last night. The only reason I wanted to implement into my 3cx system is because I had my POTS line setup through and ATA FXO adapter. I just bypassed all of that and setup a VOIP.MS acct. You can verify your existing number and have that set as the outbound caller ID. Works perfectly for me.