Difference between revisions of "Talk:SMS"

From AAISP Support Site
Jump to navigation Jump to search
Line 15: Line 15:
 
# receive the SMS, it can then be logged digitally if the customer wants that, leaving the communication channel open for the next steps if required to deliver confirmation the message has reached its destination
 
# receive the SMS, it can then be logged digitally if the customer wants that, leaving the communication channel open for the next steps if required to deliver confirmation the message has reached its destination
 
# if the real terminal equipment, with the internet suggesting that Gigaset devices understand SMS "over, somehow" RTP, understands the ETSI specification equally whether the analogue or IP based interface is used, then switch roles to SM-SC, setting the caller ID to a recognised BT Text number so the station knows to answer it automatically.
 
# if the real terminal equipment, with the internet suggesting that Gigaset devices understand SMS "over, somehow" RTP, understands the ETSI specification equally whether the analogue or IP based interface is used, then switch roles to SM-SC, setting the caller ID to a recognised BT Text number so the station knows to answer it automatically.
# The message can also or instead be transferred via a variety of other methods, without analogue emulation, such as SMPP.
+
# The message can also or instead be transferred via a variety of other methods, without analogue emulation, such as [https://wiki.wireshark.org/SMPP SMPP]
   
 
== Outgoing messages ==
 
== Outgoing messages ==

Revision as of 00:27, 13 October 2021

SMS and calls

If the incoming SMS delivery calls have a caller ID in the BT Text, the chances are there that it understands ETSI ES 201 912, and for incoming SMS, refers to the caller as the SM-SC and recipient as SM-TE, or use the implementation in Asterisk

This may be true even where the call is really SIP and RTP over IP, so there is digital (SMS) over analogue (FSK) over digital going on. (voice codec)

Having the message recovered digitally by the Voip service provider may be helpful for the "tight delay bounds" issue on the asterisk article, even if it is then relayed via a role switch:

Incoming messages

  1. As per "annex A.2" When the call is not witheld and caller id = BT Text receive number, answer the call in the network, and perhaps, start recording as a fallback
  2. Play the initial FSK communication, in the SM-TE role
  3. the SM-SC, hopefully, detects it is talking to an SM-TE rather than a person, and cancels any text-to-speech, once successful confirmation is obtained according to the protocol then call recording can stop and any recording discarded.
  4. receive the SMS, it can then be logged digitally if the customer wants that, leaving the communication channel open for the next steps if required to deliver confirmation the message has reached its destination
  5. if the real terminal equipment, with the internet suggesting that Gigaset devices understand SMS "over, somehow" RTP, understands the ETSI specification equally whether the analogue or IP based interface is used, then switch roles to SM-SC, setting the caller ID to a recognised BT Text number so the station knows to answer it automatically.
  6. The message can also or instead be transferred via a variety of other methods, without analogue emulation, such as SMPP

Outgoing messages

If the station supports SMS on PSTN, it may support the same interface over IP codecs, then "calls" to BT Text outgoing shortcodes are very likely attempts to send an SMS this way.

  1. As with "annex A.1" If caller-id is not witheld, answer the call, in the SM-SC role
  2. Log the outgoing SMS if required and transmit onwards

Michael (talk) 22:17, 12 October 2021 (BST)