Still about voice messages : When an Echolink connection occurs, if I have eannmode = 1 in rpt.conf, I can hear the node number. But if I set eanmode=2 (which should spell the callsign), I don't hear anything (only "..connected to MyNode"). Any idea ? Moreover, I'd kile to playback the word "Echolink" somewhere when an Echolink connection occurs. Is it possible to do that ? Thank you in advance. 73 de TK1BI
Hi, Le 03/04/2016 14:56, Toussaint OTTAVI a écrit :
When an Echolink connection occurs, if I have eannmode = 1 in rpt.conf, I can hear the node number. But if I set eanmode=2 (which should spell the callsign), I don't hear anything (only "..connected to MyNode").
Any clues about why Echolink would spell the calling number, but not the callsign ?
Le 06/04/2016 20:38, Toussaint OTTAVI a écrit :
Any clues about why Echolink would spell the calling number, but not the callsign ?
A little bit more strange : - My Echolink node is connected to a hub - My radio node is connected to the same hub If you connect to Echolink, you will hear a callsign, but not your callsign ! A valid callsign, but a totally unknown one !!! At the same time, on the radio node, I can just hear "connected", but no callsign at all... -- After rebooting all, no more callsigns, nowhere...
Just a guess... Missing sound file(s) Conflicting settings echolink.conf and rpt.conf When you hear some other callsign, it will announce the proxy station and not the proxy user for non direct connects. Some proxy's don't have proper handling and that can screw things up. ...mike/kb8jnm
Hi,
Le 03/04/2016 14:56, Toussaint OTTAVI a écrit :
When an Echolink connection occurs, if I have eannmode = 1 in rpt.conf, I can hear the node number. But if I set eanmode=2 (which should spell the callsign), I don't hear anything (only "..connected to MyNode").
Any clues about why Echolink would spell the calling number, but not the callsign ? _______________________________________________ App_rpt-users mailing list App_rpt-users@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.
Le 06/04/2016 23:45, mike@midnighteng.com a écrit :
When you hear some other callsign, it will announce the proxy station and not the proxy user for non direct connects. Some proxy's don't have proper handling and that can screw things up.
I'm quite disappointed with the Echolink module. Despite my tries, I didn't manage to have it work as expected. I'm using the Android Echolink client. I do not have any control about what proxy is used. Sometimes, I hear an unknown callsign. But most of the time, I hear no callsign at all. I never heard *my* callsign ! Am I the only one having this behaviour ? Moreover, my radio node is connected to a hub. When my Echolink node is also connected to the hub, on the radio, I can hear four quick acute bips before the "normal" bip (remotetx or linkunkeyct). I tried all the CTs, but I didn't find where those are located, and I didn't manage to remove them. When the Echolink node is disconnected from the hub, I do not hear those 4 bips. From where are they coming ? And how to remove / change them ? Thank you in advance...
Your complaint of echolink experience should be directed at echolink. Nobody here can control or enforce poxy's proper handling. Your CT settings are all in rpt.conf unlinkedct=ct2 remotect=ct3 linkunkeyct=ct8 nolocallinkct=1 ; Use unlinkedct if only connected to a local node & [telemetry] ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048) ct2=|t(660,880,150,2048) ct3=|t(440,0,150,4096) ct4=|t(550,0,150,2048) ct5=|t(660,0,150,2048) ct6=|t(880,0,150,2048) ct7=|t(660,440,150,2048) ct8=|t(700,1100,150,2048) ;As far as what the numbers mean, ;(0.0.10.0) ; | | | |-------amplitude ; | | |-----------duration ; | |--------------Tone 2 ; |----------------Tone 1 So you might just look at your config for the node and see what CT is the 4 beeps and look for that setting in the node stanza. ...mike/kb8jnm
Le 06/04/2016 23:45, mike@midnighteng.com a écrit :
When you hear some other callsign, it will announce the proxy station and not the proxy user for non direct connects. Some proxy's don't have proper handling and that can screw things up.
I'm quite disappointed with the Echolink module. Despite my tries, I didn't manage to have it work as expected. I'm using the Android Echolink client. I do not have any control about what proxy is used. Sometimes, I hear an unknown callsign. But most of the time, I hear no callsign at all. I never heard *my* callsign ! Am I the only one having this behaviour ?
Moreover, my radio node is connected to a hub. When my Echolink node is also connected to the hub, on the radio, I can hear four quick acute bips before the "normal" bip (remotetx or linkunkeyct). I tried all the CTs, but I didn't find where those are located, and I didn't manage to remove them. When the Echolink node is disconnected from the hub, I do not hear those 4 bips. From where are they coming ? And how to remove / change them ?
Thank you in advance... _______________________________________________ App_rpt-users mailing list App_rpt-users@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.
Hi, Le 14/04/2016 05:22, mike@midnighteng.com a écrit :
Your complaint of echolink experience should be directed at echolink. Nobody here can control or enforce poxy's proper handling.
It's not a complaint about Echolink ;-) It's a question about the Echolink channel driver for app_rpt. The purpose was to see if other people are experiencing the same problem, or if I'm the only one having this problem (which would imply a problem in my configuration)...
Your CT settings are all in rpt.conf
unlinkedct=ct2 remotect=ct3 linkunkeyct=ct8 nolocallinkct=1 ; Use unlinkedct if only connected to a local node
&
[telemetry] ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
So you might just look at your config for the node and see what CT is the 4 beeps and look for that setting in the node stanza.
That's the problem : none of them has 4 fast high frequency beeps. I also created a "dummy" tone which is easy to recognize (400 Hz during 2 seconds). I put this to every ct I found in rpt.conf. And I still hear 4 (or 5) very fast high frequency beeps when Echolink node is conected to the hub !!! I was wondering if there are some hidden and/or hardcoded CTs. I'll try browse the sourcecode ASAP.
Le 14/04/2016 12:06, Toussaint OTTAVI a écrit :
I was wondering if there are some hidden and/or hardcoded CTs. I'll try browse the sourcecode ASAP.
I found this "hidden" courtesy in app_rpt.c: {"ranger","|t(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,150,0)"} This one is not (re-)defined in my default rpt.conf. According to the source, this "ranger" courtesy is sent when a "RANGER" node is connected. Also, all "RANGER" node numbers should begin with "9". And my Echolink node number, choosed at random, is... 99 ! So, I found my answer ;-) But, what on earth is a "RANGER" node ??? -- Then, I'll try to : - rename my Echolink node number to something else not starting with "9" - redefine the "ranger" ct in rpt.conf. That would allow a "special" ct when the Echolink node is connected (which is an interesting behavior)
To be in compliance/play nice with other All Star nodes, make your Echolink node, if you only intend it to be accessed locally, as opposed to being on a public All Star node for anyone to get directly, start with 1. For instance, attach your echolink node to node 199 and define that in your rpt.conf instead of just 99. -- Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
On Apr 14, 2016, at 6:36 AM, Toussaint OTTAVI <t.ottavi@bc-109.com> wrote:
Le 14/04/2016 12:06, Toussaint OTTAVI a écrit :
I was wondering if there are some hidden and/or hardcoded CTs. I'll try browse the sourcecode ASAP.
I found this "hidden" courtesy in app_rpt.c: {"ranger","|t(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,50,0)(1800,0,60,3072)(0,0,150,0)"} This one is not (re-)defined in my default rpt.conf.
According to the source, this "ranger" courtesy is sent when a "RANGER" node is connected. Also, all "RANGER" node numbers should begin with "9". And my Echolink node number, choosed at random, is... 99 !
So, I found my answer ;-)
But, what on earth is a "RANGER" node ???
-- Then, I'll try to : - rename my Echolink node number to something else not starting with "9" - redefine the "ranger" ct in rpt.conf. That would allow a "special" ct when the Echolink node is connected (which is an interesting behavior) _______________________________________________ App_rpt-users mailing list App_rpt-users@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.
Le 14/04/2016 14:40, Buddy Brannan a écrit :
attach your echolink node to node 199 and define that in your rpt.conf instead of just 99
Hi, Thank you for your comments. Our network will be local only (island-wide, <10 repeaters). It will not be connected to Allstar network for now. I missed the fact "9" was a reserved prefix for "ranger" nodes (even if I have no idea about what "ranger" is). I'll rename the Echolink node to 199, and I think it will do the job. 73 de TK1BI
Here is a very old message about what a Ranger node is. http://ohnosec.org/pipermail/app_rpt-users/2011-November/003369.html I don't know the whole story about them but wanted to inform those interested, what they were about. Sent from my iPhone Bob Prybyzerski 631-960-1051 W2YMM
On Apr 14, 2016, at 8:53 AM, Toussaint OTTAVI <t.ottavi@bc-109.com> wrote:
Le 14/04/2016 14:40, Buddy Brannan a écrit :
attach your echolink node to node 199 and define that in your rpt.conf instead of just 99
Hi,
Thank you for your comments. Our network will be local only (island-wide, <10 repeaters). It will not be connected to Allstar network for now. I missed the fact "9" was a reserved prefix for "ranger" nodes (even if I have no idea about what "ranger" is).
I'll rename the Echolink node to 199, and I think it will do the job.
73 de TK1BI
_______________________________________________ App_rpt-users mailing list App_rpt-users@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.
Not start a new discussion... But 146.55 is not in the band plan here in the Pacific Northwest. We are on 20 KHz channel spacing. 146.52, 146.54, 146.56 etc. -----Original Message----- From: Bob Prybyzerski Sent: Thursday, April 14, 2016 6:45 AM To: Toussaint OTTAVI Cc: <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Echolink : Now hearing four (unwanted) quickbips -> RANGER hidden courtesy Here is a very old message about what a Ranger node is. http://ohnosec.org/pipermail/app_rpt-users/2011-November/003369.html I don't know the whole story about them but wanted to inform those interested, what they were about. Sent from my iPhone Bob Prybyzerski 631-960-1051 W2YMM
On Apr 14, 2016, at 8:53 AM, Toussaint OTTAVI <t.ottavi@bc-109.com> wrote:
Le 14/04/2016 14:40, Buddy Brannan a écrit :
attach your echolink node to node 199 and define that in your rpt.conf instead of just 99
Hi,
Thank you for your comments. Our network will be local only (island-wide, <10 repeaters). It will not be connected to Allstar network for now. I missed the fact "9" was a reserved prefix for "ranger" nodes (even if I have no idea about what "ranger" is).
I'll rename the Echolink node to 199, and I think it will do the job.
73 de TK1BI
_______________________________________________ App_rpt-users mailing list App_rpt-users@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@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.
Understand. For more history see http://www.arrl.org/news/fcc-denies-petition-seeking-to-designate-nationwide... I may be missing something, but don't see a reason RANGER cant be implemented on a node unofficially. It just doesn't accomplish the goal. I like the idea, and wondered what might not have been said to justify the proposed usage. Seems to me the reasoning was sound. Thanks, Bob kk6ecm 73 Sent from iPad
On Apr 14, 2016, at 9:52 AM, Jim <jimw7ry@gmail.com> wrote:
Not start a new discussion... But 146.55 is not in the band plan here in the Pacific Northwest.
We are on 20 KHz channel spacing. 146.52, 146.54, 146.56 etc.
-----Original Message----- From: Bob Prybyzerski Sent: Thursday, April 14, 2016 6:45 AM To: Toussaint OTTAVI Cc: <app_rpt-users@ohnosec.org> Subject: Re: [App_rpt-users] Echolink : Now hearing four (unwanted) quickbips -> RANGER hidden courtesy
Here is a very old message about what a Ranger node is. http://ohnosec.org/pipermail/app_rpt-users/2011-November/003369.html
I don't know the whole story about them but wanted to inform those interested, what they were about.
Sent from my iPhone Bob Prybyzerski 631-960-1051 W2YMM
On Apr 14, 2016, at 8:53 AM, Toussaint OTTAVI <t.ottavi@bc-109.com> wrote:
Le 14/04/2016 14:40, Buddy Brannan a écrit :
attach your echolink node to node 199 and define that in your rpt.conf instead of just 99
Hi,
Thank you for your comments. Our network will be local only (island-wide, <10 repeaters). It will not be connected to Allstar network for now. I missed the fact "9" was a reserved prefix for "ranger" nodes (even if I have no idea about what "ranger" is).
I'll rename the Echolink node to 199, and I think it will do the job.
73 de TK1BI
_______________________________________________ App_rpt-users mailing list App_rpt-users@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@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@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.
Not sure about the four beeps, I've not gotten those and my Echolink is pretty active. There's only one courtesy tone that isn't defined like the others...well, not quite like, anyway. I think it's the one for a remote connect for the remote end. Look for the line in the [Telemetry] stanza called remotetx Sorry, I said it's for the remote end transmit, but to tell you the truth, I'm never sure about that, it may be for when a remote connection is active but plays for local transmissions. Anyway, look for that. The thing about not hearing your call when connecting through a proxy, afraid that really is a thing, yes. It must be something to do with how Echolink is sending the ID information to the node. A direct connect of course always announces the correct call. I'm fairly certain there's nothing that can be done about this. -- Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
On Apr 14, 2016, at 6:06 AM, Toussaint OTTAVI <t.ottavi@bc-109.com> wrote:
Hi,
Le 14/04/2016 05:22, mike@midnighteng.com a écrit :
Your complaint of echolink experience should be directed at echolink. Nobody here can control or enforce poxy's proper handling.
It's not a complaint about Echolink ;-) It's a question about the Echolink channel driver for app_rpt. The purpose was to see if other people are experiencing the same problem, or if I'm the only one having this problem (which would imply a problem in my configuration)...
Your CT settings are all in rpt.conf
unlinkedct=ct2 remotect=ct3 linkunkeyct=ct8 nolocallinkct=1 ; Use unlinkedct if only connected to a local node
&
[telemetry] ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
So you might just look at your config for the node and see what CT is the 4 beeps and look for that setting in the node stanza.
That's the problem : none of them has 4 fast high frequency beeps.
I also created a "dummy" tone which is easy to recognize (400 Hz during 2 seconds). I put this to every ct I found in rpt.conf. And I still hear 4 (or 5) very fast high frequency beeps when Echolink node is conected to the hub !!!
I was wondering if there are some hidden and/or hardcoded CTs. I'll try browse the sourcecode ASAP.
_______________________________________________ App_rpt-users mailing list App_rpt-users@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.
participants (6)
-
Bob Prybyzerski -
Buddy Brannan -
Jim -
kk6ecm -
mike＠midnighteng.com -
Toussaint OTTAVI