HiPath 4000 - Ports List

Port List
- Port List for SIP Clients
- Ports List for HFA Clients
- List_of_TCP_and_UDP_port_numbers

Port List for SIP Clients

Server default Port	Client default Port	Protocol Stack	Service
5010 – 5059	5010 – 5059	RTP-RTCP / UDP	Payload Transport VoIP
5060	1024 – 65535	SIP / TCP	SIP subscriber in case of TCP
5061	1024 – 65535	SIP / TLS	SIP subscriber in case of TLS
5060	5060	SIP / UDP	SIP subscriber in case of UDP
---	1024 – 65535	HTTP / TCP	XML applications in phone, connects to an application server
---	1024 – 65535	LDAP / TCP	Directory access via LDAP
---	68	DHCP / UDP	DHCP Client
---	1024 – 65535	DNS / TCP_UDP	DNS Client
8085	---	HTTP / TCP	DLS contact me service – workpoint side
---	18443	HTPS/ TCP – SSL/TLS	Default communication of “DLS workpoint interface”
---	18444	HTTPS / TCP – SSL/TLS	Secure mode communication of “DLS workpoint interface”
21	1024 – 65535	FTP / TCP	Connection to the control port of FTP server
1024 – 65535	20	FTP / TCP	FTP Client which uses the FTP server in active mode
---	443	HTTPS / TCP – SSL/TLS	HTTPS file download server
---	1024 – 65535	SNMP / UDP	Client application which sends QDC data to the QCU
---	1024 – 65535	SNMP / UDP	Part of SNMP-Agent – sending Traps
161	---	SNMP / UDP	Part of SNMP-Agent – receive Set/Get commands
---	123	SNTP / UDP	SNTP Client – queries time information in unicast operation
123	---	SNTP / UDP	SNTP Client – receive time information in broadcast operation
8085	---	http / TCP	Web Server for WBM access
443	---	HTTPS / TCP – SSL/TLS	Secure Web Server for WBM access
65530	---	HTTP / UDP	OpenStage Phone Manager
65531	---	HTTP / TCP	OpenStage Phone Manager
---	514	UDP	Remote Trace
---	65530	UDP	HPT- debug IF.Only avail.when a dongle file is present on the phone
---	22	TCP	SSh(Secure Shell Remote Login)
1024-65535		UDP	Syslog Client(sends Traces to a syslog server)
5050-5059	5050-5059	RTP / UDP	Video H.263

Ports List for HFA Clients

Gateway Port Allocation

Port	Protocal	Function	Remark
20	TCP	FTP data only ifFACCMODE=1 (HFAB -DEBUG)	HG3530
21	TCP	FTP server only if FACCMODE=1 (HFAB -DEBUG)	HG3530
23	TCP	Telnet (command line Interface) only if FACCMODE=1 (HFAB - DEBUG)	HG3530
24	TCP	Telnet (stdio) only if FACCMODE=1 (HFAB - DEBUG)	HG3530
161	SNMP	SNMP (Get/Set) for the local SNMP agents	HG3530
162	SNMP	SNMP (Traps)	HG3530
1720	TCP	H.225 Interface	HG3530
4060	TCP	Cornet TC Logon	HG3530
4711	TCP	DSP Debug only if FACCMODE=1 (HFAB - DEBUG)	HG3530
8082	TCP	HTTP only if FACCMODE=1 (HFAB - DEBUG)	HG3530
1024-65535	TCP	H.245 Interface	HG3530
29100-29399*	UDP	(240 consecutive ports for RTP and RTCP)	HG3530

*) The actual port range used for RTP/RTCP connections can be configured system-wide (HFAB-ASC-UDPPORT). A range of 240 ports is always used. The port with the lowest value can be set to even values in the range [4352 ... 65280].

Client Port Allocation

Port	Protocal	Function	Remark
21	TCP	FTP-Server
53	UDP	DNS
67	UDP	DHCP
161	SNMP	SNMP Get/Set
162	SNMP	SNMP Traps
8082	TCP	Administration
8085	TCP	http

The signaling connection between the terminal and HFA (Common) Gateway uses a secure TCP connection and the voice data are transferred via an H.323 connection using the RTP/RTCP protocol. Both connections can now be routed differently in a single LAN. This means it is possible for there to be signaling although the voice connection is temporarily interrupted.

Registration : Firstly an HFA user needs a separate IP address, a subnetwork mask and - optionally - the specification of a default (customer network) router. In the case of a Soft Client, it has, of course, the advantage that it uses the network card of the PC and, consequently, no settings are required.
However, in the case of an HFA fixed device, the IP settings must be made. This is either done “automatically“ via DHCP (default setting of the HFA fixed terminals) or manually.

A HFA user with IP settings now attempts to register with the appropriate gatekeeper. Its gatekeeper is the HG 3500 at whose position it is configured. In order to find its “home“ HG 3500, its IP address must be set up at the terminal.
This alone, however, is not sufficient. The HG 3500 still has to check whether the user who is sending it a “Registration Request“ is actually authorized to register with it. The terminal must also send it the user number for checking the user identity. The HG 3500 then asks the HiPath 4000 whether this user number is set up at its position. If it is, the HFA user is registered. If not, the HFA user is denied.

Thus, the user number must be set up beforehand on the terminal. To prevent a user simply registering himself with the subscriber number of another colleague, it is even possible to set up a so-called IP password (IPPASSW) in the AMO SBCSU. This can only be changed via the administrator, but not by the user at the terminal. If an IP password is set up in the AMO SBCSU, it must also be configured at the terminal. Otherwise, the subscriber is not registered.

Note: In some customer networks it may also be necessary to preset the L2 prioritization and the VLAN ID at the HFA terminal. Here, however, it is also possible to automate this via DHCP.

Following successful registration, the HG 3500 transfers data concerning the HFA user to the AMO SBCSU such as, e.g. device type, IP address, etc. (SBCSU / branch TYPE=OPTIDAT). These data can also be viewed in the UW7 via the Configuration Menu in the user overview.