Can a private note call an offsite public node, and vice-versa?

AllStarLink
1

Hi. I have a private node 4447000 colocated in a Pi with a public node 40980. They can communicate between themselves.

At the bottom of rpt.conf I added complimentary entries so that the private node should take a call from outside, and I have one on the public offsite node trying to communicate.

When the outside node 409843 calls private node 4447000 I see:

NOTICE[364]: chan_iax2.c:9271 socket_process: Rejected connect attempt from 69.125.214.167, request ‘s@radio-secure’ does not exist
Notice the strange space and characters just after ‘request’

Here’s the entries:

409843 = radio@127.0.0.1:4563/409843,NONE
1999 = radio@127.0.0.1:4563/1999,NONE
4447000 = radio@123.987.654.321,4447000,NONE

40980 = radio@127.0.0.1/40980,NONE
409810 = radio@127.0.0.1/409810,NONE
4447000 = radio@127.0.0.1/4447000,NONE
1998 = radio@127.0.0.1/1998,NONE
40981 = radio@192.168.1.6:4570/40981,NONE
409843 = radio@123.456.789.123:4563/409843,NONE

I wonder if anything jumps out at you. Thanks

-Pres W2PW

2 
4447000 = radio@123.987.654.321:PORT/4447000,NONE

Specify the port number. And even though you don’t need to do this on internal connections, I do it anyway as it is likely causing you to overlook it.

https://wiki.allstarlink.org/wiki/Private_nodes

3

OK, I’ll give that a try. Still puzzled about the characters in the error message though

4

You will have to look in your dialplan for that. (extensions.conf)
It may be nothing but the s is likely this
[radio-secure]

exten => 1990,s,rpt,1990

But note there has to be a 1st instruction before a second can use next - n
Likely an error in copy/pasting, but that is a guess. You have to look.

exten => 1990,1,rpt,1990

A second line of instruction ‘could’ look like this

exten => 1990,1,Playback bla bla bla
exten => s,n,rpt,1990

s = SAME or the same extension.

There are lots of shortcuts for the dialplan, and I would suggest as you learn it, use none of them till you fully grasp it. It can complicate debugging.

I never use same, I use next (n) where I will likely adjust with more lines in the plan over time so I don’t have to renumber them.

5

OK, learning more about this mysterious extensions.conf that I’ve been guessing about for so many years

6

Mike,

On this calling node I added the port even though it’s the default, and it works from that direction, outside->in.

409843 = radio@127.0.0.1:4563/409843,NONE
1999 = radio@127.0.0.1:4563/1999,NONE
4447000 = radio@96.57.21.77:4569/4447000,NONE

And while initially failing, inside->out works after this:

40980 = radio@127.0.0.1/40980,NONE
409810 = radio@127.0.0.1/409810,NONE
4447000 = radio@127.0.0.1/4447000,NONE
1998 = radio@127.0.0.1/1998,NONE
40981 = radio@192.168.1.6:4570/40981,NONE
409843 = radio@69.125.214.167:4563/409843,NONE

Mike, please enjoy a beverage of your choice with my compliments.

-Pres

7

Just for the general reader consumption,
There is no default port. There is only a described internal port.
The only place you do not ‘have to use it’ is those described as
radio@127.0.0.1 (internal-local)
But I suggest putting it in there anyway. Don’t be so lazy.
radio@127.0.0.1:4569/

It’s a matter of understanding your config at a glance in one place.
When you have many servers and nodes on them, you will come to appreciate it.

I always add a comment after the string to say what it is as well. ; node on server

1951 = radio@73.117.115.176:8119/1951,NONE ; Echolink -R 804396 on RPTRs

Just my way of doing it. Your mileage may vary.
But I do not have to chase files to see settings.

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.