APPENDIX F
Interoperability with an MSE Corps or Division
Interoperability and Connectivity
a. Interoperability and connectivity between an MSE equipped corps/ division and one that is not equipped with MSE (that is, an Improved Army Tactical Communications System (IATACS) or plain ATACS equipped division) are accomplished in several ways. This appendix focuses on interfacing the ACUS of the MSE and ATACS equipped units in three different ways. Paragraph F-5 describes data communications.
b. The three methods described show how an MSE small extension node switch (SENS) (AN/TTC-48) interfaces with an IATACS switch (AN/TTC-41). Interfacing requires slight modification to existing configurations of the AN/TTC-41 and AN/TTC-48. The three primary methods of making this ACUS interconnection are as follows:
- Method 1, Type V circuit card to Type I circuit card.
- Method 2, Type V circuit card to Type II circuit card.
- Method 3, Type VI circuit card to Type VI circuit card (the preferred method).
Connections and procedures depend on the availability of circuit cards. Close coordination between planners and installers is required.
Interface Method 1--Type V to Type I
a. Method 1 shown in Figure F-1 interfaces the AN/TTC-41 (SB-3614A) using a Type I card to the AN/TTC-48 (SENS) Type V DCO port. Data base entries required to implement method 1 are very minor, but extensive operator intervention is required.
b. Method 1 achieves reliable voice communications across the MSE/ IATACS boundary. The MSE operator must use a TA-312 telephone which is wired in parallel with the SENS DCO terminal to send a 20-Hz ringdown signal to the IATACS operator. Telephone calls cannot be automatically routed across the networks and both operators must intercept and extend calls. Another disadvantage of this approach is the SENS loses its ability to interface with a public switch.
c. Method 1 does not achieve data communications (that is, computer-to-computer) across the MSE/IATACS boundary. Data communications is not achieved because computers (MCS or TACCS) must be configured differently to interface with the ACUS (MSE or IATACS) to which they are connected. With MSE, the computers are configured for digital connection to the DSVT or DNVT. With IATACS, the computers are configured for analog modem connection. These configurations are incompatible with each other.
Figure F-1. MSE-IATACS interface method 1--Type V to Type I.
d. The following procedures are required to network IATACS with MSE using interface method 1.
(1) Directly connect the two switchboards (SBs) with field wire using the two DCO access terminals on the SENS (2-wire DC closure, pulse dial) and a Type I card (2-wire line, ringdown) in the SB-3614A. A TA-312 is attached to the same SENS DCO terminals that send a 20-Hz ringdown signal to the SB-3614A. The signal alerts the IATACS operator that a call is coming in from the MSE operator.
(2) This interface does not allow automatic routing between the two networks. Subscribers in the MSE network are given the SENS call service position number (LNXXXXX) and are required to place all calls to the IATACS network through the SENS operator. Subscribers in the IATACS networks are given the MSE network area code (NYX) and the designated MSE interface number assigned to the DCO line. They are required to place all calls to the MSE network through the IATACS operator.
(a) The MSE operator places all calls to the IATACS network by dialing 5C and cranking the TA-312 thus signaling the IATACS operator. The IATACS operator lets the SB ring for 5 seconds and answers the SB. The SENS operator gives the SB-3614A operator the requested IATACS subscriber number and the SB-3614A operator extends the call to the requested IATACS subscriber. When the IATACS subscriber answers the call, the operator tells him to standby for a call and then presses CALL RELEASE.
(b) The MSE operator intercepts all calls from the IATACS network on the DCO lines. The MSE operator knows of an incoming call from the IATACS network when the TA-312 attached to the shared DCO port rings. The SEN operator lets the TA-312 ring twice and then answers the incoming call on the SENS operator's DNVT. The SENS operator extends calls into the MSE network in the normal manner.
(3) This method does not require any additional circuit cards but requires a TA-312 (from the IATACS network) and some data base changes for operation.
e. SENS procedures required for operation are as follows:
(1) Initialize the SB-4303 with the normal procedures ensuring that the Type V termination card is set with switches to the left for pulse dial.
(2) If required, and upon direction of SYSCON, reprogram terminals 29 and 30 to remove the nonsecure warning tone with these procedures. Reprogram as follows:
FO 06 29 34 000 000 000 000 R
FO 06 30 34 000 000 000 000 R
(3) For each additional terminal, the SENS operator will program the following:
FO 06 TT 34 000 000 000 000 R (TT = terminal number)
FO 08 TT 11 R
(4) Reprogram the switch locator table as follows:
I 02 2 5C R (deletes 5C entry)
FO 02 2 5C 02 11 2 R (adds 5C with new routing)
(5) Connections from the AN/TTC-48 to the AN/TTC-41 will be made with the existing 2-wire interfaces. At the AN/TTC-48, connect to the SEP DCO lines (terminations 29 and 30). At the AN/TTC-41, connect to the two Type I terminals identified by the AN/TTC-41 operator (terminations 11 and 12). These termination numbers at the AN/TTC-41 can be changed to suit the local data base. If additional Type V cards are available at the SENS and Type I cards are available at the SB-3614A, more line interfaces can be added. (One Type V card and one Type I card will provide two additional gateway trunks.) Connecting the additional 2-wire lines to the SENS J-1077 takes place using the receive pair at the J-box.
(6) Once the operator's DNVT is affiliated, dial 5C and crank the TA-312 to access the AN/TTC-41.
NOTE: Ensure the node switch (NS) does not assign commercial access to the SENS trunk group cluster.
f. AN/TTC-41 procedures required for operation are as follows:
(1) Select two Type I terminals and place the mode switch (switches 1 and 3) to the center for RINGDOWN EINE mode and the ON/OFF mode switch (switches 2 and 4) to the right. Assign directory numbers (XXX) to the two Type I terminals with normal procedures. Assign the following to class of service:
FO 06 10 01 000 000 000 R
(2) Assign routing to the MSE network using the local subscriber table with the following:
FO 01 500 10
(3) Connect each of the terminals to the SENS DCO binding posts with WF-16 or WD-1.
(4) The AN/TTC-41 operator calls the SENS operator by dialing the directory number (XXX) assigned to the terminals (Type I card terminations).
g. MSE system planning required for operation is as follows.
NOTE: MSE users could intercept the operator by programming the NS with the 5C (DCO access). However, this is not recommended since a real DCO access or another AN/TTC-48 to AN/TTC-41 network interface could be in operation and the 5C request will not be properly routed.
(1) Publish the SENS call service position DNVT phone number as the operator access the AN/TTC-41 network.
(2) Provide the SENS operator with phone directories for the AN/TTC-41 network and the MSE network since calls from both networks are intercepted at the SENS.
(3) Determine if the adjacent network meets security requirements. Instruct gateway SENS to clear nonsecure warning tone when appropriate.
h. IATACS system planning required for operation is as follows:
(1) Publish the NYX area code of the MSE network plus XXXXXXX (any digit O through 9) as the primary access to MSE (SENS operator intercept). The seven X digits can be assigned at random since they are not actually used for routing. Assign digits that are easy to remember.
(2) Publish the directory number of the Type I terminals (PR-SL-XXXX) as another access to the MSE SENS operator. A fixed directory number could be assigned to simplify the dialing instructions for the network.
(3) The AN/TTC-41 operator should provide the SENS operator with directory assistance in the AN/TTC-41 network.
i. MSE subscriber dialing instructions for calling through SENS/AN/TTC-41 gateway are as follows:
(1) Dial the published directory number for operator assisted calls to the AN/TTC-41 network. The number is LNXXXXX (seven-digit SENS operator's DNVT).
(2) Give the SENS operator the desired IATACS directory number and the SENS operator will give the number to the SB-3614A operator for routing.
j. IATACS subscriber dialing instructions for calling through SENS/AN/TTC-41 gateway are as follows:
(1) Dial the published directory number for operator assisted calls to the MSE network.
(2) The SENS operator answers the call and extends the call into the MSE network after the SENS operator is told (or determines) the MSE number to be called. (The seven-digit MSE number is LNXXXXX.)
Interface Method 2--Type V to Type II
a. Method 2 shown in Figure F-2 is similar to method 1. Method 2 interfaces the AN/TTC-41 (SB-3614A) with the AN/TTC-48 (SENS) Type V DCO port using a Type II card which is a standard available card for the AN/TTC-41. Data base entries required to implement method 2 are very minor.
b. Method 2 also achieves reliable voice communications across the MSE/IATACS boundary, but significant intervention by the SENS operator is required. The TA-312 telephone and AN/TTC-41 operator intervention, as in method 1, are no longer required. Telephone calls cannot be automatically routed across the networks. The SENS operator must extend all calls from or into the IATACS network. Method 2, like method 1, has the disadvantage that the SENS loses its ability to connect to a DCO.
Figure F-2. MSE-IATACS interface method 2--Type V to Type II
c. Method 2 does not achieve data communications across the MSE/IATACS boundary for the same reasons described for method 1.
d. The following procedures are required to network IATACS switching systems with MSE using the SENS Type V DC closure card as a gateway to the AN/TTC-41 Type II common battery card. (See Figure F-2.)
(1) Collocate an MSE SENS AN/TTC-48 with an IATACS AN/TTC-41 and directly connect the two with field wire using the two DCO access terminals on the SENS (2-wire, DC closure, pulse dial) and any two terminals using a Type II termination card (2-wire, common battery, pulse dial) in the AN/TTC-41. When collocation is not possible, the MSE and AN/TTC-41 can interface with AN/TRC-145/151 or TACSAT multichannel systems.
(2) This interface does not allow automated routing between the two networks and requires operator intercept at the SENS AN/TTC-48. Subscribers in the MSE network are given the SENS call service position number (LNXXXXX) and are required to place all calls to the IATACS network through the SENS operator. Subscribers in the IATACS network are given the MSE network area code (NYX) and the telephone drop number assigned to the Type II terminations in the AN/TTC-41 (XXX). They are required to place all calls to the MSE network through the SENS operator.
(3) The SENS operator places calls to the IATACS network by dialing 5C and after receiving dial tone from the AN/TTC-41, directly dials the seven-digit AN/TTC-41 user's directory number.
(4) The SENS operator intercepts all calls from the IATACS network simply by going off-hook with his DNVT. He extends calls into the MSE network in the normal manner and connects the two parties.
NOTE: When receiving a call from the AN/TTC-41, the SENS operator must not depress the CALL ANS push button. It might cause damage to the Type V card at the SENS.
(5) This method does not require any special equipment or additional circuit cards for either the SENS or the AN/TTC-41 (unless more than two gateway trunks are required) but does require some data base entries for operation which follow.
e. SENS procedures required for operation are as follows:
(1) Initialize the SB-4303 with the normal procedures ensuring that the Type V termination card is set with switches to the left for pulse dial.
(2) If required, and upon direction of SYSCON, reprogram terminals 29 and 30 to remove the nonsecure warning tone using the following:
FO 06 29 34 000 000 000 000 R
FO 06 30 34 000 000 000 000 R
(3) For each additional terminal, the SENS operator will program the following:
FO 06 TT 34 000 000 000 000 R (TT = terminal number)
FO 08 TT 11 R
(4) Reprogram the switch locator table as follows:
I 02 2 5C R (deletes 5C entry)
FO 02 2 5C 02 11 2 R (adds 5C with new routing)
(5) Connections from the AN/TTC-48 to the AN/TTC-41 will be made with the existing 2-wire interfaces. At the AN/TTC-48, connect to the SEP DCO lines (terminations 29 and 30). At the AN/TTC-41, connect to the two Type II terminals identified by the AN/TTC-41 operator (terminations 11 and 12). These termination numbers at the AN/TTC-41 can be changed to suit the local data base. If additional Type V cards (MSE) and Type II cards (IATACS) are available, more line interfaces can be added. (One Type V card and one Type II card will provide two additional gateway trunks.) Connecting the additional 2-wire lines to the SENS J-1077 takes place using the receive pair at the J-box.
(6) Once the operator's DNVT is affiliated, dial 5C to access the AN/TTC-41. When dial tone is received, dial the AN/TTC-41 telephone (TA-838) to validate the interface.
NOTE: Ensure the NS does not assign commercial access to the SENS trunk group cluster.
f. AN/TTC-41 procedures required for operation are as follows:
(1) Select two Type II terminals and place the card switch positions to the left for pulse dial. Assign directory numbers (XXX) to the two Type II terminals with normal procedures. Assign the following to class of service:
FO 06 TT 11 000 000 000 000 R (TT = terminal number)
(2) Assign the two Type II terminals to a trunk group as follows:
FO 08 TT BB R
Where:
TT = Type II card terminal numbers.
BB =Trunk group number (10 or above).
NOTE: Using a trunk group authorizes an automatic line hunting to access each Type II termination.
(3) Assign routing to the MSE network using the switch locator table with the following:
FO 02 3 NYX 10 BB O R
Where:
NYX = MSE network area code.
BB = Trunk group number (10 or above).
(4) Connect each of the terminals to the SENS DCO binding posts with WF-16 or WD-1.
(5) The AN/TTC-41 operator has two options in dialing the SENS operator.
(a) One option is for the AN/TTC-41 operator to dial the directory number (XXX) assigned to the terminals (Type II card terminations).
(b) The second option is to dial 9 NYX XXXXXXX as a normal subscriber; XXXXXXX can be any digit, since the routing to MSE will be done using the MSE unit NYX area code. The seven X digits are to fill the dialing memory of the SB-3614 and are not interpreted by either the AN/TTC-41 or the AN/TTC-48. The SENS operator will answer and place a call into the MSE network (parent NS) to verify the interface.
g. MSE system planning required for operation is as follows.
NOTE: MSE users could intercept the operator by programming the NS with 5C (DCO access). However, this is not recommendedsince a real DCO access or another AN/TTC-48 to AN/TTC-41 network interface could be in operation and the 5C request will not be routed properly.
(1) Publish the SENS call service position DNVT phone number as the operator access the IATACS network.
(2) Provide the SENS operator with phone directories for the IATACS network and the MSE network since calls from both networks are intercepted at the SENS.
(3) Determine if the adjacent network meets security requirements. Instruct gateway SEN to clear nonsecure warning tone when appropriate.
h. IATACS system planning required for operation is as follows:
(1) Publish the NYX area code of the MSE network plus XXXXXXX (any digit O through 9) as the primary access to MSE (SENS operator intercept). The seven X digits can be assigned at random since they are not actually used for routing. Assign digits that are easy to remember.
(2) Publish the directory number of the Type II terminals (PR-SL-XXXX) as another access to the MSE SENS operator. A fixed directory number could be assigned to simplify the dialing instructions for the network.
(3) The AN/TTC-41 operator should provide the SENS operator with directory assistance in the IATACS network.
i. MSE subscriber dialing instructions for dialing through the SENS/AN/TTC-41 gateway are as follows:
NYX PR-SL-XXX
Where:
NYX = adjacent corps area code
PR = primary route
SL = switch location
XXXX = local subscriber directory number
(1) Dial the published directory number for operator assisted calls to the IATACS network. The number is LNXXXXX (seven-digit SENS operator's DNVT).
(2) Give the SENS operator the desired IATACS directory number and the SENS operator will dial it for you. The seven-digit IATACS subscriber directory number is PR-SL-XXX.
j. IATACS subscriber dialing instructions for dialing through the SENS/AN/TTC-41 gateway are as follows:
(1) Dial the published directory number for operator assisted calls to the MSE network. The SENS operator will answer the call. The IATACS subscriber has two options.
(a) Option 1 is to dial 9 NYX XXXXXXX. (NYX is the MSE unit area code and XXXXXXX is the random access number.)
(b) Option 2 is to dial PR-SL-XXX which is the Type II card.
(2) Give the SENS operator the desired MSE directory number and the SEN operator will dial it for you. The seven-digit MSE subscriber's directory number is LNXXXXX.
Interface Method 3--Type VI to Type VI
a. Method 3 shown in Figure F-3 interfaces the MSE AN/TTC-48 (SENS) to an IATACS AN/TTC-41 network using Type VI tone burst confirmation trunking cards in both systems (NS MSE version or lower software). Data base entries required to implement method 3 are significant. A special analog data base profile is required in the NS which can not be accomplished by the operator with version OY-3.0 SCOLOP.
b. Method 3 achieves reliable voice communications across the MSE/IATACS boundary and allows calls to route automatically between the networks (no operator intervention required). Implementing this method requires installing additional circuit cards (two Type VIs, one Type II, three analog gates, and one DTMF receiver) into the SENS. These cards must be obtained from the IATACS network (AN/TTC-41). This procedure automatically routes calls across the networks and retains the SENS ability to interface with a public switch. The procedure also extends the distance between the SENS and AN/TTC-41 switches using AN/TRC-145 LOS and/or TACSAT AN/TSC-85/93 multichannel.
Figure F-3.MSE-IATACS interface method 3--Type II to Type VI.
c. The Method 3 approach provides the SENS with analog subscriber loop ability using a Type II card. This allows computers in both networks to be configured for analog modem connection; therefore, protocols would be compatible. Using this technique, TACCS data communications across the MSE/IATACS boundary is successful but MCS data communications unsuccessful. The MCS software aborts data transmission before the communications systems achieve terminal connection. Software changes are required to prevent the MCS software from aborting prior to connection.
(1) When the MSE system is expanded as shown in Figure F-4 to provide a more realistic tactical network, TACCS data communications across the MSE/IATACS boundary becomes marginal.
(2) Assessment of test results and research indicates that data transmissions using standard analog modem connections over MSE analog subscriber loops will probably be unreliable over extended tactical networks. In a simple network (Figure F-4), an STU-III secure telephone, connected to the MSE analog subscriber loop (Type II card), provides secure communications. Significant performance degradation will occur over a realistic tactical MSE network due to the increase in analog transmission impairments. Figure F-3 also shows a TACCS (with BLAST software) to DDN connectivity through the MSE DCO port. TACCS with BLAST software will access a CTASC-I over extended distances to send and receive DAMMS-R files and free text messages. As the MSE network is expanded (Figure F-4), data communications degrades.
d. The following procedures are required to network IATACS switching systems with MSE using SENS Type VI 4-wire confirmation trunking cards in the SENS and AN/TTC-41 switching systems.
(1) The SENS operator must affiliate an analog phone with the SENS for each terminal that interfaces the AN/TTC-41. This identifies the terminal as a legal subscriber for access into the MSE network. To use this implementation, the SENS needs additional circuit cards as listed in the implementation specifics section.
Figure F-4. MSE/IATACS expanded network.
(2) In the MSE network, the NSs and LENs need to upload deterministic routing entries into the data base under the direction of SYSCON. SYSCON must assign the IATACS network an NYX area code. Each switch then enters, via the ANY MAMA command, the routing for this NYX. Additionally, the SYSCON must select an LN that will not be assigned within MSE. This LN will be set up in the SENS data base for routing over the trunk group to the IATACS network. If the SENS that is used as a gateway does not have local subscribers connected to it, then this LN need not be reserved. The reason for this is that subscribers in both networks use an area code to reach the other network. e. Connections between the SENS and the AN/TTC-41 are accomplished via 4-wire confirmation trunks. Four confirmation trunks connect these two switches. Figure F-3 shows the appropriate termination numbers and interconnection details.
(1) At the SENS, the following circuit cards shall be added: three analog gates, one DTMF receiver, two Type VI CCA for confirmation trunks, and one Type II CCA to affiliate the confirmation trunks. A TA-838 or equivalent telephone is also required. Install these circuit cards in the following slots:
(a) Analog gates into slots Al9, A21, and A23.
(b) DTMF RCVR into slot A22.
(c) Type II CCA to affiliate the termination that will be used to interface the AN/TTC-41.
(d) Type VI CCA into slots A31 and A35.
(2) It is important to follow the affiliation instructions. At the NS that is to be connected to the SENS, a special analog profile will be set up. The following four numbers with this profile will be preaffiliated: 7600111, 7601111, 7602111, and 7603111. The LN here is 76. This LN needs to match the NN of the IATACS network for proper routing.
f. The affiliation process for the TA-838 is shown in Table F-1.
Table F-1. Affiliation process for TA-838.
Table F-1a. Affiliation process for TA-838. (continued)
Table F-1b. Affiliation process for TA-838. (continued)
Table F-1c. Affiliation process for TA-838. (continued)
Table F-1d. Affiliation process for TA-838. (continued)
(1) Once all cards are in, power on the SB. (Do not cold start.) In program mode, enter the following:
FO 07 21 R
FO 07 22 R
FO 07 23 R
FO 07 24 R
FO 06 21 46 004 000 000 000 R
FO 06 22 46 004 000 000 000 R
FO 06 23 46 004 000 000 000 R
FO 06 24 46 004 000 000 000 R
P 07 R
(2) The four terminations that now have a phone number associated with them have been purposely assigned the wrong class mark for the type of circuit card installed the (Type VI). The FO 07 command places the terminations out of service to allow the modification of the terminations class of service (the FO 06 command).
g. The special analog profiles for the AN/TTC-48 and AN/TTC-41 are listed below.
(1) AN/TTC-48 data base. (See Table F-2.)
Table F-2. AN/TTC-48.
(2) AN/TTC-41 data base. All incoming calls from MSE to the IATACS network depend on SWL table entries that are normally part of the AN/TTC-41 data base. It is important that the NN code of the IATACS network match the LN code that is being used in MSE. (See Table F-3.)
Table F-3. AN/TTC-41.
(3) AN/TTC-47 data base.
(a) At each NS, the operator must enter a route to the 301 (or the assigned NYX) gateway SENS. A special data base must be made also with a modified profile for the analog subscriber numbers to be used for routing from the IATACS network. With NS software version OY-3.0 SCOLOP, this special data base profile cannot be created by the NS operator. Contractor support is required to accomplish the task of creating a special analog data base profile tape; however, this shortcoming will be corrected in the near future.
(b) Subscribers from MSE dial 301 76XXXXX to gain access to the IATACS network. The LN in this application is 76 and can be changed under the direction of SYSCON. This LN has to match the AN/TTC-41 NN for proper automated routing. The XXXXX that is dialed will be the two-digit switch code (XX) and the person's three-digit directory number (XXX). By using this convention, MSE subscribers will connect directly to an IATACS network subscriber without any operator intervention.
(c) Subscribers from the IATACS network who know the MSE subscribers LNXXXXX, dial 9 814 LNXXXXX; otherwise they dial the operator at the gateway AN/TTC-41 for connection to the SENS operator.
a. MCS data communications does not work across the MSE/IATACS boundary (digital/analog) and TACCS communications were marginal due to frequency repeatability degradation above 2000 Hz. Because of the problems experienced with data communications, alternative solutions to using ACUS switched circuits were investigated. The most logical solution for passing data across the MSE/IATACS boundary is to utilize unused channels of the multichannel system connecting the MSE and IATACS switches. Method 3 provides four common-user analog trunks for MSE/IATACS connectivity which leaves eight unused channels that could be dedicated to MCS or TACCS gateway functions. CNR could also be used as a gateway to bridge the MSE/IATACS boundary.
b. An automated MCS gateway/relay solution using the dedicated channel approach was tested and validated over AN/TRC-145 and TACSAT. If an MCS in the MSE network wanted to send a message to an MCS in the IATACS network, he would send the message to the MSE gateway MCS. The MSE gateway MCS would receive the message on channel 1 and examine the message header and nodal address. If the nodal address is a user in the IATACS network, the MSE gateway MCS will automatically relay or route the message out channel 2, over the dedicated multichannel circuit to the IATACS gateway MCS. The IATACS gateway MCS will examine the message header and nodal address and automatically route the call over channel 1 to the appropriate MCS user in the IATACS network.
c. Figure F-5 shows the setup for single MCS gateways. Table F-4 shows system initialization for a single MCS gateway.
Figure F-5. Single MCS gateway.
Table F-4. System initialization--single MCS gateway.
Table F-4a. System initialization--single MCS gateway. (continued)
d. Figure F-6 shows the setup for dual MCS gateway. Table F-5 shows system initialization for dual MCS gateway.
Figure F-6. Dual MCS gateway.
Table F-5. System initialization--dual MCS gateway.
Table F-5a. System initialization--dual MCS gateway. (continued)
e. Table F-6 shows system initialization for the unit MCS.
Table F-6. System initialization--unit MCS
f. Figures F-7 and F-8 show the automatic routing of MCS messages using the relay function.
Figure F-7. MCS gateway/relay MSE-AN/TRC-145-IATACS.
Figure F-8. MCS gateway/relay MSE-TACSAT-IATACS.
Conclusions and Recommendations
a. Method 1 requires an unacceptable level of operator intervention and is not recommended.
b. Method 2 is recommended if requirements can be satisfied with the SENS operator extending all calls from or into the IATACS network. The SENS loses its ability to connect to a public switch, but no additional circuit cards are required to implement this method.
c. Method 3 is recommended where requirements dictate automated call routing across the networks. The SENS retains its ability to connect to a public switch, but additional circuit cards are required to implement this method. The additional circuit cards are not authorized for MSE units and support from the contractor (GTE) is required to provide the special NS analog profile tape.
d. Data transmission using analog modem signals over tactical MSE networks is unreliable due to frequency repeatability and instability above 2000 Hz. Therefore, it is recommended that gateway solutions using dedicated channels be used to bridge the MSE/IATACS (digital/analog) boundary.
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
