2905

IANA registers TCP port 2905 as m3ua, with RFC 4666 as its reference. RFC 4666 defines M3UA for carrying SS7 MTP3-user signalling, such as ISUP and SCCP messages, over IP. It describes use between a signalling gateway and an application, or between IP-based applications. The registration does not show that a particular host runs M3UA on this port.

RFC 4666 recommends SCTP for M3UA because of its signalling transport features. It permits TCP in certain scenarios, including back-to-back connections without redundancy requirements. Thus, a TCP service on 2905 could be M3UA, but the port number alone cannot identify the application or its configuration.

The supplied evidence does not establish the intended audience or access policy for a deployment. Treat an observed listener as unverified until its protocol and operational context are confirmed; no prevalence, safety, or malware conclusion follows from the registry assignment.

Registered use

IANA assigns m3ua to TCP port 2905, referencing RFC 4666.

Protocol context

M3UA transports SS7 MTP3-user signalling over IP; RFC 4666 recommends SCTP and permits TCP in certain scenarios.

Exposure

Unknown. The evidence does not establish whether a deployment should be internet-facing, restricted, or internal-only.

Verification

A port assignment alone does not confirm that an observed service is M3UA.

IANA service name

m3ua [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Protocol purpose

Carries SS7 MTP3-user signalling over IP

RFC reference

RFC 4666 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Recommended transport

SCTP; TCP is permitted in certain scenarios [Confirmed] — https://www.rfc-editor.org/rfc/rfc4666.txt

Deployment prevalence

Unknown [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv