> Most (even so-called "Public Safety ready") IP linking
> systems DO NOT have ANY way to notify the dispatcher
> that their transmissions are NOT going out over the air,
> or that the link coming in from the field radio units is down.
... and most regular conventional Public Safety Systems do
not normally have any way to notify dispatch their transmissions
are not going out over the air.
So... in each example I deal with... we figure out a practical
way. We removed that ideal reverse burst in a Major Fire
Dispatch System because they want to hear the repeater squelch
close crash noise.
We have on channel different location monitor receivers
(normally cross muted console audio) flashing a status active
light when ever an on-channel signal is received.
There are many tricks of the trade to ensure systems are
on the air.
> The system used Multicast IP (mistake number one), UDP (maybe
> mistake number two),
Both Multicast and UDP are not to blame... someone didn't
engineer the system properly.
> and when I said, "Unplug the Ethernet jack from the
> repeater" while the dispatch console was "transmitting"...
> there was ZERO alarm indication ANYWHERE to tell either
> the dispatcher, the officers in the field, or the
> technicians -- THAT THE SYSTEM WAS DOWN.
Once again...someone didn't engineer the system properly.
Wow Nate... now how do you really feel about VoIP/RoIP?
:-)
cheers,
s.
