Short answers to common questions about the IPSC3 beta rollout, new routing features, repeaters, support and reporting problems. This page is intended as a practical starting point and will be refined as testing continues.
IPSC3 is close to beta testing after alpha testing with network operators. The plan is to move most ARNSW RadNet repeaters across first if final checks go well, with a selectable Pi-Star testing server requested so hotspot users can also help beta test when available.
VKDMR is moving to IPSC3 to modernise the Australian DMR core and better support how the network is used today. IPSC3 improves repeater handling, hotspot handling, routing visibility, scan behaviour, private call support and audio feedback while keeping the network focused on reliable amateur radio communication.
IPSC2 provided the previous generation bridge and routing platform. IPSC3 is the locally developed replacement used by VKDMR for live routing decisions, repeater and hotspot state tracking, dashboard visibility, talkgroup scan, private call routing, parrot support and stricter handling of edge cases that affected some radios.
For normal users, the aim is not to make operating more complicated. The aim is to make the network more predictable, easier to diagnose and more robust across Motorola IPSC repeaters, MMDVM hotspots, trunks and future integrations.
Use a direct, non-group call to the destination radio ID on TS1. IPSC3 tracks where radios were last seen and routes the private call automatically to the repeater or hotspot where that radio was last active, provided it has been seen within the roaming dwell window. If the destination cannot be found, the caller receives a voice busy message saying the callsign or radio ID is unavailable.
Key TG 777 TS1 from a repeater or hotspot to place that endpoint into scan mode. IPSC3 then listens for active traffic on VKDMR and approved connected networks including CQUK, BrandMeister VK and Quadra, and translates that audio back to TG 777 TS1.
If you reply on TG 777 TS1, IPSC3 sends your audio back to the last active talkgroup automatically. When that group goes quiet, the endpoint returns to scan mode. You can cancel scan by keying another talkgroup or TG 400.
IPSC3 currently recognises two custom options in the MMDVM options field. Option names are case-insensitive and multiple options can be separated with semicolons.
ScanExclude=505,3801,3802,8409 prevents those talkgroups from being sent to that hotspot while it is in Scan Talkgroup 777 mode. This is a per-hotspot setting and does not affect normal direct or camped talkgroup use, and it does not affect other hotspots.
TalkerAlias=Y enables outbound talker alias injection for that MMDVM hotspot using CALLSIGN - First Name from the radio ID database. It is off by default, and TalkerAlias=N keeps it explicitly disabled. Use this option with caution because talker alias can cause unexpected behaviour with some radios. If in doubt, do not use this option. Unsupported options are shown as Options Ignored in the hotspot hover/details so users can see exactly what IPSC3 is using.
Yes. Parrot on TG 9990 works with direct and group calls on repeaters, simplex hotspots and duplex hotspots. It records your audio, plays it back, then reads back your callsign if your radio ID resolves. If it cannot resolve your callsign, it speaks the radio ID in full.
IPSC3 knows the difference between simplex and duplex hotspots. When a simplex hotspot moves to a 380x or other dynamic talkgroup, IPSC3 mutes TG 505 and other competing traffic on that hotspot until the selected talkgroup has been quiet long enough to time out. This stops the hotspot being dragged back to TG 505 while you are trying to use another group.
The VKDMR Network is administered by the VK DMR Working Group. The group is made up of licensed amateur operators who volunteer their time to supervise, maintain and improve the network for the amateur radio community. Repeaters and sites are also supported by local clubs, custodians and partner organisations.
If you want to add a repeater to VKDMR, start by contacting the VK DMR Working Group via the VK DMR Network [OFFICIAL] Facebook group. Include the proposed site, callsign, frequencies if known, internet access, power arrangements, coverage goal and who will act as custodian.
If the proposed repeater is in New South Wales, contact the ARNSW RadNet coordinator through ARNSW as well. ARNSW contact details are available from the ARNSW contact page.
For general user issues or beta feedback, report the problem through the VK DMR Network [OFFICIAL] Facebook group or by direct message to the IPSC3 maintainer if requested. For urgent repeater-site issues, also contact the local repeater custodian or club if known.
Useful bug reports include the time of the test, your radio ID, source repeater or hotspot, talkgroup, timeslot, what you expected to happen, what actually happened and whether the dashboard showed RX, TX, scan or private call activity.
A lot of IPSC3 testing involves keying repeaters, hotspots or trunks with no audio path or no practical way to respond. If you hear testing activity and do not get a reply, assume testing is in progress rather than being ignored.