• We do not provide troubleshooting help for unsupported phones. Please try with a supported phone.
  • V20 Update 10 Alpha Learn more

3cx SBC and Gigaset N510 Dect Phones

Status
Not open for further replies.

Hoygen83

Bronze Partner
Advanced Certified
Joined
Apr 3, 2020
Messages
26
Reaction score
4
Hello,
in a remote location we have a Gigaset N510 station, and in the same location we have an SBC 3cx connected to our main PBX in the cloud.
I was reading here: https://www.3cx.com/sip-phones/gigaset-n510/ and here https://www.3cx.com/sip-phones/manually-provision-gigaset-n510/
I quote:
"Known Limitations
Note that these phones can not be used from a remote location or in combination with a 3CX in the cloud.
  • No STUN Support
  • No SBC Support
  • No Full CTI Support (Make Call Only)
  • No Company Phonebook
  • No LCD Language Provisioning
  • No Distinctive Ringing for external, queues or ivrs
  • No 3CX Firmware Management
  • No Admin Password Provisioning
  • No support for Paging Groups (incl. Multicast)
  • Extension’s surname must be set and must only contain letters without special characters
  • No Parking Orbit Support"
So, knowing the ip of the SBC, there is no manual way I could configure the dect to work with the SBC?
 
Right now I had a working environment performing those steps, just for the time needed to order and install compatible dect phones:
I made an extension only for the single handheld.
I configured N501 following this steps https://www.3cx.com/sip-phones/manually-provision-gigaset-n510/
I specified as disabled the option in the extension " Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked) "
Now the phones are somehow working (but I would like that theyr traffic is encapsulated in the tunnel between 3cx and sbc).
 
This is a non-supported/non-tested setup so first I personally can't recommend it as it make your customers unhappy when it doesn't work, or even worse, when it is unreliable.

The general logic is that in the Registrar field, you put the 3CX FQDN, and in the Outbound Proxy field you put the SBC IP Address.
Again though, I must recommend against it.
 
Now the phones are somehow working (but I would like that theyr traffic is encapsulated in the tunnel between 3cx and sbc).
If they are registered using the SBC, and not directly to the 3CX Server, then yes, they would be using the tunnel like any other device, at that location.
 
If this is a phone that you plan on keeping long-term, then consider replacing it with a fully featured, fully supported DECT Phone otherwise you may get complaints of incorrect operation or may need to troubleshoot it more often that it's worth.

Check out the DECT section here, we recently added support for Yealink W90 which supports multiple stations too:
https://www.3cx.com/sip-phones/
 
  • Like
Reactions: Hoygen83
Thank you very much for the tip!
If that dect is compatible with sbc I will suggest it for sure.
 
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK