English
EnglishEspañolFrançaisالعربيةDeutschPortuguêsItalianoفارسیBahasa IndonesiaاردوTiếng ViệtBahasa MelayuRomânăΕλληνικάहिन्दीNederlandsTürkçePolskiไทยУкраїнськаРусскийČeština한국어বাংলা日本語简体中文繁體中文FilipinoKiswahiliSvenskaעבריתSuomiDanskMagyarNorsk bokmålதமிழ்

Your country is detected for each new visit. You can choose your country and language.

Phones & messengers / Detailed guide

Terra 400: voice unavailable or call stays active

Check the existing USB data session, the call’s direction and the handset tone before treating a voice failure as an antenna fault.

Applies to: Match Terra 400 and part number TR400 on the installed unit. The shared manual also names Oceana 400; do not extend its instructions to Terra 800, an IsatDock cradle or another Beam terminal. Record the existing antenna and cable-kit labels without disconnecting them.

Work through these checks

  1. Separate data use from voice availability

    Manual page 24 says a USB circuit-switched data connection prevents RJ11/POTS voice calls in either direction and gives an unavailable tone. The call LED flashes yellow during data use. Read this state with the owner of the data application; do not start another paid session, unplug equipment or terminate a managed transfer merely to test voice.

    What the result means: Do not treat every yellow CALL as an active satellite transfer: the table distinguishes steady DTR present from flashing data call in progress. If a managed transfer was active, report that occupancy rather than interrupting it to test voice or replacing the antenna.

  2. Identify an incoming call that has not ended

    For incoming calls, page 24 documents a default hold of about 90 seconds after the local POTS handset is placed on hook. The calling party can end it immediately by hanging up. Distinguish this documented behavior from a new failed call; do not repeatedly redial while the previous call remains active. Record direction and elapsed time for support.

    What the result means: The approximately 90-second behavior is documented for incoming calls under default operation, not a universal timeout for every call. Keep direction and both parties’ known hangup times. A longer or differently configured case needs support interpretation rather than repeated paid attempts.

  3. Read the tone before changing settings

    Page 25 distinguishes a continuous dial tone, short progress beeps three seconds apart, and a fast rising off-hook warning after more than 15 seconds out of a call. PIN and PUK prompts are separate security states: use provider instructions, never guessed codes. Preserve Falcon call-processing settings; page 24 says they can modify dialed prefixes when enabled, so record that state rather than copying another installation’s numbers.

    What the result means: An unavailable tone differs from progress beeps or the off-hook warning. If SIGNAL also cycles green/yellow/red, preserve CALL and MSG together for the coded error table on page 25: that is not the ordinary voice/data occupancy table. Do not guess security codes or disconnect an antenna from the colour alone.

When to stop and get help

If the terminal sounds an alarm, use its normal power control to switch it off safely and stop. Beam associates this alarm with an RF short; leave antenna and cable fault isolation to a qualified technician.

What to tell support

Give authorized support the TR400 label and passive antenna/cable identities, simultaneous SIGNAL/CALL/MSG states, exact tone, call direction, local/remote hangup times if known and existing USB activity. Include whether Falcon call processing was already enabled; keep numbers and account identifiers private. Historical driver instructions do not establish current computer compatibility.

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.