So it was a rainy day...and just built up an ASL3 on a HP thin client. That works fins as a repeater controller. I can connec to it from another node, no problem. So decided to see about remote base. And control of my FT-1000D. I added this to the nodes section of rpt.conf:
in [nodes] I added ,Y to the end of the 2428 line, and in the other node I tried to connect to I added the same ,Y on the node 2428 line It won't connect. It did before I added the remote base lines.
On another point I wanted to see if the PC could control the FT-1000D so I also installed hamlib and it does indeed control the rig and read the rig.
Do I have the remote syntax correct? The 2428 node info was placed at the end of rpt.conf by asl-menu so I added the rest of the info in there. Kind of uncertain where the remote stuff goes in ASL3. Also, why phone_functions? I also added the mode control line 6 = remote,6 to functions-remote
Summarizing, the node works perfectly as a conventional ASL box. The PC can control the HF rig. The PC won't "answer" in remote base mode. This is the same problem I have had all along with remote base in ASL3
when in asterisk -r on 2428 I get this error: WARNING[4351][C-00000006]: app_rpt.c:6134 rpt_exec: Node 2428 is not ready yet, rejecting call on IAX2/192.168.1.225:4570-6521
George,
I would check the properties of /dev/ttyUSB0 when you are not running hamlib.
Be sure it can be opened by asterisk for r/w.
You might even 777 it for a test. First having it plugged into the rig.
on issues of dtmf assignment, until you know you are good on that, why not use the command line using remote,x so you know the command is issued.
I've made hamlib work with asterisk before though before ASL3. But I don't want to use hamlib. Cannot (easily) enter freq from the linked allstar radios. I really want to use the remote base in ASL. But beginning to realize that it isn't really working. My test with hamlib was just to see if the box can control the FT1000D. And it does. Remember I said that setting the node up as a plain old repeater or hotspot does in fact allow connections from other nodes but as soon as I add remote=, iport=, iospeed=, etc the node will not accept connections from anywhere. So somehting isn't "turning on" the remote base feature. I even did authevel=0.
So to anybody reading this...has anyone gotten remote base to work in ASL3? If so can you send along your rpt.conf file so I can maybe figure out whet I did incorrectly??
I really like the idea of doing this with the FT1000D since it drives a FL7000 amp and the 1000D controls the band switching on the amp.
just looked this up in the current app_rpt.c and it is line 6225 now, not 6134:
myrpt = NULL;
/* see if we can find our specified one */
for (i = 0; i < nrpts; i++) {
/* if name matches, assign it and exit loop */
if (!strcmp(tmp, rpt_vars[i].name)) {
myrpt = &rpt_vars[i];
if (!myrpt->ready) {
ast_log(LOG_WARNING, "Node %s is not ready yet, rejecting call on %s\n", rpt_vars[i].name, ast_channel_name(chan));
return -1;
}
break;
}
}
I did not notice the error in the listing on the first read.
George,
What exact command did you run when you got this error ?
Guessing you are connecting from some other node inside your NAT.
And that this is a connection error ?
Hope you remember that when defined as a remote base
2428=radio@108.196.236.231:4571/2428,108.196.236.231,y
That 'only one' connection is possible. And don't know what error message happens when a second is tried.
You can run it without the "Y" if that is the issue. That is all the designation really does as far as I have ever found. I think that was to prevent public connections to it when it was listed as a public node and already connected to your main node.
Band limits and commands are all specified in rpt.conf so no application by any other means.
So, outside of that, it is just another node. If there are connection issues, it just goes to node/dialplan setup.
That's not the result of any command, couldn't because the node I was connecting from, 2360, could never connect. These two nodes, 2428 (remote) and 2360 are on the same network and each had an entry in the other's [nodes] list so they could "find" each other. Yes, I'm well aware of "Y" in node statements.
I had tried to connect them without "Y" as just normal nodes, that worked fine. But changing 2428 to remote base "Y" and would not connect and got this error.