This problem occurs when there is poor signal quality. Users who are attempting to make data calls from inside of a building also tend to have this difficulty.

When your call drops, observe the signal strength indicator in the corner of the LCD on the phone or your computer and verify that your signal is in the range of 4 to 5 bars.

If you are not getting 4 to 5 bars of signal, you may want to adjust your antenna location to get a better view of the sky.

If the problem persists, please contact the dealer through whom you purchase  service.

To initialise the Iridium data terminal to receive an incoming data call, start a Terminal Program (such as HyperTerminal) with the following settings: 19200* bps, 8, N, 1, Flow Control = None.

Once connected , type the following AT commands:

AT+IPR=x (where x baud of Terminal Program, according to
ATS0=1  (This turns on auto-answer)

1 = 600 bps
2 = 1200 bps
3 = 2400 bps
4 = 4800 bps
5 = 9600 bps
6 = 19200 bps (default)

E.g. AT+IPR=5 sets to 9600bps Terminal rate)

AT&W0  (This stores the current (active) settings to Profile 0 of the RST100).

The device is now ready to answer an incoming data call automatically. During the waiting period, the Data RX activity timeout can expire, and Voice calls can be made (Applies only to RST100 model, with serial numbers > 10001000).

* The baud rate can be set to whatever baud rate the device answering the call is going to need and not necessarily 19.2k.  The “RING” string should be decipherable by the target device/program.

Refer to the Beam Data Guide for more information.

To configure your RST remotely you will need to know its Phone Number, and Supervisor PIN (and also the Security code if sending SSAS commands).

Remote commands are supported on RST100 and RST200 firmware 3.2 (or greater), and all RST03x firmware.

The command is constructed by using the same keyboard strokes used if you were to change the setting using the Supervisor Menu (connected to Hyper Terminal) via the Log Port @ 9600 baud.

The Complete Remote Command Guide will show you how to send remote commands to your Beam Iridium Terminal.

Download the Remote Command guide from the RST100's Common Resources tab.

After typing the dial string ATDT the Call LED would blink amber, but after about 5 to 10 seconds, it would extinguish, and HyperTerminal would lock up.

This happens if the ‘Settings - Data/SIM -Timeouts - Data RX’ in the Beam Management System (BMS) software is set to a time interval, which is shorter than the time taken for an Iridium data call to be made. 

The recommended default is 40sec.

Each Iridium sim card comes with two MSISDNs.  MSISDN-A is the standard phone number supplied with a sim card for voice and sms.  MSISDN-C is the data number.

If the Iridium terminal is configured as a modem to receive and send data, then you will need to dial into the terminal's MSISDN-C number. (This is not an Iridium internet access number).

The sim card/service provider can give you the MSISDN-C.

Also, make sure that the terminal is capable of auto-answering incoming calls if unattended and set to auto baud. Some remote terminals do not respond to auto-baud quite well and therefore it is best to try different baud rates until you can establish a PPP connection.

This error message appears when either you are using the wrong access number or the sim card is not provisioned for data use:

Below are the known access numbers:
Telstra (Australia) - 66666
Iridium (Worldwide) - 008816000025

If you have a local service provider with Iridium, their access number might be different. Once you find out that number and if different from the list above, please contact us at This email address is being protected from spambots. You need JavaScript enabled to view it. so we can add that number to our list of data access numbers.

To view the firmware version, use the relevant Beam Software Management tool available for download from the product support page.

To configure your RST remotely you will need to know its Phone Number, and Supervisor PIN (and also the Security code if sending SSAS commands).

Remote commands are supported on RST100 and RST200 firmware 3.2 (or greater), and all RST03x firmware.

The command is constructed by using the same keyboard strokes used if you were to change the setting using the Supervisor Menu (connected to Hyper Terminal) via the Log Port @ 9600 baud.

Complete Remote Command Guide will show you how to send remote commands to your Beam Iridium Terminal.

The Remote Command guide can be downloaded from the RST100's Common Resources tab. 

To upgrade the firmware on your Beam docking station or terminal follow the steps below:

1. Download the software management tool on the product support page.
2. Install the software package on your computer.
3. Connect the Beam docking station or terminal to the power supply.
4. Connect the Beam docking station or terminal to the computer via USB or RS232 (whichever is applicable).
5. Run the software management tool and follow the instructions on the screen.
   1. If your docking station or terminal is running an old version firmware, the software management tool will immediately recommend the update.
   2. If a fresh install of the tool does not recommend a firmware update, then your docking station or terminal is running the latest firmware.

Please ensure you have downloaded the latest version of the Beam Software Management tool from the product's support page.

The software management tool includes the required USB drivers to enable communication between the computer and the Beam docking station or terminal.

Also, refer to the Software Management tool's release note for operating system compatibility.

In addition please try the following process:

• Restart the PC
• Removing the USB cable from the device to the PC
• Power cycle the device
• Retry upgrading firmware

1. Is the card inserted the correct way?  The notch on the sim card should align with the notch on the sim tray.
2. Check the SIM and phone contacts. If they are dirty, clean them with an anti-static cloth.
3. Is the gold chip visibly damaged or scratched?  If so, contact your service provider for assistance.

If you enter the PIN incorrectly 3 times, the SIM card locks, and you need to enter the PUK. You must use the PUK code supplied by your Service Provider to unlock the SIM. If you don't have a PUK code please contact your Service Provider.

Yes, this can be turned off via a range of different methods.

For more information, check out the Sim Pin Configuration Guide.

<Insert link: Sim Pin Configuration Guide>

If the Handset says its BLOCKED, it means you have entered the PIN 3 times incorrectly.

You need to enter your PUK code. This can be obtained from your service provider.

You can UNBLOCK a sim card via a range of different options.

Download the Sim Pin Configuration guide here for the instructions.

Dial 698698 to enter the Crew Calling platform.  

Enter your PIN.  Then you are presented with 4 choices.  

Enter "3" to activate the captain's PIN for voice calls only.  

After you do this, you will always be prompted for a PIN when making voice calls, however you will never have to enter a PIN for data calls.

The Subscriber Identity Module (SIM) often referred to as a simcard, typically is provisioned and issued by a Service Provider (SP) with an associated Personal Identification Number (PIN), sometimes referred to as PIN1.

It is possible to request simcards without PINs. When the satellite device first powers on, if the unit is set to request that the user enter the PIN code then until this has been successfully completed the unit will not register, place calls or receive calls.

Enter the PIN2 unblocking key (PUK2) or contact your service provider for further assistance.

A “check card” message means there is something wrong with the sim card and how it is inserted/installed in the sim tray.

Usually, there is a contact problem between the sim and the sim tray.

A couple of things to check:

• Is the sim card installed the right way in the sim tray?  See screenshots below for reference only and may not represent your exact product.
• Make sure the contacts are ok, no damage, etc. See screenshots below for reference.
• Once all checks have been performed and the error message persists to appear, check the sim card with a different unit and see if the error message follows.
• If the error message follows, then the sim or how the sim is inserted could be the problem.
• If the error message stays with the unit, then try a new sim, if the error message still appears, then there must be something wrong with the sim tray or the unit itself.

On a docking station/ terminal with status LED, the Status Led will change to green when the terminal is registered to the network.

For an RST100 terminal, the signal LED will change from Red to Green.

For Oceana/Terra 400 terminals, the signal LED on the terminal will change to GREEN (Good Signal Registered) or YELLOW (poor signal registered) when it is registered and able to make calls on the network.

Refer to the product's user manual for more information.

Ensure your terminal’s antenna is installed where there are no obstructions and has a clear line of sight to the satellite with no obstacles which could block the signal.

Check the antenna cable and all connections are secure and no bends or breaks / cuts in the cable

Check for any RF interference near the antenna that maybe causing problems. If there is, shut them down and re test, if works ok, then you will have to relocate the antenna elsewhere

Check with your service provider that the service has been activated.

For Inmarsat subscribers, check the coverage map to ensure service is available at your location or if there is service outage in the area.

If problem persists, contact your service provider.

All wireless devices, including satellite telephones, are susceptible to RF (Radio Frequency) interference from other electronic devices. This problem is especially evident when numerous antennas and broadcasting devices are located within close proximity to each other.

A good example would be onboard a ship. It is important that certain considerations be taken into account for best performance when an Iridium/Inmarsat system is installed.

Causes of RF Interference:

Some subscribers have contacted Iridium regarding the loss of signal quality when they operate their equipment near active Inmarsat terminals. The power with which Inmarsat units transmit can overpower the Iridium unit’s ability to properly maintain a quality connection with the Iridium satellite constellation. Inmarsat terminals are often found in the same locations as Iridium subscribers, such as harbors, airports and especially onboard ships.

