IPSC3 supports direct MMDVMHost hotspot connections for simplex and duplex hotspots. A direct MMDVMHost connection is preferred over DMRGateway unless the operator has a specific routing requirement and understands the extra rewriting layer.
DMR+_IPSC3-VKDMR.1 unless the local RF design requires otherwise.
Hotspots advertise software and package identities during MMDVM login.
IPSC3 uses those values to display badges for Pi-Star, WPSD, BlueDV, VoxDMR,
OpenSPOT, M1KE, QSO1, and MMDVM-based software. QSO1 is recognised from
advertised software or package names such as QSOOne, not from
an operator's callsign. It has a gold badge and a separate registration
graph category; identifying it does not change simplex/duplex handling.
The Stats page includes each detected
software family in the hotspot registration trend and groups unknown future
identities under Other, so new clients remain visible even before a
dedicated badge is added.
Administrators can manage rejected software and package names under
Configuration > Blocked Hotspots > Rejected MMDVM Clients.
Enter exact names separated by commas or newlines. Either the reported
software ID or package ID may match; matching ignores case and surrounding
spaces. Callsigns are not compared. SPEAK-HB is rejected by default.
Clearing the list disables name-based rejection without removing individual
hotspot ID blocks.
Matching inbound MMDVM clients are refused at registration, including session recovery after a daemon restart. Already connected matching clients are disconnected within approximately ten seconds of a policy change. The policy is refreshed in the background and does not add database reads to voice packet processing or fan-out. Trunks and POC authentication are unaffected. Software names are self-reported identifiers, not cryptographic proof of the software being used; a modified client can report a different name.
IPSC3 recognises a small set of custom commands in the MMDVM options string. Option names are case-insensitive and multiple options can be separated with semicolons.
| Option | Effect |
|---|---|
ScanExclude=505,3801,3802 |
While the hotspot is in Scan Talkgroup 777 mode, do not send the listed talkgroups to that hotspot. |
ScanInclude=3801,3802 |
While the hotspot is in Scan Talkgroup 777 mode, only send the listed talkgroups to that hotspot. |
TalkerAlias=Y or TalkerAlias=N |
Enable or disable IPSC3 talker alias injection for that hotspot. The default is off. |
DashboardToken=your-secret |
Enables self-service dashboard access for that hotspot so the hotspot user can start or cancel scan mode and cancel the current dynamic camp from the hotspot detail page. |
ScanExclude and ScanInclude only affect scan-mode
output to the hotspot. They do not affect normal direct talkgroup use, camped
talkgroups, private calls, GPS/data handling, trunks, repeaters, or other
hotspots.
ScanInclude is the reverse of ScanExclude. If
ScanInclude=3801,3802 is set, scan mode will only pass traffic
from talkgroups 3801 and 3802 to that hotspot. If both options are present,
ScanExclude wins for any talkgroup that appears in both lists.
ScanInclude=3801,3802;TalkerAlias=N
DashboardToken gives a hotspot user limited self-service access
to that hotspot on the dashboard without needing a normal operator account.
When a token is configured, the hotspot callsign becomes clickable on the
public hotspot dashboard. The token itself is masked in hover/details output.
After entering the correct token, the browser receives a signed hotspot-owner cookie for that specific hotspot. The user can then start or cancel scan mode for that hotspot only, and can cancel that hotspot's current dynamic camp. The token does not grant access to operator mode, repeater conversion, system configuration, or other hotspots.
DashboardToken=ChangeThisLongRandomValueUse a token at least six characters long. Allowed characters are letters, numbers, dot, underscore, colon, at sign, plus and dash. Do not use the same token on multiple hotspots.
If IPSC3 reports that a dashboard token has been revoked, replace the
DashboardToken value with a new unique random value and reconnect
the hotspot. Previously exposed values remain blocked even if a hotspot
reconnects with the old option string.
TalkerAlias=Y asks IPSC3 to inject a short UTF-8 talker alias on
outbound traffic to that MMDVM hotspot using RadioID database information.
This can be useful on radios that display talker alias correctly, but it
should be enabled with caution because some radios and some configurations do
not handle talker alias consistently.
If in doubt, leave talker alias off.