[Logic] Certificates for Calls prior to Upgrading

Tue, 23 Sep 2003 16:27:25 EDT

here is an excerpt from an upcoming FAQ on this issue.
=20
If you need further info let me know.
=20
73, Dave, [email protected]
=20
3. Call Sign Issues

=20

I have an old callsign or two, and I would like to enter logs for those call=
s=20
into LoTW also.  How do I do that?

=20

This is one of the most common questions fielded by the LoTW staff.  The=20
first concept to remember is that each and every different callsign must hav=
e its=20
own certificate.  Every LoTW participant should obtain a certificate for=20
his/her primary callsign=E2=80=94that is, for the callsign that is presently=
 being used in=20
the place where the applicant lives most of the time.  Do not request=20
certificates for additional callsigns until you have received your certifica=
te for=20
your primary callsign.  Once you have received that first certificate for yo=
ur=20
primary call, you can then request additional certificates for your other ca=
lls.=20
 You should use the primary certificate to sign each additional request.  Th=
e=20
TQSLCert program will prompt you to sign those requests and it is strongly=20
recommended that you do so.  Signing the requests allows the LoTW website to=
=20
easily group together all of the QSOs made under your various callsigns  for=
 your=20
viewing pleasure.

=20

LoTW checks the FCC database for existing callsigns for U.S. applicants, so=20
that is why you cannot initially request a certificate for your old callsign=
,=20
which probably isn=E2=80=99t in the database (or your old call has been reis=
sued to=20
someone else, and the data won=E2=80=99t match for your name or address). =20

=20

Stations outside the U.S. also should begin by asking for a certificate for=20
primary callsigns.  After the first certificate for the present callsign is=20
received, then each subsequent request for certificates for old calls should=
 be=20
signed with the present/primary callsign=E2=80=99s certificate.  LoTW will t=
hen be able=20
to keep all the data from old callsigns together with the present callsign=
=E2=80=99s=20
logs in an orderly fashion.

=20

How do I complete the date ranges on the certificate request for my present=20
callsign?

=20

The beginning date for the certificate should either be the issue date of th=
e=20
first license for your call (some calls/licenses have been renewed many=20
times) or the first date of QSOs made with that call.  The ending date shoul=
d be=20
left blank.  Certificates will expire after one year and will be easily rene=
wed.

=20

Do not guess on the dates for any callsign on any certificate!  Some calls=20
have been used more than once, and some have been used many times.  LoTW wil=
l=20
only issue one certificate per callsign for any given date.  If someone atte=
mpts=20
to obtain a certificate for a call that includes a date that is already bein=
g=20
used on another certificate (e.g,. a contest call like VP5B that is issued=20
over and over to different people), the request will be rejected.  If you=20
believe that someone has incorrectly dated a certificate, please send a note=
 to <A HREF=3D"mailto:[email protected]">
[email protected]</A>.=20

=20

How do I complete the date ranges on the certificate request for my old=20
callsign?

=20

The beginning date for the certificate should either be the starting date of=
=20
the first license for that call (some calls/licenses have been renewed many=20
times) or the first date of QSOs made with that call.  The ending date shoul=
d be=20
the last date that QSOs were made with the call, or the expiration date on=20
the license if you have it. =20

=20

Do not guess on the dates for any certificate!  Some calls have been used=20
more than once, and some have been used many times.  LoTW will only issue on=
e=20
certificate per callsign for any given date.  If someone attempts to obtain=20=
a=20
certificate for a call that includes a date that is already being used on an=
other=20
certificate (e.g,. a contest call like VP5B that is issued over and over to=20
different people), the request will be rejected.  If you believe that someon=
e=20
has incorrectly dated a certificate, please send a note to <A HREF=3D"mailto=
:[email protected]">[email protected]</A>.=20

 I operated from a place where no additional license is required (CEPT=E2=
=80=94i.e.,=20
F/NT1N)=E2=80=94what do I need to submit for authentication?

=20

In most cases you cannot get a certificate for a portable call without first=
=20
getting a certificate for your primary call.  After receiving the certificat=
e=20
for your primary call, simply follow the instructions for obtaining a=20
certificate for additional calls.  LoTW is programmed to recognize reciproca=
l=20
operating agreements where known, including the countries participating in t=
he CEPT=20
(European Conference of Postal and Telecommunications Administration) agreem=
ent,=20
and the IARP (International Amateur Radio Permit) Convention.  In most cases=
=20
it will not be necessary to supply additional documentation to obtain a=20
certificate.  However, some DXCC countries that fall within CEPT, such as Cr=
ozet=20
Island (FT5W) will require typical DXCC supporting documentation as noted he=
re=20
https://www.arrl.org/lotw/docreq

