Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
mdhelp: add a basic sat>ip server setup guide.
  • Loading branch information
Mark Clarkstone authored and perexg committed Nov 10, 2016
1 parent dfcb9d0 commit 9690773
Showing 1 changed file with 48 additions and 11 deletions.
59 changes: 48 additions & 11 deletions docs/class/satip_server.md
@@ -1,17 +1,7 @@
SAT>IP Server is something like DVB network tuner. Tvheadend can
SAT\>IP Server is something like DVB network tuner. Tvheadend can
forward mpegts input streams including on-the-fly descramling to SAT\>IP
clients.

Only networks with the “SAT>IP Source” field set are exported through
the SAT>IP protocol. This field is matched through the “src” parameter
requested by the SAT>IP client. Usually (and by default) this value is 1.
For satellite tuners, this value determines the satellite source (dish).
By specification position 1 = DiseqC AA, 2 = DiseqC AB, 3 = DiseqC BA, 4
= DiseqC BB, but any numbers may be used - depends on the SAT\>IP
client. Note that if you use a similar number for multiple networks, the
first matched network containing the mux with requested parameters will
win (also for unknown mux).

!['SAT\>IP Config tab'](static/img/doc/satipconfig.png)

---
Expand All @@ -28,3 +18,50 @@ Button | Function
<tvh_include>inc/common_button_table_end</tvh_include>

---

###General Information

Only networks with the “SAT>IP Source” field set are exported through
the SAT>IP protocol. This field is matched through the “src” parameter
requested by the SAT>IP client. Usually (and by default) this value
is 1. For satellite tuners, this value determines the satellite source
(dish). By specification position 1 = DiseqC AA, 2 = DiseqC AB, 3 =
DiseqC BA, 4 = DiseqC BB, but any numbers may be used - depends on the
SAT>IP client. Note that if you use a similar number for multiple
networks, the first matched network containing the mux with requested
parameters will win (also applies to unknown muxes).

---

###Basic Configuration Guide

####1. Define the RTSP Port

This can be anything you like, however it is
recommended that you use 9983 (to avoid permission issues). Entering
zero (0) in this field will disable the server.

####2. Export the Tuners

In the *Exported tuners* section enter the
number of tuners (per delivery system) that you'd like to export. This
setting lets the client know how many tuners are available for use.
While you can enter any number you like here, exporting more tuners
than you have can lead to scanning/tuning failures, e.g. "No free tuner".

####3. Export Your Networks

Tvheadend won't export any tuners without any assigned networks, if you
haven't already done so you must enter a *SAT\>IP source number* for
a [network](mpegts_network). If you don't export a network you may see
the following debug error message.

`satips: SAT>IP server announces an empty tuner list to a client <IP ADDRESS OF CLIENT> (missing network assignment)`

####4. Configure Your Client

Hopefully (and if everything went to plan) your client should have
now detected Tvheadend as a SAT\>IP server, if not, you may want to
trigger service discovery or restart it.

---

0 comments on commit 9690773

Please sign in to comment.