|
# 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
# Play the initial FSK communication, in the SM-TE role
# If the SM-SC, such as BT Text or AQL, reply with FSK quickly in accordance with ETSI ES 201 912 then accept the SMS digitally and deliver via usual API options, otherwise
# 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.
# send dialpad digits to have SM-SC play SMS as text-to-speech
# 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
# then record it like voicemail, attempt send the recording [VoIP_-_Voicemail via email] and if successful, ask the SM-SC to delete the delivered SMS.
# 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 [https://wiki.wireshark.org/SMPP SMPP]
== Outgoing messages ==
| 