diff --git a/docs/anveo-direct-setup-guide.md b/docs/anveo-direct-setup-guide.md index b8c063c..f219370 100644 --- a/docs/anveo-direct-setup-guide.md +++ b/docs/anveo-direct-setup-guide.md @@ -297,9 +297,10 @@ them. Android's Messages app reads the telephony SMS provider, which only the cellular radio (or whichever app holds the default-SMS-app role) writes to; -iOS lets nothing write to Messages at all. Codes arrive as ntfy push -notifications instead — which, for a passcode you're about to read and type, -is the more useful place anyway. +iOS lets nothing write to Messages at all. No SIP client can inject into +either, so texts to this number arrive in **Sipnetic's own message thread** +(or whichever softphone is registered to the owning extension) and nowhere +else. That's a platform limit, not something the delivery path chooses. ## Provider risk and keeping the number diff --git a/services/pstn-trunk.sh b/services/pstn-trunk.sh index 429a7c3..dff3b18 100644 --- a/services/pstn-trunk.sh +++ b/services/pstn-trunk.sh @@ -2503,11 +2503,17 @@ Dashboard's Extensions tab, live, no restart needed. ## Receiving SMS on the trunk DID -Not handled by this service — SMS and voice are configured separately at the -provider, and inbound SMS doesn't touch Asterisk at all. \`sudo ./setup.sh -sms-inbound\` sets up verification codes arriving as ntfy push notifications; -see that service's README for the short-code and mobile-DID caveats that -decide whether codes actually get through. +Configured separately at the provider (voice and SMS are independent settings +on an Anveo DID), then handled by \`sudo ./setup.sh sms-inbound\` — which +reads THIS service's \`pstn-personal-dids.conf\`/\`pstn-groups.conf\` to work +out which extension or Ring Group owns the destination DID, exactly as the +inbound-voice ring logic above does, and delivers the text into Asterisk over +AMI as a SIP MESSAGE. Install this service first; that one depends on these +files existing. + +See that service's README for the short-code and mobile-DID caveats that +decide whether codes actually get through, and for why outbound SMS isn't a +path yet. ## Managing this from a web UI