Editor, Interface administrators, Administrators
19
edits
This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!
mNo edit summary |
|||
(21 intermediate revisions by 6 users not shown) | |||
This page gives an overview to using our services for '''SMS'''.
==Inbound SMS==
This is where text messages are sent to us to
Where
{{CPbox|#Click on the number you want to manage
#Click the Incoming tab, scroll to the bottom of the page
#Enter the details into the SMS Inbound box}}
[[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 address - emails the SMS
*Fediverse address - toots the SMS (as a ''direct mention'')
*Mobile number - sends the SMS to another mobile number (chargeable)
*Web URL - sends the SMS as an http/https GET/POST
*SIM ICCID - when offered, sends to a SIM directly (SIP2SIM)
==Outbound SMS==
Any of our VoIP Numbers can be used to send SMS messages. Just beware that not all numbers can receive an SMS message.
You can send in the following ways:
*Via our web form: http://aa.net.uk/telecoms-sendsms.html
*Via the [[SMS API]]
*Via a SIP2SIM SIM (in a suitable handset or device). See: [[SIP2SIM and SMS]]
===Multipart texts===
Where possible multi-part
==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
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.
If you have a presentation number set up for your VoIP, this will be used unless you specify an originator. You can specify the presentation number, or the main number.
If you ask us, we can allow sending of text
===UTF8 Character Sets===
The SIP2SIM service does handle all of the GSM character set options, including the 7 bit character set with escaping, the 8 bit binary messages (assuming latin1 character set), and the 16 bit character set with UCS16 surrogates for full unicode.
Internally we convert all messages to UTF-8. If we are sending messages to your own gateway or email they will be in UTF-8.
Our outgoing SMS carriers to external mobiles do not support everything, sadly, and so some characters may get lost on the way. We can only suggest testing yourself to confirm.
===SMS error codes===
This is a list of internal error codes which may be shown on CDRs if something went wrong:
* -201 no target found for incoming SMS to customer
* -204 error while HTTP posting to customer's server
* -202 and -203 invalid destination email address
* -301 no destination number
* -302 and -303 no SMS content to deliver
* -304 this is a status report, not a normal SMS
* -305 message billing error - eg we won't send the message as we don't know who to bill
* -306 too many message parts
* -702 failed to route message - possible if sending to a totally invalid number
* -801 and -802 are decoding errors while packing to TPDUs
* -803 originator address not allowed
[[Category:SMS]]
|