Revision as of 05:57, 7 April 2024 (view source) RevK (talk \| contribs) No edit summary ← Older edit		Revision as of 06:00, 7 April 2024 (view source) RevK (talk \| contribs) (→‎HTTP) Newer edit →
You will note that we have tried to use field names to match GSM 03.40 values. Other values may be included. For legacy reasons you can prefix the URL specified with a * to also send the older field names of timestamp, originator, destination, message. We support UTF-8 coding of the full GSM 7 bit character set (including £$¥èéùìòÇØøÅåΔ_ΦΓΛΩΠΨΣΘΞÆæÉÄÖÑÜ§äöñüà€¡¿). ~~Whilst~~Not ~~one~~all ~~message~~of isour ~~normally~~SMS upinterconnects tohandle 160 characters some characters are coded using two characters using an ESC prefix in the 7 bit alphabet (€,[,\,],^,{,\|,},~). The message will be coded as 7, 8 or 16 bit depending on what you include in the text, and this will impact the numberall of ~~message parts that may be sent. If you include~~ the ~~invalid UTF-8 sequence 0xC0 0x80~~coding, ~~then~~so ~~that~~we ~~includes a null in~~send the message. ~~If you include any unicode characters beyond U+0xFFFF then UTF-16 coding is used and sending of text in is UCS2 format. Not all interconnects or devices~~as ~~understand~~best ~~UTF-16~~we ~~format~~can. The response text starts with either ERR: and an error message or OK:

SMS API (view source)