Hi all!
I have a question that relates to the logging/recording of the callsigns
that connect to my node.
In the log file - I am seeing "EchoIRLP: connected echolink XXXXXX 1".
When there is a second station that connects in (at the same time) - I am seeing "EchoIRLP: connected echolink XXXXXX 2". The node has limited connections - hence this question.
I am only seeing the initial call sign recorded in the "$LOCAL/echo_call" file.
I am trying to find (I guess?) the EchoIRLP script that is making the log details with the "connected echo link" reference - however thus far -
without avail. I am hoping that this command line will help point me in the direction as to where the initial/additional/subsequent connection details are sourced.
Can anyone advise what script is picking up these connection details and where/if I am able to see these details as I am wishing to extract this
data for notification purposes.
Appreciate your assistance - Hope everyone is well?
Dave,
VK4DAK
On 01-30-21 17:07, VK4DAK wrote to echoirlp@groups.io <=-
Hi all!
I have a question that relates to the logging/recording of the
callsigns that connect to my node.
In the log file - I am seeing "EchoIRLP: connected echolink XXXXXX 1". When there is a second station that connects in (at the same time) - I
am seeing "EchoIRLP: connected echolink XXXXXX 2". The node has limited connections - hence this question.
I am only seeing the initial call sign recorded in the
"$LOCAL/echo_call" file.
I am trying to find (I guess?) the EchoIRLP script that is making the
log details with the "connected echo link" reference - however thus far
- without avail. I am hoping that this command line will help point me
in the direction as to where the initial/additional/subsequent
connection details are sourced.
On 01-30-21 18:35, VK4DAK wrote to echoirlp@groups.io <=-
Thanks for your reply.
I have been looking through all of the EchoIRLP scripts and what files they reference....
The one that "appears" to be similar to the one that I mention is found
in the "echoirlp_status" file
if [ "$1" = "connected" ]; then
if [ "$2" = "echolink" ]; then
"$ECHO_SCRIPT"/echo_inbound $3 $4 $5
elif [ "$2" = "outbound" ] ; then
"$ECHO_SCRIPT"/call_status $3 $4 $5
fi
fi
I am trying to achieve this via the custom_on file rather than mess
with existing EchoIRLP files
What I am wishing to achieve is something similar to (still working on
my syntax/crash management):
# Record Callsign Details in Text File
if [ "$1" = "connected" ] && [ "$2" = "echolink" ]; then
cat ("$ECHO_SCRIPT"/echo_inbound $3) >>
$CUSTOM/data/record_call.txt fi
I cannot find reference to $3 input in the echo_inbound script....
The only reference is:
if [ "$CUSTOM_ON" = "YES" ] ; then
if [ -f $CUSTOM/custom_on ] ; then
$CUSTOM/custom_on "$1" "$2" "$3" "$4"
fi
fi
I am trying to basically extract the connected callsign only and cat
that to the record_call.txt file for reference. I am wishing for it to
be done "live" rather than run a batch script to extract the same data from the log file.
Looks like I may have got it working....That will work, at least for inbound connections. If you wanted to log outbound connections as well, then you'd need to add another identical
I have modified the "echoirlp-status" file to the following:
if [ "$1" = "connected" ]; then
if [ "$2" = "echolink" ]; then
"$ECHO_SCRIPT"/echo_inbound $3 $4 $5
#
echo $3 >> /home/irlp/custom/data/record_call.txt
#
elif [ "$2" = "outbound" ] ; then
"$ECHO_SCRIPT"/call_status $3 $4 $5
fi
fi
Now - there may be a better way to do this (capture all incoming callsigns)so feedback is always welcome.
The callsign stored in the $LOCAL file appears to be the station that createsthe initial connection.
[Edited Message Follows]not referencing my station in the count.
G'day Tony
Thanks for your response.
Here is an extract of my log file as requested:
Jan 28 2021 07:32:42 +1000 EchoIRLP: connected echolink VK4MGC 1
Jan 28 2021 07:32:49 +1000 EchoIRLP: connected speakfreely VK4DAK-R 2
Jan 28 2021 07:33:42 +1000 EchoIRLP: connected echolink VK2LRB 3
As you can see, there are two inbound active connections (MGC and LRB). I am
Yup, upon further investigation - it looks like the relevant callsigns arereference at $1 in the echo_inbound. I am guessing that since we are referencing the echo_inbound file - this should take care of the IRLP side of callsigns being recorded.
If $1 in custom_on is called, it would possibly make reference to bothIRLP/EL calls, so might be best to stick to the echo_inbound file?
Hi Tony,purposes of this task (hence the quick connections) to see if I could get the scripting to work. Have since reverted back to original settings.
Thanks for your suggestions. I temporarily allowed 2 stations in for the
As it stands, I seem to have it working for the purposes I need (at thisstage).
I will investigate the script a little more now that I know where to lookcorrectly and that my idea path is on the “right track”.
Interesting reading going thru all the scripts and seeing how the magic comestogether!
Yes, this scripting works as what I was aiming.(Inbound), for the desired task.
Personally I am only wishing to collate the individual callsigns connected
For any issues, I can obtain the timestamp details from the log file.True. :) Timestamps are trivially easy to add, if you change your mind. :)
Thanks again for your assistance Tony - as always!You're welcome. :)
| Sysop: | deepend |
|---|---|
| Location: | Calgary, Alberta |
| Users: | 239 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 32:01:15 |
| Calls: | 1,432 |
| Files: | 3,327 |
| Messages: | 358,214 |