RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell...

15
© 2006 MicroBlue Software, LLC 1 eQSO eQSO Ken Behrens KBØYLN © 2006 MicroBlue Software, LLC 2 Description Description eQSO is client / server software designed by Amateur Radio enthusiasts for linking Amateur Radio RF gateways and repeaters via the Internet. The software may be used by licensed Amateur Radio operators and unlicensed Short Wave Listeners (SWL) provided the rules are followed. FOR MORE INFO... www.eQSO.org © 2006 MicroBlue Software, LLC 3 Description (continued) Description (continued) Application written by Paul Davies MØZPD in the UK. Uses Voice over Internet Protocol (VoIP) to connect Ham radios to the Internet. Free software (donations accepted) with online registration required. RADOPS eQSO Presentation 03/27/2006 Page 1 of 15

Transcript of RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell...

Page 1: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

© 2006 MicroBlue Software, LLC 1

eQSOeQSO

Ken BehrensKBØYLN

© 2006 MicroBlue Software, LLC 2

DescriptionDescription

eQSO is client / server software designed by Amateur Radio enthusiasts for linking Amateur Radio RF gateways and repeaters via the Internet. The software may be used by licensed Amateur Radio operators and unlicensed Short Wave Listeners (SWL) provided the rules are followed.

FOR MORE INFO...

www.eQSO.org

© 2006 MicroBlue Software, LLC 3

Description (continued)Description (continued)

Application written by Paul Davies MØZPD in the UK.Uses Voice over Internet Protocol (VoIP) to connect Ham radios to the Internet.Free software (donations accepted) with online registration required.

RADOPS eQSO Presentation03/27/2006

Page 1 of 15

Page 2: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

© 2006 MicroBlue Software, LLC 4

Description (continued)Description (continued)

Differs from EchoLink and IRLP in that it is based on the concept of a radio Net where all listen and talk on the same channel.3 components– PC client– RF Gateway– Conference server

© 2006 MicroBlue Software, LLC 5

Software ComparisonSoftware ComparisonQuick Comparison of Amateur VoIP Systems

Feature IRLP EchoLink eQSO WIRES-II Year first released 1997 2002 (iLINK 2001) 2002 2002 Software and Hardware cost (for connecting a single node) US $

$150 (including CD and suggested

donation)

$0 - 100 (depending on interface used)

$0 - 100 (depending on interface used)

$150 - $180 (selection of online supplier quotes)

PC Access NO YES YES NO Conference Servers YES YES YES YES Connect to multiple nodes (w/o conference server) NO YES NO YES

Group calling NO NO NO YES

DTMF control YES YES YES (Special version only) YES

Operating System Linux (FreeBSD port planned)

Windows (Linux, Mac, Java 3rd party ports)

Windows, Linux (server only, gateway daemon port planned)

Windows

Audio quality Excellent (ADPCM) V.good (GSM) Very Good Good Fair - good

Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No

Number of ports required for firewall configuration (TCP/UDP)

1/20 0/2 0/0 10000/10000

Region of greatest popularity USA, Canada, Australia USA, Europe, Asia Europe Japan

SWL Access (other than local scanner users or streaming audio from selected nodes/conferences)

NO NO YES NO

© 2006 MicroBlue Software, LLC 6

PC ClientPC Client

Runs on your PC.Requires access to Internet via high speed or dial up connection.– Dial up can be very slow and drop

connections.Must allow port 10024 to pass through your firewall.Must have a sound card and headset or speakers.

RADOPS eQSO Presentation03/27/2006

Page 2 of 15

Page 3: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

© 2006 MicroBlue Software, LLC 7

PC Client (continued)PC Client (continued)

Win98/98SE/ME/2000/XP) are supported.Will run on Win95, but not supported.No plans for a native Linux version.– Will run on a Linux platform using

“Wine” (Windows Emulator software).

© 2006 MicroBlue Software, LLC 8

PC Client (continued)PC Client (continued)

