Jump to content

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!

SMS: Difference between revisions

SMS (view source)

Revision as of 06:14, 7 April 2024

65 bytes removed ,  7 April
→‎Inbound SMS
 
(6 intermediate revisions by 2 users 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 textsSMS messages properly from most networks. All of our 01, 02 and 03 numbers can receive textsSMS messages from Three properly, it seems. Attempts to send textsSMS messages to other geographic numbers (i.e. those starting 01 and 02) cause a call to be made and the textSMS message read out by an automated system.
 
Where textsSMS messages can be received properly, and this includes all cases where A&A customers send textsSMS messages through us, the textSMS message will be sent on to you by your choice of means. This is based on the incoming textSMS message setting onin the control pages for your number.
 
{{CPbox|#Click on the Numbernumber you want to manage▼
Our SIP2SIM service is also able to receive SMSs.
#Click the Incoming Tabtab, scroll to the bottom of the page▼
 
#Enter the details in tointo the SMS Inbound box}}▼
▲{{CPbox|#Click on the Number you want to manage
▲#Click the Incoming Tab, scroll to the bottom of the page
▲#Enter the details in to 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===
If you simply put in an email address, then the text 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 put any incoming text handling in to the control pages, but you have an email address defined for the number.
 
*Email address - emails the SMS
===SIP2SIM===
*Fediverse address - toots the SMS (as a ''direct mention'')
If you include a 19 digit string starting 89 which is the SIM ICCID for one of your SIP2SIM cards then the text will be passed to the SIM directly as a normal text. SIP2SIM charges apply for the SIP2SIM side as an incoming text. See: [[SIP2SIM and SMS]]
*Mobile number - sends the SMS to another mobile number (chargeable)
 
*Web URL - sends the SMS as an http/https GET/POST
===HTTP===
*SIM ICCID - when offered, sends to a SIM directly (SIP2SIM)
If you put an entry starting http:// or https:// then we will attempt to send the text 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 text. If the URL does not, then an HTTP POST is done using URL encoded form data. See: [[SMS API]]
 
==Outbound SMS==
Any of our VoIP Numbers can be used to send SMSs,SMS messages. justJust beware that not all numbers can receive an SMS message.
 
You can send in the following ways:
*Via a SIP2SIM SIM (in a suitable handset or device). See: [[SIP2SIM and SMS]]
 
===Multipart texts===▼
Where possible multi-part textsSMS messages are automatically handled, concatenated before being passed to you, or split from your message in tointo 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 text 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.
==Other Information==
*Sending SMS from us to a web form, you can use http, but that is not encrypted, so we recommend https.
===Texts to SIP2SIM SIMs===
*Sending SMS from us by email may use encryption between email servers, or may not, and mail server operators could access messages.
Using our normal text services setting the destination number as the SIM ICCID (19 digit number starting 89) will send the text to the SIM.
*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.
You can also use the outgoing text gateway using the SIM ICCID as the username and a password as set in the SIM config on the control pages. In this case you do not need to specify the 'da'.
 
▲===Multipart texts===
▲Where possible multi-part texts are automatically handled, concatenated before being passed to you, or split from your message in to 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 text messages.
 
===Itemised billing===
Your bill will show the number of textsSMS messages sent and received per number. The optional XML/JSON version of your bill contains detailed information for each textmessage 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.
 
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 -based originators on a per account basis. You will need to be an established customer. This can be withdrawn at any time.
 
===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.
 
Sending SMS to the SIP2SIM service can be done via our gateway/api and we accept UTF-8 which we will convert as needed in to the necessary GSM character coding scheme and split for multi part messages automatically.
 
 
===SMS error codes===
* -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
Retrieved from ‘http://support.aa.net.uk/Special:MobileDiff/15827...17264’