uhf tacsat /dama multi-service tactics, techniques ... - UHF-Satcom.com
uhf tacsat /dama multi-service tactics, techniques ... - UHF-Satcom.com
uhf tacsat /dama multi-service tactics, techniques ... - UHF-Satcom.com
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
B-4<br />
Table B-1. Information Request Codes<br />
Note: If action states contact NCTAMS – the RSSCs may be contacted for assistance.<br />
Code Condition Action<br />
82 Requested party unknown. Check call<br />
directory and retry.<br />
The requested user or guard does not<br />
exist in the controller database.<br />
83 Cannot add users to this guard.<br />
The requesting party is connected to a<br />
guard and attempted to add user port(s)<br />
to the guard connection.<br />
84 Cannot add a guard to an existing call.<br />
The requesting user is participating in a<br />
call and attempting to add a guard.<br />
85 Requesting party is not authorized to<br />
activate this guard.<br />
The requesting user attempted to activate<br />
a guard, but this user is not authorized to<br />
activate the guard for one of the following<br />
reason:<br />
• The requesting party attempted to<br />
activate a private guard, but is not a net<br />
controller for this guard (All).<br />
• This is a <strong>com</strong>mon guard and <strong>com</strong>mon<br />
guards cannot be activated by a user<br />
(SAC only).<br />
• This <strong>com</strong>mon or private guard is<br />
specified in the <strong>com</strong>munications plan but<br />
is not active at this time (SAC only).<br />
86 Requesting party is not a member of this<br />
private guard.<br />
The requesting user attempted to join a<br />
private guard, but the user is not an<br />
authorized member of this private guard.<br />
87 JMINI controller sends this code.<br />
Requested user’s terminal is unauthorized<br />
or zeroized.<br />
The user‘s terminal is marked in the<br />
controller database as unauthorized or<br />
zeroized.<br />
Check the terminal or network address in the<br />
<strong>service</strong> setup and retry. If the network<br />
address is correct and terminals are active on<br />
the network, the controller may not have<br />
activated the network address. Contact<br />
NCTAMS. (If unable to contact NCTAMS, try<br />
making a conference call.)<br />
Terminal is not at SVC idle. Teardown and<br />
retry the call. (Even if it says SVC idle, try this<br />
procedure first.)<br />
Terminal is not at SVC idle. Teardown and<br />
retry the call. (Even if it says SVC idle, try this<br />
procedure first.)<br />
The JMINI database marked the net guard<br />
address wrong. Contact NCTAMS to correct<br />
error.<br />
OR<br />
The unit requested a private guard and the<br />
NCS has not or is not setting up the <strong>service</strong> to<br />
the network first.<br />
Terminal not listed as part of the private<br />
network.<br />
OR<br />
Called the wrong net guard address (check<br />
<strong>service</strong> set up). Contact NCTAMS.<br />
Ensure terminal called the correct address. If<br />
yes, contact NCTAMS about the address to<br />
determine why it is marked this way.