From 0a3acc50d00af33a639983b934b5c39f64e893ab Mon Sep 17 00:00:00 2001 From: Simon Date: Fri, 16 Sep 2016 13:59:15 +0100 Subject: [PATCH] More readme updates --- README.TGRewrite | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.TGRewrite b/README.TGRewrite index 9c19c36..5d92fee 100644 --- a/README.TGRewrite +++ b/README.TGRewrite @@ -10,18 +10,19 @@ 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. Rewrite is also enabled if an outbound call is made to a talkgroup and then TG9 is activated -during the callhang period. +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. +talkgroup briefly, as before. Alternatively, you can wait for inbound audio to +re-activate the rewrite, then respond during the CallHang period. 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. +"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.