Technical Note
Aastra 5000 Solution
List of the TCP and UDP ports used in “Aastra 5000 Solution”
The purpose of this note is to list all TCP and UDP ports used by every component of the A5000 solution
(R5.2 release).
This document is published for information only.
This technical note is referenced in Aastra internal documentation AMT/PSD/SYS/0001/03/02/EN.
These port numbers are listed for the whole Aastra products including Aastra 5000 Server, PBX (and
Gateways), IP terminals, Management Center and PC applications
(NT 092, NT_092, NT_092ed5, NT_092ed5_En)
NT_092ed5_En
05/07/2010
Summary
1
IP TERMINALS .......................................................................................................................................... 5
1.1
i2052 softphone 5
1.2
i2070 attendant console 5
1.3
H323 V4 Terminal 5
1.4
i7xx and cartouche IP 6
1.5
Aastra 675xi Terminals 6
1.6
Aastra 53xxip Terminals 7
1.7
DHCP 7
1.8
DECT over IP solution (OMM & RFP) 7
1.9
DRG22i terminal adapter 8
2
PBX and Gateways (AX Series & M65xx & NeXspan) ................................................................................ 9
2.1
DATA Tunnel 9
2.2
« CRI » ports 9
2.3
TCP‐IP/DATA Gateway 9
2.4
DATA/TCP‐IP GATEWAY 11
2.5
SNMP Agent 12
2.6
PBX AXD (Duplicated) 12
2.7
SIP Protocol 12
2.8
LDAP Directory 12
2.9
AM7450 Management 12
2.10 NTP server 13
2.11 GDB application 13
2.12 RTP/RTCP for Voice Over IP Gateway 13
NT_092ed5_En
Page 2 /24
05/07/2010
3
CALL MANAGER ..................................................................................................................................... 14
3.1
DATA Tunnel 14
3.2
« CRI » Ports 14
3.3
TCP‐IP/DATA Gateway 14
3.4
DATA/TCP‐IP Gateway 14
3.5
SNMP Agent 14
3.6
Duplicated Linux Call Server 14
3.7
SIP Protocol 15
3.8
LDAP Directory 15
3.9
AM7450 Management 15
3.10 NTP server 15
3.11 GDB application 15
4
NETWORK MANAGEMENT ..................................................................................................................... 16
4.1
M7430 – NeXspan Network Manager 16
4.2
AM7450 – NeXspan Network Manager 16
5
TAPI IP‐IP GATEWAY .............................................................................................................................. 18
6
H.323/MOVACS GATEWAY .................................................................................................................... 18
7
Proxy NAT SBC....................................................................................................................................... 18
8
Proxy TLS TCP UDP................................................................................................................................. 19
9
ACP (Aastra Communication Portal)....................................................................................................... 19
10 TWP (Telephony Web Portal)................................................................................................................. 20
11 UCP (Unified Communication Platform) ................................................................................................. 21
12 M7900 ‐ DECT ALARM SERVER ............................................................................................................... 22
13 SYSLOG.................................................................................................................................................. 22
14 As a reminder ........................................................................................................................................ 23
14.1 Terminal Proxy Server (TPS) NT_092ed5_En
23
Page 3 /24
05/07/2010
14.2 i2004 set 23
14.3 SIP Terminals (i220, 480i, 9112i & 9133i) 24
14.4 REDUNDANCY (DOUBLE TAKE) 24
14.5 M7425 (& OMSE & M7415) 24
NT_092ed5_En
Page 4 /24
05/07/2010
1 IP TERMINALS
1.1
i2052 softphone
•
Signalling for Telephony Services (VTI/XML protocol)
• Sends to TCP port 3199 of the PBX/Call Manager
• Receives on TCP port number selected by the PC Windows system.
•
Voice flow (RTP/RTCP protocols)
• Sends to UDP port numbers specified of the PBX/Call Manager
• Receives on UDP ports 40000 and 40001
(set default values at the terminal and PBX configuration level).
Note: Before R2.1 PBX release, the UDP port numbers for RTP/RTCP were configured with 2005 and
2006 default values (values may be changed using terminal configuration)
1.2
i2070 attendant console
Signalling for Telephony Services (VTI/XML protocol)
• Sends to TCP port 3209 (through “SERV-POWIN”) of the PBX/Call Manager
• Receives on TCP port number selected by the PC Windows system.
•
1.3
Voice flow through digital sets
H323 V4 Terminal
•
Signalling for Telephony Services (H225 protocol)
• Sends to TCP port 1720 of the PHM.
• Receives on TCP port 1720.
•
Signalling for H245 protocol set dynamically.
•
Voice flow (RTP/RTCP protocols)
• Sends to UDP port numbers specified of the PBX/Call Manager
• Receives on UDP ports 1024 to 65535
NT_092ed5_En
Page 5 /24
05/07/2010
1.4
i7xx and cartouche IP
•
Signalling for Telephony Services (“I” proprietary protocol encapsulated using TCP-IP frames):
• Sends to TCP port 3199 of the PBX/Call Manager
• Receives on TCP port number selected by the system.
•
Voice flow (RTP/RTCP protocols)
• Sends to UDP port numbers specified of the PBX/Call Manager
• Receives on UDP ports 40000 and 40001, set by software, non configurable values.
(RTCP port 40001 unused for the moment).
•
The Downloading feature used ofr upgrading terminal software
• Listens TCP port 9410.
1.5
Aastra 675xi Terminals
•
Signaling for Telephony (SIP protocol):
• sends to UDP port 5060 (configurable) of the SIP access
• receives on UDP port number selected by the terminal (value is configurable; by default this
value is set to 5060).
•
Voice flow (RTP/RTCP protocols):
• sends to UDP port numbers specified by the PBX/Call Manager ;
• receives on UDP ports 40000/40001 (first call) and 40002/40003 (in case of a second call);
default values that may be changed by configuration (RTCP port number unused for the
moment).
•
The Downloading feature used for upgrading terminal software
• Sends and receives on TCP port 21 used by FTP server (or UDP port 69 used by TFTP
server)
•
Configuration via proxy XML
• Connects to Apache server (PBX or Call Manager) via the proprietary TCP port 4443 (https
protocol).
•
NTP server
• Connects to NTP server (PBX or Call Manager in that case) via the UDP port 123.
NT_092ed5_En
Page 6 /24
05/07/2010
1.6
Aastra 53xxip Terminals
•
Signaling for Telephony (SIP protocol):
• sends to UDP port 18060 (configurable) of the SIP access;
• receives on UDP port number selected by the terminal (value is configurable; by default this
value is set to 18060).
•
Voice flow (RTP/RTCP protocols):
• sends to UDP port numbers specified by the PBX/Call Manager ;
• receives on UDP ports 30000 and 30001; default values that may be changed by
configuration (RTCP port number unused for the moment).
•
The Downloading feature used for upgrading terminal software
• Sends and receives on TCP port 21 (configurable) used by FTP server.
1.7
DHCP
•
An IP terminal configured to get its parameters from a DHCP server uses the following ports:
• sends to UDP port 68 of the DHCP server;
• receives responses from the DHCP server on UDP port 67.
1.8
DECT over IP solution (OMM & RFP)
•
Signaling for Telephony (proprietary SIP protocol):
• sends to UDP port 5060 (configurable) of the SIP access;
• receives on UDP port number selected by the OMM (value is configurable; by default this
value is set to 5060).
•
Voice flow (RTP/RTCP protocols) at RFP level:
• sends to UDP port numbers specified by the PBX/Call Manager ;
• receives on UDP ports 16320 to 16391; default values that may be changed by configuration
(RTCP port number unused for the moment).
•
DECT over IP application uses also the following ports: Telnet (23), DHCP (67 and 68), TFTP (69),
http (80), SNMP (161 and 162), OMM resiliency (TCP port 16322) and specific ports 8106 and
8107 for DECT Monitor among others.
NT_092ed5_En
Page 7 /24
05/07/2010
1.9
DRG22i terminal adapter
•
Signaling for Telephony (SIP protocol):
• sends to UDP port 5060 (configurable) of the SIP access;
• receives on UDP port number 5060 and 5062, values set by initialization file (may be
changed by configuration).
•
Voice flow (RTP/RTCP protocols):
• sends to UDP port numbers specified by the PBX/Call Manager ;
• receives on RTP ports 40000 and 40008; values set by initialization file (may be changed by
configuration) - (RTCP port numbers are unused for the moment).
•
DRG22i adapter uses also the following ports: TFTP (69) and/or FTP (21) for downloading feature
used for upgrading terminal software and setting initial values, http (80) for Web configuration,
SNMP (161 and 162) for supervision.
NT_092ed5_En
Page 8 /24
05/07/2010
2
PBX and Gateways (AX Series & M65xx & NeXspan)
2.1
DATA Tunnel
•
The initiator of the tunnel (tunnel “master”) sends to TCP port 1998 for TCP-IP session
establishment.
•
The reception port number, on the mother board, is chosen by the system (Linux from R5.1 on)
•
The reception port number, on the PTx board, is set among a range, whose values are configured
for each PTx card. The range default values are from 41000 to 41999.
Note: In the PBX release R1.2, the reception port number was set from 0 to 1024.
2.2
« CRI » ports
•
“ CRI ” ports are particular TCP-IP ports used to reach some PBX applications avoiding access to
internal servers, which means:
• port 3199 is used for ‘IP terminals’ Signaling (avoiding access to servers like SERV-POWIN
or SERV-IP), and replaces the 3209 port (see below) ;
• port 3198 is used for ‘H323/MOVACS Gateway’ Signaling (avoiding access to server
“SERV_H323”), and will replace the port 3208 (see below) ;
• port 3197 is used for “http signaling”
2.3
TCP-IP/DATA Gateway
•
To be compliant with MML specifications, TCP-IP port numbers used for TCP-IP/DATA gateways
must be defined with values greater than 2000 (except value 80 used for the Web MML in F5 -Call
Server- and F6 -NeXspan C/S/L/D- systems).
A list of TCP-IP port numbers used to reach all the PBX applications is proposed with default values
(refer to the table in the following pages). Using this list will provide a homogeneous numbering plan in
all the PBX networks or installations.
This list begins with the value 3200. The DATA Services which can be reached are those of the
NeXspan having an IP access card. These DATA services are either internal servers or servers
addressed through X25 access of this NeXspan.
A column is added to mention on which network the data flow is transported in case of separation
between management flow and telephony.
NT_092ed5_En
Page 9 /24
05/07/2010
Table of the TCP-IP /DATA gateway associations
TCP-IP INTERNAL SERVER or Server ACCESS
Port
Server
Address
Mode
2001 to Unassigned
3196
Tel
3197 to Not available (CRI use only)
3199
Tel
3200 to reserved
3203
Admin
3204
KITAXE Server (records)
012
Non D
3205
reserved
3206
EAS Server (for LCR et TPS)
3207
reserved
3208
H.323 Server (for H.323/MOVACS gateway)
01191
TPKT
Tel
3209
Gateway Server for Attendant Console and
Software phone on PC (TD/PC)
01190
TPKT
Tel
3210
reserved
3211
CSTA Server
Admin
013
TPKT
Admin
Tel
011600
Non D
Tel
Tel
MUFACT Server (record multiplexer with
communication records and service records, with
alarms)
01410030
TPKT
Admin
3218
EAS Server for ACD (for M7403 for instance)
013
TPKT
Admin
3219
EAS Server (for proxy XML)
013
Non D
Admin
TPKT
Tel
3220 to Internal server called by the TAPI Gateway
3283
3284 to reserved
3287
“ SAESAE ”
Tel
MUFACT Server (record multiplexer with only
service records / alarms)
014130
3289 to reserved
3290
NT_092ed5_En
“ SAESAE ”
Tel
3217
3288
Call Data
Admin
3212 to reserved
3216
Network
TPKT
Admin
Admin
Page 10 /24
05/07/2010
3291
MUFACT Server (record multiplexer with only
communication records)
014100
Admin
3292 to Reserved if more ports are needed for a server (in
3299
the case of one card “provides” several CCUs)
Tel
3300
reserved
Tel
3301
CSTA Server (similar to 3211 but in TPKT
mode)
011601
TPKT
Tel
3302
AFISER Server (echo service)
01000
TPKT
Tel &
Admin
3303
AFISER Server (echo service)
01000
Non D
Tel &
Admin
3304
MUFACT Server for billing application (record
multiplexer with only communication records
and no acknowledgement)
014000
Non D
Admin
3305 to Reserved pour future applications
3399
Tel
3400 to Reserved for services dedicated to administration
3499
network (in case of data flow separation)
Admin
3500 to Reserved for calls automate (Park management)
3599
Admin
3600 to Unassigned
7999
Tel
8000
None
Not available (EXP use only, internal port used
by Apache to access WEB MMI, loop on port
127.0.0.1)
8001 to Unassigned
65534
2.4
Tel
DATA/TCP-IP GATEWAY
•
The destination port used by the PBX to initiate TCP-IP session is defined by MML. This session is
always transported on the “telephony network”.
Note: The requirement “value higher than 2000” has been suppressed
•
The reception port number for the gateway is selected among a range which may be configured for
each PTx. The range is by default from 41000 to 41999. On the mother board this reception port
number is chosen by the system (Linux from R5.1 on).
Note: In the R1.2 PBX release (as for the DATA tunnel), the port number was selected in the
range: 0 to 1024.
NT_092ed5_En
TPKT
Page 11 /24
05/07/2010
2.5
SNMP Agent
•
2.6
The SNMP agent of the NeXspan XS/XL/XD receives requests on the UDP port 161 and sends its
responses from the same port to the UDP port of the “manager”. It sends SNMP traps on UDP port
162 of the “manager”.
PBX AXD (Duplicated)
•
The heartbeat mechanism uses the UDP port 694 (default value).
•
The DRBD replication mechanism uses the TCP port 7788 (default value).
•
These default values are configurable in the script that manages the duplication feature.
2.7
SIP Protocol
•
Signaling for Telephony (SIP protocol):
• sends to UDP port selected by the terminal (default value 5060),
• receives on UDP port number (configurable value; by default this value is set to 5060).
•
The SIP gateway module dialogues with the PBX over an internal TCP-IP session
• sends to TCP port 3199 (configurable) of the PBX,
• receives on the TCP port selected by the system.
2.8
LDAP Directory
•
The PBX dialogues with external applications or AM7450 using LDAP protocol via the TCP port
389.
•
“White Pages” service
• The “white pages” service is reached via the HTTP port (TCP) 80.
2.9
AM7450 Management
•
The PBX dialogues with the AM7450 for files transfer and configuration functions using https
protocol via the TCP port 443.
NT_092ed5_En
Page 12 /24
05/07/2010
2.10
NTP server
•
The PBX accesses to a NTP server via the UDP port 123.
•
The PBX is the NTP server for the Aastra 675xi terminals. It receives requests on the UDP port
123.
2.11
•
GDB application
Software debugging with GDB application uses the TCP port 1005.
2.12
•
RTP/RTCP for Voice Over IP Gateway
The UDP port numbers for RTP/RTCP protocols of the Voice Over IP Gateway may be configured
for each PTx. The default values are from 40000 to 40078 (depending on the selected Time Slot
number).
NT_092ed5_En
Page 13 /24
05/07/2010
3
CALL MANAGER
3.1
DATA Tunnel
•
The initiator of the tunnel (tunnel “master”) sends to TCP port 1998 to establish TCP-IP session.
•
The reception port number is defined by the system (Linux from R5.1 on).
3.2
« CRI » Ports
•
3.3
3197, 3198 and 3199: same as for PBX.
TCP-IP/DATA Gateway
•
3.4
3200 and +: idem PBX.
DATA/TCP-IP Gateway
•
The destination port used by the Call Manger to initiate TCP-IP session is configured using MML.
•
The reception port number is defined by the system.
3.5
SNMP Agent
•
UDP Ports 161 et 162: idem PBX.
3.6
Duplicated Linux Call Server
•
The heartbeat mechanism uses the UDP port 694 (default value).
•
The DRBD replication mechanism uses the TCP port 7788 (default value).
•
These default values are configurable in the script that manages the duplication feature.
NT_092ed5_En
Page 14 /24
05/07/2010
3.7
SIP Protocol
•
Signaling for Telephony (SIP protocol):
• sends to UDP port selected by the terminal (default value 5060),
• receives on UDP port number (configurable value; by default this value is set to 5060).
•
The SIP gateway module dialogues with the Call Manager over an internal TCP-IP session
• sends to TCP port 3199 (configurable) of the Call Manager,
• receives on the TCP port selected by the system.
3.8
LDAP Directory
•
The Call Manager dialogues with external applications or AM7450 using LDAP protocol via the
TCP port 389.
•
“White Pages” service
• The “white pages” service is reached via the HTTP port (TCP) 80.
3.9
AM7450 Management
•
3.10
The Call Manager dialogues with the AM7450 for files transfer and configuration functions using
https protocol via the TCP port 443.
NTP server
•
The Call Manager accesses to a NTP server via the UDP port 123.
•
The Call Manager is the NTP server for the Aastra 675xi terminals. It receives requests on the
UDP port 123.
3.11
•
GDB application
Software debugging with GDB application uses the TCP port 1005.
NT_092ed5_En
Page 15 /24
05/07/2010
4
NETWORK MANAGEMENT
4.1
M7430 – NeXspan Network Manager
•
The BUFTIC server is connecting to the management center using TCP port 9010.
•
UAD device is connecting to management center using TCP port 11009.
•
TCP port 9500 in the M7430 is used for transit flow through M7430 (AG-COMM).
•
The management center applications are connecting to the PBX using TCP-IP session on the
ports 3200 and + (above) of the TCP-IP/DATA gateway (refer to the table described previously for
more details)
4.2
AM7450 – NeXspan Network Manager
•
LDAP directory
• The AM7450 receives requests from clients (PBX & applications) on the TCP port 389 and
sends answers on the same port,
• The AM7450 sends queries to others LDAP directories on the TCP port 389,
• The replication feature between the AM7450 and the PBX/Call Manager uses proprietary
messages exchanged also on the TCP port 389.
•
SNMP supervision
• The AM7450 sends its requests to SNMP clients (PBX/Call Manager) on the UDP port 161 of
the SNMP agent (PBX/Call Manager) and receives the responses on the same port,
• The AM7450 receives traps from the SNMP clients (PBX/Call Manager) on the UDP port 162.
An internal port 33333 is used to redirect these traps towards the management portal of the
AM7450.
•
Nagios
• The AM7450 accesses the Nagios application using http on the TCP port 90.
•
Files transfer
• The AM7450 performs files transfer to and from PBX/Call Manager via the HTTPS port (TCP)
443.
•
Terminal Management
• The AM7450 delivers files on a TFTP or FTP server. These files will be downloaded by
terminals (675xi and 53xxip ranges) via the TFTP port (UDP) 69 or FTP port (TCP) 21.
NT_092ed5_En
Page 16 /24
05/07/2010
•
AM7450 clients
• The AM7450 clients reach the Web services (apache server) via the HTTPS port (TCP) 443.
This server gives access to the AM7450 services via a TCP connection on port 20911.
• The AM7450 clients reach also the VT100 and Web MMI services (intermediary towards PBX
ports 3201 to 3220) via the TCP ports 8201 to 8220.
• The AM7450 clients listen on TCP port 40000 following their subscription’s submission to
notification service performs using http or https.
• The AM7450 reaches the AM7450 clients via TCP port 44555.
•
PBX/Call Manager configuration
• The XML protocol used for configuration is carried using HTTPS on TCP port 443.
•
M7430 link
• The ports from 5800 to 5809 are used to launch VNC clients on the M7430 from the AM7450
client. These are ports on the M7430 application.
•
NTP server
• The AM7450 accesses to a NTP server via the UDP port 123.
•
SMTP server
• The AM7450 accesses to a SMTP server via the TCP port 25.
•
UCP configuration
• The AM7450 accesses to the UCP via the TCP port 13888.
NT_092ed5_En
Page 17 /24
05/07/2010
5
TAPI IP-IP GATEWAY
•
Applications (and some terminals) access to the gateway using a TCP-IP session established on
the gateway TCP-IP port 5001.
•
TAPI gateway establishes one or more TCP-IP sessions with the PBX using port numbers from
3220 to 3283 (mentioned in the TCP-IP/DATA table described previously)
6
H.323/MOVACS GATEWAY
•
Signaling for Telephony Services (H.225 protocol) :
• sends calls towards terminals on TCP 1720 ;
• receives on TCP 1720.
•
Signaling for H.245 protocol : set dynamically (values are defined in Radvision stack configuration
file).
•
Signaling for Telephony Services (MOVACS protocol over IP) :
• sends to TCP port 3208 of the PBX/Call Manager ;
• receives on TCP port number selected by the Windows system.
7
Proxy NAT SBC
•
Signaling for Telephony Services (SIP protocol) :
• sends to UDP port (value is configurable; by default this value is set to 5060) ;
• receives on 1 or 2 UDP ports (values are configurable; by default these values are set to
5060 & 5064).
•
Relay for RTP flow
• On one side, sends and receives on RTP ports configured in the SER proxy /SBC (port range
set by default from 40000 to 41000),
• On the other side, sends and receives on the RTP ports of the equipments (terminals or
trunks) negotiated by the system (PBX/Call Manager/SER proxy/SBC).
NT_092ed5_En
Page 18 /24
05/07/2010
8
Proxy TLS TCP UDP
•
Signaling for Telephony Services (SIP protocol) :
• on terminal side : sends and receives on port 5061 (TLS), 5062 (TCP) or 5063 (UDP) –
theses values are configurable.
• on GSI side : sends and receives on UDP ports 5161 (associated to 5061), 5162 (associated
to 5062) and 5163 (associated to 5063) – theses values are configurable.
Note: the UDP port 5060 of the GSI is still valid for direct dialog with terminals. 9
ACP (Aastra Communication Portal)
•
The port numbers used between the M7480 server and its client applications (users, API user,
Service Manager, Administrator, Wall Display) must be defined by configuration and the definition
range must be configured too (refer to the document dealing with ACP configuration in a firewall
environment).
•
TCP/UDP port 80 is used for HTTP communication between the server and its clients (every client
using Web services)
•
TCP port 135 is used for communications of DCOM type
•
TCP ports 139 & 445 are used for file sharing.
•
Dialog with LDAP directory using TCP port 389.
•
Dialog with CSTA server of the PBX/Call Manager is using TCP port 3211.
•
Signaling for Telephony Services (VTI/XML protocol):
• sends to TCP port 3199 of the PBX/Call Manager ;
• receives on TCP port number selected by the ACP’s operating system
•
Voice flow (RTP/RTCP protocols):
• sends to UDP port number specified by the PBX/Call Manager ;
• receives on UDP ports numbered from 40000 to 40127 (depending on the selected Time Slot
number -from 0 to 63).
NT_092ed5_En
Page 19 /24
05/07/2010
10 TWP (Telephony Web Portal)
•
Dialog with CSTA server of the PBX/Call Manager is using TCP port 3211.
•
Signaling for Telephony Services (VTI/XML protocol):
• sends to TCP port 3199 of the PBX/Call Manager ;
• receives on TCP port number selected by the TWP’s operating system.
•
Voice flow for TWS Media Server (RTP/RTCP protocols):
• sends to UDP ports number specified by the PBX/Call Manager ;
• receives on UDP ports from 2700 to 27xx depending on the number of accesses used by the
TWS (default values that may be changed by configuration at TWP level).
•
Dialog between TWP and user’s station:
• TWP receives requests on TCP ports 80 (http), 9000, 2500 and 2501,
• TWP uses Netbios ports 137 and 138 for desktop mode
• User’s station receives supervision information on UDP ports 33000 to 33006 ;
•
Dialog between TWP and other servers:
• TWP dialogues with SMS server via the port SMPP 2775, with LDAP server via the port 443
(https) and with Exchange server via the port 80 (http) or 443 (https).
•
From and to user’s stations:
• TWS phone VoIP (softphone) receives on UDP port 8500 (modifiable value)
• TWS Visio receives on UDP ports 19798 & 19799 (modifiable values)
NT_092ed5_En
Page 20 /24
05/07/2010
11 UCP (Unified Communication Platform)
•
UCP receives connection on the following ports for various protocols.
• on TCP port 21 used by FTP server (Fax downloading)
• on TCP port 80 used by http and port 443 used by https (Web client)
• on TCP port 110 used by POP3
•
UCP opens connection on the following ports for various protocols
• on TCP port 135 used by RPC for file replication system (backup)
• on TCP port 389 used by LDAP
• on TCP port 943 used by IMAP over SSL
•
UCP opens and receives connection on the following ports for various protocols.
• on TCP port 25 used by VPIM & SMTP
• on TCP port 143 used by IMAP
•
Dialog with CSTA server of the PBX/Call Manager is using TCP port 3211.
•
Signaling for Telephony Services (VTI/XML protocol):
• sends to TCP port 3199 of the PBX/Call Manager ;
• receives on TCP port number selected by the PC Windows system
•
Voice flow (RTP/RTCP protocols):
• sends to UDP ports number specified by the PBX/Call Manager ;
• receives on UDP ports from 40000 to 40127 (depending on the selected Time Slot number from 0 to 63).
•
UCP receives connection on the following ports for various applications.
• on TCP port 8201 used by UC Nuance Loader
• on TCP port 11000 used by UM monitor
• on TCP port 13777 used by UC client manager
• on TCP port 13888 used by AM7450
NT_092ed5_En
Page 21 /24
05/07/2010
12 M7900 - DECT ALARM SERVER
•
Signaling for Telephony Services (VTI/XML protocol) :
• sends to TCP port 3199 of the PBX/Call Manager ;
• receives on TCP port number selected by the PC Windows system.
•
Signaling with alarms station (port com emulation):
• sends to TCP ports 7901 to 7905 of the alarms station ;
• receives on TCP ports 7901 to 7905 from the alarms station.
13 SYSLOG
•
The UDP port 514 for SYSLOG purpose is used by the various products of the solution.
NT_092ed5_En
Page 22 /24
05/07/2010
14 As a reminder
14.1
•
Terminal Proxy Server (TPS)
Signaling for Telephony Services (Unistim protocol on secured UDP):
• sends to i2004 terminals and receives i2004 terminal information on UDP port 5000 (this
value can be changed by configuration at TPS level _ - but this value must match the
value configured in the terminals).
•
Signaling for Telephony Services (VTI/XML protocol) :
• sends to TCP port 3199 of the PBX/Call Manager (may be changed using TPS
configuration);
• receives on TCP port number selected by the PC Windows system
•
Integrated directory access;
• sends to TCP port 3203 of the PBX/Call Manager (may be changed using TPS
configuration);
• receives on TCP port number selected by the PC Windows system
•
Access to EAS server necessary for key programming ;
• sends to TCP port 3206 of the PBX/Call Manager (configurable in TPS) ;
• receives on TCP port number selected by the PC Windows system
14.2
•
i2004 set
Signaling for Telephony Services (Unistim protocol on secured UDP):
• Sends to the TPS and receives from the TPS on UDP port 5000 (which may be changed by
terminal configuration).
•
Voice flow (RTP/RTCP protocols):
• Sends to UDP port number transmitted by PBX/Call Manager through TPS ;
• receives on UDP ports 40000 and 40001 (default value defined by TPS and configured at the
TPS level).
• Note: Before R2.1 PBX release, the default values of UDP port numbers for RTP/RTCP were
set to 4000 and 4001 (default value defined by TPS and configured at the TPS level).
NT_092ed5_En
Page 23 /24
05/07/2010
14.3
•
SIP Terminals (i220, 480i, 9112i & 9133i)
Signaling for Telephony (SIP protocol):
• sends to UDP port 5060 (configurable) of the SIP gateway;
• receives on UDP port number selected by the terminal (value is configurable; by default this
value is set to 5060).
•
Voice flow (RTP/RTCP protocols):
• sends to UDP port numbers specified by the PBX/Call Manager ;
• receives on UDP ports 40000 and 40001; these values may be changed by configuration
(default RTCP port number 40001 unused for the moment).
14.4
•
REDUNDANCY (DOUBLE TAKE)
Two port numbers are used for Redundancy (Double Take):
• 1105 port for Heart Beat ;
• 1100 port used for communication between the servers.
14.5
M7425 (& OMSE & M7415)
•
The BUFTIC server is connecting to the management center using TCP port 9010 (this value may
be changed using configuration procedure).
•
The management center applications are connecting to the PBX using TCP-IP session on the
ports 3200 and + (above) of the TCP-IP/DATA gateway (refer to the table described before for
more details)
•
The M7425 Management Center Server listens to TCP port 9008 for the dialog with management
center Clients in JAVA/XML.
NT_092ed5_En
Page 24 /24
05/07/2010