[App_rpt-users] COP command fail
mike at midnighteng.com
mike at midnighteng.com
Fri Apr 29 00:26:48 UTC 2016
I have always pushed everyone to keep the commands organized.
Like this...
81-
82-
831-
832-
84-
8551-
8552-
8553-
86-
There is a problem if you don't keep them organized.
You can create dups and not realize it.
If you have a command the starts
85
then you can not have one that goes beyond that starting with the same digit(s) like
851
Because asterisk will always execute the first match no matter what (85).
So hopefully, you don't have a command "8" or
other commands that start "851,8512, 85123 )
Since your pad test has started 1234. Try testing abcd instead of numbers and it
could tell you something about what dup numbers you have.
But also make sure that user functions are enabled but it does not sound like that
at all.
So, I really think you just have a structure problem with your commands.
It is more common a problem than you think
but it looks like a duck, quacks like a duck...
Try to fully understand what I wrote above and look at your commands again.
The example above keeps you from making blunders as you expand your capabilities
making new commands. My command list is quite large with many calls to scripts.
I can quickly see when I need to add digits to a array of existing commands to add
a string of new ones.
...mike/kb8jnm
> Mike:
>
> I am further confused. I moved the command to *89 and rebooted. The
> test when like this ...
>
> *891234# - Fail
>
> *89A1B2# - Fail
>
> *89999# - lets try a shorter very different string - Works
>
> *899999# - is 5 char length OK - Works
>
> *898888# ... 7777# .... 2222# .... 1111# - they all work
>
> *891234# - Works
>
> *891234# - Works
>
> and many more worked ... and then it just stopped and I can't find a
> pattern to restart it.
>
> Rebooted, still not working. Very discouraging.
>
> ...STeve - KF5VH
>
>
> On 4/28/2016 5:38 PM, mike at midnighteng.com wrote:
>> Have you tried to assign this to some other command like *88 or *89 and test it ?
>>
>> ....mike/kb8jnm
>>
>>
>>
>>> I found that setting "rpt debug level 7" provided so trace information.
>>> But, I have never seen a list of "mode" numbers. Can any one shed some
>>> light? The command is suppose to say on the RF "1 2 3 4 Pound".
>>> There are two attempts ... 1) rpt fun and 2) rpt cmd.
>>>
>>> KF5VH-AS1*CLI> rpt debug level 7
>>> app_rpt Debugging enabled, previous level: 0, new level: 7
>>> KF5VH-AS1*CLI> rpt fun 42316 *851234#
>>> [Apr 28 16:34:12] NOTICE[3084]: app_rpt.c:4366 cancel_pfxtone:
>>> cancel_pfxfone!![Apr 28 16:34:12] NOTICE[3084]: app_rpt.c:12890
>>> collect_function_digits: digits=8 source=0
>>> [Apr 28 16:34:12] NOTICE[3084]: app_rpt.c:4366 cancel_pfxtone:
>>> cancel_pfxfone!![Apr 28 16:34:12] NOTICE[3084]: app_rpt.c:12890
>>> collect_function_digits: digits=85 source=0
>>> [Apr 28 16:34:12] NOTICE[3084]: app_rpt.c:12523 function_cop: Padtest
>>> entered[Apr 28 16:34:12] NOTICE[3084]: app_rpt.c:12962
>>> collect_function_digits: rv=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:4366 cancel_pfxtone:
>>> cancel_pfxfone!![Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12890
>>> collect_function_digits: digits=851 source=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12529 function_cop: Padtest
>>> len= 1 digits=1[Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12962
>>> collect_function_digits: rv=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:4366 cancel_pfxtone:
>>> cancel_pfxfone!![Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12890
>>> collect_function_digits: digits=8512 source=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12529 function_cop: Padtest
>>> len= 2 digits=12[Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12962
>>> collect_function_digits: rv=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:4366 cancel_pfxtone:
>>> cancel_pfxfone!![Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12890
>>> collect_function_digits: digits=85123 source=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12529 function_cop: Padtest
>>> len= 3 digits=123[Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12962
>>> collect_function_digits: rv=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:4366 cancel_pfxtone:
>>> cancel_pfxfone!![Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12890
>>> collect_function_digits: digits=851234 source=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12529 function_cop: Padtest
>>> len= 4 digits=1234[Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12962
>>> collect_function_digits: rv=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:4366 cancel_pfxtone:
>>> cancel_pfxfone!![Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12890
>>> collect_function_digits: digits=851234# source=0
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12529 function_cop: Padtest
>>> len= 5 digits=1234#[Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:10558
>>> rpt_telemetry: Tracepoint rpt_telemetry() entered mode=19
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:10558 rpt_telemetry:
>>> Tracepoint rpt_telemetry() entered mode=46
>>> [Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12535 function_cop: Padtest
>>> exited[Apr 28 16:34:13] NOTICE[3084]: app_rpt.c:12962
>>> collect_function_digits: rv=3
>>> KF5VH-AS1*CLI> rpt cmd 42316 cop 32 1234#
>>> [Apr 28 16:37:14] NOTICE[3084]: app_rpt.c:12529 function_cop: Padtest
>>> len= 5 digits=1234#[Apr 28 16:37:14] NOTICE[3084]: app_rpt.c:10558
>>> rpt_telemetry: Tracepoint rpt_telemetry() entered mode=19
>>> [Apr 28 16:37:14] NOTICE[3084]: app_rpt.c:10558 rpt_telemetry:
>>> Tracepoint rpt_telemetry() entered mode=46
>>>
>>> ...STeve - KF5VH
>>>
>>>
>>> On 4/27/2016 1:02 PM, Steve Mahler wrote:
>>>> Brett:
>>>>
>>>> Thank you for the suggestion. When I attempt ...
>>>>
>>>> KF5VH-AS1*CLI> rpt cmd 42316 cop 32 1234#
>>>>
>>>> from "asterisk -rvvvvvvv" there is no diagnostic output and no audio.
>>>> I used the occasion to confirm that app_rpt was seeing *851234# as
>>>> touch tones from the RF side.
>>>>
>>>> A search of rpt.conf has three occurrences of /85/. Two inside of
>>>> comments and one is the actual command.
>>>>
>>>> 1) Would rpt cmd 42316 cop 32 1234# normally have diagnostic output?
>>>>
>>>> 2) If not, maybe the audio is not getting out to the TX.
>>>>
>>>> ...STeve - KF5VH
>>>>
>>>> On 4/27/2016 12:22 PM, Brett Friermood wrote:
>>>>> Are you able to get it to function using "rpt cmd <NODE> cop 32 <DTMF
>>>>> string>"?
>>>>>
>>>>> That would help to track down whether there is an issue with defining
>>>>> the command as *85 or not. Given that it worked with *89 there is a
>>>>> possibility *85 is somehow being defined elsewhere in the .conf file
>>>>> or ignored for other reasons.
>>>>>
>>>>> Brett
>>>>>
>>>>> On Wed, Apr 27, 2016 at 11:42 AM, Steve Mahler <kizzy at lusfiber.net
>>>>> <mailto:kizzy at lusfiber.net>> wrote:
>>>>>
>>>>> Good Morning!
>>>>>
>>>>> Previous I had DMTF readback working at command *89. After
>>>>> rejuggling the order (to *85) the command seems to be totally
>>>>> ignored. This is also true if I use rpt fun NODE *851234#. The
>>>>> code fragment looks like ...
>>>>>
>>>>> ;
>>>>> ; <<< 8 >>> BASIC USER COMMANDS
>>>>> ;
>>>>> ; 80=
>>>>> 81=localplay,/var/lib/asterisk/sounds/KF5VH-AS1/receiver-pl-ann
>>>>> 82=status,12 ;Say Time of Day Local
>>>>> 83=cop,55 ;Parrot Once
>>>>> 84=status,11 ;Force ID LOCAL
>>>>> 85=cop,32 ;Test TouchTone *85A1B2#
>>>>> 86=cmd,/etc/asterisk/scripts/wxzip/Alert2
>>>>> 87=autopatchup,context=wxzip,noct=1,farenddisconnect=1,dialtime=20000,quiet=1
>>>>> 88=autopatchup,context=wxzipf,noct=1,farenddisconnect=1,dialtime=20000,quiet=1
>>>>> 89=autopatchup,context=wxzipexf,noct=1,farenddisconnect=1,dialtime=20000,quiet=1
>>>>> ;
>>>>>
>>>>> Any ideas on where to look or how to trace?
>>>>>
>>>>> ...STeve - KF5VH
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> App_rpt-users mailing list
>>>>> App_rpt-users at ohnosec.org <mailto: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
>>>>> visithttp://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.
>
More information about the App_rpt-users
mailing list