[nos-bbs] JNOS & tactical calls

[Harry Stone]

Michael,
     Thanks very much, that should solve my problem!  I had no TacCalls file
at all, I didn't know that how it works.

harry
KD0NFY



On Mon, Mar 28, 2011 at 5:39 PM, Michael Fox - N6MEF <n6mef at mefox.org>wrote:

> Hi Harry,
>
>
>
> Fish, K6FSH was the originator of that code, so perhaps Fish or Maiko may
> comment here on the code details.
>
>
>
> I can comment on the configuration side.  The way it works is it looks for
> a file called “TacCalls” in the JNOS directory.  If the login is found in
> the TacCalls file, then the person is logged in.  If the login is not found
> in the TacCalls file, then the usual call sign validity check is run.  The
> formatting rules for the TacCalls file are:
>
>
>
> 1)  The file is a plain text file
>
> 2)  Lines beginning with “#” are ignored (comments)
>
> 3)  Blank lines are ignored
>
> 4)  Valid tactical calls are listed one per line, beginning in the first
> column.
>
> 5)  White space followed by anything else on the line after each tactical
> call is ignored.
>
>
>
> So our typical TacCalls file looks like:
>
>
>
> # comment
>
> # comment
>
> #
>
> # Tactical Calls for Division ABC
>
> #
>
> abc123                  Division abc, site 123
>
> abc456                  Division abc, site 456
>
>
>
> #
>
> # Tactical Calls for Division 123
>
> #
>
> 123ppp                 Division 123, site ppp
>
>
>
> Etc.
>
>
>
> In our county network, we allow each agency to submit a list of tactical
> calls.  We concatenate them together to form the TacCalls file.  Here’s a
> link to the instructions we provide our folks.  Hope it helps:
> http://www.scc-ares-races.org/packet/SCC_Pkt_Tac_Call_Request_v100913.pdf.
> Note that we require a description next to teach tactical call.  But that is
> an administrative requirement.  It is not required by the code.
>
>
>
> A note on performance:  Our tactical call list current 678 lines long, yet
> we perceive no difference in login speed with or without the tactical call
> lookup.
>
>
>
> Michael
>
> N6MEF
>
>
>
>
>
>
>
> *From:* nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] *On
> Behalf Of *Harry Stone
> *Sent:* Monday, March 28, 2011 2:04 PM
> *To:* TAPR xNOS Mailing List
> *Subject:* [nos-bbs] JNOS & tactical calls
>
>
>
> I see in the config header that tactical call checks can be defined, but
> defining that and re-compiling seems to disable any kind of call sign
> validity check.  Is that by design, or am I just missing something else I
> need to enable or disable?
>
>
>
> The calls I need to be able to accept for login follow this rather loose
> convention:
>
>
>
> 1CGEOC
>
> 1CGEM1
>
> 1CGEM2
>
>
>
> etc.
>
>
>
> Thanks!
>
> harry
>
> KD0NFY
>
>
> --
> Have old memories and young hopes.
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>


-- 
Have old memories and young hopes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20110328/5f89abb5/attachment.html>