The location of the Inmarsat unit’s antenna in relation to the Iridium unit’s antenna plays a significant role in determining the degree of signal degradation that an Iridium subscriber can expect to experience. All Iridium units are susceptible to this interference, regardless of the type of antenna being used.

Generally speaking, an Iridium unit, be it a handset using its internal antenna or a fixed terminal when attached to an externally mounted antenna and located within 15 and 45 meters (50 to 150 feet, respectively) of an operating Inmarsat Standard-C terminal, will likely experience degraded performance.

Other sources of RF interference such as Globalstar units, radar devices and broadcast stations can provide interference for Iridium units, but usually are not encountered as frequently as Inmarsat terminals.

Also refer to “Assuring Quality of Iridium Service” in the Antenna Installation Guide.

Make sure the following are observed:

• Power supply level is steady and never fluctuates.
• Antenna is connected to the dock or terminal with a Beam approved cable.
• Antenna installation guide is followed.
• The sim is active, else request service provider to reset the service on the sim.

Yes, The user must use “AT Commands", through the data port.  The AT commands use the standard GSM ‘PDU’ format.

Iridium AT Command Guide

SMS-MT messages can be sent to an Iridium phone/Beam docking station/terminal in one of 5 ways:

By sending an SMS-MO message from another Iridium phone.  Current limitation is 160 characters.

By sending an SMS-MO message from a cellular phone ( if available ).

By sending an e-mail to This email address is being protected from spambots. You need JavaScript enabled to view it. where xxxxxxxxxxxx is the 12-digit Iridium phone number. The subject line is ignored.  “Plain Text” format is recommend for the e-mail message. Not available for Telstra 01471xxxxx services

By using the “Send a Satellite Message” feature at www.iridium.com. 
Not available for 01471xxxxx services

By sending an SMS-MO message from another Beam Iridium device, by using the Beam Management System, Software>Messages tab.

Yes.  A user can originate an SMS message from an Iridium phone or Beam device (up to 160 Characters), and send that message to another Iridium phone, to an e-mail address, or to a cellular phone ( if available).

Before using SMS-MO, you must…

• Have an active postpaid / Prepaid or Crew Calling SIM card account.

• Enter the SMS Service Center Number (SMSC) into the phone / Beam device, which stores the number on the SIM card. This number MUST be entered in one of these two ways: 00881662900005 or +881662900005 for an Iridium SIM, and 0061418706700 or +61418706700 for a Telstra SIM. 

Check / enter Service Center Number:

Via the handset:

To enter the Service Center Number:

• Press the ‘Envelope’ key.
• Scroll to ‘Message Settings'. Press OK.
• Scroll to ‘Service Center'. Press OK.
• For an Iridium SIM, enter 00881662900005 or +881662900005. 
• For a Telstra SIM, enter +61418706700.
• Via the Beam Management System (BMS) software:
• Enter number in the “Settings - “Data/SIM” - “SIM/SMS” tab.
• For an Iridium SIM, enter 881662900005. 
• For a Telstra SIM, enter 61418706700. 
• Click on another tab or field to commit the change in the Beam Management System (BMS) software.  Please allow a few seconds for number to be displayed and changed.

Solution 1:  Recipient phone # or e-mail address entered incorrectly. Make sure phone number was entered as 00 or +, Country Code, Phone Number. Make sure e-mail was entered with a space between the e-mail address and the message.  For a Telstra SIM and Telstra SMS, the phone number is all that is needed, e.g. 0409xxxxxx.

Solution 2: Check expiry period.  If recipient did not turn on their phone within the expiry period, message was deleted before delivery.

There is a known problem (acknowledged by Iridium) that when SMS messages are being delivered AND the user is simultaneously reading or replying to existing messages (via the handset), the phone may lock up.  The only way the display can be restored is by recycling power to the device.  

• Iridium 9575 Extreme Handset firmware HL15002 fixed this issue.
• Iridium 9555 Handset firmware HT15002 fixed this issue.
• 9522 Transceiver ST15001 fixed this issue.
  (Applicable only to Beam-Iridium Docking stations/terminals)

NOTE: When handset display lockup occurs, this will not affect any other functionality of the device, and Voice calls via the RJ11 port (if applicable), and also ‘Comm Port / USB ' data calls are still possible.

To verify the software version on the Iridium handset enter *#91# on the handsets' keypad.

To verify the software version on the LBT device (internal to the RST device) enter *#91# on the keypad of an Intelligent Handset.  This is also available on the Status tab of the Beam Management System software (in the ‘LBT Firmware’ field).

Was the dialled number entered in international format? All calls made from the Iridium satellite system with a Iridium "8816" service must be in international format.

If the service is a Telstra "01471" service then the Telstra calling formats must be used. Dial all numbers the same as you would from a standard mobile except fixed calls must have the Area code (0X) included.

Check the signal strength indicator. If the signal is weak, ensure the antenna has a clear line-of-sight to the sky and there are no buildings, trees, or tall structures around.

Try to register manually.

Is RESTRICTED displayed? Check the Call Barring setting.

Has a new SIM card been inserted? Check that no new restrictions have been imposed.

Check to see if fixed dialling list is enabled. If so, calls can only be made to numbers or prefixes that are on the list.

An intelligent handset will never produce a dial tone. You will hear very soft beeps while the call is dialling but you will not hear any audio when not in a call.

Check whether it is connected to the dock/terminal. Try resetting the terminal by pressing the reset button.

If the Intelligent Handset is used with the RST100 or a 9522 Transceiver, open the sim card slot and make sure the switch position is at RS232 (as labelled).

Make sure the volume on the intelligent handset is set to high until it is audible in the installed environment.

The IP Address is 12.47.179.11

directip.sbd.iridium.com / port 10800 which should resolve to 12.47.179.12:10800

Before an SBD can be sent, the LBT (in the Beam Device) or Iridium satellite phone must be provisioned for SBD. This includes Data being activated on your account and a destination address setup for the SBD to be sent to.

The destination address can be set to a specific IMEI number, an email address, or a direct IP Address / port.

Your service provider will be able to assist you in provisioning of your device.

Refer to the Beam Data Guide for more information on sending SBD's.

Messages sent to an ISU from the Host are sent to the email address: This email address is being protected from spambots. You need JavaScript enabled to view it.

1. Placing at least one, and up to a total of four, IMEI(s) into the subject line of the email identifies the destination ISU(s).
2. If there is more than one destination IMEIs then list the additional IMEIs on the subject line separated with a single space between each IMEI.
3. White listing may be used to restrict the originator of MT-SBD messages to particular IMEIs. This restriction will fork for email and Direct IP.
4. The message must contain a properly formatted sender (“From:” address), otherwise the message will be dropped by the GSS.
5. The data message to the ISU must be carried as an attachment to the email:
   1. The attachment name must have a ‘.sbd’ file name extension: E.g. ‘importantdata.sbd’
   2. File names must be 80 characters or less. (Including the .sbd extension.)
   3. File names are not case sensitive.
      1. The maximum size of the binary message (not the Base64 version) is ISU specific and is between one byte and the maximum MT message size stated in Section 1.5
      2. The GSS will reject message sizes that are too large for a particular ISU type.
6. The attachment must use standard Multipurpose Internet Mail Extensions (MIME) Base64 encoding as defined in RFC 2045.
7. Multiple messages may be queued by a single email by including the additional separate attachments in the email message, subject to the maximum number of messages permitted in the queue.
   1. Note that if one of the attachments has an incorrect extension (.sbd), while others are correct then no error indication email will be sent.
   2. A single email with multiple attachments creates a MT-SBD message from each attachment. In other words – one email with ten attachments creates ten entries for the destination ISU.
8. The message body plays no role in the message transfer process; any information contained in the body will be discarded.
9. A maximum of 50 messages may be in any ISU’s queue at any one time regardless of whether they where sent as an individual message with attachment or a single message with multiple attachments. The GSS will reject any message over this limit.

The maximum recommended signal drop from the passive satellite antenna to the Iridium transceiver( either a handset or Beam device) is 3dB. (Not applicable when using RST740).

For optimal performance, we recommend using the shortest length of cable and the fewest number of connectors possible. You must ensure that the cable used conforms to this.

An example of attenuation for RG213 cable is 0.33dB per metre @ 1.6Ghz, therefore the maximum cable length is 8m (allowing up to 0.5dB for cable interconnections).

LMR400 cable in comparison has a better attenuation figure of 0.18dB per metre.

Feel free to use the Beam Iridium Online Cable calculator to design your cable for a Beam Iridium docking station or terminal.