Home

Search the wiki

»

API Documentation


Mobile Payment


Other






It is possible to submit binary messages that include a User Data Header.

This is most useful when:

a) Your application already has the ability to generate a complete data-block that includes the User Data Header.

b) You need to support binary content that is not currently supported by the Gateway Operator.

Raw Binary Data is sent as a hex-encoded string much in the same way as for logos, but the hex-encoded data-string must also contain a valid UDH, and the OP (operation) child-element of the element must be set to the value of 8:

<OP>8</OP>

The hex-encoded string must be placed in the Text-element:

<TEXT>0605041582000042F22000480E010000000000000000000
0000000000000000000006010000806000001C0707C003E0E0380
03E0734E0072CE07C000E031DA005B8C070000207FBA005DFE040
001FFC1EA005783FF801F0046BE007D6200F8000070DA005B0E00
00000070F4002F0E000000007078001E0E0000000020000000040
000000000000000000000</TEXT>

The Gateway will treat each binary message as one SMS and will not perform any splitting if the content is too long. Thus the application must perform the splitting and include information about this in the UDH if needed. The hex-encoded data-block must not exceed 280 characters in length (140 bytes when decoded).

Note: UDH is disabled by default for new accounts unless it is checked off the order form, but can be enabled any time and free of charge upon request.

See Also

Wikipedia: User Data Header
Gateway interfaces: | XML | HTTP | SMTP | SOAP | SFTP BatchLoader
Intouch interfaces: REST | Syncopy

© Copyright Link Mobility ASA.





GuestLogin