Update TGRewrite readme
This commit is contained in:
parent
ff04fea52f
commit
11c869d177
1 changed files with 9 additions and 1 deletions
|
@ -8,13 +8,21 @@ TG Rewrite, when enabled for a slot, rewrites the DST ID of incoming talkgroup
|
|||
traffic to TG9, alowing audio to be heard by any user monitoring TG9 on that
|
||||
slot. If the user then replies on TG9, as long as they key-up during the
|
||||
CallHang period, the DST ID (TG) is again rewritten on the outbound traffic,
|
||||
which transparently maps back to the originating talkgroup.
|
||||
which transparently maps back to the originating talkgroup. Rewrite is also
|
||||
enabled if an outbound call is made to a talkgroup and then TG9 is activated
|
||||
during the callhang period.
|
||||
|
||||
To use a User Activated talk-group, briefly key-up on that talk-group to
|
||||
activate it, then switch back to TG9 and talk as normal. If the CallHang period
|
||||
expires, you may need to activate the talk-group again by keying up on that
|
||||
talkgroup briefly, as before.
|
||||
|
||||
Note, proper ettiquette dictates that the user confirms the repeater is free
|
||||
before activiating this feature. It is best to ensure the slot is keyed from
|
||||
"cold" when activating a talkgroup for rewrite. Although not strictly neccesary,
|
||||
it may be advantageous to also disconnect the repeater from the reflector system
|
||||
first, if using slot 2.
|
||||
|
||||
It is useful to set the CallHang parameter to a generous amount. I am currently
|
||||
using seven seconds.
|
||||
|
||||
|
|
Loading…
Reference in a new issue