Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-df02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 0CFE6380000BB; Sat, 26 May 2012 13:59:45 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1SYLFu-0007CU-9r for rs_out_1@blacksheep.org; Sat, 26 May 2012 18:58:22 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1SYLFt-0007CL-Ke for rsgb_lf_group@blacksheep.org; Sat, 26 May 2012 18:58:21 +0100 Received: from smtpout2.wanadoo.co.uk ([80.12.242.42] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1SYLFi-0003RJ-6V for rsgb_lf_group@blacksheep.org; Sat, 26 May 2012 18:58:20 +0100 Received: from AGB ([2.26.29.3]) by mwinf5d21 with ME id Ehy51j00D041qnW03hy63Z; Sat, 26 May 2012 19:58:08 +0200 Message-ID: <61427033514D45BFB8B2EF71F1852B21@AGB> From: "Graham" To: References: <4FC09C56.40006@psk31.plus.com> In-Reply-To: <4FC09C56.40006@psk31.plus.com> Date: Sat, 26 May 2012 18:58:01 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Antivirus: avast! (VPS 120526-0, 26/05/2012), Outbound message X-Antivirus-Status: Clean X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Ok Thanks I had thought the MM was grouped under /M .. the /B apparently is a requirement for Fixed beacons , may be not in the uk though , however at the moment the Op coding map will not allow , / suffixes to be added to the call sign , there is one user who wants to run the (beacon ?) as maritime mobile .. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.12.242.42 listed in list.dnswl.org] 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 64bc660a83b79b15f4c44d2b2147e02d Subject: Re: LF: Q What are the permitted suffixes to the call these days ? Content-Type: multipart/alternative; boundary="----=_NextPart_000_008E_01CD3B71.79A56C80" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:489360224:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d40d64fc11a113d82 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_008E_01CD3B71.79A56C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ok Thanks=20 I had thought the MM was grouped under /M .. the /B apparently = is a requirement for Fixed beacons , may be not in the uk though , = however at the moment the Op coding map will not allow , / = suffixes to be added to the call sign , there is one user who = wants to run the (beacon ?) as maritime mobile .. =20 The OP-30 second Op05 mode may be added to experimental vhf = beacons, which require the /B to comply with the licensing, there = is a re-vamp of the coding due out soon, which should allow = /P /M /B to be added to the call , I must admit , using Op mobile = did not figure in the envisaged use's ! Tnx -G.. From: g3zjo=20 Sent: Saturday, May 26, 2012 10:03 AM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Q What are the permitted suffixes to the call these = days ? Hey Graham I have a whole collection of BR68's some are dated some are not, best = thing to make sure you were up to date was to chose by how yellow the = paper had become. Now its better to refer to Section 2 Terms, conditions and limitations = document for the UK. First even official Beacons in the UK do not sign /B and no reference is = made in T c & l doc as far as I can see. All other suffixes are merely recommendations and are:- Alternative Address may use /A Temporary Location may use /P Mobile Location may use /M Maritime Mobile may use /MM Aeronautical Mobile I bet these days 'could' be possible T c & l state = 'Without prejudice to Clause 1 of this License... shall not....in any = Aircraft or Airborne Vehicle." Eddie G3ZJO On 26/05/2012 00:21, Graham wrote:=20 Q What are the permitted suffixes to the call these days ? Are /P Portable /M Mobile /B Beacon , Now the only = suffixes in use ? The MM maritime mobile and AM Aeronautical Mobile are now = grouped as / M ? and /A alternative is no longer valid ? Tnx -G. No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2176 / Virus Database: 2425/5021 - Release Date: = 05/25/12 ------=_NextPart_000_008E_01CD3B71.79A56C80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ok Thanks
 
I had thought the MM  was  grouped  under =20 /M   .. the  /B   apparently  is a = requirement=20 for  Fixed  beacons , may  be  not  in = the  uk=20 though , however  at the  moment the  Op  = coding  map=20 will  not  allow , /  suffixes to  be  = added  to=20 the  call sign , there is one  user who  wants to  = run=20 the  (beacon ?)   as  maritime  mobile=20 ..  
 
The  OP-30 second  Op05  mode may be = added =20 to  experimental   vhf  beacons, which  require = the  /B  to  comply with the  licensing,  there = is  a  re-vamp  of the  coding due  = out  =20 soon,  which  should allow   /P  /M  /B = to =20 be  added to the  call , I must admit , using  Op = mobile =20 did  not  figure in the  envisaged  use's !
 
Tnx -G..
 
 

From: g3zjo
Sent: Saturday, May 26, 2012 10:03 AM
Subject: Re: LF: Q What are the permitted suffixes to the = call these=20 days ?

Hey Graham

I have a whole collection of BR68's = some are=20 dated some are not, best thing to make sure you were up to date was to = chose by=20 how yellow the paper had become.

Now its better to refer to = Section 2=20 Terms, conditions and limitations document for the UK.

First even = official Beacons in the UK do not sign /B and no reference is made in T = c &=20 l doc as far as I can see.

All other suffixes are merely = recommendations=20 and are:-

Alternative Address may use /A
Temporary Location = may use=20 /P
Mobile Location may use /M
Maritime Mobile may use=20 /MM

Aeronautical Mobile I bet these days 'could' be possible T c = & l=20 state 'Without prejudice to Clause 1 of this License... shall not....in = any=20 Aircraft or Airborne Vehicle."

Eddie G3ZJO


On = 26/05/2012=20 00:21, Graham wrote:=20
Q  What are the  permitted  suffixes to the =20 call  these days  ?
 
Are   /P   Portable    = /M  =20 Mobile    /B    Beacon   , Now = the =20 only  suffixes  in use ?
 
The  MM  maritime  mobile  and  AM  = Aeronautical  Mobile  are  now  grouped  = as  /=20 M    ?
and  /A   alternative is no longer  valid = ?
 
Tnx -G.

No virus found in = this=20 message.
Checked by AVG - www.avg.com
Version: 2012.0.2176 / = Virus=20 Database: 2425/5021 - Release Date: = 05/25/12


------=_NextPart_000_008E_01CD3B71.79A56C80--