Cisco Cisco Meeting Server 2000

Note: SIP endpoints or Lync clients external to the network may still need a third party device to
route SIP signaling across their firewall.

Table 4 below lists the ports required to be open for SIP/Lync call traversal.

Table 4: Ports to open for SIP/Lync call traversal

Link

Component

Connecting
to

Destination
port to
open port

Traffic
type

Traffic direction
with respect to
component

Configurable

1

Edge server
(private
interface)

Call Bridge

Any
unused
port, e.g.
3061

SIP,
TLS

Incoming from Call
Bridge

Yes

2

Edge server
(public
interface)

Remote SIP
devices

5061 (Note
1)

SIP 
TLS
(Note
2)

Incoming/Outgoing

Yes

3

Call Bridge

TURN
server

32768-
65535

Media
UDP

(STUN,
RTP)

Incoming/Outgoing

No

3

Call Bridge

TURN
server

32768-
65535

Media
TCP
(RDP)

Incoming/Outgoing

No

3

Call Bridge

TURN
server

3478

Media
UDP

Incoming

No.

3

Call Bridge

TURN
server

3478

Media
TCP

Incoming

Yes, see note 4.

4

TURN server

Remote SIP
devices

32768-
65535

Media
UDP

(STUN,
RTP)

Incoming/Outgoing

No

4

TURN server

Remote SIP
devices

32768-
65535

Media
TCP

(RDP)

Incoming/Outgoing

No

3,4

TURN server

Remote SIP
devices

3478

UDP

Incoming/Outgoing

Yes

3,4

TURN server

Remote SIP
devices

443
(Note 3)

TCP

Incoming/Outgoing

Yes

Note 1: Port 5061 is normally used for SIP TLS