Nodes not connecting with *3, all other functions work

AllStarLink
1

This issue is similar to at least two other posts but with significant differences.

We have a rather strange issue on three nodes and three others in the group have a similar problem.

  1. rpt cmd 58nnn1 ilink 3 55553 ; connects properly from CLI
    *806 ; from mic keypad disconnects properly
    *155553 ; from mic keypad disconnects properly
    rpt cmd 58nnn1 ilink 1 55553 ; disconnects properly from CLI
    rpt fun 58nnn1 *155553 ; disconnects properly from CLI
    ; transmit and receive is identified as
    ; proper from the parrot site.
    *815 ; reports status properly

  2. rpt fun 58nnn1 *355553 ; does NOT connect from CLI
    ; it simply shows next CLI command line.

  3. *355553 ; does NOT connect from mic keypad
    ; CLI shows proper decoding

  4. Call into 58nnn1 ; from other nodes works properly.

  5. Call into 58nnn1 ; from iPhone Repeater Phone works properly.

Everything appears to work normally, except the *3 function. Apparently, something is amiss in rpt.conf [functions] stanza. Mandatory command codes show ‘3 = ilink,3’.

We have rebuilt three different nodes, with 3 different Raspberry Pi 3B+, three different RL-20 boards, and three different SD cards with three different images. The setups use XYL’s NNX node registration on one, and two different NNX node numbers &servers from my call. All behave the same.

Each test is with a single node behind the router. The Calix router on the fiber-optic cable has been replaced.

Suggestions would be appreciated.

2

Are you running asl3-asterisk package version 20.9.1+asl3-3.0.4? This sounds like it’s related to this bug that was fixed in 3.0.4 - app_rpt: Correct 5 digit node lookup from 4 digit node by KB4MDD · Pull Request #372 · AllStarLink/app_rpt · GitHub.

3

Thank you for the quick response.
Yes that update is installed.

This is the CLI response using rpt fun:
node58nnn1*CLI> rpt fun 58nnn1 355553
node58nnn1CLI> rpt fun 58nnn1 355553
node58nnn1CLI>

Another observation when entering from the mic DTMF keypad.
CLI shows decode properly for *35555, but does not decode the last 3.
If trying to connect to a 6 digit NNX, it does not decode the last two digits.
It appears to decode 4-digits, but not five or six.
The RL-20 board shows it is hung up with the COS light staying on for about a minute. Keying does not break the hang-up.

I appreciate your efforts to decipher this.

ASL3 install is so fabulous compared to older ASL2 and brandX.

4

If this is verbatim, you’re missing the *. You need to use:

rpt fun 58nnn1 *355553
5

Apologize. That was typo. This is copy and paste.

Connected to Asterisk 20.9.1+asl3-3.0.4-1.deb12 currently running on node58nnn1 (pid = 4081)
node58nnn1*CLI> rpt fun 58nnn1 355553
node58nnn1CLI> rpt fun 58nnn1 355553
node58nnn1CLI>

6

I notice that the * is deleted and font goes to italic when paste as text. Try again.

Connected to Asterisk 20.9.1+asl3-3.0.4-1.deb12 currently running on node58nnn1 (pid = 4081)
node58nnn1*CLI> rpt fun 58nnn1 355553
node58nnn1CLI> rpt fun 58nnn1 355553
node58nnn1CLI>

7

One more time, perhaps quotes will fix.

Connected to Asterisk 20.9.1+asl3-3.0.4-1.deb12 currently running on node58nnn1 (pid = 4081)
"node58nnn1*CLI> rpt fun 58nnn1 355553"
"node58nnn1CLI> rpt fun 58nnn1 355553"
"node58nnn1CLI> "

8

Interesting.
The editor responds to the * before the remote node by dropping it, then converts the digits font to italics.
The next lines lose its asterisk even before the CLI and the remote node number.

It looks normal on entry, but when reply, the post is reformated.

9

At the cli type core set debug 4 app_rpt.so
Then try your connection. Post the debug messages.

You can turn off the debug messages with core set debug 0 app_rpt.so

10

And wrap anything you don’t want formatting in triple back ticks. That will preserve all formatting and avoid markdown. Woud look like

```
Somthing
Something else
```

11

Thanks for back tick hint.

Connected to Asterisk 20.9.1+asl3-3.0.4-1.deb12 currently running on node58nnn1 (pid = 4081)

node58nnn1*CLI> core set debug 4 app_rpt.so
Core debug was 0 and has been set to 4 for 'app_rpt'.
node58nnn1*CLI> rpt fun 58nnn1 *355553
node58nnn1*CLI>

Interesting. No response here, nothing in logs, nothing in diagnostic reports. Did I miss something?

I certainly appreciate your time and effort.

12

Are you literally typing ‘58nnn1’ ?

13

Good catch. No nnn are digits in my actual 6 digit node number.

14

As an additional trial, in rpt.conf [functions] stanza, I mapped *A to replicate *3.

A = ilink,3

same response as *3 whether using keypad DTMF or CLI > rpt fun.

Using DTMF, CLI does not catch and display but four digits.

Just chatting with two others that are updating nodes. They are also encountering problems connecting. Several can connect with Allmon, but not DTMF.

I can connect with rpt cmd, but not rpt fun or DTMF.

So the issue is not unique to a particular node, operator, or network.

Thanks for comments and help.

15

As another data point, a macro was set.

1 = *355553#

It performs just same as *3 anywhere else. Decodes 4 digits and locks up for aboutn one minute.

16

I can confirm that in normal/stock configurations this works just fine:

Core debug was 0 and has been set to 4 for 'app_rpt'.
node460181*CLI> rpt fun 460181 *348496
node460181*CLI> rpt nodes 460181

************************* CONNECTED NODES *************************

T43211, T45839, T47735, T48496, T527250, T535071, T545661, T54610
T55735, T574079, T58751

Have you customized something in rpt.conf or extensions.conf? I also note that core set debug 4 app_rpt.so seems to have no output for me either.

Do a rpt lookup 55553?

17

The logger configuration in asterisk is not configured to show debug information. Please edit /etc/asterisk/logger.conf. Change the following:

console => notice,warning,error,dtmf
to be
console => notice,warning,error,dtmf,debug

In the cli type logger reload

You can then issue the command core set debug 4 app_rpt.so and attempt the connection.

18

These are the changes in rpt.conf to activate the COS LED on the RL-20 board.

events=events                       ;MOD remove comment to activate events stanza
961 = cop,62,GPIO8=1        ; MOD Send message to GPIO pin8 - turn on COS LED
962 = cop,62,GPIO8=0        ; MOD Send Message to GPIO pin8 - turn off COS LED

[events]
;;;;; Events Management ;;;;;
;status,2 = c|f|RPT_NUMLINKS               ; Say time of day when all links disconne>

58nnn1,*961 = f|t|RPT_RXKEYED               ; MOD Trigger COS when R>
58nnn1,*962 = f|f|RPT_RXKEYED               ; MOD Release COS when R>

I note all changes by a comment with my initials, so I can track changes.
This is corresponding change in simpleusb.conf

[58nnn1](node-main)
gpio8 = out0  ; MOD COS LED

I appreciate that *3 obviously worked in some systems since it was released.

Not only my three nodes but others in our group are encountering similar issues, ie
can connect with Allmon or rpt cmd, but not rpt fun.

One of those does not have the COS commands and was not aware.

I will make a complete new image and update the results.

In meantime, we will retry the console debug suggestion.

Thanks for all the suggestions. We surely appreciate all the time and energy helping us resolve the problem.