In April 2005, W1AQ added Echolink to the repeater.  While it was nice to have, it always caused a conflict with the existing IRLP system that was on the repeater.  IRLP was maintained by Mark, N2PGD in Bristol, on a PL tone of 173.8.  Echolink was setup on a different PL of 88.5.  The reasoning for this was that the two systems would not talk to each other.  There was a few times that both systems became active at the same time.  The other situation was  if someone ran no tone, or the 173.8 tone, audio would not be transmitted through the system and those on Echolink would not hear anyone.  If they talked during a conversation in progress, they would invertly double with someone on the repeater. 

During the 2006, IRLP became troubled and unusable.  There would be times where the received audio would be chattering and we couldn't hear them clearly enough.  Others time, our audio going into IRLP couldn't not be heard.  After Field Day 2006, IRLP was shut down.  Although attempts were made to correct the problems, in the end, we did a new install of the IRLP system.  We also, by mutual agreement, decided to move the node from Bristol to West Warwick, the site of the Echolink installation. ARASNE had discussed in detail of getting EchoIRLP on the system, but had always evaluated the current system safeguards from unlicensed persons accessing the repeater from Echolink.  The trustee set guidelines to have a "allow" list of PC users that could access the system.  Initially this began as just members of ARASNE itself.  We began to relax the policy a little, and then allowed persons who inquired about access.  Although this met the requirements of what we were looking for, the downside was that repeaters and links were also denied access.  Once someone tried to contact the Echolink, and was denied, their call was usually added to the "allow" list.  

Since the time that EchoIRLP was  first released, it's security procedures became more flexible.  It now allowed to block PC users, while having an "allow" list such as Echolink had.  Under this conditions, EchoIRLP was going to become a reality.

The main IRLP node was reinstalled and moved to West Warwick.  Once we knew that we no longer had problems with the node itself. EchoIRLP was added.  It was a test phase, and could be reversed back to the original install.  I am happy to say that we have not had any problems with it since then, and it has been a huge move forward for us.  No longer are conversations with Echolink VOX, but with COS.  Also, no more interruptions from internet users.  They are politely told that the "system is busy with local traffic".  This also means there is only one PL, and most people are using that PL, thus most are heard when someone connects.  We can now allow unrestricted access to repeaters and links without any addition configuring.

Check us out at:

    IRLP Node# 4907 and Echolink Node #147330

IRLP Connect - Dial node number.

Echolink Connect -  Dial * then node number

 IRLP & Echolink Disconnect - 73

See who is currently connected