Breaking News

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 PortClient default PortProtocol StackService
5010 – 50595010 – 5059RTP-RTCP / UDPPayload Transport VoIP
50601024 – 65535SIP / TCPSIP subscriber in case of TCP
50611024 – 65535SIP / TLSSIP subscriber in case of TLS
50605060SIP / UDPSIP subscriber in case of UDP
---1024 – 65535HTTP / TCPXML applications in phone, connects to an application server
---1024 – 65535LDAP / TCPDirectory access via LDAP
---68DHCP / UDPDHCP Client
---1024 – 65535DNS / TCP_UDPDNS Client
8085---HTTP / TCPDLS contact me service – workpoint side
---18443HTPS/ TCP – SSL/TLSDefault communication of “DLS workpoint interface”
---18444HTTPS / TCP – SSL/TLSSecure mode communication of “DLS workpoint interface”
211024 – 65535FTP / TCPConnection to the control port of FTP server
1024 – 6553520FTP / TCPFTP Client which uses the FTP server in active mode
---443HTTPS / TCP – SSL/TLSHTTPS file download server
---1024 – 65535SNMP / UDPClient application which sends QDC data to the QCU
---1024 – 65535SNMP / UDPPart of SNMP-Agent – sending Traps
161---SNMP / UDPPart of SNMP-Agent – receive Set/Get commands
---123SNTP / UDPSNTP Client – queries time information in unicast operation
123---SNTP / UDPSNTP Client – receive time information in broadcast operation
8085---http / TCPWeb Server for WBM access
443---HTTPS / TCP – SSL/TLSSecure Web Server for WBM access
65530---HTTP / UDPOpenStage Phone Manager
65531---HTTP / TCPOpenStage Phone Manager
---514UDPRemote Trace
---65530UDPHPT- debug IF.Only avail.when a dongle file is present on the phone
---22TCPSSh(Secure Shell Remote Login)
1024-65535UDPSyslog Client(sends Traces to a syslog server)
5050-50595050-5059RTP / UDPVideo H.263
Ports List for HFA Clients

HFA Port.jpg

Gateway Port Allocation

PortProtocalFunctionRemark
20TCPFTP data only ifFACCMODE=1 (HFAB -DEBUG)HG3530
21TCPFTP server only if FACCMODE=1 (HFAB -DEBUG)HG3530
23TCPTelnet (command line Interface) only if FACCMODE=1 (HFAB - DEBUG)HG3530
24TCPTelnet (stdio) only if FACCMODE=1 (HFAB - DEBUG)HG3530
161SNMPSNMP (Get/Set) for the local SNMP agentsHG3530
162SNMPSNMP (Traps)HG3530
1720TCPH.225 InterfaceHG3530
4060TCPCornet TC LogonHG3530
4711TCPDSP Debug only if FACCMODE=1 (HFAB - DEBUG)HG3530
8082TCPHTTP only if FACCMODE=1 (HFAB - DEBUG)HG3530
1024-65535TCPH.245 InterfaceHG3530
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

PortProtocalFunctionRemark
21TCPFTP-Server
53UDPDNS
67UDPDHCP
161SNMPSNMP Get/Set
162SNMPSNMP Traps
8082TCPAdministration
8085TCPhttp


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.

No comments