Services

Hermes Genesis offers services to assist consumers and business organizations to gain full control of their processes and make the right business decisions at the right time through real-time access to mission critical information by admittance technology, process, and people.


Our Services Are

Shortcode Sharing Shortcode Hosting Bulk SMS
Dictionary News Software Development
Contact Center Content Sharing VAS Content
Audio Visual Content Monitor Training

CIMD

Computer Interface to Message Distribution (CIMD) is a proprietary short message service centre protocol developed by Nokia for their SMSC (now: Nokia Siemens Networks).

Syntax

An example CIMD exchange looks like the following:

<STX>03:007<STX><TAB>021:12345678<TAB>033:hello<TAB><ETX>
<STX>53:007<TAB>021:12345678<TAB>060:971107131212<TAB><ETX>

Each packet starts with STX (hex 02) and ends with ETX (hex 03). The content of the packet consists of fields separated by TAB (hex 09). Each field, in turn, consists of a parameter type, a colon (:), and the parameter value. Note that the last field must also be terminated with a TAB before the ETX.

Two-digit parameter types are operation codes and each message must have exactly one. The number after the operation code is the sequence number used to match an operation to its response. The response code (acknowledgement) of the message is equal to the operation code plus 50.

In the example above, the operation code 03 means submit message. Field 021 defines the destination address (telephone number), with field 033 is the user data (content) of the message. Response code 53 with a field 060 time stamp indicates that the message was accepted; if the message failed, the SMSC would reply with field 900 (error code) instead. A good number of supporting software to implement CIMD is available from Nokia's Web site to build CIMD client. You can fire SMS from message center with the help of CIMD client tools.

Short Message Peer-to-Peer

The Short Message Peer-to-Peer (SMPP) protocol is a telecommunications industry protocol for exchanging SMS messages between SMS peer entities such as short message service centers and/or External Short Messaging Entities. It is often used to allow third parties (e.g. value-added service providers like news organizations) to submit messages, often in bulk.

The protocol is based on pairs of request/response PDUs (protocol data units, or packets) exchanged over OSI layer 4 (TCP session or X.25 SVC3) connections. PDUs are binary encoded for efficiency.

The most commonly used versions of SMPP are v3.3, the most widely supported standard, and v3.4, which adds transceiver support (single connections that can send and receive messages). Data exchange may be synchronous, where each peer must wait for a response for each PDU being sent, and asynchronous, where multiple requests can be issued in one go and acknowledged in a skew order by the other peer. The latest version of SMPP is v5.0.

Loading... Please wait...