To comply with international radio regulations, eQSO restricts SWL (unlicensed users) operation to talking only to other PC users.– Some servers severely limit SWL use. – A few prohibit use by SWL’s.

© 2006 MicroBlue Software, LLC 9

PC Client (continued)PC Client (continued)

May install on multiple machines– General Rules (International some do not apply to the US)

• However (if you have only one call sign) you can only run one at a time.

• DO NOT use the same call sign more than once. (You will be removed from the system).

• If you have multiple call signs, PLEASE DO NOT log in with more than one, unless absolutely necessary.

• Multiple log-ins waste server bandwidth. You risk being removed from the system for wasting bandwidth.

RADOPS eQSO Presentation03/27/2006

Page 3 of 15

Page 4: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

© 2006 MicroBlue Software, LLC 10

RF GatewayRF Gateway

A Gateway (a computer connected to a radio transceiver) facilitates worldwide communications for radio transceivers that normally only have a range of a few miles.Has two functions.– Radio receives local (short range)

amateur radio transmissions. • The audio is fed into soundcard. • eQSO Gateway software sends the voice

© 2006 MicroBlue Software, LLC 11

RF Gateway (continued)RF Gateway (continued)

Some gateways are called 'simplex links' (those with a “-L” suffix) because the Gateway radio transceiver receives and transmits (alternately) on the same frequency.A few Gateways are 'duplex repeaters', (those with a “-R” suffix) which use a separate receiver and transmitter on different frequencies.

© 2006 MicroBlue Software, LLC 12

Conference ServerConference ServerA server hosts rooms on the eQSO system. Click “See who’s on the system” to see the current list of servers. At the top of the list is the main eQSO server.Below that (towards the bottom of the screen) are other servers. Some of these servers have only one or two rooms.

RADOPS eQSO Presentation03/27/2006

Page 4 of 15

Page 5: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

© 2006 MicroBlue Software, LLC 13

Conference Server (continued)Conference Server (continued)

Those without a plus(+) sign are not currently in use. (i.e. room(s) are empty) Rooms are entered in the same way as on the main server. “Open” the server by clicking the (+) sign. Highlight the ROOM you are interested in. Click “connect to selected room” at the top of the screen.

© 2006 MicroBlue Software, LLC 14

Conference Server (continued)Conference Server (continued)

