Property:me anony-voipkpid-($num)-($num).ctl

---

BoxMatrix >> System >> me_anony-voipkpid-($num)-($num).ctl

@ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl

News

Selectors

Models

Accessories

Components

Environment

Config

Commands

System

Webif

Software

Develop

Lexicon

Community

Project

Media

---

Devices

Filesystems

Partitions

Sockets

Netlink

Pipes

Interfaces

Bridges

Ports

Events

Sources

Sinks

AVMIPC

Processes

Watchdogs

Memory

Slab

Vmalloc

ProcFS

SysFS

Research

---

Linux-Socket

Socket:	me_anony-voipkpid-($num)-($num).ctl   -   type DGRAM	Wiki	Freetz	IPPF	whmf	AVM	Web
Location:	System >> Linux-Sockets   -   Origin: AVM
Path:	/var/tmp
Properties:	Firmware: 7.08 - 8.00
Function:	Anonymous avmipc endpoint to trigger KPI creation by voipkpid.

Goto:   Dependencies   -   Model-Matrix   -   Missing Supportdata   -   SMW-Browser

Details

This endpoint is orininally called 'me__anony-voipkpid-($num)-($num).ctl' but MediaWiki fails on double '_'.
Example: /var/tmp/me__anony-voipkpid-1300-1382297367.ctl. The first number is the pid of the serving proceess.
In aicmd avmipcd datastore show this appears as _anony-voipkpid-1300-1382297367.

Before firmware 7.39 all anonymous avmipc endpoints were named me_anony($num)-($num).ctl.
This has been adapted by the Supportdata2 scanner to make the Dependencies per daemon work for pre 7.39 firmware.
Read more about this adaption in the me_anony($num)-($num).ctl article.

The purpose of anonymous endpoints is not to hide its owner but to avoid name colissions in the filesystem.
A socket named by its owner like me_multid.ctl can only exist one time, for a process which can only run in one instance.
A socket name adding the process's pid like me_aicmd-($num).ctl permits for multiple instances, but only supports one
socket named like this per process. That's why processes running in multiple instances which require numerous sockets add
a second long number to their name, which may be the address of the csock, like me_anony-ctlmgr-($num)-($num).ctl.

You should be aware that the Dependencies collect relations of all instances of anonymous endpoints of a process.

Dependencies

Daily updated index of all dependencies of this socket. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.

Relation	Typ	Object	Mod	Firmware	Info	Origin
Served by	cmd	voipkpid (avmcmd)	31*	7.08 - 8.00	VoIP quality KPI collector daemon.	AVM
Listens to	avmipc	KPI_PRE_INFORM_NOTIFY	18**	7.29 - 7.57	Trigger event to create KPI.	AVM
2 dependencies for this socket

Model-Matrix

Daily updated index of the presence, path and size of this socket for each model. Last update: 2024-11-15 07:09 GMT.
Showing all models using this socket. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl) label in the Model column shows which CPU is meant for Multi-Linux models.
Note that this list comes from Supportdata-Probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata file or just a disabled feature.

Model	Firmware	Path	Server
FRITZ!Box 4050	7.90	/var/tmp	voipkpid
FRITZ!Box 4060	7.28 - 7.29	/var/tmp	voipkpid
FRITZ!Box 5530 Fiber (main)	7.19 - 7.29	/var/tmp	voipkpid
FRITZ!Box 5590 Fiber (main)	7.27 - 7.81	/var/tmp	voipkpid
FRITZ!Box 5690 Pro (main)	7.61	/var/tmp	voipkpid
FRITZ!Box 6430 Cable (atom)	7.29	/var/tmp	voipkpid
FRITZ!Box 6490 Cable (atom)	7.20 - 7.24	/var/tmp	voipkpid
FRITZ!Box 6590 Cable (atom)	7.20	/var/tmp	voipkpid
FRITZ!Box 6591 Cable (atom)	7.21 - 7.29	/var/tmp	voipkpid
FRITZ!Box 6660 Cable (atom)	7.23 - 7.29	/var/tmp	voipkpid
FRITZ!Box 6670 Cable (atom)	7.59 - 7.61	/var/tmp	voipkpid
FRITZ!Box 6690 Cable (atom)	7.29 - 7.57	/var/tmp	voipkpid
FRITZ!Box 6850 LTE	7.21	/var/tmp	voipkpid
FRITZ!Box 6850 5G	7.25 - 7.30	/var/tmp	voipkpid
FRITZ!Box 6890 LTE v1 (main)	7.28	/var/tmp	voipkpid
FRITZ!Box 6890 LTE v2 (main)	7.51	/var/tmp	voipkpid
FRITZ!Box 7430 (main)	7.21 - 7.29	/var/tmp	voipkpid
FRITZ!Box 7490 (main)	7.08 - 7.59	/var/tmp	voipkpid
FRITZ!Box 7510	7.29	/var/tmp	voipkpid
FRITZ!Box 7520	7.21 - 7.29	/var/tmp	voipkpid
FRITZ!Box 7520 v2 (main)	7.29 - 7.30	/var/tmp	voipkpid
FRITZ!Box 7530	7.20 - 8.00	/var/tmp	voipkpid
FRITZ!Box 7530 AX	7.20 - 7.39	/var/tmp	voipkpid
FRITZ!Box 7560 (main)	7.29 - 7.30	/var/tmp	voipkpid
FRITZ!Box 7580 (main)	7.21	/var/tmp	voipkpid
FRITZ!Box 7583 (main)	7.21 - 7.59	/var/tmp	voipkpid
FRITZ!Box 7583 VDSL (main)	7.21	/var/tmp	voipkpid
FRITZ!Box 7590 (main)	7.21 - 7.90	/var/tmp	voipkpid
FRITZ!Box 7590 AX (main)	7.25 - 8.00	/var/tmp	voipkpid
FRITZ!Box 7590 AX v2 (main)	7.31	/var/tmp	voipkpid
FRITZ!Box 7690	7.60 - 7.61	/var/tmp	voipkpid
31 models use this socket

Missing Supportdata

The data in this article is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.

Model	Method	Info
FRITZ!Box WLAN 3270 IT	lua	http://fritz.box/support.lua
FRITZ!Box Fon ata	html	http://fritz.box/html/support.html
FRITZ!Box Fon ata 1020	html	http://fritz.box/html/support.html
FRITZ!Box Fon 5010	html	http://fritz.box/html/support.html
FRITZ!Box Fon 5012	html	http://fritz.box/html/support.html
FRITZ!Box Fon 5113	html	http://fritz.box/html/support.html
FRITZ!Box Fon WLAN 7113 INT	html	http://fritz.box/html/support.html
Speedport W 501V	telnet
Speedport W 722V	console
Eumex 300 IP	telnet
10 models without supportdata probes

SMW-Browser

Property:me anony-voipkpid-($num)-($num).ctl

Information is currently being retrieved from the backend.