Closed 0perationPrivacy closed 3 years ago
Turn on the toggle for P2P instead of A2P
https://portal.telnyx.com/#/app/numbers/my-numbers On all your numbers,
routing
tabOn my UK number it gave me an error first saying it's not supported on the number. Then I tried it on my US number and the toggle switched. A min later I went back to the UK number and tried to toggle it to P2P and it worked!
Then i sent a test message and now the sender
is switched with the actual phone number !
Even though there's a red x next to that feature and it says "feature not available for this number", it still works (screenshot of test)
Before & After (with and without the P2P setting in Twilio)
Next: I'm looking into integrating this setting in the API to automate it so the user doesn't have to manually change the setting. Stay tuned. Following up with support.
(support pointed me to this link as a reference) https://www.twilio.com/guidelines/us/sms
In my test: ✅ Twilio-US to UK number works ❌ Twilio-UK to US fails
One-way communications 🤷🏽♂️
Here is my experience just now with Telnyx: = Traffix Type was P2P for the new profile created by OP = Message marked as sent from WebUI at 14:40 = Received by Telnyx 14:40:39, but status was "failed" with title "Undeliverable" event type "message.finalized" = Then got status "failed" with event type "message.sent" starting 14:50:29 and finishing 14:50:39 = about the same time - 14:51 - it was delivered to a NL smartphone by SMS
This means that it is on Telnyx side .... but it takes about 10 min to send a message ??
PS: The sender is "(501)" in the SMS, and in Telnyx Debug messages as below - still "Sender", in WebUI is correct "+316xxxxx":
{ "cc": [], "completed_at": null, "cost": { "amount": "0.0400", "currency": "EUR" }, "direction": "outbound", "encoding": "GSM-7", "errors": [], "from": { "carrier": "Telnyx", "line_type": "Wireless", "phone_number": "Sender" <<<<<< still wrong <<<<< }, "id": "40317bd4-e8bd-4bb1-83e2-706f50239baa", "media": [], "messaging_profile_id": "40017bd3-c55c-4ebd-b409-f76f3065434a", "organization_id": "2a0c02db-0d43-478f-b1f4-d805e6834917", "parts": 1, "received_at": "2021-09-11T12:50:27.906+00:00", "record_type": "message", "sent_at": "2021-09-11T12:50:20.960+00:00", "tags": [], "text": "Test to temp xxxx", "to": [ { "carrier": "", "line_type": "", "phone_number": "+316xxxxxxx", "status": "sent" } ], "type": "SMS", "valid_until": "2021-09-11T13:50:27.906+00:00", "webhook_failover_url": "", "webhook_url": "https://voip.operationprivacy.com/api/setting/sms-status/telnyx" }
Just to be sure I've re-tried the same. This time it took about 10 sec to deliver, the sender field in Telnyx Debug log is still "Sender", but in actual SMS the sender number is different again, this time it shown as from "+33 6 xxx" instead of "(501) xxx". At least that delay was a temporary issue. Attached is the complete obfuscated log, the "failed" is, seems, a bug in OP, so creating a new GitHub issue
When sending an sms to a non-US number, the recipient sees the incoming message number as
sender
and thus cannot reply. This is the same behavior from Twilio and Telnyx's own interface (and not an issue with the app). Support cases are open with both of them to get to the bottom of this.Checklist:
[x] Made sure there are no restrictions in the account for international number sending
[x] Made sure the number supports sms (not all do)