Dual fallback hardened VoIP system with signal quality measurement
A hardened VoIP system is presented that includes secure push-to-talk voice functionality. Through the addition of encryption, authentication, user filtering, and integration with new and existing LMR systems, a secure voice platform ensures malicious software, unauthorized access and brute force security attacks will not compromise the voice communications of the system. The VoIP system is engineered to ensure graceful system degradation in the event of maintenance activities, natural disasters and failure modes. The hardened VoIP system offers the functions a LMR trunking system while utilizing broadband connections. Private calls, group calls, Emergency Alarms with covert monitoring capability, scanning and priority scanning may be incorporated into the system. The system includes a VoIP controller that serves as a trunking controller, manages available VoIP based conference bridges, and assigns them as needed to the parties involved in each voice call. The system includes multiple fallback methods that may be prioritized based on pre-failure analytics.
1. A mobile device having a first primary operational state, a secondary primary operational state, a first fallback state, and a second fallback state,
the mobile device configured
in the first primary operational state to
receive from a first land mobile radio system
a first Land Mobile Radio (LMR) status signal, and
provide VoIP communication over a cellular communications system;
in the second primary operational state to
receive from a second land mobile radio system
a second LMR status signal, and
provide VoIP communication over the cellular communications system; and
to transition from the first primary operational state to the second primary operational state upon failing to receive the first LMR status signal.
2. The mobile device of claim 1 wherein
the mobile device is configured
in the first primary operational state to
receive via a cellular communications system
a VoIP status signal from a VoIP controller,
in the second primary operational state to
receive via the cellular communications system
the VoIP status signal from the VoIP controller,
in the first fallback state to
provide voice communication over the first land mobile radio system;
in the second fallback state to
provide voice communication over the second land mobile radio system; and
to transition from the first primary operational state to the first fallback state upon failing to receive the VoIP status signal from the VoIP controller;
to transition from the second primary operational state to the second fallback state upon failing to receive the VoIP status signal from the VoIP controller.
3. The mobile device of claim 2 wherein the mobile device is configured to transition from the second primary operational state to the first primary operational state upon receiving the first LMR status signal.
4. The mobile of claim 2 wherein
the mobile device is configured
in the first primary operational state to
receive the first LMR status signal following a verification of receipt of the VoIP status signal from the VoIP controller, and
in the second primary operational state to
receive the second LMR status signal following the verification of receipt of the VoIP status signal from the VoIP controller.
5. The mobile device of claim 2 wherein
the mobile device is configured to
determine a signal quality of the cellular communications system with a Session Initiation Protocol/Real-Time Transport Control Protocol (SIP/RTCP), and
transition from the first primary operational state to the first fallback state upon the signal quality of the cellular communications system passing a predetermined threshold.
6. The mobile device of claim 5 wherein the predetermined threshold is a threshold of at least one of packet loss, latency, and jitter buffer depth.
7. The mobile device of claim 5 wherein
the mobile device is configured to
transition from the first primary operational state to the first fallback state upon the signal quality passing the predetermined threshold when the mobile device is receiving the VoIP status signal from the VoIP controller.
8. The mobile device of claim 2 wherein
the mobile device further includes a first auxiliary data state and a second auxiliary data state;
the mobile device configured
in the first auxiliary data state to
receive via an auxiliary data communications system
an auxiliary data status signal from the VoIP controller,
receive from the first land mobile radio system
the first LMR status signal, and
provide VoIP communication over the auxiliary data communications system;
in the second auxiliary data state to
receive via the auxiliary data communications system
the auxiliary data status signal from the VoIP controller,
receive from the second land mobile radio system
the second LMR status signal, and
provide VoIP communication over the auxiliary data communications system;
to transition from the first auxiliary data state to the first fallback state upon failing to
receive the auxiliary data status from the VoIP controller;
to transition from second auxiliary data state to the second fallback state upon failing to
receive the auxiliary data status from the VoIP controller; and
to transition from the first auxiliary data state to the second auxiliary data state upon failing
to receive the first LMR status signal.
9. The mobile device of claim 8 wherein
the mobile device is further configured
to transition from the first primary operational state to first auxiliary data state upon failing to receive the VoIP status signal and receiving the auxiliary data status signal; and
to transition from the first primary operational state to first fallback state upon failing to receive the VoIP status signal and failing to receive the auxiliary data status signal.
10. A VoIP controller having a first primary operational state, a second primary operational state, a first fallback state, and a second fallback state,
the VoIP controller configured
in the first primary operational state to
receive via a cellular communications system
a first VOIP heartbeat signal from a first mobile,
receive a first Land Mobile Radio (LMR) status signal associated with a first land
mobile radio system from the mobile device,
maintain a database with
a first identifier associating the first mobile device with the cellular communications system and
a second identifier associating the first mobile device with the first land mobile radio system;
in the second primary operational state to
receive via the cellular communications system the first VOIP heartbeat signal from the first mobile device,
receive a second LMR status signal associated with a second land mobile radio system from the mobile device,
maintain the database with
the first identifier associating the first mobile device with the cellular communications system and
the second identifier associating the first mobile device with the second land mobile radio system;
in the second primary operational state to
receive via a cellular communications system
the first VOIP heartbeat signal from the mobile device,
receive via a second land mobile radio system
a second LMR status signal,
transmit a first status control signal to the mobile device, and
maintain the database with
the first identifier associating the first mobile device with the cellular communications system and
a third identifier associating the first mobile device with the second land mobile radio system;
in the first fallback state to
monitor a channel of the first land mobile radio system associated with the mobile device;
in the second fallback state to
monitor a channel of the second land mobile radio system associated with the mobile device;
to transition from the first primary operational state to the first fallback state upon failing to receive the first VoIP heartbeat signal from the mobile device; and
to transition from the second primary operational state to the second fallback state upon failing to receive the first VoIP heartbeat signal from the mobile device.
11. The VoIP controller of claim 10 wherein
the VoIP controller is configured to determine a signal quality of the cellular communications system with a Session Initiation Protocol/Real-Time Transport Control Protocol, and transition from the first primary operational state to the first fallback state upon the signal quality passing a predetermined threshold.
12. A computing device hosting a VoIP push-to-talk (PTT) configuration application, the computing device configured to:
detect a user action taken at a remote client device providing an interface to the VoIP push-to-talk configuration application, the user action taken including an activation of an add group graphical object associated with adding a new group to an existing VoIP PTT radio system, and responsively:
detect a second user action taken at the remote client device including entrance of an identifier that uniquely identifies the new group and entrance of a group type indication indicating whether the new group is a VoIP-only group or a converged VoIP and land mobile radio (LMR) group;
update a voice service stack associated with the VoIP PTT radio system to include the new group in the existing VoIP PTT radio system;
update, via the voice service stack associated with the VoIP PTT radio system, existing other VoIP mobile radios in the VoIP PTT radio system that the new group has been added to the VoIP PTT radio system; and
where the group type indication indicates that the new group is a converged VoIP and LMR group:
register, via the voice service stack, at a land mobile radio (LMR) interface stack of a particular LMR radio system indicated via the second user action, that the new group has been added to the VoIP PTT radio system.
13. The computing device of claim 12 , wherein the cloud computing device is further configured to register the new group at the particular LMR radio system by transmitting a registration message to an on-premises gateway device disposed at a same location as the particular LMR radio system and having a hardware address associated with the particular LMR radio system stored at the cloud-based VoIP push-to-talk configuration application.