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

Feature request: Multi-site Pirrot #35

Open
tekk opened this issue Jun 1, 2020 · 1 comment
Open

Feature request: Multi-site Pirrot #35

tekk opened this issue Jun 1, 2020 · 1 comment
Assignees

Comments

@tekk
Copy link
Contributor

tekk commented Jun 1, 2020

There are basically three options when you want to build a duplex repeater on PMR446 band and not have your input overloaded by the output:

  1. Make the repeater input in LPD band (50 mW absolute maximum PEP) and output on PMR446 band, and use a sub-1000-EUR duplexer
  2. Buy a duplexer that has offset of 600kHz (this can go up to several thousands of EUR) and have both input and output on PMR446
  3. Make a multi-site repeater where on one site you make input and few kilometers away you make output site. Places are linked with a low latency link, or cable. Both input and outpur are on PMR446 band. This way you don't overload the input receiver.

The multi-site scenario is widely used in duplex repeaters on 10m and 6m amateur bands, since duplexers needed here would cost thousands of EUR.
Is it possible in any manner to make Pirrot work as multi-site duplex repeater? I'm thinking of a low latency TCP/UDP or Websockets link on an open (and forwarded) port (or SSH tunnel) with voice compression (i.e. Speex or Opus, or OGG) which would stream the input from one site to another Pirrot instance on the output site in real time? Both instances would need to have it's IDs, or at least possibility to set the transmission line (IP and port of Pirrot on the output site - to stream audio in real time).
I'm aware that this is not a trivial task to do, and I'm willing to help.
Thanks again for your awesome work on Pirrot!

@allebb allebb self-assigned this Jun 1, 2020
@allebb
Copy link
Owner

allebb commented Jun 1, 2020

Thanks for the feature request Peter. I'll investigate this week about the best way to implement such a feature :) (low-latency, internet based communication between two controllers being the key I guess 👍 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants