whatportis.com
suggest an edit →

Port 1167Conference Call Signaling

UDP port 1167 is commonly associated with signaling traffic for telephony and conference calling solutions, particularly legacy or specialized systems. It enables the setup, management, and teardown of audio conference sessions across IP networks. The use of UDP facilitates low-latency communication ideal for real-time voice traffic, though it can introduce challenges related to reliability and security. This port is often utilized in enterprise conferencing setups or hardware appliances supporting VoIP-based conference call features..

inNetwork ServicesVoice and Chat
transport
udp

single transport

in transit
cleartext

payload readable on path

assignment
unofficial

used by convention

risk
4/10

caution

lookups
9,135

rank 533 of 993 · top 54%

Technical Details

what runs on :1167

Port 1167 over UDP is typically leveraged by conferencing systems for signaling and control message exchange during multi-party voice calls. These communications often manage session initiation, participant management, media negotiation, and termination. Because it relies on UDP, communication benefits from minimal overhead and reduced latency, making it suitable for real-time scenarios like voice communications.

While this is not an IANA officially assigned port, some proprietary or legacy telephony solutions have standardized on UDP 1167 for internal operations or within enterprise networks. Usage may vary across different vendors, but generally encompasses signaling traffic — this does not usually carry the voice payload itself, which tends to use dynamically negotiated RTP streams.

Integration with larger VoIP environments can see this port facilitated by PBX systems, conference bridges, or dedicated hardware appliances. The reliance on UDP requires additional mechanisms such as sequence numbering and retries in higher-layer protocols to compensate for potential packet loss or disordering.

Security Information

exposure of :1167

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

network services averages 3.9 across 604 ports — this one sits 0.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

unofficial

used by convention, not registered — what answers here varies by deployment

reachable over

udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

Common Vulnerabilities:

  • Exposed UDP 1167 can be targeted by attackers to enumerate conferencing systems or attempt unauthorized call participation.
  • Protocol weaknesses may expose identifying details or session parameters subject to interception or tampering.
  • Because UDP is connectionless, it is more easily exploited via spoofing, reflection, or amplification attacks.
  • Lack of encryption can enable eavesdropping or man-in-the-middle attacks on control messages.

Common Mitigations:

  • Restrict inbound and outbound traffic on port 1167 using firewall rules to trusted hosts/networks.
  • Deploy access control lists (ACLs) on network equipment to prevent unauthorized signaling communication.
  • Enforce strong authentication and authorization mechanisms within conferencing services.
  • Consider utilizing VPNs or encrypted signaling mechanisms (such as TLS) to protect control plane messages.
  • Monitor and log port activity for unusual patterns that might indicate scanning, abuse, or attack attempts.

Related Ports

all 604 in network services →

the 8 most looked-up other ports in network services — 604 ports carry that label.

portservicerisk
:9080Groove RPCcaution
:6543Jetnetcaution
:5938TeamViewercaution
:8291Winbox MikroTik Admincaution
:3233WhiskerControl Protocolcaution
:3268Microsoft Global Catalog (GC)caution
:135Microsoft EPMAPcaution
:3128Tatsoft Default HTTP Proxycaution

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted