Applies to: An already installed MissionLINK 700 system using the terminal and portal shown in quick-start guide PN 3402174-1 Rev B. Confirm the label and firmware before following it. MissionLINK 200 and marine VesseLINK are separate products; do not assume identical menus, wiring or indicators.
Work through these checks
Identify the lights
Let the normal startup finish. On this terminal, System flashing green means booting/busy. Satellite flashing green means acquiring; solid green indicates normal status, while solid blue specifically indicates satellite data passing. A red fault light needs the corresponding alert, not a guess from color alone.
What the result means: System booting/busy, satellite acquisition and satellite data passing are separate stages. Solid blue on the named Satellite light is the data-passing indication; solid green is normal operation, not proof of this application’s successful transfer. Pair any red pattern with its actual alert.
Read the local status
Use your installed Wi-Fi network or an authorized computer on one of the three LAN ports. The separately marked WAN port is for an upstream network and is not the same connection. On the terminal network, open http://portal.thaleslink exactly; do not append .com. Use your current authorized login. Wi-Fi OFF alone does not prove satellite failure when using Ethernet.
What the result means: A responding portal confirms local access, while the full alert and service view address satellite state. Wi-Fi off can coexist with working Ethernet. The separately marked WAN is an upstream path, not a substitute local-client port.
Compare the original activity with the existing data route
Use the original failed activity as the reference rather than loading another webpage. Read the Dashboard’s current Satellite Connection and Data Route (Satellite or WAN). The WAN status quick view is informational and separates WAN PORT STATE, INTERNET CONNECTION and CURRENT DATA PATH. Record the observed route and full active alert; leave Satellite Data activation/deactivation and routing settings unchanged. A working local portal or upstream WAN does not by itself prove the satellite path.
What the result means: The original attempt, current route and active alert can now be handed over separately. A current WAN route or satellite state may differ from the state at the failure time; preserve both timestamps instead of generating traffic to recreate the fault.
When to stop and get help
Leave antenna installation, DC wiring and transmitting-terminal commissioning to qualified personnel. Do not alter Distress settings, expose account identifiers, install firmware or factory-reset a managed terminal as a trial. Do not use an emergency call to test it. Red critical faults or repeated registration failure belong with Thales and your airtime provider.
What to tell support
Give authorized support the exact terminal/software, original time and failed activity, named System/Satellite/Wi-Fi patterns, local portal result, full current alert and displayed satellite/WAN data route. Keep the current status separate from earlier symptoms. Send IMEI, SIM details and original logs only privately; do not publish credentials, addresses or account records.
Common questions
Where is the full user manual?
The local management portal has Help links to the user and installation manuals. Use the document matching your system. Thales’ customer service can arrange authorized documentation access; an installation manual does not authorize an untrained person to commission a transmitter.
Can I inspect diagnostics without interrupting calls?
In original MissionLINK manual PN 84468 Rev B (September 2018), Diagnostics > Satellite Modem is view-only. Record System Status and Constellation Status for authorized support. This applies to the portal generation documented in that edition; confirm your installed firmware documentation before following menu paths. It is separate from the administrator’s Self-Test action.
Does INITIATE TEST simply refresh the status?
No. Rev B sections 4-41–4-42 require administrator access and a YES, TEST confirmation. The built-in test makes the terminal unavailable for several minutes and drops ongoing calls and data sessions. Preserve current evidence first; arrange a service interruption with the responsible operator before any test. Do not run it merely to refresh a page.
Why might the visible log miss an earlier event?
Rev B section 4-45 limits Most Recent Log Entries to the last 100 entries. Diagnostics > Logs > DOWNLOAD LOGS saves a ZIP with additional detail for authorized troubleshooting. Keep the file private and preserve it before changes. DELETE LOGS erases evidence and is not a repair. The Alerts page lists currently active alerts; a cleared alert does not prove what caused the earlier fault.
Do all SIM or antenna alerts mean the same fault?
No. In PN 84468 Rev B, Table 6-2 (6-7–6-8), BCX_SIM means the modem failed to read the SIM; SIM_MISSING means no SIM was detected. ANT_CABLE reports excessive cable loss, while ANT_MISSING means the antenna was not detected. Save the exact alert, severity and time for the provider or installer. Match your firmware’s manual before interpreting these older portal codes. They do not by themselves prove a cancelled account, sky obstruction or a need to buy a new antenna. Leave live RF connections and hardware replacement to qualified service.
Why can WAN internet work while an external phone call fails?
The original MissionLINK manual PN 84468 Rev B, section 2-3, separates WAN least-cost routing for data from external voice calls over Iridium. A working upstream internet connection does not establish satellite voice availability. Record the current data route, satellite status and the affected phone separately. Do not reconnect a handset to the WAN port or start paid calls to prove the data path. This is the September 2018 portal generation: have the operator confirm installed firmware and service before applying its routing description to newer equipment.
Why does only one registered phone ring for an incoming line?
In PN 84468 Rev B, Status > Phones lists registered phones and their extensions (section 4-10). Registration and incoming-line assignment are different checks. Phone Settings maps each inbound Iridium line to one extension; an extension can separately have one, several or no outbound lines assigned. A listed phone may therefore not be the target for the called number. Ask the administrator to read the existing mapping and compare the affected extension and call direction. Preserve assignments, credentials and call logs; do not press APPLY, delete extensions or replace passwords during diagnosis. Share numbers and account information privately with authorized support.
Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.
