Talk:SMS: Difference between revisions
Appearance
Content deleted Content added
| (2 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
# If the caller (SM-SC) replies with FSK quickly in accordance with ETSI ES 201 912 then accept the SMS digitally and deliver as an [[SMS#Inbound_SMS|Inbound SMS]], otherwise: |
# If the caller (SM-SC) replies with FSK quickly in accordance with ETSI ES 201 912 then accept the SMS digitally and deliver as an [[SMS#Inbound_SMS|Inbound SMS]], otherwise: |
||
# send dialpad digits to have SM-SC play SMS as text-to-speech |
# send dialpad digits to have SM-SC play SMS as text-to-speech |
||
# 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. |
# 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, then end the call. |
||
== End user equipment interaction == |
|||
== Outgoing messages == |
|||
End user SIP equipment may support ETSI ES 201 912 over RTP, if so then: |
|||
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. |
|||
* VoIP supplier could implement that by divert outgoing calls to well known SM-SC numbers to the provider SM-SC |
|||
# As with "annex A.1" If caller-id is not witheld, answer the call, in the SM-SC role |
|||
* Also have an option to rôle switch to SM-SC to deliver messages to it, after having [[SMS#Itemised_billing|logged them]], if customer wanted that. |
|||
# Log the outgoing SMS if required and transmit onwards |
|||
= Experimenting = |
= Experimenting = |
||