开云体育

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

Conferencing


kf4vgx
 

Today a Repeater connected to my Repeater from the effected area.

And was Told by the NC the Basics of what was going on.
He then was told the same thing by another Ham.

The man disconnected his Repeater from my Conference server Repeater.



No reason to give double instructions , You needed that Repeater for
Reports.
Now you may never see this Repeater in your conference server to
offer you reports.


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.

73 KF4VGX


Tony Langdon, VK3JED
 

At 12:14 AM 14/08/2004, you wrote:

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.
Good point. However, some problems don't always become evident until we hit a real live situation. Watching the net today after my shift, I noticed conferencing gave two problems:

1. Less granular control over the stations connecting. This meant that sometimes a whole group of stations might have to be muted, rather than just one.

2. Potential for loops. There seemed to be a couple of loops during the course of the net between 7 and 10:30AM EDT.

The listen only conferences did work well.

My opinion is that stations should connect with multi-conferencing turned OFF. The only stations that should be allowed to conference should be:

Conference rooms providing a listen only service.

Conference rooms providing additional bandwidth to supplement *WX_TALK*

The IRLP <--> Echolink cross link station (usually KD4RAA-L).

Also noticed some confusion among Echolink users about how IRLP works. Because IRLP is DTMF driven, and the DTMF tones are muted, it is not uncommon to have short carrier bursts (1-2 secs) when an IRLP station disconnects. Also, when an IRLP node connects to the reflector, a very short (around 0.25m sec or less) pulse may propagate through to Echolink. These are normal. It requires someone to check on the IRLP side for abnormal operation. Danny, myself and a few others are able to do this.

Anyway, we can work on these little hitches as we go along, it's all a learning curve.

73 de VK3JED


kf4vgx
 

The listen only conferences did work well.


I agree here ,listen only works fine from the RF Side ,not when a
Repeater or link connects to the station with conferencing ,listen
only activated.


73 KF4VGX

over all
Its is working quite well ;-)


 

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 mesage 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@...?



The net is a wild frontier.Dont like what you read,use your delete key.


 



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.


Thats understandable to need to manage stations that are only reporting from the field.
Regarding the LIDS...unfortunately those type will be everywhere and in everything no matter what type of policies are implemented in the future.
To keep LIDS out of everything would require all hams to take an IQ test and hold a PHD.



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.


Education on the proper setup of a link/repeater in connection with VoIP.That is the key.Until then there will be mass problems.
If there were more responsible node ops out there to disable local traffic from getting into the network,then "managing" those nodes not in the effected areas or in a future target zone would not be necessary.

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

I would love to,but over half a million vistors and residents in Northeast NC and the Outer Banks depend on three radio stations here that I'm a part of to get the word out. I cant do both Ham radio and broadcast radio too.
That was proven during many past tropical systems in this area....plus during Isabel,a week and a half non-stop giving information when no area station would do so or were off the air because of the storm.

When it comes to chaos,panicky people,every emergency organization,private organization calling,faxing and stopping by plus getting the latest weather reports and NHC updates....I think I know it all to well.




Bob Carter
Operations/Engineering--Max Media Radio Group/NC Division
WGAI-NewsRadio 560 AM Stereo .., WCXL 104.1 Beach 104..., WQDK 99.3
Q-Country..., WWOC 94.5 WaterCountry 94.5
--------------------------------------------------------------------
Mid-Atlantic Engineering Services--providing radio stations with engineering
services in the middle eastern Atlantic area.E-mail:MidAtlanticEngin@...
--------------------------------------------------------------------
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@...?




 

In a message dated 8/14/2004 2:27:02 AM Eastern Daylight Time, w0jay@... writes:

And yeah there was people conecting and calling CQ. Did you stop and think maybe some of them people that did that was connected to another link that just happended to be connected to the wx_talk server. Not there falt. When I conenected to EDU_Net server it didnt tell me that there was a wx_net. SO maybe your just taking that to far. But who am I?



Point taken ...but when I was learning the ropes of ham radio,I was always taught that that it was good amateur practice to listen first before saying anything,then when I did say something I'd put out a quick question..."is this frequency in use?" instead of rattling out 10 CQ's in a row..which isnt good amatuer practice either.



Hope your freiends and family made out ok through the storm.

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@...?



The net is a wild frontier.Dont like what you read,use your delete key.




 

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@...


Tony Langdon, VK3JED
 

At 12:55 PM 14/08/2004, you wrote:

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's pretty full on there.

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.
Indeed. And the number of people that simply DON'T LISTEN and just jump on and call CQ without waiting to see if there is traffic.

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.
Agreed.

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'm muting one every several minutes on *WX_TALK* at the moment. Most are bouncing/pulsing repeaters, with the odd LID to round it off.

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.
Looks like the subject of further discussion for this group and maybe a Saturday net... :-)


If you wish to experience it first hand, please
volunteer for a Net Control Duty !
Seems when I'm not net control, I'm also doing admin stuff. :-)

73 de VK3JED


Richard Cook
 

A HUGE thank you to you for the net.? I hope I was a positive input.
?
I sayed on as long as the power was avaiable, but now I am on the laptop with dial up, ugg.
?
I think some policies should be in place too.
?
Perhaps in the future have the two links, one for rx only and one for nodes whom are directly in the path only.
?
Remember, you may think, what is one node with noises going to do ? But if a couple do join in, then chaos will run amok.
?
Just my .02
?
No damage here that I can see in the dark.
I am tired and going to bed.
73's and thanks again for the net.
?
?


73's
Richard Cook
W2RAC
IRLP Node 4053
446.950 tone127.3
Port Orange, FL


Do you Yahoo!?
- 50x more storage than other providers!


Jay
 

开云体育

Hey All..
?
Well yes I live in Las Vegas. I also lissend to the net. I have family and friends that live in tampa. Some are hams. I think the net went fine. So what there was some ping pong going on with the repeaters. And yeah there was people conecting and calling CQ. Did you stop and think maybe some of them people that did that was connected to another link that just happended to be connected to the wx_talk server. Not there falt. When I conenected to EDU_Net server it didnt tell me that there was a wx_net. SO maybe your just taking that to far. But who am I?
?
Anyway theres my 2cents. I though it was good net. Good job!!?I did relay some info over to people in st pete and clearwater and tampa.
?
Hope things get better. And look me up if need a net controler? noproblum. Ill do it all the way from sin city.
?

73 W0JAY (Jay)
Oran J Spaulding Jr
Echilink Node? #71794
?


 

Many good observations and comments here.
I'm not necessarily proud of all of them, but there is certainly some truth to them.

This has been a most interesting event and much has been learned.
Primarily, as the size of this net grows, equally do the issues involved in managing and operating it.

The WX-TALK server sits on an OC3, so bandwidth was never an issue. There was one point we were sitting with almost 100 direct connects and I heard a little chop and did wonder if it was related, however it turned out to just be the linked station's connection. BUT, having hundreds of links on a single conference server does present it's own set of challenges and issues to deal with, which I'm sure a lot of you witnessed.

This combined Net Operation has tremendous potential but it will take a lot of effort to perfect it.

We will be introducing an outline soon regarding some sweeping proposed changes that need to be implemented in order for this net to operate effectively and efficiently in the future. This will be open for discussion and input by all... as this is a team effort.

Thanks,
Kevin Anderson
WX-TALK Net Manager
KD5WX