Cisco Cisco Meeting Server 1000
Cisco Meeting Server Release 2.0 : Single Split Meeting Server Deployments
82
Link
Component
Connecting
to
to
Destination
port to
open port
port to
open port
Traffic
type
type
Traffic direction
with respect to
component
with respect to
component
Configurable
3
Call Bridge
TURN
server
server
32768-
65535
65535
Media
TCP
(RDP)
TCP
(RDP)
Incoming/Outgoing
No
3
Call Bridge
TURN
server
server
3478
Media
UDP
UDP
Incoming
No.
3
Call Bridge
TURN
server
server
3478
Media
TCP
TCP
Incoming
Yes, see note 4.
4
TURN server
Remote SIP
devices
devices
32768-
65535
65535
Media
UDP
UDP
(STUN,
RTP)
RTP)
Incoming/Outgoing
No
4
TURN server
Remote SIP
devices
devices
32768-
65535
65535
Media
TCP
TCP
(RDP)
Incoming/Outgoing
No
3,4
TURN server
Remote SIP
devices
devices
3478
UDP
Incoming/Outgoing
Yes
3,4
TURN server
Remote SIP
devices
devices
443
(Note 3)
(Note 3)
TCP
Incoming/Outgoing
Yes
Note 1: Port 5061 is normally used for SIP TLS
Note 2: Only SIP TLS is supported, there is no support for UDP or TCP on port 5060
Note 3: Using the MMP command turn tls <port> will change the TCP port that the TURN server listens on for
both Call Bridge and App connections..
both Call Bridge and App connections..
11.1 Configuring SIP/Lync call traversal
1. Set up a SIP Edge on the Edge server.
a. Configure the internal interface and port for communication to the Call Bridge. If the Call
Bridge is using port 5061, then use a different port.
sipedge private <interface>:port
sipedge private <interface>:port
for example:
sipedge private a:3061
b. Configure the external interface and port on the SIP Edge
sipedge public b:5061
for example:
sipedge public b:5061
11 SIP and Lync call traversal of local firewalls (BETA)