=20

Someone else has been issued my old callsign.  I would like to submit logs=20
for that old call to LoTW.  How can I do that?

=20

Assuming that you have received a certificate for your present callsign, thi=
s=20
is a simple problem.  You can request a certificate for your old call using=20=
=20
TQSL Cert but you must be sure that the beginning date for the certificate i=
s=20
either be the starting date of the first license for that call (some=20
calls/licenses have been renewed many times) or the first date of QSOs made=20=
with that=20
call.  The ending date should be the last date that QSOs were made with the=20
call, or the expiration date on the license if you have it. =20

=20

Do not guess on the dates for any certificate!  Some calls have been used=20
more than once, and some have been used many times.  LoTW will only issue on=
e=20
certificate per callsign for any given date.  If someone attempts to obtain=20=
a=20
certificate that includes a date that is already being used on another=20
certificate for that call (i.e.,. a contest call like VP5B that is issued ov=
er and over=20
to different people), the request will be rejected.  If you believe that=20
someone has incorrectly dated a certificate, please send a note to <A HREF=
=3D"mailto:[email protected]">
[email protected]</A>.=20

 I am trying to get a certificate for my present U.S. call, which begins wit=
h=20
an A (like AA9AK).  When I submit the request I receive back a message from=20
LoTW that says the request has date errors.  How do I fix that?

=20

This error usually occurs because someone has requested a certificate for a=20
call that has an invalid start date.  The U.S. did not regularly issue calls=
=20
beginning with =E2=80=9CA=E2=80=9D until after 1976.  If you have entered a=20=
start date before=20
1976, the certificate cannot be issued.  Make sure you have either entered t=
he=20
actual start date for the first QSO you made with your =E2=80=9CA=E2=80=9D c=
all, or the exact=20
issue date of the first license for that call.

=20

I used the same call from several different locations in the same DXCC entit=
y=E2=80=94
I didn=E2=80=99t sign portable.  Do I need a separate certificate for each l=
ocation?

=20

No.  In TQSL you can create as many different station locations (the QTH fro=
m=20
where you operated) as you need.  You will need to consolidate those QSOs=20
from each different location, however.  Once you have parsed your log correc=
tly,=20
you then sign those log extracts with your primary certificate, but make sur=
e=20
you select the correct station location for that particular log extract.

=20

If you signed with a portable, such as NT1N/6, or NT1N/R, you should obtain=20=
a=20
separate certificate for those calls.  Remember, those stations who worked=20
you as NT1N/6 will not get a match to their data if you sign your NT1N/6 log=
=20
with your NT1N certificate=E2=80=94each QSO you submit will be tagged with N=
T1N instead=20
of the correct NT1N/6.

=20

I changed my call=E2=80=94do I need another certificate?  Can I still access=
 my old=20
data?

=20

Yes.  You can continue to access your old data records with your existing=20
password.  When you request a certificate for the new call, make sure to sig=
n the=20
request with the certificate for your previous call so that all your records=
=20
will continue to be tied together.

=20

I am a QSL Manager.  Do I need to have separate certificates for each call I=
=20
manage? Are there other requirements for me and my client(s)?

=20

Yes.  QSL managers and their clients will have to show the LoTW administrato=
r=20
proof that the authority to participate in LoTW has been granted.  A client=20
station owner/operator who resides permanently outside the United States,=20
should submit a note of permission, a license copy, and a copy of one other=20
official document, via postal mail to the LoTW Administrator, 225 Main St.,=20
Newington, CT 06111, USA.  This note should specifically authorize the QSL m=
anager to=20
participate in LoTW.  This situation will be relevant when the client statio=
n=20
does not choose to participate in LoTW himself, i.e., he does not want to=20
obtain a certificate and send the logs to LoTW directly. =20

=20

QSL managers for temporary stations, or DXpedition stations, will have to=20
submit the normal license and other necessary documentation via the postal m=
ail=20
to the LoTW Administrator after they apply for a certificate for the managed=
=20
call.  The QSL Manager should have previously obtained a certificate for his=
=20
primary call.

=20

There may be other important issues with regard to QSL managers and LoTW, so=
=20
feel free to write <A HREF=3D"mailto:[email protected]">[email protected]<=
/A> with any questions.

73,
George K3GV

DX: Long may it live !

If it isn't LOGic, then it isn't LOGging

--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
The reason this message is shown is because the post was in HTML
or had an attachment.  Attachments are not allowed.  To learn how
to post in Plain-Text go to: http://www.expita.com/nomime.html  ---