Is there a way to change my configuration the same way unticking the echolink enable in the web portal configuration and sending in the server? Would I have to rename the echolink.conf file or is there an easier one place value? Thanks
The way I do that is to add another node to your server and attach Echolink to that new node. Then you can dis/connect your main node to Echolink at will. -- Tim :wq On Jun 23, 2014, at 9:47 AM, Greg <kb1ncj@gmail.com> wrote:
Is there a way to change my configuration the same way unticking the echolink enable in the web portal configuration and sending in the server? Would I have to rename the echolink.conf file or is there an easier one place value? Thanks _______________________________________________ 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.
Bear in mind that, while this is a great solution (I use this myself), outbound Echolink connections can still be made from the node that isn’t defined as Echolink if it’s on the same machine. For example, my radio is on node 2331. I have Echolink on node 25829. So if I want to hear stations connected to me via Echolink, I have to connect 2331 to 28529, both on the same machine. Any station that initiates a connection to my Echolink node connects to 28529. However, even if I have 28529 disconnected from my radio node 2331, I can initiate connections to Echolink nodes, even though the node that incoming connections are on is disconnected. I therefore make it a practice to remotely control 28529 and make all my Echolink connections from there, just to keep things straight in my head. I forget occasionally. BTW, Echolink stations have told me that my node isn’t the only one that does the following thing, so I wonder if anyone knows why, or even better, knows how to fix it. If I have more than, say, 2 or 3 Echolink stations connected, Echolink starts sounding “watery”, or has audio dropouts, or anyway, outgoing audio suffers quite a lot. All downstream audio, that is to say, audio coming into the node and being transmitted out the All Star radio, always sounds fantastic. Asterisk connections sound great both ways. Echolink, however, starts sounding awful for anything coming out of, though not going into, the All Star/Echolink connection. So if you’re listening to my node on Echolink, you’ll hear pretty rotten upstream audio. If you listen locally to all other stations, everything sounds beautiful. My suspicion is some transcoding issue, but I wonder if anyone else has a clue about this? Or am I even explaining it in a way that makes sense? On Jun 23, 2014, at 12:51 PM, Tim Sawyer <tim.sawyer@mac.com> wrote:
The way I do that is to add another node to your server and attach Echolink to that new node. Then you can dis/connect your main node to Echolink at will. -- Tim :wq
On Jun 23, 2014, at 9:47 AM, Greg <kb1ncj@gmail.com> wrote:
Is there a way to change my configuration the same way unticking the echolink enable in the web portal configuration and sending in the server? Would I have to rename the echolink.conf file or is there an easier one place value? Thanks _______________________________________________ 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.
On Mon, Jun 23, 2014 at 12:56 PM, Buddy Brannan <buddy@brannan.name> wrote:
... BTW, Echolink stations have told me that my node isn’t the only one that does the following thing, so I wonder if anyone knows why, or even better, knows how to fix it. If I have more than, say, 2 or 3 Echolink stations connected, Echolink starts sounding “watery”, or has audio dropouts, or anyway, outgoing audio suffers quite a lot. All downstream audio, that is to say, audio coming into the node and being transmitted out the All Star radio, always sounds fantastic. Asterisk connections sound great both ways. Echolink, however, starts sounding awful for anything coming out of, though not going into, the All Star/Echolink connection. So if you’re listening to my node on Echolink, you’ll hear pretty rotten upstream audio. If you listen locally to all other stations, everything sounds beautiful. My suspicion is some transcoding issue, but I wonder if anyone else has a clue about this? Or am I even explaining it in a way that makes sense?
Sounds like a bandwidth issue to me. Unless you're on a symmetric connection, most consumer connections are asymmetric with a much slower upload speed than download. If I'm not mistaken all VOIP connections are UDP so any packet collisions cause those packets to never arrive at the destination. This would explain why the inbound Echolink connections sound fine to you, even when there are many, but the outbound connections don't. Too much data trying to use the limited bandwidth causing dropped packets and missing audio. I'm not intimately familiar with the inner workings of AllStar, but I believe the fact that AllStar functions well along side the flakey Echolink connections stems from using IAX for the inter-Asterisk connections. I'm sure someone will correct me if I'm too far off. Brett KQ9N
I’d agree with you, except that it *only* happens with Echolink connections, and I have a pretty consistent 5mbps upstream speed. On Jun 23, 2014, at 9:27 PM, Brett Friermood <brett.friermood@gmail.com> wrote:
On Mon, Jun 23, 2014 at 12:56 PM, Buddy Brannan <buddy@brannan.name> wrote:
... BTW, Echolink stations have told me that my node isn’t the only one that does the following thing, so I wonder if anyone knows why, or even better, knows how to fix it. If I have more than, say, 2 or 3 Echolink stations connected, Echolink starts sounding “watery”, or has audio dropouts, or anyway, outgoing audio suffers quite a lot. All downstream audio, that is to say, audio coming into the node and being transmitted out the All Star radio, always sounds fantastic. Asterisk connections sound great both ways. Echolink, however, starts sounding awful for anything coming out of, though not going into, the All Star/Echolink connection. So if you’re listening to my node on Echolink, you’ll hear pretty rotten upstream audio. If you listen locally to all other stations, everything sounds beautiful. My suspicion is some transcoding issue, but I wonder if anyone else has a clue about this? Or am I even explaining it in a way that makes sense?
Sounds like a bandwidth issue to me. Unless you're on a symmetric connection, most consumer connections are asymmetric with a much slower upload speed than download.
If I'm not mistaken all VOIP connections are UDP so any packet collisions cause those packets to never arrive at the destination. This would explain why the inbound Echolink connections sound fine to you, even when there are many, but the outbound connections don't. Too much data trying to use the limited bandwidth causing dropped packets and missing audio.
I'm not intimately familiar with the inner workings of AllStar, but I believe the fact that AllStar functions well along side the flakey Echolink connections stems from using IAX for the inter-Asterisk connections.
I'm sure someone will correct me if I'm too far off.
Brett KQ9N
On 6/23/14 12:51 PM, Tim Sawyer wrote:
The way I do that is to add another node to your server and attach Echolink to that new node. Then you can dis/connect your main node to Echolink at will.
I second this method, Tim. Probably the best method; that way, you set up a 'dummy load' echolink host assigned to an allstar node...and, in combination with allmon, you can attach (from a remote site, over https), a connection to your server farm, connect your dummy echo host to the rest of the network, connect to the dummy with a handy echo application, chat away...then disconnect when done. Saves being bothered by (l)users who seem to do nothing but drive-by connections day in and day out. -- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me. Sent from my MacBook Pro.
participants (5)
-
Brett Friermood -
Bryan D. Boyle -
Buddy Brannan -
Greg -
Tim Sawyer