Cisco Expressway IP Port Usage Configuration Guide
Preface
Change History
Table 1 Cisco Expressway IP Port Usage Configuration Guide Change History
DateChangeReason
July
CorrectionOutbound SIPsignaling removed from MRAdiagram and table.
2017
April
2017
New
document
Related Documents
For Installation, See:
■ Cisco Expressway Virtual Machine Installation Guide on the Expressway installation guides page.
■ Cisco Expressway CE1100 Appliance Installation Guide on the Expressway installation guides page.
For Administration and Maintenance:
■ See Expressway Administrator Guide
■ See the Cisco Expressway Serviceability Guide on the Expressway Maintain and Operate Guides page.
■ See Cisco Expressway External Policy Deployment Guide at the Cisco Expressway Series Configuration
Guides page.
For Clustering and Certificates (All Deployments):
■ See Cisco Expressway Certificate Creation and Use Deployment Guide on the Expressway configuration
guides page.
■ See the Cisco Expressway Cluster Creation and Maintenance Deployment Guide, for your version, on the
Cisco Expressway Series configuration guides page.
New format for information previously held in Expressway IP Port Usage for FirewallTraversal.
For Basic Call Control Deployment:
See Cisco Expressway Registrar Deployment Guide on the Expressway configuration guides page.
For Mobile and Remote Access to Cisco Unified Communications Manager Services:
See Mobile and Remote Access Through Cisco Expressway on the Expressway configuration guides page.
For Remote Configuration of MRA:
See Cisco Expressway RESTAPIReference Guide on the Expressway installation guides page.
For Microsoft Interoperability:
■ See Cisco Expressway with Microsoft Infrastructure Deployment Guide on the Expressway configuration
guides page.
■ See Cisco Jabber and Microsoft Skype for Business Infrastructure Configuration Cheatsheet on the
Expressway configuration guides page.
For Cisco Meeting Server:
■ See the Cisco Meeting Server installation guides page.
■ See deployment guides on the Cisco Meeting Server configuration guides page.
2
Page 3
Cisco Expressway IP Port Usage Configuration Guide
■ See the Cisco Expressway with Cisco Meeting Server Deployment Guide on the Expressway configuration
guides page.
Contents
Preface2
Change History2
Related Documents2
How to Use This Document5
Default Port Ranges5
Basic Networking Connections7
Basic Networking:Expressway7
Networking Port Reference:Expressway7
Basic Networking:Traversal Pair9
Networking Port Reference:Expressway Traversal Pair10
Clustering Connections12
Cluster Connections Before X8.812
Cluster Port Reference Before X8.812
Cluster Connections X8.8 Onwards13
Cluster Port Reference X8.8 Onwards13
Provisioning, Registrations, Authentication, and Calls14
SIP Calls15
SIP Calls Port Reference16
H.323 Calls18
H.323 Calls Port Reference20
TMS Connections22
TMS Port Reference22
LDAP Connections24
LDAP Port Reference24
Mobile and Remote Access26
MRA Connections26
MRA Port Reference27
Jabber Guest Services29
Jabber Guest:Dual NICDeployment30
Jabber Guest:Dual NICDeployment Ports31
3
Page 4
Cisco Expressway IP Port Usage Configuration Guide
Jabber Guest:Single NICDeployment32
Jabber Guest:Single NICDeployment Ports33
Microsoft Interoperability Using Gateway Expressway34
On-Premises Microsoft Clients34
Off-Premises Microsoft Clients35
Expressway with Microsoft Infrastructure Port Reference36
Cisco Meeting Server38
Web Proxy for Cisco Meeting Server WebRTC Connections38
Web Proxy for Cisco Meeting Server Port Reference39
SIP Edge for Meeting Server Connections40
SIP Edge for Cisco Meeting Server Port Reference41
XMPP Federation43
XMPP Federation Connections43
XMPP Port Reference44
Serviceability45
Serviceability:Expressway-C45
Serviceability:Traversal Pair46
Serviceability Ports:Traversal Pair46
Cisco Legal Information47
Cisco Trademark47
4
Page 5
Cisco Expressway IP Port Usage Configuration Guide
How to Use This Document
The purpose of this document is to help you configure and troubleshoot connections between infrastructure
components related to Expressway deployments.
There is a section for each of the popular Expressway deployments. Each has a diagram showing the major
infrastructure components and the connections between them, and also lists the connections in a table format.
The deployments build on each other where necessary. For example, if you wish to implement Mobile and Remote
Access, you should first configure a traversal pair. These relationships are described in the relevant deployment
guides.
Default Port Ranges
The following defaults are used throughout this document. Default port ranges may occasionally change (if
unavoidable) as new features are developed. Our documents list the current default ports for the given version
number.
Note:In some cases throughout this document we list port ranges used by third party infrastructure. These are default
values and we cannot guarantee that these are correct for your environment. We recommend you follow the
supplier's documentation to configure those connections.
3478On Expressway-E only. Configurable to a port >= 1024
3478-3483On Large Expressway-E only. Configurable to a six port range with
Details
first port >=1024.
UDPTURN relays24000-
On Expressway-E only.
29999
5
Page 6
Cisco Expressway IP Port Usage Configuration Guide
Table 2 Default Port Ranges on Expressway (continued)
ProtocolPurposeCurrent
Range
UDPRTP/RTCPmedia 36000-
59999
UDPMultiplexed
media on
Small/Medium
2776/2777
OR
36000/36001
Expressway-E
systems
UDPMultiplexed
media on Large
36000-
36011
Expressway-E
systems
Details
The range is configurable.
On S/MExpressway, the first two ports can be used for multiplexed
media if you do not use default/custom ports.
On LExpressway, the first twelve ports of the range are used for
multiplexed media. You cannot customize that subrange.
2776/2777 is older pair but kept as default by the ability to
customize when the new default range was introduced with
S/Msystem options. Custom pair is defined on Configuration>Traversal >Ports.
On Expressway-E only.
Note:In the connection maps and port references we do not show
all the port options for the sake of clarity. For example, if the
diagram shows 2776/2776, but you have chosen to use
36000/36001 instead, then you don't need to also open 2776/2777.
New range introduced with Largesystem option. This range is
always the first twelve ports of the RTP/RTCPmedia range, so it
will be different if you configure a different media range.
On Expressway-E Large OVAs or large scale appliances only.
Note:In the connection maps and port references we do not show
all the port options for the sake of clarity. For example, if the
diagram shows 2776/2776, but you have a large Expressway, then
you should open the first twelve ports of the media range instead of
2776/2777.
TCPSIPtraversal7001Configurable. SIPlistening port on the first Expressway-E traversal
server zone. Subsequent traversal server zones will use incremental
port numbers, eg. 7002, by default.
UDPH.323 traversal6001Configurable. H.323 listening port on the first Expressway-E
traversal server zone. Subsequent traversal server zones will use
incremental port numbers, eg. 6002, by default.
6
Page 7
Cisco Expressway IP Port Usage Configuration Guide
Could be translated by
the firewall to port where
the media egressed,
rather than an endpoint
port
UDPExpressway-E36000-59999
Assent RTP
(traversed
media)
Expressway-E36000-59999UDPSIPendpoint
(or its
firewall)
>=1024
Expressway waits until it
receives media, then sends
media to that source port
(which could be the port where
the media egressed the firewall,
not an endpoint port)
TURNcontrol Any
IPaddress
TURNmedia
Expressway-E24000-29999UDP
TURNmediaAny
IPaddress
>=1024 (signaling port
†
from endpoint or the
firewall)
>=1024
‡
Port of relevant
UDP
&TCP
&TCP
UDP
&TCP
ExpresswayE
Any
IPaddress
Expressway-E24000-29999
3478 (Small/Medium)
3478-3483 (Large)
>=1024
ICEcandidate:host
IPport, server reflexive
port (outside firewall
port), or TURNserver
port
† The request could be from any IPaddress, unknown to the TURNserver. Assume for example, that endpoint A and
endpoint C (TURNclients) in the diagram can use the Expressway-E TURNserver. The actual IPaddress from which
the TURNserver receives the request could be the endpoint's firewall egress address (NATed).
‡ The media could go to any of the candidate addresses. For example, before ICEnegotiation the TURNserver does
not know which of endpoint B's candidate addresses will be the highest priority.
Note:The endpoints A, B, and C in the diagram only show media connections to avoid unnecessary lines. They would
use the same signaling connections as shown for the other endpoints / bridges.
17
Page 18
Cisco Expressway IP Port Usage Configuration Guide
H.323 Calls
Note:This diagram and following table apply specifically to Cisco VCSdeployments. You can use this information to
prepare an Expressway-based H.323 deployment, but remember that Expressway-Edoes not accept H.323
registrations.
18
Page 19
Cisco Expressway IP Port Usage Configuration Guide
19
Page 20
Cisco Expressway IP Port Usage Configuration Guide
Cisco Expressway IP Port Usage Configuration Guide
TMS Connections
TMS Port Reference
Cisco TMS can have two IPaddresses; for managing public systems, or managing systems on the LAN. On Cisco
TMS, go to Administrative Tools > Configuration > Network Settings >Advanced Network Settings. You should use
the TMSpublic address with the Expressway-E, and the default LANaddress with the Expressway-C.
22
Page 23
Cisco Expressway IP Port Usage Configuration Guide
Table 11 TMSPort Reference
PurposeSrc. IPSrc. portsProtocol Dest. IPDst.
Ports
SNMPfor discovery of
Expressway-E
SNMPfor discovery of
Expressway-C
HTTPManagement of
Expressway-E
HTTPManagement of
Expressway-C
HTTPSManagement of
Expressway-E
HTTPSManagement of
Expressway-C
Feedback events (HTTP)Expressway-E
Cisco TMS ExternalIP1024-
65535
Cisco TMS1024-
65535
Cisco TMS ExternalIP1024-
65535
Cisco TMS1024-
65535
Cisco TMS ExternalIP1024-
65535
Cisco TMS1024-
65535
1024-
private
65535
Feedback events (HTTP)Expressway-C1024-
65535
Feedback events (HTTPS)Expressway-E
private
102465535
Feedback events (HTTPS)Expressway-C1024-
65535
UDPExpressway-E private 161
UDPExpressway-C161
TCPExpressway-E privateIP80
TCPExpressway-E privateIP80
TCPExpressway-E private 443
TCPExpressway-C443
TCPCisco TMS ExternalIP80
TCPCisco TMS80
TCPCisco TMS ExternalIP443
TCPCisco TMS443
23
Page 24
Cisco Expressway IP Port Usage Configuration Guide
LDAP Connections
LDAP Port Reference
You can choose to use an LDAPserver to authenticate and authorize administrator or user logins. You would only
need to allow the LDAPports inbound from the Expressway-E in the rare case where you want a user to log in from
outside the network and you also do not allow credentials to be stored on the Expressway.
24
Page 25
Cisco Expressway IP Port Usage Configuration Guide
Table 12 LDAPPort Reference
PurposeSrc. IPSrc. ports Protocol Dest. IPDst.
Ports
Authentication requests from the Expressway-C Expressway-C1024-
65535
Authentication requests from the Expressway-EExpressway-E
private
Encrypted authentication requests from the
Expressway-C1024-
Expressway-C
Encrypted authentication requests from the
Expressway-E
Expressway-E
private
102465535
65535
102465535
TCPDirectory
Server
TCPDirectory
Server
TLSDirectory
Server
TLSDirectory
Server
389
389
636
636
25
Page 26
Cisco Expressway IP Port Usage Configuration Guide
Mobile and Remote Access
MRA Connections
26
Page 27
Cisco Expressway IP Port Usage Configuration Guide
MRA Port Reference
Table 13 Connections Between Off-premises Endpoints and the Expressway-E
*On Large systems you can configure a range of TURN request listening ports. The default range is 3478 – 3483.
‡ Port translation in external firewall
† Inbound media ports only required for unidirectional media initiated from Jabber Guest client, eg. BFCP. Otherwise
it is enough to allow the outbound media range from Expressway-C to Expressway-E (previous row).
EphTCPExpressway-C5060
Server
EphTLSExpressway-C5061
Server
33
Page 34
Microsoft Interoperability Using Gateway Expressway
On-Premises Microsoft Clients
Cisco Expressway IP Port Usage Configuration Guide
34
Page 35
Off-Premises Microsoft Clients
Cisco Expressway IP Port Usage Configuration Guide
35
Page 36
Cisco Expressway IP Port Usage Configuration Guide
Expressway with Microsoft Infrastructure Port Reference
Notes about the deployment connections and ports
■ Trunk connections between Microsoft infrastructure elements not shown.
■ Media/signaling connections required for Microsoft client to client calls not shown.
■ Microsoft port ranges may vary from those shown here; check the Microsoft documentation to determine the
port ranges defined for your infrastructure.
■ Cisco Unified Communications Manager and collaboration endpoint connections not shown (for clarity). You
can see an example of those on MRA Connections, page 26.
■ Multiple media paths are possible because there are two TURNservers in the DMZ. "Any" source IPaddress is
listed because ICEnegotiation could mean the media path uses a relay address provided by one of the
TURNservers, or a reflexive address from the egress side of a firewall/NAT.
■ The Microsoft Interoperability service on the gateway Expressway has a shared pool of media ports (default
56000-57000). The service can use any port in the range for media connection on either TCPor
UDPtransport.
■ The drawing shows two IPaddresses on the Expressway-E because you may have one or two NICs enabled
on the Expressway-E. The address you enter for the TURNserver (on the Microsoft interoperability
configuration of the gateway Expressway) is the one that should listen on 3478 (TCPand UDP).
Table 18 SIPSignaling Port Reference
PurposeSrc. IPSrc. portsProtocol Dest. IPDst.
SIPsignaling to Lync
environment
SIPsignaling from Lync
environment
SIP signalingMicrosoft
Gateway
Expressway
Lync
FEServer
25000-29999TLSLync FEServer5061
Ephemeral ports
(1024-65535)
TLSGateway Expressway:
MSinterop B2BUA
5061MTLSMicrosoft Edge5061
client
SIP signalingMicrosoft
5061MTLSMicrosoft client5061
Edge
SIP/TLS & TCPTURNMicrosoft
443TLSMicrosoft Edge443
client
SIP/TLS &TCPTURNMicrosoft
443TLSMicrosoft client443
Edge
STUNMicrosoft
3478UDPMicrosoft Edge3478
client
STUNMicrosoft
3478UDPMicrosoft client3478
Edge
Ports
65072
36
Page 37
Cisco Expressway IP Port Usage Configuration Guide
Table 19 Media Path Port Reference
PurposeSrc. IPSrc.
ports
AVmedia to on-prem Lync clientsGateway
Expressway
Screen sharing from on-prem Lync
Lync client
5600057000
443
clients
Media from Microsoft interoperability
B2BUA towards on-premises Cisco
Gateway
Expressway
5600057000
collaboration recipients
ICEnegotiation and TURNrequests
from Gateway Expressway to
Gateway
Expressway
5600057000
Expressway-E TURNserver
UDPTURNmedia relaysExpressway-
E
2400029999
TURNserver
TCPTURNmedia relaysExpressway-
E
2400029999
TURNserver
Protocol Dest. IPDst. Ports
UDPLync clientsLync client
media ports
TCPGateway
56000-57000
Expressway
UDPDeployment
dependent; bridge,
Endpoint media
ports
endpoint, or a
SIPproxy
UDP or
TCP
Expressway-E
TURNserver
UDP3478
TCP3478
(3478-3483 on
large systems)
UDPAny (reflexive or
relay) from
MSclient or Edge
50000-59999
(Edge range) or
client media
ports
TCPAny (reflexive or
relay) from
MSclient or Edge
50000-59999
(Edge range) or
client media
ports
VCS Only
Presence to Lync FEServer
VCS Only
B2BUAcommunication with an
external transcoder (eg. Cisco AMGW)
Gateway
Expressway
Gateway
Expressway
10011TLSLync FEServer5061
65080TLSExternal transcoder5061
37
Page 38
Cisco Expressway IP Port Usage Configuration Guide
Cisco Meeting Server
Web Proxy for Cisco Meeting Server WebRTC Connections
38
Page 39
Cisco Expressway IP Port Usage Configuration Guide
Web Proxy for Cisco Meeting Server Port Reference
Table 20 Web Proxy for Meeting Server
PurposeSrc. IPSrc.
ports
WebRTC client
access
Web interface
access
SSHtunnels for
firewall traversal
SIPsignalingExpressway-C25000-
TURNclient
requests
TURNclient
requests
TURNrelays
† You must change the administration port because WebRTCclients use 443. If the WebRTCbrowser tries to access
port 80, the Expressway-E redirects the connection to 443.
*Options for alternative management ports are shown on the web interface. You can use the CLIto change it to a
different port, eg. 7443, so that you can lock it down. We strongly advise against opening an external management
port on the public IPaddress. If the browser tries to access port 80, the Expressway-E redirects the connection to
your chosen port.
‡
Guest PCs1024-
65535
Administrator
PCs
Expressway-C30000-
Any IPUDP and
Meeting
Server
Expressway-E
public IP
102465535
35999
29999
3478UDP and
2400029999
ProtocolDest. IPDst. Ports
TLSExpressway-E publicIP443
TLSExpressway-E IPNOT443
TCPExpressway-E privateIP2222
TCP or
TLS
TCP
TCP
UDPand
TCP
Expressway-E7001 (for first traversal zone;
Expressway-E
TURNserver public IP
Expressway-E
TURNserver private IP
Expressway-E publicIP24000-29999
†
7002 for second etc.)
3478
3478
*
‡ You must configure your external firewall to allow NATreflection for the Expressway-Epublic IPaddress. (Firewalls
typically mistrust packets that have the same source and destination IPaddress)
39
Page 40
Cisco Expressway IP Port Usage Configuration Guide
SIP Edge for Meeting Server Connections
40
Page 41
Cisco Expressway IP Port Usage Configuration Guide
SIP Edge for Cisco Meeting Server Port Reference
Table 21 SIPEdge for Meeting Server Port Reference
Could be the firewall
port where the media
egressed, rather than
an endpoint port
>=1024
Could be the firewall
port where the media
egressed, rather than
an endpoint port
UDPExpressway-E36000-59999
UDPExpressway-E36000-59999
(or its
firewall)
41
>=1024
Expressway waits until it
receives media, then
sends media to that
source port (which could
be the port where the
media egressed the
firewall, not an endpoint
port)
Page 42
Cisco Expressway IP Port Usage Configuration Guide
Table 21 SIPEdge for Meeting Server Port Reference (continued)
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.
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.
Any Internet 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 IP addresses or phone
numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version
should be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco
website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other
countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. 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. (1110R)
Cisco Systems, Inc.www.cisco.com
47
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.