Syntax
A typical EMI/UCP exchange looks like this : ^B01/00045/O/30/66677789///1//////68656C6C6F/CE^C ^B01/00041/R/30/A//66677789:180594141236/F3^C The start of the packet is signaled by ^B (STX, hex 02) and the end with ^C (ETX, hex 03). Fields within the packet are separated by / characters. The first four fields form the mandatory header. the third is the ''operation type'' (O for operation, R for result), and the fourth is the ''operation'' (here 30, "short message transfer"). The subsequent fields are dependent on the operation. In the first line above, '66677789' is the recipient's address (Technical limitations
The two-digit ''transaction reference number'' means that an entity sending text messages can only have 100 outstanding messages (per session); this can limit performance, but only over a slow network and with incorrectly configured applications on one's SMSC (for example one session, with number of windows greater than 100). In practice it does not have any impact on delivery throughput. The EMI UCP documentation does not specify a default alphabet for alphanumeric messages after decoding from hex digits. (It specifies an alphabet of IRA for the ''encoded'' message, which is the same as 7 bitAlternatives
* Short message peer-to-peer protocol (SMPP) also providesExternal links