NOTE. Some servers have password only access. Once in a new server, you can change (or create rooms) in the same way as in the main server (providing it has sufficient bandwidth.

© 2006 MicroBlue Software, LLC 15

KBKBØØYLN eQSO ServerYLN eQSO ServerClosed server.– Password controlled access.– Limit of 8 concurrent users.

• May increase if bandwidth permits.Access via port 10024.2 Rooms defined.– RADOPS.

• Connected to Kenwood TS-2000 transceiver.• Tuned to KØFEZ 2m repeater.

– Test Room.• No radio – use for off air conversations.

RADOPS eQSO Presentation03/27/2006

Page 5 of 15

Page 6: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

© 2006 MicroBlue Software, LLC 16

KBKBØØYLN eQSO Server (cond)YLN eQSO Server (cond)You can define your own room.Runs daily 0500-1800L.– Can run other hours by request.

Backup Downtime.– 0001-0830L Sunday full system backup.– 0001-0100L Monday-Saturday incremental

backup.Authorized to distribute & register SWL PC Client to Divan Reps without going through eQSO registration process.

© 2006 MicroBlue Software, LLC 17

ProceduresProcedures

Download software.Register on the eQSO web site.Install and Active software.Configure the Client.Send e-mail request to KBØYLN for password.

FOR MORE INFO...

Download and register software from www.eQSO.org

© 2006 MicroBlue Software, LLC 18

How it all worksHow it all works

Page 1

eQSO System Diagram

Internet

65.101.226.41homebrew

Hub

`

DSL Modem

ZoneAlarm Pro

ZoneAlarm Pro

eQSO Gateway

Kendecom2m Repeater

ICOM440 Repeater

eQSO Client

eQSO Client

KenwoodTS-2000

eQSO Conference Server

RigBlaster PlusSound Card

eQSO Client

RADOPS eQSO Presentation03/27/2006

Page 6 of 15

Page 7: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

© 2006 MicroBlue Software, LLC 19

HandoutsHandouts

System diagram.Screen Shots.eQSO History.

© 2006 MicroBlue Software, LLC 20

Live DemonstrationLive Demonstration

RADOPS eQSO Presentation03/27/2006

Page 7 of 15

Page 8: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

Page 1

eQSO System Diagram

Internet

65.101.226.41homebrew

Hub

`

DSL Modem

ZoneAlarm Pro

ZoneAlarm Pro

eQSO Gateway

Kendecom2m Repeater

ICOM440 Repeater

eQSO Client

eQSO Client

KenwoodTS-2000

eQSO Conference Server

RigBlaster PlusSound Card

eQSO Client

Page 8 of 15

RADOPS eQSO Presentation03/27/2006

Page 9: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

RADOPS eQSO Presentation03/27/2006

Page 9 of 15

Page 10: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

RADOPS eQSO Presentation03/27/2006

Page 10 of 15

Page 11: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

RADOPS eQSO Presentation03/27/2006

Page 11 of 15

Page 12: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

RADOPS eQSO Presentation03/27/2006

Page 12 of 15

Page 13: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

EQSO - Hampedia.com http://www.hamsexy.com/wiki/index.php/EQSO

EQSOFrom Hampedia.com

eQSO is a client server application written by Paul Davies M0ZPD. The system comprises a central server to which any combination of PC clients or RF Gateway Clients can connect. Server administrators and users can set up any number of conference rooms. The most popular room being 101ENGLISH.

Radio Amateurs use their handportable, mobile or fixed radios to transmit into their local RF gateway typically on the VHF and UHF bands. Their voice is packetised and sent over the internet in real time and simultaneously out to all other gateways in the same conference room. These gateways then re-broadcast the voice out on various frequencies across the world depending on which gateways happen to be in the same room - rather like a world wide simplex channel or HF Net. The same thing happens in reverse so two way conversations can take place.

Radio Hams use the system to keep in touch with friends abroad, talk about technical topics or just while away long car journeys. Shortwave listeners (SWL) can also listen in either via a PC connected to the room using PC client software or via their local gateway over the air, much as they do on the shortwave amateur radio bands.

Simple On-line registration is required, the username being the amateur's callsign. Unlicenced listeners will be allocated a SWL callsign and the software will prevent them them talking in any room which has one or more RF gateways present. This ensures that SWL's can talk to each other as well as licenced amateurs (for training purposed) but stops them transmitting (illegally) on the air through RF gateways.

The PC and RF gateway client software is free and can be downloaded from www.eqso.net (http://www.eqso.net) .

eQSO differs from other VoIP systems such as IRLP and Echolink in that it is based on the concept of a radio Net. i.e. everyone sits and listens on the same channel. It is possible for RF users to QSY away from 101ENGLISH using DTMFto a small number of preset rooms e.g. 101GW, 102GW, 103GW etc - rather like moving from the calling channel to a simplex channel either side. PC clients on the other hand have more flexibility and can create their own channel and call itwhat they like.

Once downloaded the software defaults to room 101ENGLISH on the main eQSO server. However, there is nothing to stop users setting up their own private servers which can be made secure through the use of passwords and alternate TCPports.

Retrieved from "http://www.hamsexy.com/wiki/index.php/EQSO"

Categories: VOIP repeater linking | Things to do with Ham Radio

This page was last modified 00:22, 9 November 2005.

RADOPS eQSO Presentation03/27/2006

Page 13 of 15

Page 14: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

Article from an eQSO User

HOW IT ALL BEGAN Around the year 1999 or a little earlier ( we stand to be corrected ) an enterprising young man Adrian, G7WFM, discovered a way to link his 2 metre ham radio equipment to the internet. Not wanting to be in breach of his licensing conditions he made steps to get permission from the powers that be to do this legally. This was granted to him and others followed in his footsteps and from that small beginning we had the new experience of digital VOIP Ham Gateway linking communication in the UK.

It is thought that it was around for some time in the States before the UK had a go at it but it was a major breakthrough for the UK to get the Dinosaurs bones moving in the corridors of power to grant permission. ( Its easier to move Nuclear waste and dump it than to get any decision about Ham radio usage in the UK)Anyway, from that beginning all was not smooth running.The first program to be used was Iphone. This was a commercial server system which was used where a few hams had written programs to adapt its use so that rooms appeared which stations could enter and have contacts similar to room 101english. The problem was that we had no control available as to who came in the room and from time to time the rooms were visited by those who had had brain surgery which had gone wrong.

There were no courtesy tones and it was difficult for the gateway keepers to send station idents from their gateways without chopping up users incoming audio.In 2001 the Iphone server became unstable and again ways around this were devised.After it had settled down a question was put to Dave G4CGB at a club evening at the Hillcrest ARS in Dudley by Paul M0ZPD. “ how is the gateway going then ?”

Dave’s reply was “well, glad you asked because we have no courtesy tones we have no way of putting out idents like a repeater does without chopping users audio , other than that fine we seem to just blunder on, but its great fun”Paul remarked that he would have a go at fixing this and came up with a little bolt on program which did all the missing things. Marvellous !What happened then, you guessed it, 3 weeks later Iphone went belly up and we had nothing for a week or two.

The dedicated gate keepers battled on and several other programs were tried. TEAMSOUND, ROGER WILCO and a few others were tried but were all lacking in some way.In the mean time Paul M0ZPD was busy writing the first version of eQso. It took several versions to get it perfected. The main problem for months was it consumed resources and after an hour your pc locked up and died. The server fell over every hour and in those days users had to be glued to their Pc’s to keep the software going. But it was all worth it hearing all the Dx stations coming in on 2 metres.

Sanity returned to the hobby of VIOP gateway linking towards the end of 2001 when the software versions became stable and from then on Paul has provide us with more control for admins and much better overall views of the system with easier movement from room to room.Up until the early 2002 a good old boy G7WZL John was providing the server on his broadband connection but as new users came along this took up his bandwidth and we went through a spell of lots of packet lost , and I mean lots of packet loss.Then the yanks arrived. Johnny K5JD in Richmond Texas saw we were in need of assistance and has dedicated the spare capacity on his office system since around early in 2002. What a difference it made. Fantastic, clear audio with hardly any breaks and a pleasure to listen to. We owe a lot to the Yanks one way or another. We owe our thanks to Johnny for his provision and trust and hope his system remains available to us to use for many years in the future. Thankyou Johnny from all who use the server.

There are many others who have indeed spent many hours behind the scenes from the beginning

Page 1 of 2Untitled

http://www.eqso.org/eqsoinfo/articles/article1.html

RADOPS eQSO Presentation03/27/2006

Page 14 of 15

Page 15: RADOPS eQSO Presentation 03/27/2006 eQSO€¦ · Scripting interface / API Yes (bash shell script/Linux) Yes (Windows COM) Unsure No Number of ports required for firewall configuration

up until now writing programs, preparing help files, monitoring the rooms (Admins) for none conforming audio noises.Eqso is not a program which runs itself, it has to be carefully monitored and groomed by those who enjoy its provision and agree to help in its function.Thankyou lads for your support.And of course, the users who have had to get used to a new way of communicating with different protocols need a mention here.Well, that’s it, we await a new version which we hope will give us better movement around the rooms using DTMF tones. Paul is working on it right now so stay tuned for the next version coming your way soon.

Dave G4CGB July 2003

Page 2 of 2Untitled

http://www.eqso.org/eqsoinfo/articles/article1.html

RADOPS eQSO Presentation03/27/2006

Page 15 of 15