开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Re: Conferencing


 

Gentlemen, I hope you can appreciate the magnitude of
managing a net of this size, with 90% of the nodes
connecting having absolutely no business in the
Conference other than their sheer curiosity. We have
over 200 repeaters on IRLP and Echolink connected, not
to mention the many individual PC users.

It is a nightmare for both Kevin and myself just
managing the internet side of things, much less having
to address the incredible amount of ancillary traffic
that has absolutely nothing to do with the net. I am
absolutely appalled by nodes from BOTH IRLP and Echolink
that connect to an Emergency Response Net and
immediately throw out their call sign without monitoring
first. It is quite obvious that many Amateurs still have
little experience with Emergency nets.

The point to move traffic off of the WX Talk conference
is not because of bandwidth, but one of managing ONLY
the stations that need to report. More than half of the
effort of net control is moving LIDS off the net. This
has certainly been an educational experience if nothing
else, but will certainly lead to some policy
implementation for future nets.

We MUST have node operators that have links to
repeaters, configure their systems to allow Voice Audio
ONLY, without all of the courtesy tones, alerts, hang
times and connect announcements. It should not be
necessary to have all of the extra conferences but it
becomes a necessity... if nothing else, to keep the
interference to a minimum and pass useful traffic from
the affected areas.

I suppose I am tired from having done this duty for the
last three days straight, so I don't want to sound to
harsh, but be assured that we will have information on
the voipwx.net page on exactly where you should connect
during the next event. I appreciate all of the nodes
and repeater owners participating now that continue to
tolerate the problem issues of other operators for the
benefit of the net.

If you wish to experience it first hand, please
volunteer for a Net Control Duty !

Danny Musten KD4RAA
Echolink - IRLP VOIPWXNET Bridge Manager
Raleigh Reflector 9210

-----Original Message-----
From: KC4QLP@... [mailto:KC4QLP@...]
Sent: Friday, August 13, 2004 9:51 PM
To: VOIP-WXNET@...
Subject: Re: [VOIP-WXNET] Conferencing


In a message dated 8/13/04 10:50:52 AM Eastern Daylight
Time, kf4vgx@... writes:



NC control is NC, We don't need two give the same
information twice
to the same person.

Also if your not wanting or have a need for Conferencing
from
Repeaters or links . It should be posted on How were are
expected to
bring our Repeaters and links into the WX-Talk server.




Yep..repeating the info twice only ties up the system
and prevents needed traffic from getting through.
Plus I could not help but notice the message repeated to
the point of insanity asking stations to connect to
other conference nodes.
Question...if the WX_TALK conference can handle up to
300 connecting stations and problems with bandwidth
start to occur at say ,arbitrary number of 150
connections...then why is it stated that the node can
handle 300 stations? Maybe I'm missing something,but I
just wanted to bring that up.

Other than that...all seems well so far today.

My station will be around again tomorrow to keep an eye
on the Elizabeth City area as I'm sure the guys on the
Outer Banks may be up and running tomorrow as Charely
passes through eastern NC

73,


Bob Carter - KC4QLP
--------------------------------------------------------
------------
Echolink RF node 56703 / eQSO crosslink
145.250 VHF repeater,440.850 UHF link,29.630 repeater
--------------------------------------------------------
------------
Owner and moderator of:
Echolink-Open-List@...

AMStereo@...,Freebayhams@...

Join [email protected] to automatically receive all group messages.