Difference between revisions of "IMBE Link"
Jump to navigation
Jump to search
(Created page with "This is the working page for IMBE Link. = Features = == 1.0 == First version, needs to incorporate the basics of PNXmono, but in a modular format. * config file in a tra...") |
|||
Line 21: | Line 21: | ||
* Courtesy tones as files - allow them to be defined | * Courtesy tones as files - allow them to be defined | ||
− | * Proxy of | + | * Proxy of v.24 frames, only the IMBE data should be passed to the Quantar, control data should be stripped out |
** prevents channel changes | ** prevents channel changes | ||
* mute when RSSI/QOI value is below a given value (perhaps play a tone here?) | * mute when RSSI/QOI value is below a given value (perhaps play a tone here?) | ||
+ | * stats collected and ASTRO ID recorded | ||
+ | * improved logging and debugging | ||
+ | * output status of system via named pipe/logic on pi. | ||
+ | ** this would be used to block the system on P25 only for a set period of time. | ||
+ | ** Could be accomplished via channel change too. | ||
+ | ** Ideally would make the [[Allstar and P25 on Quantar|mixed mode operation]] easier without as many wildcard functions. | ||
== 2.0 == | == 2.0 == | ||
+ | |||
+ | * FDTI to Quantar v.24 interface. | ||
+ | |||
+ | * recording of conversations and metadata | ||
+ | |||
+ | * Bridge system | ||
+ | * * This would be a confederation of linking and registration servers to reflect the traffic | ||
+ | |||
+ | * System Wide Stats dashboard | ||
== 3.0 == | == 3.0 == | ||
+ | |||
+ | * Asterisk channel driver | ||
= Features defined = | = Features defined = |
Revision as of 04:19, 19 November 2017
This is the working page for IMBE Link.
Contents
Features
1.0
First version, needs to incorporate the basics of PNXmono, but in a modular format.
- config file in a traditional unixy format. No stupid C# bullshits
- Support for p25 data via STUN to cisco doing HDLC to the 9600 bps quantar v.24 interface.
- Two operational modes
- Traditional link, where the quantar does local repeat and the application handles network linking.
- Base station mode, the quantar does not repeat anything, the app repeats all data to the quantar, like an analog controller.
- In base mode, it can limit encrypted audio locally too, or force rewriting of talkgroup/messages
- Support for talk group scanning
- This would be a registration and priority matrix for individual talk groups
- support for talk back with ability to define the hang time
- Ability to block encryption or allow encryption (force encryption?)
- Courtesy tones as files - allow them to be defined
- Proxy of v.24 frames, only the IMBE data should be passed to the Quantar, control data should be stripped out
- prevents channel changes
- mute when RSSI/QOI value is below a given value (perhaps play a tone here?)
- stats collected and ASTRO ID recorded
- improved logging and debugging
- output status of system via named pipe/logic on pi.
- this would be used to block the system on P25 only for a set period of time.
- Could be accomplished via channel change too.
- Ideally would make the mixed mode operation easier without as many wildcard functions.
2.0
- FDTI to Quantar v.24 interface.
- recording of conversations and metadata
- Bridge system
- * This would be a confederation of linking and registration servers to reflect the traffic
- System Wide Stats dashboard
3.0
- Asterisk channel driver