Cisco TelePresence Video Communication Server (Cisco VCS) IP Port Usage for Firewall Traversal. Cisco VCS X8.5 December 2014
|
|
|
- Mae Wiggins
- 9 years ago
- Views:
Transcription
1 Cisco TelePresence Video Communication Server (Cisco VCS) IP Port Usage for Firewall Traversal Cisco VCS X8.5 December 2014
2 Contents: Cisco VCS IP port usage Which IP ports are used with Cisco VCS? Which IP ports need to be allowed through firewalls? Format of information Traversing firewalls Administration SIP calls H.323 calls Internal Administration SIP calls H.323 calls 2
3 Guide to this document: format of information Source of messaging Cisco Cisco VCS Expressway Server listening port Direction firewall needs to be opened Destination of messaging Management control Open firewall to to Direction of management / calls S = Source port, typically Details of what defines the IP port ID / range DNS server Destination of messaging: DNS UDP S UDP Source of messaging: Destination of messaging: IP port letter reference for more details default / expected port range in italics Firewall needs to have a pinhole open for at least all s at source to all listening ports at listener Source of messaging: IP port letter reference for more details default / expected port range in italics When a firewall allows an outbound message through, it is assumed that responses (up to about 20 to 30 seconds after the original send) will be allowed back through the firewall 3
4 Administration: Cisco Management system Management control Open firewall http https ssh SNMP management computer(s) TCP S TCP S TCP S UDP S Private to Private to TCP TCP TCP UDP Management ports only open ports for the management methods to be used S = Source port, typically 4
5 Administration: Cisco PC listening port Management ports only open ports for the management methods to be used Management control Open firewall to private to private management computer(s) NTP UDP LDAP (for login) TCP 389 or or 636 Syslog UDP UDP TCP Ue to * UDP Ve to * Ue = VCS TCP ephemeral port range defaults to to * Ve = VCS UDP ephemeral port range defaults to to * * The default ephemeral port range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X8.1. 5
6 Administration: Cisco TMS (listening) port TMS (listening) port Call direction TMS to to TMS Open firewall n/a n/a External IP address of TMS External IP address of TMS https (TMS to VCS and secure feedback from VCS to TMS) http (feedback to TMS) TCP S TCP TCP TCP TCP S TCP S S = Source port, typically SNMP (To TMS) UDP S UDP
7 Administration: Cisco Server listening port Management control Open firewall to to DNS Server DNS UDP S UDP S = Source port, typically 7
8 SIP traversal call Call direction Open firewall SIP signaling Assent RTP (traversal media) Assent RTCP (traversal media) Inbound and outbound calls TCP & TLS A to to ** to ** Private to TCP and TLS B to *** to *** A = Protocols > SIP > TCP Outbound port start to end: default = to B = Zones > Traversal Client > SIP port, typically 7001 for first traversal zone, 7002 for second etc. Y C = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** / *** ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. *** Systems prior to X8 that are upgraded to X8.2 or later will continue to use the previous media demultiplexing RTP /RTCP ports, typically 2776/
9 SIP call to endpoint with Call direction endpoint Outbound to an endpoint in the endpoint Inbound from an endpoint in the Open firewall to to SIP signaling RTP RTCP UDP C 5060 TCP & TLS A to to ** to ** Any UDP & TCP & TLS F 5060 or UDP: C 5060 TCP: K 5060 TLS: L to ** to ** Any UDP G 5060 or TCP & TLS H C = Protocols > SIP > UDP port: default = 5060 A = Protocols > SIP > TCP Outbound port start to end: default = to F = defined by endpoint s registration (or not registered, IP port is defined by DNS lookup) any port, often 5060 for UDP K = Protocols > SIP > TCP port: default = 5060 L = Protocols > SIP > TLS port: default =5061 G = any port, often 5060 for hard endpoints H = any port Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on VCS Expressway): default = to ** E = Endpoint media port range; value used is specified in the SDP: = any IP port above 1024 = to ** for another VCS = 2326 to 2385 for MXP static setting = to for MXP dynamic setting ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. 9
10 SIP call to endpoint behind non SIP-aware firewall Call direction endpoint Outbound to an endpoint behind a firewall endpoint Inbound from an endpoint behind a firewall Open firewall to to SIP signaling RTP RTCP UDP C 5060 TCP & TLS A to to ** to ** Any UDP & TCP & TLS F 5060 or UDP N UDP N UDP: C 5060 TCP: K 5060 TLS: L to ** to ** Any UDP, TCP & TLS: Q UDP N UDP N C = Protocols > SIP > UDP port: default = 5060 A = Protocols > SIP > TCP Outbound port start to end: default = to F = defined by endpoint s registration (or if call is to a non registered endpoint, IP port is defined by DNS lookup) any port, often 5060 for UDP K = Protocols > SIP > TCP port: default = 5060 L = Protocols > SIP > TLS port: default =5061 Q = Egress IP port from far end non-nat aware firewall: any port Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on VCS Expressway): default = to ** N = VCS waits until it receives media, then it sends its media to the IP port from which the media was received (egress port of the media from the far end non SIP-aware firewall): any port ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. 10
11 SIP additional ports for ICE endpoint endpoint message direction Outbound from VCS to endpoint in internet Inbound from an endpoint in internet to VCS Open firewall to to TURN server control TURN server media Any N/A N/A UDP R 3478 (to 3483) UDP to * UDP N UDP to * Any UDP M UDP N M = IP port of signalling from endpoint may be ephemeral IP port of endpoint (if no firewall), or IP port of the outside firewall : = any IP port above 1024 N = IP port of relevant ICE candidate host IP port, Server reflexive IP port (outside firewall port) or TURN server port: = any IP port above 1024 R = On Large VCS systems you can configure a range of TURN request listening ports * For new installations of X8.1 or later, the default range for TURN relay media ports is The previous default range of still applies to earlier releases that have upgraded to X
12 H.323 traversal call using Assent Call direction Open firewall Initial RAS connection Q 931 / H.225 signaling Inbound and outbound calls UDP R C 1719 TCP P to H.245 TCP P to Assent RTP (traversal media) Assent RTCP (traversal media) to ** to ** Private to UDP D 6001 TCP T 2776 TCP T *** *** R C = Protocols > H.323 > Gatekeeper > Registration UDP port: default = 1719 P = Protocols > H.323 > Gatekeeper > Call signaling port range start to end: default = to D = Zones > Traversal Zone > H.323 port, typically 6001 for first traversal zone, 6002 for second etc. T = Traversal > Ports > H.323 Assent call signaling port: default = 2776 Y C = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** / *** ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. *** Systems prior to X8 that are upgraded to X8.2 or later will continue to use the previous media demultiplexing RTP /RTCP ports, typically 2776/
13 H.323 traversal call using H / 19 non-muxed media Call direction Open firewall Initial RAS connection Q 931 / H.225 signaling Inbound and outbound calls UDP R C 1719 TCP P to H.245 TCP P to Assent RTP (traversal media) Assent RTCP (traversal media) to ** to ** Private to UDP D 6001 TCP M 1720 TCP U to ** to ** R C = Protocols > H.323 > Gatekeeper > Registration UDP port: default = 1719 P = Protocols > H.323 > Gatekeeper > Call signaling port range start to end: default = to D = Zones > Traversal Zone > H.323 port, typically 6001 for first traversal zone, 6002 for second etc. M = Protocols > H.323 Call signaling TCP port: default = 1720 U = Traversal > Ports > H.323 H call signaling port: default = 2777 Y C = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** Y E = Local Zone < Traversal Subzone > Traversal Media port start to end (configured on ) : default = to ** ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. 13
14 H.323 traversal call using H / 19 multiplexed media Call direction Open firewall Initial RAS connection Q 931 / H.225 signaling Inbound and outbound calls UDP R C 1719 TCP P to H.245 TCP P to Assent RTP (traversal media) Assent RTCP (traversal media) to ** to ** Private to UDP D 6001 TCP M 1720 TCP U *** *** R C = Protocols > H.323 > Gatekeeper > Registration UDP port: default = 1719 P = Protocols > H.323 > Gatekeeper > Call signaling port range start to end: default = to D = Zones > Traversal Zone > H.323 port, typically 6001 for first traversal zone, 6002 for second etc. M = Protocols > H.323 Call signaling TCP port: default = 1720 U = Traversal > Ports > H.323 H call signaling port: default = 2777 Y C = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** Y E = Local Zone < Traversal Subzone > Traversal Media port start to end (configured on ) : default = to ** / *** ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. *** Systems prior to X8 that are upgraded to X8.2 or later will continue to use the previous media demultiplexing RTP /RTCP ports, typically 2776/
15 H.323 call with registered endpoint with Call direction endpoint Outbound to an endpoint in the endpoint Inbound from an endpoint in the Open firewall to to Initial RAS connection Q 931 / H.225 signaling Any - - UDP R E 1719 TCP P to H.245 TCP P to RTP RTCP to ** to ** TCP G 1720 TCP H TCP M 1720 TCP P to to ** to ** Any UDP J 1719 TCP K 1720 TCP H R E = Protocols > H.323 > Gatekeeper Registration > UDP port, default = 1719 J = Endpoint RAS, typically 1719 P = Protocols > H.323 > Gatekeeper > Call signaling port range start to end: default = to G = Endpoint signaling port, specified in registration: any port, typically 1720 M = Protocols > H.323 Call signaling TCP port: default = 1720 K = Endpoint signaling port: any port, typically 1720 H = Endpoint H.245 signaling port: = any IP port = to to another VCS = 5555 to 5574 for MXP static setting = to for MXP dynamic setting Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on VCS Expressway): default = to ** E = Endpoint media port range; value used is specified in codec negotiations: = any IP port above 1024 = to ** for another VCS = 2326 to 2385 for MXP static setting = to for MXP dynamic setting ** The default media port range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X
16 H.323 call with a non-registered endpoint with IP Call direction endpoint Outbound to an endpoint in the endpoint Inbound from an endpoint in the Open firewall to to Initial RAS connection Q 931 / H.225 signaling Any Any TCP P to H.245 TCP P to RTP RTCP to ** to ** TCP G 1720 TCP H TCP M 1720 TCP P to to ** to ** TCP K 1720 TCP H P = Protocols > H.323 > Gatekeeper > Call signaling port range start to end: default = to G = Endpoint signaling port, specified by a) IP Port in call request b) DNS lookup for URI to call c) 1720 if but no port specified Can be: any port, typically 1720 M = Protocols > H.323 Call signaling TCP port: default = 1720 K = Endpoint signaling port: any port, typically 1720 H = Endpoint H.245 signaling port: = any IP port = to to another VCS = 5555 to 5574 for MXP static setting = to for MXP dynamic setting Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on VCS Expressway): default = to ** E = Endpoint media port range; value used is specified in codec negotiations: = any IP port above 1024 = to ** for another VCS = 2326 to 2385 for MXP static setting = to for MXP dynamic setting ** The default media port range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X
17 H.323 call with endpoint supporting Assent behind firewall Firewall R E = Protocols > H.323 > Gatekeeper Registration > UDP port, default = 1719 Q =Egress IP port from far end non-h.323 aware firewall: any port Call direction Open firewall Initial RAS connection Q 931 / H.225 signaling Inbound from or outbound to an endpoint in the behind a firewall UDP R E 1719 TCP T 2776 H.245 TCP T 2776 RTP RTCP ** / *** ** / *** to Any UDP Q TCP Q TCP Q UDP N UDP N T = Traversal > Ports > H.323 Assent call signaling port: default = 2776 Y E = Local Zone < Traversal Subzone > Traversal Media port start to end (configured on ) : default = to ** / *** N = Egress IP port of media from far end non-h.323 aware firewall: any port For calls made from the to the endpoint: 1. sends a message to the endpoint using the return path of the established RAS (registration) connection 2. The endpoint then makes a TCP connection out through its firewall to the VCS Expressway (port T must be open on the firewall local to the VCS Expressway) 3. Any further connections required (e.g. H.245) are requested by the VCS Expressway over the established TCP connection, and the endpoint initiates them (to port T ) ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. *** Systems prior to X8 that are upgraded to X8.2 or later will continue to use the previous media demultiplexing RTP /RTCP ports, typically 2776/
18 H.323 call with endpoint supporting H / 19 non-mux media Firewall R E = Protocols > H.323 > Gatekeeper Registration > UDP port, default = 1719 Call direction Open firewall Initial RAS connection Q 931 / H.225 signaling Inbound from or outbound to an endpoint in the behind a firewall UDP R E 1719 TCP M 1720 H.245 TCP U 2777 RTP RTCP to ** to ** to Any UDP Q TCP Q TCP Q UDP N UDP N Q =Egress IP port from far end non-h.323 aware firewall: any port M = Protocols > H.323 Call signaling TCP port: default = 1720 U = Traversal > Ports > H.323 H call signaling port: default = 2777 Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** N = Egress IP port of media from far end non-h.323 aware firewall: any port For calls made from the to the endpoint: 1. sends a message to the endpoint using the return path of the established RAS (registration) connection 2. The endpoint then makes a TCP connection out through its firewall to the VCS Expressway (port M must be open on the firewall local to the VCS Expressway) 3. Any further connections required (e.g. H.245) are requested by the VCS Expressway over the established TCP connection, and the endpoint initiates them (to port U ) ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. 18
19 H.323 call with endpoint supporting H / 19 multiplexed media Firewall R E = Protocols > H.323 > Gatekeeper Registration > UDP port, default = 1719 Q = Egress IP port from far end non-h.323 aware firewall: any port Call direction Open firewall Initial RAS connection Q 931 / H.225 signaling Inbound from or outbound to an endpoint in the behind a firewall UDP R E 1719 TCP M 1720 H.245 TCP U 2777 RTP RTCP ** / *** ** / *** to Any UDP Q TCP Q TCP Q UDP N UDP N M = Protocols > H.323 Call signaling TCP port: default = 1720 U = Traversal > Ports > H.323 H call signaling port: default = 2777 Y E = Local Zone < Traversal Subzone > Traversal Media port start to end (configured on ) : default = to ** N = Egress IP port of media from far end non-h.323 aware firewall: any port For calls made from the to the endpoint: 1. sends a message to the endpoint using the return path of the established RAS (registration) connection 2. The endpoint then makes a TCP connection out through its firewall to the VCS Expressway (port M must be open on the firewall local to the ) 3. Any further connections required (e.g. H.245) are requested by the over the established TCP connection, and the endpoint initiates them (to port U ) ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. *** Systems prior to X8 that are upgraded to X8.2 or later will continue to use the previous media demultiplexing RTP /RTCP ports, typically 2776/
20 SIP/H.323 Authentication: Cisco PC listening port Management ports only open ports for the management methods to be used Management control Open firewall to private to private management computer(s) H.350 TCP 389 or or 636 TCP Ue to * Active Directory direct UDP 53 UDP 88 TCP 88 UDP 389 TCP 389 or 636 TCP 445 or , 88, 389 or 636, 445 or 139 UDP Ve to * TCP Ue to * Ue = VCS TCP ephemeral port range defaults to to * Ve = VCS UDP ephemeral port range defaults to to * * The default ephemeral port range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X
21 Administration: Cisco Management system listening port Management control Private network Open firewall n/a management computer(s) S = Source port, typically http TCP S TCP https ssh TCP S TCP S TCP TCP SNMP UDP S UDP
22 Administration: Cisco Management system listening port Management control Private network Open firewall n/a management computer(s) S = Source port, typically NTP UDP UDP LDAP TCP http (feedback to TMS) TCP TCP S TCP S DNS UDP UDP S 22
23 Administration: local endpoint Management system Endpoint listening port Management control Private network Open firewall n/a management computer(s) Endpoint S = Source port, typically http TCP S TCP https TCP S TCP ssh telnet TCP S TCP S TCP TCP SNMP UDP S UDP
24 Administration: local endpoint Management system Management control Private network Open firewall n/a management computer(s) S = Source port, typically NTP UDP UDP http (feedback to TMS) TCP TCP S DNS UDP UDP S 24
25 SIP: internal Endpoint listening port listening port Endpoint Call direction to endpoint Endpoint to Open firewall n/a n/a SIP signaling RTP RTCP UDP C 5060 TCP & TLS A to to ** to ** of endpoint UDP & TCP & TLS F 5060 or UDP: C 5060 TCP: K 5060 TLS: L to ** to ** of endpoint UDP G 5060 or TCP & TLS H C = Protocols > SIP > UDP port: default = 5060 A = Protocols > SIP > TCP Outbound port start to end: default = to F = defined by endpoint s registration (or if call is to a non-registered endpoint, IP port is defined by DNS lookup) any port, often 5060 for UDP K = Protocols > SIP > TCP port: default = 5060 L = Protocols > SIP > TLS port: default =5061 G = any port, often 5060 for hard endpoints H = any port Y C = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on VCS Control): default = to ** E = Endpoint media port range; value used is specified in the SDP: = any IP port above 1024 = to ** for another VCS = 2326 to 2385 for MXP static setting = to for MXP dynamic setting ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. 25
26 H.323: internal Endpoint listening port listening port Endpoint Call direction to endpoint Endpoint to Open firewall n/a n/a Initial RAS connection Q 931 / H.225 signaling Any - - UDP R C 1719 TCP P to H.245 TCP P to RTP RTCP to ** to ** TCP G 1720 TCP H TCP M 1720 TCP P to to ** to ** Any UDP J 1719 TCP K 1720 TCP H R C = Protocols > H.323 > Gatekeeper Registration > UDP port, default = 1719 J = Endpoint RAS, typically 1719 P = Protocols > H.323 > Gatekeeper > Call signaling port range start to end: default = to G = Endpoint signaling port, specified in registration: any port, typically 1720 M = Protocols > H.323 Call signaling TCP port: default = 1720 K = Endpoint signaling port: any port, typically 1720 H = Endpoint H.245 signaling port: = any IP port = to to another VCS = 5555 to 5574 for MXP static setting = to for MXP dynamic setting Y C = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on VCS Control): default = to ** E = Endpoint media port range; value used is specified in codec negotiations: = any IP port above 1024 = to ** for another VCS = 2326 to 2385 for MXP static setting = to for MXP dynamic setting ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. 26
27 Unified Communications : to Unified CM, IM&P IM&P Unified CM-UDS Management system listening port Management control Private network Open firewall n/a XMPP (IM and Presence) Unified CM, IM and Presence servers and CUC TCP 7400 (IM&P server) TCP Ue to * Ue = VCS TCP ephemeral port range defaults to * * The default range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X8.1. UDS (provisioning and phonebook) TCP 8443 (Unified CM server) TCP Ue to * SOAP (IM and Presence Service) TCP 8443 (IM&P node) TCP Ue to * HTTP (configuration file retrieval) TCP 6970 (Unified CM server) TCP Ue to * CUC (voic ) TCP 443 (CUC server) TCP Ue to * 27
28 Unified Communications : Control (private) to Expressway () IM&P Unified CM-UDS server (listening) port A = Protocols > SIP > TCP Outbound port start to end: default = to B = Zones > Traversal Client > SIP port, typically 7001 for first traversal zone, 7002 for second etc. Message direction Open firewall XMPP (IM and Presence) SSH (HTTP/S tunnels) SIP signaling SIP media TURN server control Inbound and outbound calls TCP Ue to * TCP Ue to * TCP & TLS A to to ** UDP Private to TCP 7400 TCP 2222 TCP and TLS B / *** UDP 3478 (to 3483) R R = On Large VCS systems you can configure a range of TURN request listening ports Ue = VCS TCP ephemeral port range defaults to to * Y C = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on ): default = to ** / *** * The default ephemeral port range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X8.1. ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. *** Systems prior to X8 that are upgraded to X8.2 or later will continue to use the previous media demultiplexing RTP /RTCP ports, typically 2776/
29 Unified Communications: Expressway () to internet IM&P Unified CM-UDS endpoint server (listening) port endpoint N = VCS waits until it receives media, then it sends its media to the IP port from which the media was received (egress port of the media from the far end non SIP-aware firewall): any port Message direction Outbound to an endpoint in the Inbound from an endpoint in the Open firewall to to XMPP (IM and Presence) UDS (phonebook and provisioning) TURN server control / media SIP signaling SIP media Address of Any IP address Address of Any IP address n/a n/a TCP 5222 TCP S n/a n/a TCP 8443 TCP S n/a n/a UDP 3478 (to 3483) R / to * TLS to to ** TLS S UDP N TLS to ** UDP S TLS S UDP N R = On Large VCS systems you can configure a range of TURN request listening ports S = Source port, typically Y E = Local Zone > Traversal Subzone > Traversal Media port start to end (configured on VCS Expressway): default = to ** * For new installations of X8.1 or later, the default range for TURN relay media ports is The previous default range of still applies to earlier releases that have upgraded to X8.1. ** The default media port range of to applies to new installations of X8.1 or later. In Large systems the first 12 ports in the range to are used for multiplexed traffic only. In Small/Medium systems you can either explicitly specify the 2 ports to use for multiplexed traffic or use the first 2 ports from the media port range. The previous default range of still applies to earlier releases that have upgraded to X8.1 or later. 29
30 Unified Communications: Jabber Guest (internet to ) Jabber Guest Server Unified CM Jabber Guest Client Listening Port SIP UA Source Port S = Source port, typically Management Control Inbound from SIP UA in the Open Firewall to IP Address - HTTPS traffic TCP 9443 HTTP traffic TCP 9980 TURN Server Control UDP 3478 (to 3483) - Any (or specific IP) TCP S (to TCP 443) TCP S (to TCP 80) UDP S Must translate the destination port of 443 to 9443 for all HTTPS (and 80 to 9980 for HTTP) traffic that targets the address from Jabber Guest clients. 30
31 Unified Communications: Jabber Guest ( to ) Jabber Guest Server Unified CM Jabber Guest Client Source Port Listening Port E = Configurable TCP ephemeral port range (on ) T C = Configurable TCP outbound port range (on ) Management Control Open Firewall Outbound from to Private to Public NAT d T E = Configurable SIP port for Unified Communications traversal zone between (on ) Yc = Configurable traversal media ports range (on ) IP Address SSH (HTTP/S tunnels) Traversal Zone SIP signal Media - TCP E to *1 TLS T C to * to *3 - () SSH 2222 TLS T E to *4 Y E = Non-Configurable TURN relays media ports range () *1 The default ephemeral port range of applies to new installations of X8.1 or later The previous default range of still applies to earlier releases that have upgraded to X8.1 *2 The default outbound port range of applies to new installations of X8.1 or later and earlier releases that have upgraded to X8.1 *3 The default media port range of applies to new installations of X8.1 or later The previous default range of still applies to earlier releases that have upgraded to X8.1 or later *4 The default TURN relay media port range of applies to new installations of X8.1 or later The previous default range of still applies to earlier releases that have upgraded to X8.1 31
32 Unified Communications: Jabber Guest ( to ) Jabber Guest Server Unified CM Jabber Guest Client Listening Port Source Port Yc = Configurable traversal media ports range (on ) Y E = Non-Configurable TURN relays media ports range (on ) Management Control Open Firewall IP Address IP Ports Media Inbound from () to to *1 Public NAT d to Private - (Public) to *2 *1 The default media port range of applies to new installations of X8.1 or later The previous default range of still applies to earlier releases that have upgraded to X8.1 *2 The default TURN relay media port range of applies to new installations of X8.1 or later The previous default range of still applies to earlier releases that have upgraded to X8.1 32
33 Unified Communications: XMPP federation ( / IM&P Server) IM&P IMP Client Source Port Listening Port XMPP Open Firewall Outbound from to () Private to IP Address - - XMPP TCP E (Ephemeral port) TCP 7400 E= VCS TCP ephemeral port range defaults to * IM&P Server Listening Port Source Port * The default range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X8.1. XMPP Outbound from to IM&P Server Open Firewall - IP Address - IM&P Server - XMPP TCP 7400 TCP E (Ephemeral port) 33
34 Unified Communications: XMPP federation ( and ) IM&P IMP Client Listening Port Federated XMPP Server Source Port XMPP Open Firewall Inbound from internet to () to IP Address - XMPP TCP 5269 Source Port - Federated XMPP Server TCP Ephemeral port Federated XMPP Server Listening Port E= VCS TCP ephemeral port range defaults to * * The default range of applies to new installations of X8.1 or later; the previous default range of still applies to earlier releases that have upgraded to X8.1. XMPP Open Firewall Outbound from () to internet to IP Address - - Federated XMPP Server XMPP TCP E (Ephemeral port) TCP
35 SIP B2BUA and Microsoft Lync Lync Client 3478 outbound UDP required Lync Front-End Lync Edge Server Public IP only NAT not supported Lync Client 3478, * inbound UDP if the Expressway is used for media only to NAT Lync gateway VCS B2BUA Expressway Public NAT supported on Expressway Expressway IP can be private 3478 * outbound UDP from B2BUA to Expressway Internal Firewall External Firewall (assumes response back allowed) Only Internal IP needed * On Large VCS systems you can configure a range of TURN request listening ports (3478 to 3483). For new installations of X8.1 or later, the default range for TURN relay media ports is The previous default range of still applies to earlier releases that have upgraded to X
36 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB s domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Any Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual es or phone numbers in illustrative content is unintentional and coincidental Cisco Systems, Inc. All rights reserved.
Cisco Expressway IP Port Usage for Firewall Traversal. Cisco Expressway X8.1 D15066.01 December 2013
Cisco Expressway IP Port Usage for Firewall Traversal Cisco Expressway X8.1 D15066.01 December 2013 Contents: Cisco Expressway IP port usage Which IP ports are used with Cisco Expressway? Which IP ports
Ports Reference Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release 9.0
Ports Reference Guide for Cisco Virtualization Experience Media Engine for SUSE Linux Release 9.0 Ports 2 Virtualization Experience Media Engine 2 Virtualization Experience Client Manager 3 Cisco Jabber
Cisco Collaboration with Microsoft Interoperability
Cisco Collaboration with Microsoft Interoperability Infrastructure Cheatsheet First Published: June 2016 Cisco Expressway X8.8 Cisco Unified Communications Manager 10.x or later Microsoft Lync Server 2010
Cisco TelePresence VCR Converter 1.0(1.8)
Cisco TelePresence VCR Converter 1.0(1.8) Software release notes D14725.02 February 2011 Contents Contents Document revision history... 3 Introduction... 4 New features in version 1.0(1.8)... 5 Convert
Troubleshooting Procedures for Cisco TelePresence Video Communication Server
Troubleshooting Procedures for Cisco TelePresence Video Communication Server Reference Guide Cisco VCS X7.2 D14889.01 September 2011 Contents Contents Introduction... 3 Alarms... 3 VCS logs... 4 Event
Cisco TelePresence Management Suite Provisioning
Cisco TelePresence Management Suite Provisioning Troubleshooting guide D14427.03 December 2010 Introduction Table of Contents Introduction... 3 Provisioning logs... 4 Cisco TMS provisioning directory logs...
Unified Communications Mobile and Remote Access via Cisco VCS
Unified Communications Mobile and Remote Access via Cisco VCS Deployment Guide Cisco VCS X8.2 Cisco Unified CM 9.1(2)SU1 or later January 2015 Contents Mobile and remote access overview 4 Jabber client
Cisco Unified Communications Self Care Portal User Guide, Release 10.5(1)
Cisco Unified Communications Self Care Portal User Guide, Release 10.5(1) Unified Communications Self Care Portal 2 Unified Communications Self Care Settings 2 Phones 4 Additional Settings 12 Revised:
Cisco TelePresence Authenticating Cisco VCS Accounts Using LDAP
Cisco TelePresence Authenticating Cisco VCS Accounts Using LDAP Deployment Guide Cisco VCS X8.1 D14465.06 December 2013 Contents Introduction 3 Process summary 3 LDAP accessible authentication server configuration
UCi2i Video Conference Endpoint Firewall Requirements. UCi2i Video Conference Endpoint Firewall Requirements
1 UCi2i Video Conference Endpoint Firewall Requirements 2 UCi2i VC Endpoint Firewall Requirements Dear customer, Due to the implementation of our secure video network, there are a few firewall rules that
Cisco TelePresence VCR MSE 8220
Cisco TelePresence VCR MSE 8220 Getting started 61-0008-05 Contents General information... 3 About the Cisco TelePresence VCR MSE 8220... 3 Port and LED location... 3 LED behavior... 4 Installing the VCR
Unified Communications Mobile and Remote Access via Cisco Expressway
Unified Communications Mobile and Remote Access via Cisco Expressway Deployment Guide Cisco Expressway X8.1.1 or later Cisco Unified CM 9.1(2)SU1 or later January 2015 Contents Mobile and remote access
Cisco Unified Communications Manager SIP Line Messaging Guide (Standard)
Cisco Unified Communications Manager SIP Line Messaging Guide (Standard) For Cisco Unified Communications Manager Release 8.5(1) These materials are made available by Cisco as a courtesy to provide certain
Unified Communications Mobile and Remote Access via Cisco VCS
Unified Communications Mobile and Remote Access via Cisco VCS Deployment Guide Cisco VCS X8.1.1 or later Cisco Unified CM 9.1(2)SU1 or later January 2015 Contents Mobile and remote access 4 Jabber client
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0 Software Release Notes May 2014 Contents Introduction 1 Changes to interoperability 1 Product documentation 1 New features
Application Note. Onsight Connect Network Requirements v6.3
Application Note Onsight Connect Network Requirements v6.3 APPLICATION NOTE... 1 ONSIGHT CONNECT NETWORK REQUIREMENTS V6.3... 1 1 ONSIGHT CONNECT SERVICE NETWORK REQUIREMENTS... 3 1.1 Onsight Connect Overview...
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.1
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.1 Software Release Notes May 2014 Contents Introduction 1 Changes to interoperability 1 Product documentation 2 New features
Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway)
Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway) Deployment Guide Cisco VCS X8.1 D14651.08 August 2014 Contents Introduction 4 Example network deployment 5 Network
Cisco TelePresence Management Suite 15.0
Cisco TelePresence Management Suite 15.0 Software Release Notes July 2015 Product Documentation The following documents provide guidance on installation, initial configuration, and operation of the product:
Enabling Single Sign- On for Common Identity using F5
Enabling Single Sign- On for Common Identity using F5 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS
Cisco TelePresence MCU Accessing Conferences
Cisco TelePresence MCU Accessing Conferences Getting started 14523.02 Contents Introduction... 3 Calling in to conferences... 4 Dialing in using a hardware video endpoint... 4 Dialing in using a software
Sample Configuration: Cisco UCS, LDAP and Active Directory
First Published: March 24, 2011 Last Modified: March 27, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS
TelePresence Migrating TelePresence Management Suite (TMS) to a New Server
TelePresence Migrating TelePresence Management Suite (TMS) to a New Server THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
LifeSize Transit Deployment Guide June 2011
LifeSize Transit Deployment Guide June 2011 LifeSize Tranist Server LifeSize Transit Client LifeSize Transit Deployment Guide 2 Firewall and NAT Traversal with LifeSize Transit Firewalls and Network Address
QoS: CBQoS Management Policy-to- Interface Mapping Support Configuration Guide, Cisco IOS XE Release 3S (Cisco ASR 1000)
QoS: CBQoS Management Policy-to- Interface Mapping Support Configuration Guide, Cisco IOS XE Release 3S (Cisco ASR 1000) Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706
StarLeaf Network Guide
Network Guide Contents Introduction------------------------------------------------------------------------------------------------------------------------- 3 Registration to the ------------------------------------------------------------------------------------------
Replacing MCU Software with TelePresence Server Software on Cisco TelePresence MCU 5300 Series. Last Updated: February 2016
Replacing MCU Software with TelePresence Server Software on Cisco TelePresence MCU 5300 Series Last Updated: February 2016 Cisco Systems, Inc. www.cisco.com Preface Change History Table 1 Replacing MCU
UCi2i Video Conference Endpoint Firewall Requirements
UCi2i Video Conference Endpoint Firewall Requirements Page 1 Confidentiality Statement and Copyright Notice This document is published as Public and may be freely distributed. Copyright subsists in all
Cisco Unified Workforce Optimization
Cisco Unified Workforce Optimization Desktop Requirements Guide Version 10.5 First Published: June 18, 2014 Last Updated: March 6, 2015 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS
Polycom RealPresence Access Director System
Release Notes 3.1 January 2014 3725-78700-001C Polycom RealPresence Access Director System Polycom announces the release of the Polycom RealPresence Access Director system, version 3.1. This document provides
Cisco UCS Director Payment Gateway Integration Guide, Release 4.1
First Published: April 16, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
Cisco Jabber for Windows 10.5 Advanced Features Guide
First Published: August 14, 2014 Last Modified: August 26, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS
Application Note. Firewall Requirements for the Onsight Mobile Collaboration System and Hosted Librestream SIP Service v5.0
Application Note Firewall Requirements for the Onsight Mobile Collaboration System and Hosted Librestream SIP Service v5.0 1 FIREWALL REQUIREMENTS FOR ONSIGHT MOBILE VIDEO COLLABORATION SYSTEM AND HOSTED
Polycom Unified Communications in RealPresence Access Director System Environments
Solution Deployment Guide Version 4.0 June 2014 3725-78704-001D Polycom Unified Communications in RealPresence Access Director System Environments Copyright 2014, Polycom, Inc. All rights reserved. No
Polycom Unified Communications in RealPresence Access Director System Environments
Solution Deployment Guide Version 4.1 December 2014 3725-78704-001E Polycom Unified Communications in RealPresence Access Director System Environments Copyright 2014, Polycom, Inc. All rights reserved.
Cisco TelePresence Video Systems
1 Knowledge base Profile Series Quick Set Series Codec MXP Endpoints IP Video Phone MARCH 2012 Thank you for choosing Cisco! Your Cisco product has been designed to give you many years of safe, reliable
Unified Communications in RealPresence Access Director System Environments
[Type the document title] 3.0 October 2013 3725-78704-001B1 Deploying Polycom Unified Communications in RealPresence Access Director System Environments Polycom Document Title 1 Trademark Information Polycom
Cisco WebEx Meetings Server System Requirements
First Published: October 21, 2012 Last Modified: October 21, 2012 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 8 526-00 800 553-NETS
MS Skype for Business and Lync. Integration Guide
MS Skype for Business and Lync Integration Guide June 03, 2016 Contents Introduction 4 How to use StarLeaf with Microsoft Skype for Business 2015 Server 5 Pre-requisites 5 Step One: Federate between the
Cisco IOS Flexible NetFlow Command Reference
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION
Cisco TelePresence VCS Certificate Creation and Use
Cisco TelePresence VCS Certificate Creation and Use Deployment Guide Cisco VCS X8.1 D14548.08 December 2013 Contents Introduction 3 PKI introduction 3 Overview of certificate use on the VCS 3 Certificate
Application Note. Onsight Connect Network Requirements V6.1
Application Note Onsight Connect Network Requirements V6.1 1 ONSIGHT CONNECT SERVICE NETWORK REQUIREMENTS... 3 1.1 Onsight Connect Overview... 3 1.2 Onsight Connect Servers... 4 Onsight Connect Network
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.3
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.3 Software Release Notes Revised September 2014 Contents Introduction 1 Changes to interoperability 1 Product documentation
User Guide for the Cisco Unity Connection Phone Interface (Release 8.x)
User Guide for the Cisco Unity Connection Phone Interface (Release 8.x) First Published: February 02, 2010 Last Modified: November 16, 2010 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive
IP Ports and Protocols used by H.323 Devices
IP Ports and Protocols used by H.323 Devices Overview: The purpose of this paper is to explain in greater detail the IP Ports and Protocols used by H.323 devices during Video Conferences. This is essential
TMS Phone Books Troubleshoot Guide
TMS Phone Books Troubleshoot Guide Document ID: 118705 Contributed by Adam Wamsley and Magnus Ohm, Cisco TAC Engineers. Jan 05, 2015 Contents Introduction Prerequisites Requirements Components Used Related
CISCO TELEPRESENCE MANAGEMENT SUITE EXTENSION
You can read the recommendations in the user guide, the technical guide or the installation guide for CISCO TELEPRESENCE MANAGEMENT SUITE EXTENSION 2.2. You'll find the answers to all your questions on
Cisco Expressway Series
Data Sheet Cisco Expressway Series Advanced Collaboration Gateways for Simple and Secure Unified Communications Product Overview Cisco Expressway Series gateways for Cisco Unified Communications Manager
Cisco Expressway Basic Configuration
Cisco Expressway Basic Configuration Deployment Guide Cisco Expressway X8.1 D15060.03 August 2014 Contents Introduction 4 Example network deployment 5 Network elements 6 Internal network elements 6 DMZ
Disaster Recovery Configuration Guide for CiscoWorks Network Compliance Manager 1.8
Disaster Recovery Configuration Guide for CiscoWorks Network Compliance Manager 1.8 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel:
Cisco TelePresence Video Communication Server Expressway
Data Sheet Cisco TelePresence Video Communication Server Expressway Extending video communications securely beyond the enterprise Product Overview Figure 1. Cisco TelePresence Video Communication Server
Polycom RealPresence Access Director System
RELEASE NOTES Version 4.2 June 25, 2015 3725-78700-001F1 Polycom RealPresence Access Director System Polycom, Inc. 1 Polycom RealPresence Access Director System Release Notes Version 4.2 Contents What
Cisco WebEx Meeting Center with Collaboration Meeting Rooms. Enterprise Deployment Guide
Cisco WebEx Meeting Center with Collaboration Meeting Rooms Enterprise Deployment Guide October, 2015 Contents Introduction 4 Deployment Scenario 4 Example: SIP Site with Cisco Infrastructure 4 Prerequisites
Application Note - Using Tenor behind a Firewall/NAT
Application Note - Using Tenor behind a Firewall/NAT Introduction This document has been created to assist Quintum Technology customers who wish to install equipment behind a firewall and NAT (Network
FireSIGHT User Agent Configuration Guide
Version 2.2 August 20, 2015 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL
Getting started guide
Software version TC4.0 NOVEMBER 2010 For Cisco TelePresence System Profile Series, Codec C Series and Quick Set C20 / C20 Plus 1 TA - ToC - Hidden Thank you for choosing Cisco! text anchor Your Cisco product
SBC 1000 / SBC 2000 Series Configuration Guide (For Microsoft Lync Server 2013)
Configuration Guide SBC 1000 / SBC 2000 Series Configuration Guide (For Microsoft Lync Server 2013) For use with AT&T s IP Flexible Reach Enhanced Features Service on MIS, MPLS PNT or AT&T VPN Disclaimers
Cisco Smart Care Services Questions and Answers About the Voice Quality Monitor Service
Cisco Smart Care Services Questions and Answers About the Voice Quality Monitor Service For Qualified Cisco Partners October 2008 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose,
Cisco TelePresence Video Communication Server Starter Pack Express Bundle
Data Sheet Cisco TelePresence Video Communication Server Starter Pack Express Product Overview Figure 1. Cisco TelePresence Video Communication Server Starter Pack Express Bundle The Cisco TelePresence
Cisco TelePresence Video Communication Server
Cisco TelePresence Video Communication Server Figure 1. Cisco TelePresence Video Communication Server Product Overview The Cisco TelePresence Video Communication Server (Cisco VCS) is deployed as either
Acano solution. Third Party Call Control Guide. March 2015 76-1055-01-E
Acano solution Third Party Call Control Guide March 2015 76-1055-01-E Contents Contents 1 Introduction... 3 1.1 How to Use this Guide... 3 1.1.1 Commands... 4 2 Example of Configuring a SIP Trunk to CUCM...
Cisco TelePresence MCU 5300 Series
Cisco TelePresence MCU 5300 Series Version 4.3 Tutorial D14472 July 2012 Contents Contents... 2 Using the tutorial... 4 Assumptions... 4 MCU software version... 4 Logging in to the web interface... 5 Creating
Cisco Expressway Certificate Creation and Use
Cisco Expressway Certificate Creation and Use Deployment Guide Cisco Expressway X8.1 D15061.01 December 2013 Contents Introduction 3 PKI introduction 3 Overview of certificate use on the Expressway 3 Certificate
Cisco Prime Central Managing Certificates
Cisco Prime Central Managing Certificates Version 1.0.5 September, 2015 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000
Placing the BlackBerry Enterprise Server for Microsoft Exchange in a demilitarized zone
Placing the for Originally posted: June 2002 Affected software versions BlackBerry Enterprise version 2.0 for Microsoft Exchange version 2.1 for Microsoft Exchange version 3.5 for Microsoft Exchange Summary
Application Note. Onsight TeamLink And Firewall Detect v6.3
Application Note Onsight And Firewall Detect v6.3 1 ONSIGHT TEAMLINK HTTPS TUNNELING SERVER... 3 1.1 Encapsulation... 3 1.2 Firewall Detect... 3 1.2.1 Firewall Detect Test Server Options:... 5 1.2.2 Firewall
White Paper. Traversing Firewalls with Video over IP: Issues and Solutions
Traversing Firewalls with Video over IP: Issues and Solutions V Table of Contents Introduction Role of a Firewall Deployment Issues Relating to IP Video and Firewall Traversal The VCON SecureConnect Solution
Cisco Jabber for Windows 9.7 Installation and Configuration Guide
First Published: March 26, 2014 Last Modified: June 23, 2014 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS
Cisco TelePresence Video Communication Server X8.2
Cisco TelePresence Video Communication Server X8.2 Software Release Notes August 2014 Contents Product documentation 1 New features in X8.2 2 Changes in X8.1.1 4 New features in X8.1 4 Resolved issues
Cisco Expressway. Administrator Guide. Software version: X8.1 D15058.01
Cisco Expressway Administrator Guide Software version: X8.1 D15058.01 December 2013 Contents Introduction 9 About the Cisco Expressway 10 Expressway base applications 11 Standard features 11 Optional features
Cisco TelePresence Video Communication Server
Cisco TelePresence Video Communication Server Administrator Guide X7.2 January 2015 Contents Introduction 10 About the Cisco TelePresence Video Communication Server (VCS) 11 VCS base applications 12 Standard
SIP Trunking Configuration with
SIP Trunking Configuration with Microsoft Office Communication Server 2007 R2 A Dell Technical White Paper End-to-End Solutions Team Dell Product Group - Enterprise THIS WHITE PAPER IS FOR INFORMATIONAL
Avaya Port Matrix: Avaya Diagnostic Server 2.5
Avaya Matrix: Avaya Diagnostic Server 2.5 Issue 1.1 March 2015 ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC. DISCLAIMS ALL WARRANTIES, EITHER
Getting Started Guide
Collaboration Endpoint Software CE8.0 NOVEMBER 2015 For MX and SX Series D15318.01 Video Systems CE8.0, NOVEMBER 2015. 1 Thank you for choosing Cisco! Your Cisco product has been designed to give you many
Application Note. Onsight Mobile Collaboration Video Endpoint Interoperability v5.0
Application Note Onsight Mobile Collaboration Video Endpoint Interoperability v5. Onsight Mobile Collaboration Video Endpoint Interoperability... 3 Introduction... 3 Adding Onsight to a Video Conference
Application Notes for Configuring a SonicWALL VPN with an Avaya IP Telephony Infrastructure - Issue 1.0
Avaya Solution & Interoperability Test Lab Application Notes for Configuring a SonicWALL VPN with an Avaya IP Telephony Infrastructure - Issue 1.0 Abstract These Application Notes describe the steps for
Cisco TelePresence VCS Certificate Creation and Use
Cisco TelePresence VCS Certificate Creation and Use Deployment Guide Cisco VCS X8.2 D14548.10 July 2014 Contents Introduction 3 PKI introduction 3 Overview of certificate use on the VCS 3 Certificate generation
Cisco TelePresence Video Communication Server
Data Sheet Cisco TelePresence Video Communication Server Product Overview The Cisco TelePresence Video Communication Server (Cisco VCS) is deployed in three versions: Control, Expressway, and Starter Pack
SIP Trunking with Microsoft Office Communication Server 2007 R2
SIP Trunking with Microsoft Office Communication Server 2007 R2 A Dell Technical White Paper By Farrukh Noman Dell Product Group - Enterprise THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY
Session Initiation Protocol Gateway Call Flows and Compliance Information
Session Initiation Protocol Gateway Call Flows and Compliance Information Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000
StarLeaf Connectivity Services. Deployment Guide
StarLeaf Connectivity Services Deployment Guide 31 July 2015 Contents Terminology 4 Why are Connectivity Services needed? 4 What are Connectivity Services? 4 Calling scenarios 5 Architecture 7 Security
Cisco TelePresence Management Suite Redundancy
Cisco TelePresence Management Suite Redundancy Deployment Guide Version 13.2 D14570.04 September 2012 Contents Introduction 4 Supported configurations 4 Licensing 4 Database redundancy 4 Cisco TMS Provisioning
A host-based firewall can be used in addition to a network-based firewall to provide multiple layers of protection.
A firewall is a software- or hardware-based network security system that allows or denies network traffic according to a set of rules. Firewalls can be categorized by their location on the network: A network-based
650-294 Q&A. DEMO Version
TelePresence Video Field Engineer for Express Exam Q&A DEMO Version Copyright (c) 2012 Chinatag LLC. All rights reserved. Important Note Please Read Carefully For demonstration purpose only, this free
Cisco TelePresence Video Communication Server Expressway
Data Sheet Cisco TelePresence Video Communication Server Expressway Extending Video Communications Securely Beyond the Enterprise Product Overview The Cisco TelePresence Video Communication Server Expressway
nexvortex Setup Guide
nexvortex Setup Guide CUDATEL COMMUNICATION SERVER September 2012 510 S P R I N G S T R E E T H E R N D O N V A 2 0 1 7 0 + 1 8 5 5. 6 3 9. 8 8 8 8 Introduction This document is intended only for nexvortex
Avaya Port Matrix: Avaya one-x Communicator Release 6
Avaya Port Matrix: Avaya one-x Communicator Release 6 Issue 1 July 2010 ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC. DISCLAIMS ALL WARRANTIES,
Implementing Intercluster Lookup Service
Appendix 11 Implementing Intercluster Lookup Service Overview When using the Session Initiation Protocol (SIP), it is possible to use the Uniform Resource Identifier (URI) format for addressing an end
Personal Telepresence. Place the VidyoPortal/VidyoRouter on a public Static IP address
NAT Introduction: Vidyo Conferencing in Firewall and NAT Deployments Vidyo Technical Note Section 1 The VidyoConferencing platform utilizes reflexive addressing to assist in setup of Vidyo calls. Reflexive
Cisco Registered Envelope Recipient Guide
September 8, 2008 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number:
Accessibility Guidelines for Cisco Unified Contact Center Management Portal
Accessibility Guidelines for Cisco Unified Contact Center Management Portal Release 8.0(1) February 2010 Corporate Headquarters Cisco System s, Inc. 170 West Tasman D riv e San Jose, CA 95134-1706 USA
Cullen Jennings [email protected]. July 2015
Cullen Jennings [email protected] July 2015 v9 1 A B 1. Outbound STUN request to well known STUN port (3478) Firewall creates 3-tuple pinhole for incoming and outgoing STUN message with matching username
Quick Setup Guide. Integration of Aastra MX-ONE / Aastra 700 and Microsoft Lync Server 2010
Quick Setup Guide Integration of Aastra MX-ONE / Aastra 700 and Microsoft Lync Server 2010 Aastra MX-ONE TM and Aastra 700 running Telephony Server software V.4.1 SP3 and later Aastra Telecom Sweden AB
Comparing Session Border Controllers to Firewalls with SIP Application Layer Gateways in Enterprise Voice over IP and Unified Communications Scenarios
An Oracle White Paper June 2013 Comparing Session Border Controllers to Firewalls with SIP Application Layer Gateways in Enterprise Voice over IP and Unified Communications Scenarios Introduction Voice
OfficeMaster Gate (Virtual) Enterprise Session Border Controller for Microsoft Lync Server. Quick Start Guide
OfficeMaster Gate (Virtual) Enterprise Session Border Controller for Microsoft Lync Server Quick Start Guide October 2013 Copyright and Legal Notice. All rights reserved. No part of this document may be
Application Notes for Avaya IP Office 7.0 Integration with Skype Connect R2.0 Issue 1.0
Avaya Solution & Interoperability Test Lab Application Notes for Avaya IP Office 7.0 Integration with Skype Connect R2.0 Issue 1.0 Abstract These Application Notes describe the steps to configure an Avaya
Cisco Expressway CE500 Appliance
Cisco Expressway CE500 Appliance Installation Guide First Published: April 2014 Last Updated: November 2015 X8.2 or later Cisco Systems, Inc. www.cisco.com Introduction About This Document This document
Cisco EXAM - 300-075. Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) Buy Full Product. http://www.examskey.com/300-075.
Cisco EXAM - 300-075 Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) Buy Full Product http://www.examskey.com/300-075.html Examskey Cisco 300-075 exam demo product is here for you to test the
Port Utilization Guide for Cisco Unified Contact Center Express, Release 8.5(1)
Utilization Guide for Cisco Unified Contact Center Express, Release 8.5(1) For Cisco Unified Contact Center Express and Cisco Unified IP IVR Release 8.5(1) Americas Headquarters: Cisco Systems, Inc., 170
