[App_rpt-users] Need a clarification -- please

Fri Dec 26 22:05:18 UTC 2014

hi larry

just wanted to let you know that there is also a shortcut to the *1 *2 
*3 commands. if you use a 0 instead on the node number.
asterisk will act upon the last node the command was sent to also.

example.

*328162 to go to tx. after you send that command to that node. You can 
use the short cut of *20 or *10 to go to monitor or
disconnect. the 0 can be used in place of the node number to send a 
command to the last node that was accessed.
asterisk or app_rpt which is part of the allstar asterisk remembers the 
last node you sent the command to.

the 0 is used as a shortcut. it is not documented very well and not a 
lot of sysop's know about this.

ken n1dot

On 12/26/2014 4:43 PM, larry wrote:
> Mike,
>
> I did not take anything wrong ... My intention was compliment you on 
> answering with a full explanation when I failed to state my question 
> properly.
> I had overlooked that others might search this list for the 
> information I was asking about. After noting your reply it dawned on 
> me my poorly worded request might lead someone to believe that a plain 
> *1, *2, *3 would suffice as a full command rather than a full *328162 
> required for a tranceive mode connection to Node 28162.
> Your answer clarified my oversight.  WELL DONE!
>
> I also appreciate the heads up about the delay possibility you mention.
> Things like that was part of the reason for my asking.  I will keep 
> watch.
>
> My main concern is the time delay switching to the tranceive mode on a 
> monitored link.  Returning to the monitor only mode, transition time 
> shouldn't be an issue.
> Perhaps the monitor only macro should first disconnect then do a fresh 
> reconnect process. Doing it that way should prevent duplicate 
> processes from accumulating over time yet allow a single speedy 
> tranceive transition to occur.
>
> If I learn anything usefull I'll let you know.
>
> Regards
> Larry - N7FM
>
>
>
>
>
>
> On 12/26/2014 10:29 AM, mike at midnighteng.com wrote:
>> Larry,
>>
>> It was meant to be clear enough for those that stumble on it looking at
>> the mail archives.
>> Was not trying to be-little you in any way... sorry if I gave that
>> impression.
>>
>> I can only add a fact of my own experience to this...
>>
>> When I do a lot of switching between tx and rx on a node,
>> It sometimes gets a bit buggy,
>>
>> I have always thought it was just something in my nodes or config but,
>>
>> If you do the same, you might be on the watch for long hang time
>> building up on the connected node when in tx if you are switching back
>> and forth (tx/rx - *2/*3/*2) a lot.
>>
>> I do not get this when I fully disconnect from mon *1/*71 and then con
>> for tx *3.
>>
>> Perhaps someone else may have noticed this ?
>> I have not had the time to track it down as a system reboot (not
>> asterisk restart) is a quick fix when not at the console.
>>
>> ..mike/kb8jnm
>>
>>
>>> -------- Original Message --------
>>> Subject: Re: [App_rpt-users] Need a clarification -- please
>>> From: larry <larry at n7fm.com>
>>> Date: Fri, December 26, 2014 11:38 am
>>> To: app_rpt-users at ohnosec.org
>>>
>>>
>>> Thanks Stan and Mike,
>>>
>>> Being able to toggle between modes is what I needed to know.
>>>
>>> Mike,  I did understand about node numbers needing to be part of the *3
>>> or *2 command but thanks for including that information in your 
>>> explanation.
>>> Since I didn't include the full command structure inside my question
>>> your answer may clarify that point for someone that I may have confused
>>> by not doing so.
>>>
>>> Larry - N7FM
>>>
>>>
>>>
>>>
>>> On 12/26/2014 01:57 AM, mike at midnighteng.com wrote:
>>>> Larry,
>>>>
>>>> Yes for the most part...
>>>>
>>>> *2 29283  -con mon
>>>> *3 29283  -con tx-rx
>>>>
>>>> *3 alone will do nothing
>>>>
>>>> *1 29283  -disconnect only 29283
>>>> *1        -alone will do nothing
>>>> *71       -will disconnect every node connected to you mon or tx
>>>>
>>>> Command is the same live or macro.
>>>>
>>>> You do not need to disconnect (*71 or *1xxxxx) from monitor to switch
>>>> the same node to tx.
>>>>
>>>> Just issue the *3xxxxx
>>>>
>>>>
>>>> ...mike/kb8jnm
>>>>
>>>>
>>>>> -------- Original Message --------
>>>>> Subject: [App_rpt-users] Need a clarification -- please
>>>>> From: larry <larry at n7fm.com>
>>>>> Date: Fri, December 26, 2014 2:52 am
>>>>> To: app_rpt-users at ohnosec.org
>>>>>
>>>>>
>>>>> Going to create some macros but need to understand this sequence 
>>>>> before
>>>>> hand.
>>>>>
>>>>> I want to create a macro that connects a node to another node/hub 
>>>>> in the
>>>>> (*2 monitor only) mode.
>>>>>
>>>>> Later if I wish to change that same connection to a (*3 
>>>>> transceive) mode.
>>>>> Would a macro need to first issue a *1 disconnect and then reconnect
>>>>> with a *3 function or can you just issue the *3 command and toggle
>>>>> directly from monitor to transceive?
>>>>>
>>>>> I assume whatever sequence works in one direction would hold true if
>>>>> going in reverse from tranceive to monitor only.
>>>>>
>>>>> Thanks
>>>>> Larry - N7FM
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> App_rpt-users mailing list
>>>>> App_rpt-users at ohnosec.org
>>>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>>>>
>>>>> To unsubscribe from this list please visit 
>>>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and 
>>>>> scroll down to the bottom of the page. Enter your email address 
>>>>> and press the "Unsubscribe or edit options button"
>>>>> You do not need a password to unsubscribe, you can do it via email 
>>>>> confirmation. If you have trouble unsubscribing, please send a 
>>>>> message to the list detailing the problem.
>>>> _______________________________________________
>>>> App_rpt-users mailing list
>>>> App_rpt-users at ohnosec.org
>>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>>>
>>>> To unsubscribe from this list please visit 
>>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and 
>>>> scroll down to the bottom of the page. Enter your email address and 
>>>> press the "Unsubscribe or edit options button"
>>>> You do not need a password to unsubscribe, you can do it via email 
>>>> confirmation. If you have trouble unsubscribing, please send a 
>>>> message to the list detailing the problem.
>>>>
>>> _______________________________________________
>>> App_rpt-users mailing list
>>> App_rpt-users at ohnosec.org
>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>>
>>> To unsubscribe from this list please visit 
>>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll 
>>> down to the bottom of the page. Enter your email address and press 
>>> the "Unsubscribe or edit options button"
>>> You do not need a password to unsubscribe, you can do it via email 
>>> confirmation. If you have trouble unsubscribing, please send a 
>>> message to the list detailing the problem.
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>> To unsubscribe from this list please visit 
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll 
>> down to the bottom of the page. Enter your email address and press 
>> the "Unsubscribe or edit options button"
>> You do not need a password to unsubscribe, you can do it via email 
>> confirmation. If you have trouble unsubscribing, please send a 
>> message to the list detailing the problem.
>>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit 
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll 
> down to the bottom of the page. Enter your email address and press the 
> "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email 
> confirmation. If you have trouble unsubscribing, please send a message 
> to the list detailing the problem. 