Iridium 9603N SBD Transceiver (9603N)

Iridium_9603_SBD_Transceiver_4

Servicing and Warranty:

Beam Communications undertakes warranty and out of warranty servicing across our extensive product range. For further information on our servicing process and warranty terms and conditions please see our warranty Terms and Conditions

Frequently Asked Questions

SBD

Q.What is the Iridium source IP address that Mobile Originated deliveries will come from?
A.

The IP Address is 12.47.179.11

Q.What is the Iridium domain name for DirectIP Mobile Terminated messages?
A.

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

Q.For SBD DirectIP Mobile Terminated, does the cusomer need to inform Iridium of the source IP address that will be utilized?
A.

Yes, the source IP address that will be utilized to connect to the Iridium gateway needs to be included within the Iridium network firewalls, to allow for successful connection.

This request for DMT access needs to be sent to the partners Iridium Account Manager.

Q.How do I send Short Burst Data (SBD)?
A.

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.

Q.How do I send a MT SBD via email?
A.

Messages sent to an ISU from the Host are sent to the email address: [email protected]

  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.
Q.Does the 9601 / 9602(N) / 9603(N) support voice?
A.

The 9601 / 9602(N) / 9603(N)  only supports Iridium's Short Burst Data (SBD) capability. It does not support voice, circuit switched data, or short message service (SMS).

Configurations