SMS: Difference between revisions

← Older edit

SMS (view source)

Revision as of 06:14, 7 April 2024

175 bytes added , 7 April

→‎Inbound SMS

RevK

Editor, Interface administrators, Administrators

19

edits

Revision as of 10:29, 22 March 2024 (view source) RevK (talk \| contribs) (Remove SIP2SIM, add forwarding and tooting) ← Older edit		Latest revision as of 06:14, 7 April 2024 (view source) RevK (talk \| contribs) (→‎Inbound SMS)
(3 intermediate revisions by the same user not shown)
==Inbound SMS== This is where text messages are sent to us to deliver to our customers. We provide VoIP numbers in mobile range (07) and in all UK area codes and some special services (e.g. 0800). However, at present, only mobile numbers, and a few of the numbers starting 01 and 02 can receive SMS messages properly from most networks. All of our 01, 02 and 03 numbers can receive SMS messages from Three properly, it seems. Attempts to send SMS messages to other geographic numbers (i.e. those starting 01 and 02) cause a call to be made and the SMS message read out by an automated system. Where SMS messages can be received properly, and this includes all cases where A&A customers send SMS messages through us, the SMS message will be sent on to you by your choice of means. This is based on the incoming SMS message setting in the control pages for your number. You can put multiple ''targets'' separated by a space.▼ {{CPbox\|#Click on the number you want to manage [[File:InboundSMS.png\|none\|frame\|Inbound SMS option on Control Pages]] ▲You can put multiple ''targets'' separated by a space. See [[SMS API]] for how these work. ~~===Email===~~ If you simply put in an email address, then the SMS message is emailed to you. Additional email headers may be present to specify fields such as User Data Header if present, etc. This is also the default if you do not fill in any incoming SMS handling information in the control pages, but you have an email address defined for the number. Email address - emails the SMS ~~===HTTP===~~ Fediverse address - toots the SMS (as a ''direct mention'') If you put an entry starting http:// or https:// then we will attempt to send the SMS message to you using HTTP (or HTTPS). If the URL ends with a ? or & then an HTTP GET is done with a set of form fields (i.e. name=value) containing information about the SMS message. If the URL does not, then an HTTP POST is done using URL encoded form data. See: [[SMS API]] Mobile number - sends the SMS to another mobile number (chargeable) Web URL - sends the SMS as an http/https GET/POST ~~===Toot===~~ SIM ICCID - when offered, sends to a SIM directly (SIP2SIM) If you put an entry starting @ and a username and another @ and a hostname, in the format of a fediverse/mastodon account, we will send a direct message to you. Be aware that this is not private from administrators of your instance, and you cannot reply to such messages. ~~===Forward===~~ ~~If you put a mobile number (no spaces in it) we will forward the SMS to that number. This is charged to you at our usual SMS rate.~~ ==Outbound SMS== ===Multipart texts=== Where possible multi-part SMS messages are automatically handled, concatenated before being passed to you, or split from your message into parts. Unfortunately, not all of the systems to which we interconnect handle multi-part messages sensibly, and this can result in a multi-part message being delivered as multiple separate messages. ==Privacy== The whole of the traditional telecoms network has limited privacy, in that connections are not generally encrypted and may pass through several telcos, and of which could listen to calls or access SMS. The ''over the air radio'' parts of mobile calls and SMS are encrypted (though not always very well). However you should also consider privacy when forwarding SMS outside the telecoms network. Sending SMS to us, use https to ensure encryption to us. Sending SMS from us to a web form, you can use http, but that is not encrypted, so we recommend https. Sending SMS from us by email may use encryption between email servers, or may not, and mail server operators could access messages. Sending SMS by fediverse, communications are normally encrypted, but instance operators could access messages, even though sent as a ''direct mention''. If you trust your instance operator (or run yourself) this should be reasonably secure. SMS CDRs (itemised billing) show the texts, see below. ===Itemised billing=== Your bill will show the number of SMS messages sent and received per number. The optional XML/JSON version of your bill contains detailed information for each message sent or received, including the text content of the message (unless the ''private'' setting was used). Multipart texts are itemised and billed as a single text but billed for the number of parts sent. The XML identifies the number of parts.