What is the mechanism for calling methods like msgAuthenticate or msgPing?

[archie2010]

The issue

Newbie seeking help.
I am studying the Mumble code and have a question. How are methods like msgAuthenticate or msgPing called in murmur module, and what is the triggering mechanism or entry point?

Mumble version

master

Mumble component

Server

OS

Windows

Additional information

No response

[Krzmbrzl]

Server:

mumble/src/murmur/Server.cpp

Lines 1719 to 1745 in 3e56558

	#ifdef QT_NO_DEBUG
	# define PROCESS_MUMBLE_TCP_MESSAGE(name, value) \
	case Mumble::Protocol::TCPMessageType::name: { \
	MumbleProto::name msg; \
	if (msg.ParseFromArray(qbaMsg.constData(), static_cast< int >(qbaMsg.size()))) { \
	msg.DiscardUnknownFields(); \
	msg##name(u, msg); \
	} \
	break; \
	}
	#else
	# define PROCESS_MUMBLE_TCP_MESSAGE(name, value) \
	case Mumble::Protocol::TCPMessageType::name: { \
	MumbleProto::name msg; \
	if (msg.ParseFromArray(qbaMsg.constData(), static_cast< int >(qbaMsg.size()))) { \
	if (type != Mumble::Protocol::TCPMessageType::Ping) { \
	printf("== %s:\n", #name); \
	msg.PrintDebugString(); \
	} \
	msg.DiscardUnknownFields(); \
	msg##name(u, msg); \
	} \
	break; \
	}
	#endif
	switch (type) { MUMBLE_ALL_TCP_MESSAGES }

Client:

mumble/src/mumble/MainWindow.cpp

Lines 3703 to 3723 in 3e56558

	#ifdef QT_NO_DEBUG
	# define PROCESS_MUMBLE_TCP_MESSAGE(name, value) \
	case Mumble::Protocol::TCPMessageType::name: { \
	MumbleProto::name msg; \
	if (msg.ParseFromArray(shme->qbaMsg.constData(), static_cast< int >(shme->qbaMsg.size()))) \
	msg##name(msg); \
	break; \
	}
	#else
	# define PROCESS_MUMBLE_TCP_MESSAGE(name, value) \
	case Mumble::Protocol::TCPMessageType::name: { \
	MumbleProto::name msg; \
	if (msg.ParseFromArray(shme->qbaMsg.constData(), static_cast< int >(shme->qbaMsg.size()))) { \
	printf("%s:\n", #name); \
	msg.PrintDebugString(); \
	msg##name(msg); \
	} \
	break; \
	}
	#endif
	switch (shme->type) { MUMBLE_ALL_TCP_MESSAGES }

[archie2010]

Thanks