SIP and the Internet
Generic SIP port LQ
- Port 5060 (UDP or TCP) for SIP
Port 5061 (TCP) for TLS communications –if using secure SIP: LQ does not support Secure SIP and therefore does not use port 5061.- Port 4000-32767 (UDP) (send & receive) for RTP/RTCP communications (2 ports per call)
LQ 4.0 will only use ports 4000 - 4015 locally but will still be able to connect to any other RTP/RTCP ports.
Secure SIP and TCP is not supported in LQ 4.0
Network Address Translation (NAT) and Firewall
NAT and many firewalls “hide” private networks behind a public IP address. This normally means that SIP calls can be initiated from a private network to the Internet but not the other way around. Also, firewalls commonly deny access to port numbers associated with Voice Over IP (VoIP) applications.
This aspect of SIP can be handled by technologies designed to traverse firewalls such as STUN, TURN and ICE. Some VoIP service providers use proprietary server side solutions that do not require STUN/TURN/ICE servers.
Using SIP with LQ
When using SIP with LQ Series units, you need an IP - Private Branch Exchange (IP - PBX) to act as a SIP server. This PBX can be a physical unit, or you can use a cloud-based IP-PBX service.
Note: LQ SIP does not currently work with STUN/TURN/ICE.
More information on firewall/NAT:https://www.ingate.com/files/Solving_Firewall-NAT_Traversal.pdf
CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT
This solution was provided by Clear-Com via a question submitted to us by customers like you. If you wish to share with us a new solution or update an old one, please follow this link..
The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.
We are looking for your help! Please consider sharing your stories, update an old solution or help us with a new one. Follow this link to share!