Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Podporované protokoly #2

Open
3 tasks
smarek opened this issue Apr 21, 2020 · 7 comments
Open
3 tasks

Podporované protokoly #2

smarek opened this issue Apr 21, 2020 · 7 comments

Comments

@smarek
Copy link
Member

smarek commented Apr 21, 2020

Chceme aby core podporoval tyto protokoly

  1. Homebrew (MMDVMHost) pro přímé připojení malých i velkých systémů
  2. Hytera Multi-Site Connect (přímo nebo pomocí https://github.com/smarek/Hytera_Homebrew_Bridge )
  3. FastForward (P2P) pro spojení mezi instancemi master serverů

Rozhodně nechceme podporovat přímé spojení těmito protokoly

  • XLX

  • YSF

  • OpenBridge/IPSC2

  • P25

  • DV4Mini

  • WinMaster

  • SmartPTT

  • CBridge

  • D-Star
    Tyto protokoly by měly být řešeny samostatnými pluginy/bridge, které budou konvertovat nepodporovaný protokol do jednoho z podporovaných (typicky homebrew)

  • Homebrew client support

  • MMDVM client support

  • P2P Protocol support

@ok2zar
Copy link

ok2zar commented Apr 27, 2020

Ad 2: Nejsem si jist, zda by Hytera mela byt podporovana nativne. Podporu Hytery bych resil externim pluginem.

Ad 3: Tady nevim, zda reverzovat FastForward a zajistit tak kompatibilitu i BM mastery, nebo pouzit/upravit neco jineho.

@smarek
Copy link
Member Author

smarek commented Apr 27, 2020

Ad 2, preferoval bych asi externí Homebrew plugin
Ad 3, protože BrandMeister FastForward není otevřená specifikace, tak bych buď navrhnul něco vlastního, nebo stavěl na základech jiných multi-master prokotolů, BM komunitě bych nabídnul, že pokud mají zájem, tak ať zveřejní FastForward protokol a že mu přidáme podporu v jádru

@ok2zar
Copy link

ok2zar commented Apr 30, 2020

Ad 2: Souhlasim
Ad 3: Budto bude nutne udelat neco vlastniho, upravit OpenBridge a nebo najit neco vyhovujiciho. Vzhledem k postojum a chovani BM teamu si nemyslim, ze by chteli nejak spolupracovat nebo propojovat BM mastery s nasim resenim pomoci FastForwardu. Ale treba se mylim.

@iddq
Copy link

iddq commented May 10, 2020

Why don't you think about mesh network instead of centralized?

@iddq
Copy link

iddq commented May 10, 2020

What is the problem with HBlink? I mean if you want to create an alternative solution then so I think you have some problem with it. Can I ask you what is that?

@smarek
Copy link
Member Author

smarek commented May 11, 2020

@iddq if you wanna discuss, please open new ticket, but shorty answers:

  1. We want mesh with intelligent routing between masters
  2. HBLink is not easy-to-use / easy-to-configure, and we want our master software to be more brandmeister like, which HBLink currently is not

@sp2ong
Copy link

sp2ong commented Jun 5, 2020

Nice idea, I use HBLink locally and it works well but the assumptions of your project are interesting and ambitious. I keep my fingers crossed for success and I will gladly test it.

It may add support for NXDN

You may also want to think about SMS support in the network DMR. There is currently no so-called SMS Center that would receive the SMS and forward it to the sender when it joins the network.

It is worth providing the possibility of building local services available on the local server, via SMS (for example, weather reports, alerts, etc.) or by activating TG or private number to receive voice information. I have done so on HBLink if the user presses PTT to dedicate TG e.g. TG50 will receive voice information e.g. weather condition, weather alerts etc.

Good luck

73 Waldek

@OK-DMR OK-DMR locked and limited conversation to collaborators Jun 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants