Technical Details: Tyr SMS Gateway
This section provides details specific to the use of SMPP with the Tyr SMS Gateway service. Accounts may be configured different to the defaults shown below and therefore you should check your SMPP Account Details issued by Melrose Labs for details specific to your account.
Connect to any of the following hosts using your SMPP account details:
|London, United Kingdom
|Cape Town, South Africa
|North Virginia, USA
|São Paulo , Brazil
Live Coming Soon Planned
Non-TLS and TLS connections can be made depending on port use:
SMPP over TLS
We strongly recommend the use of SMPP over TLS to secure sessions between applications and our access node hosts. TLS v1.1 and v1.2 are supported. Earlier versions of TLS and SSL are deliberately not supported.
For legacy applications that do not support TLS, we recommend the use of stunnel for using SMPP over TLS.
Test an SMPP account and service from Melrose Labs or another provider using the Melrose Labs SMPP Client . Use from your web browser. No software installation necessary. Other web browser-based SMPP clients available from Melrose Labs include:
Alternatively, use our txtConsole portal to send messages, get usage reports and look-up messages.
|Submit window size
|Max. submit rate
|TX, RX, TRX
|v3.3, v3.4 (default) or v5
|10 per host
Full details of the Tyr SMS Gateway SMPP support can be found in the SMPP Protocol Implementation Conformance Statement (PICS) .
Delivery receipts and intermediate notifications have the following format and are contained in the
short_message field of the
id:IIIIIIIIII sub:SSS dlvrd:DDD submit date:YYMMDDhhmm done date:YYMMDDhhmm stat:DDDDDDD err:EEE text:
- id: message ID returned in submit_sm_resp (up to 64 characters in length)
- sub: number of messages originally submitted (set to 001)
- dlvrd: number of messages delivered (000 or 001)
- submit date: When message was submitted by ESME
- done date: When message reached final state
- stat: State of message (see Name field below)
- err: Error encountered during delivery (if any)
Additionally, the following TLVs are present in the delivery receipt:
|MC message ID of message being receipted. Should be present for MC Delivery Receipts and Intermediate Notifications.
|Delivery state as shown in below table.
|Error code specific to a wireless network (see error codes below).
|The message is scheduled. Delivery has not yet been initiated. (Intermediate)
|The message is in enroute state. (Intermediate)
|Message is delivered to destination. (Final)
|Message validity period has expired. (Final)
|Message has been deleted. (Final)
|Message is undeliverable. (Final)
|Message is in accepted state. (Final)
|Message is in invalid state.
|Message is in a rejected state. (Final)
|The message was accepted but not transmitted or broadcast on the network. (Final)
|MSISDN is unknown or invalid
|Mobile is switched off or unreachable
|Subscriber busy for MT SMS
|MSC is busy communicating with the handset for another transaction (may be receiving another SMS simultaneously)
|SS7 protocol or network failure