I wonder if anyone else got this Email? I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. — Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
Yea I got it on a few of my email address’s that are registered to call signs… Was a broadcast mail… Guess if they block me it’s one less headache to deal with... -- Fredric Moses - W8FSM - WQOG498 fred@moses.bz On Sep 3, 2014, at 10:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
agreed. it's inferior technology anyway. -- Bryan Sent from my iPhone 5...No electrons were harmed in the sending of this message.
On Sep 3, 2014, at 10:57, Fredric Moses <fred@moses.bz> wrote:
Yea I got it on a few of my email address’s that are registered to call signs… Was a broadcast mail… Guess if they block me it’s one less headache to deal with... -- Fredric Moses - W8FSM - WQOG498 fred@moses.bz
On Sep 3, 2014, at 10:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
_______________________________________________ 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.
Personally I would ignore it. Its their loss. I doubt there would be any actual blocking unless there was a flagrant violation taking place. I am certainly not going to worry about it. I have an echolink input on my Allstar hub mainly for convenience as it is mostly the Allstar users away from home using their smart phones that come in on it. Has anyone on Allstar every had a problem with unlicensed infiltration? Actually I would think echolink is easier to infiltrate than IRLP and Allstar just because there are so many gateway software packages into it. Echolink also has the most non-radio communications of any of the ham voip systems. I would say a good percentage of the communications on echolink are computer to computer. Technically you would not even need a license for that. 73 Doug WA3DSP http://www.crompton.com/hamradio From: bdboyle@bdboyle.com Date: Wed, 3 Sep 2014 11:28:00 -0400 To: fred@moses.bz CC: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Fwd: EchoLink Policy Reminder agreed. it's inferior technology anyway. --BryanSent from my iPhone 5...No electrons were harmed in the sending of this message. On Sep 3, 2014, at 10:57, Fredric Moses <fred@moses.bz> wrote: Yea I got it on a few of my email address’s that are registered to call signs… Was a broadcast mail… Guess if they block me it’s one less headache to deal with... -- Fredric Moses - W8FSM - WQOG498 fred@moses.bz On Sep 3, 2014, at 10:55 AM, Buddy Brannan <buddy@brannan.name> wrote: I wonder if anyone else got this Email? I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance? As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous. — Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name _______________________________________________ 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.
BTW, I hate autocorrect. I also hate not hitting all the letters. (Sigh) — Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
On Sep 3, 2014, at 10:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ 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.
Yes, I got it as well... Sent from my iPhone
On Sep 3, 2014, at 10:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ 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.
Did not get that email. We use Echolink for away members to check into our RACES net. It’s a pain in the butt, the huge delays causes doubling with RF stations and cell phone Echolink clients sound like poop. This new (to me) Echolink policy gives me the perfect excuse to turn it off. -- Tim :wq On Sep 3, 2014, at 7:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ 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.
I got the email too not sure what to think.. Loren Tedford (KC9ZHV) Email: lorentedford@gmail.com Email: lorentedford@live.com Email: lorentedford@aol.com Email: LorenCS@Ltcraft.net Email: lorentedford@yahoo.com Email: loren@lorentedford.com <loren@lorentedford.com> Email: loren@richlandcountycomputers.com Phone: 618-553-0806 http://www.lorentedford.com http://www.Ltcraft.net <http://www.ltcraft.net/> http://www.richlandcountycomputers.com http://kc9zhv.lorentedford.com On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ 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.
Morning All Apparently Echolink did a test and Allstarlink allowed them to register a call sign without providing a copy of a valid license, they just needed the Postal and Email address. This is not the way it works for UK License holders, we have to send a copy of our license but is it for US Stations? Regards Jon 2E0RFU ------------ Jon Byrne email@jonbyrne.com On 3 September 2014 18:41, Loren Tedford <lorentedford@gmail.com> wrote:
I got the email too not sure what to think..
Loren Tedford (KC9ZHV) Email: lorentedford@gmail.com Email: lorentedford@live.com Email: lorentedford@aol.com Email: LorenCS@Ltcraft.net Email: lorentedford@yahoo.com Email: loren@lorentedford.com <loren@lorentedford.com> Email: loren@richlandcountycomputers.com Phone: 618-553-0806 http://www.lorentedford.com http://www.Ltcraft.net <http://www.ltcraft.net/> http://www.richlandcountycomputers.com http://kc9zhv.lorentedford.com
On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan <buddy@brannan.name> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ 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.
Allstar is not an enforcement bureau. Neither is Icom, Yeasu, etc. If anyone is on the air without a proper license, I think most of us as hams are capable in knowing what to do. It's not difficult. Personally I am glad to be on a network with rich audio and away from the other undesirable nonsense. I have echolink setup but know with an allow list for emergencies only. Otherwise I would just pull it. Lu Vencl
On Sep 4, 2014, at 4:05 AM, Jon Byrne <email@jonbyrne.com> wrote:
Morning All
Apparently Echolink did a test and Allstarlink allowed them to register a call sign without providing a copy of a valid license, they just needed the Postal and Email address. This is not the way it works for UK License holders, we have to send a copy of our license but is it for US Stations?
Regards
Jon 2E0RFU
------------ Jon Byrne email@jonbyrne.com
On 3 September 2014 18:41, Loren Tedford <lorentedford@gmail.com> wrote: I got the email too not sure what to think..
Loren Tedford (KC9ZHV) Email: lorentedford@gmail.com Email: lorentedford@live.com Email: lorentedford@aol.com Email: LorenCS@Ltcraft.net Email: lorentedford@yahoo.com Email: loren@lorentedford.com Email: loren@richlandcountycomputers.com Phone: 618-553-0806 http://www.lorentedford.com http://www.Ltcraft.net http://www.richlandcountycomputers.com http://kc9zhv.lorentedford.com
On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan <buddy@brannan.name> wrote: I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ 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.
Alternative (since it does have a use...) is to register a node, assign the echolink channel to it, but leave it disconnected unless it's needed (dummy load node?) write a couple scripts that use the allstar management interface to control the node, and build a smartphone-compatible web interface to it. :) it's what i have on my node cluster. That way, you can raise the echo node when YOU need it, and take it down when you don't. Echolink is ancient technology, hasn't been updated in over a decade, but is not entirely worthless, regardless of what the League thinks. I do find it marginally useful when out of range of the NJ/PA network, but am circumspect in how it gets used. Maybe most of the clueless (l)users aren't, but I'm thinking the combined cerebral power of this list isn't in that camp. -- Bryan Sent from my iPhone 5...No electrons were harmed in the sending of this message.
On Sep 4, 2014, at 7:51, Lu Vencl <vencl@att.net> wrote:
Allstar is not an enforcement bureau. Neither is Icom, Yeasu, etc. If anyone is on the air without a proper license, I think most of us as hams are capable in knowing what to do. It's not difficult. Personally I am glad to be on a network with rich audio and away from the other undesirable nonsense. I have echolink setup but know with an allow list for emergencies only. Otherwise I would just pull it.
Lu Vencl
On Sep 4, 2014, at 4:05 AM, Jon Byrne <email@jonbyrne.com> wrote:
Morning All
Apparently Echolink did a test and Allstarlink allowed them to register a call sign without providing a copy of a valid license, they just needed the Postal and Email address. This is not the way it works for UK License holders, we have to send a copy of our license but is it for US Stations?
Regards
Jon 2E0RFU
------------ Jon Byrne email@jonbyrne.com
On 3 September 2014 18:41, Loren Tedford <lorentedford@gmail.com> wrote: I got the email too not sure what to think..
Loren Tedford (KC9ZHV) Email: lorentedford@gmail.com Email: lorentedford@live.com Email: lorentedford@aol.com Email: LorenCS@Ltcraft.net Email: lorentedford@yahoo.com Email: loren@lorentedford.com Email: loren@richlandcountycomputers.com Phone: 618-553-0806 http://www.lorentedford.com http://www.Ltcraft.net http://www.richlandcountycomputers.com http://kc9zhv.lorentedford.com
On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan <buddy@brannan.name> wrote: I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I’ve turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
— Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ 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.
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.
a good options is disable echolink only a call from webtransceiver is active and then enable when the webstransceiver isnt active El jueves, 4 de septiembre de 2014, Bryan D. Boyle <bdboyle@bdboyle.com> escribió:
Alternative (since it does have a use...) is to register a node, assign the echolink channel to it, but leave it disconnected unless it's needed (dummy load node?)
write a couple scripts that use the allstar management interface to control the node, and build a smartphone-compatible web interface to it. :) it's what i have on my node cluster.
That way, you can raise the echo node when YOU need it, and take it down when you don't.
Echolink is ancient technology, hasn't been updated in over a decade, but is not entirely worthless, regardless of what the League thinks. I do find it marginally useful when out of range of the NJ/PA network, but am circumspect in how it gets used.
Maybe most of the clueless (l)users aren't, but I'm thinking the combined cerebral power of this list isn't in that camp.
-- Bryan Sent from my iPhone 5...No electrons were harmed in the sending of this message.
On Sep 4, 2014, at 7:51, Lu Vencl <vencl@att.net <javascript:_e(%7B%7D,'cvml','vencl@att.net');>> wrote:
Allstar is not an enforcement bureau. Neither is Icom, Yeasu, etc. If anyone is on the air without a proper license, I think most of us as hams are capable in knowing what to do. It's not difficult. Personally I am glad to be on a network with rich audio and away from the other undesirable nonsense. I have echolink setup but know with an allow list for emergencies only. Otherwise I would just pull it.
Lu Vencl
On Sep 4, 2014, at 4:05 AM, Jon Byrne <email@jonbyrne.com <javascript:_e(%7B%7D,'cvml','email@jonbyrne.com');>> wrote:
Morning All
Apparently Echolink did a test and Allstarlink allowed them to register a call sign without providing a copy of a valid license, they just needed the Postal and Email address. This is not the way it works for UK License holders, we have to send a copy of our license but is it for US Stations?
Regards
Jon 2E0RFU
------------ Jon Byrne email@jonbyrne.com <javascript:_e(%7B%7D,'cvml','email@jonbyrne.com');>
On 3 September 2014 18:41, Loren Tedford <lorentedford@gmail.com <javascript:_e(%7B%7D,'cvml','lorentedford@gmail.com');>> wrote:
I got the email too not sure what to think..
Loren Tedford (KC9ZHV) Email: lorentedford@gmail.com <javascript:_e(%7B%7D,'cvml','lorentedford@gmail.com');> Email: lorentedford@live.com <javascript:_e(%7B%7D,'cvml','lorentedford@live.com');> Email: lorentedford@aol.com <javascript:_e(%7B%7D,'cvml','lorentedford@aol.com');> Email: LorenCS@Ltcraft.net <javascript:_e(%7B%7D,'cvml','LorenCS@Ltcraft.net');> Email: lorentedford@yahoo.com <javascript:_e(%7B%7D,'cvml','lorentedford@yahoo.com');> Email: loren@lorentedford.com <javascript:_e(%7B%7D,'cvml','loren@lorentedford.com');> Email: loren@richlandcountycomputers.com <javascript:_e(%7B%7D,'cvml','loren@richlandcountycomputers.com');> Phone: 618-553-0806 http://www.lorentedford.com http://www.Ltcraft.net <http://www.ltcraft.net/> http://www.richlandcountycomputers.com http://kc9zhv.lorentedford.com
On Wed, Sep 3, 2014 at 9:55 AM, Buddy Brannan <buddy@brannan.name <javascript:_e(%7B%7D,'cvml','buddy@brannan.name');>> wrote:
I wonder if anyone else got this Email?
I have my Echlin attached to an Allstar node number that only is Echlin. The RF link, which also allows dial in via All Star web transceiver or phone, stays connected to the Echlin All Star node number most of the time, but I can drop that at will. Moreover, I think I've turned off any access to the web transceiver or phone gateway to the Echlin node number. Is there anything else I need to do to be in compliance?
As a side note, all of these regulations against interconnecting systems are getting kind of ridiculous.
-- Buddy Brannan, KB5ELV - Erie, PA Phone: 814-860-3194 Mobile: 814-431-0962 Email: buddy@brannan.name <javascript:_e(%7B%7D,'cvml','buddy@brannan.name');>
Begin forwarded message:
From: "EchoLink Support" <support@echolink.org <javascript:_e(%7B%7D,'cvml','support@echolink.org');>> Subject: EchoLink Policy Reminder To: "EchoLink Node Operators" <>
We wanted to remind you of an important item in EchoLink's access policies (which can be found online at http://www.echolink.org/access_policies.htm).
In general, EchoLink does not permit cross-linking.
More specifically, EchoLink does not permit cross-linking with other VoIP systems that can be accessed off-the-air (for example, directly from a PC or Web browser). This is because other systems may have a validation procedure that is far less comprehensive than EchoLink's, and we want to continue to ensure that EchoLink is solely for use by licensed Amateur Radio operators around the world.
Therefore, while excellent systems such as Zello, AllStar, eQSO, WIRES-II, etc. all serve an important purpose within the Amateur Radio community, our policy is that they cannot be directly connected to a registered EchoLink node.
In other words, your node must function only as a direct RF gateway, and not as a cross-link to another system. If your node is reachable through another path, that path must be disabled when an EchoLink connection is in progress. For example, an EchoIRLP node is permitted, since it functions only as an RF gateway when an EchoLink connection is made.
If you are running Asterisk with app_rpt and an EchoLink channel, be sure it is configured not to allow other VoIP connections when an EchoLink station is connected. If this isn't practical, please disable the EchoLink channel.
Thanks for ensuring that your node adheres to this policy. In some cases we do restrict logins to be sure the policy is being followed.
73 EchoLink Support
(Note: This mailbox is not able to handle replies. For help and information, please see www.echolink.org/support.htm)
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org <javascript:_e(%7B%7D,'cvml','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 <javascript:_e(%7B%7D,'cvml','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 <javascript:_e(%7B%7D,'cvml','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 <javascript:_e(%7B%7D,'cvml','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.
-- Enviado desde EA8EE red movil
In case anyone is interested, my take on the whole Echolink thing is, it's an option that is available, when I want or need it. I use it to connect with my SmartPhone when I'm out of repeater range from my system, or any that are linked to it. Perfect example, I was in Ozona, Tx earlier this week, and echolinked on my phone to my repeater, after disconnecting my nodes from the outside world. Echolinked in at the time the family was going to/from work, so I could talk to them from outside the network. For that, it works great. For me. I'm leaving things as they are. -Geoff/W5OMR
participants (11)
-
Bryan D. Boyle -
Buddy Brannan -
Corey Dean -
Doug Crompton -
ea8ee -
Fredric Moses -
Geoff -
Jon Byrne -
Loren Tedford -
Lu Vencl -
Tim Sawyer