|
Page 3 of 4 System Specifications12 Gateways per Remote: Every Remote PC can simultaneously display the activity from up to 12 gateways. Each gateway can support a different set of talkgroups, channels, unit ID’s or geographic regions. The audio from the selected gateway will be played in the Remote PC’s headset or speakers. Audio from other gateways can be scanned and played through the same headset or speakers 64 Remotes per Gateway: Each gateway can support up to 64 Remote PCs. Any 25 of these remotes can be active at one time. When a field radio talks, up to 25 PC users can hear the audio. When a PC user talks, the field radios and the other 24 Remote PCs can hear the audio. Modular Design: IP|Connect is designed for growing, changing needs. The systems administrator can customize the configuration. Additional Remotes and Gateways can be added to the system without changing the application software. Each Gateway can have a unique list of Remotes and each Remote can have a unique list of Gateways. TCP/IP Control Messages: Transmission Control Protocol/Internet Protocol is used for the control messages between the Gateways and Remotes. These control messages are used to key the radio, change groups or channels, provide status information, and coordinate operations between the Remotes (clients) and the Gateways. UDP Voice Datagrams: User Datagram Protocol is used to transport the voice content between the Remotes and the Servers. Client-Server Architecture: IP|Connect uses this industry standard approach in its software design. The Remotes run a client application while the Gateways runs a server application. This approach limits the Remote PC resources required thereby enhancing the product's multitasking capabilities. This approach also limits the amount of computer network traffic required between the fixed radio and Remote PC.
|
