textbelt
textbelt copied to clipboard
typpo
receiving three messages from one invocation
initiated inside a bash script. curl http://textbelt.com/text -d number=[boost.mobile.number] -d "message={{user}} has logged on"
curl -V curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP
first one is type: Text message, From: [email protected] 2nd is Type: Multimedia message From: [email protected] 3rd is same as first. All at the same timestamp. Any thoughts? From a usability point of view, just annoying, but fully functional. I appreciate this project!
Thanks for the report. In c65892f45950fea88916723260fce2e6c8499ef3, I removed the myboostmobile.com endpoint from the list of providers. According to this thread, it is redundant with the messaging.sprintpcs.com endpoint. This may be what caused the MMS.
I also removed the mymetropcs.com endpoint, because I think it's redundant with the sprintpcs one as well. This may account for the 3rd text.
Or, I could be completely wrong. Unfortunately, I don't have a boost number to check with.
Then a good thing I found this?
It's been erratic today, at 0703 I received a 3 identical texts for the one event, Then 1249, a single for a single event, then a double for a single event at 1715 and 1716 respectively. This is not a high volume notification, so that is all the events up to now.
I can keep you posted if you like. I don't mind testing this on my boost number if that is of a help to you.
Ok. I pushed the change live so we'll see if things improve at all. The inconsistency makes me nervous.
OK, sent six more since 17:16, and you have achieved consistency! but consistently 2 per invocation.
Hope you don't mind if I piggyback here. I'm getting doubles of all texts to two different Bell phone numbers in Canada. bellmobility.ca txt.bellmobility.ca and txt.bell.ca all seem to be redundant in your providers list for Canada. I tested all three, bellmobility.ca doesn't work for my number (I get undeliverable) and the other two both work. I would guess txt.bell.ca is canonical, but I don't know where to get authoritative info on that.
I've never used javascript, but based on your comments above and a skim of the code it looks like you try to send to every provider in a region? So removing one of the txt. addresses might fix the problem if I understand correctly. I'm not sure about the bellmobility.ca address, I wonder if it's outdated or used for providers that use bell infrastructure or something.
Anyway I hope my speculation isn't totally off base, I'm not familiar with javascript or telephony. I'm having fun playing with it, great project!
Got the chance to make some updates tonight - sorry for the delay.
@jessewmc - I've removed bellmobility.ca and txt.bellmobility.ca, leaving only txt.bell.ca. Thanks for the report!
@heartbt - I wonder if the duplicate is email.uscc.net + messaging.sprintpcs.com, as US Cellular sold part of itself to Sprint and may still be supporting their email-SMS gateways? Unfortunately, removing uscc will impact US Cellular-only customers.
We can confirm this theory if you can text yourself at ##@email.uscc.net. If not, the search will continue...
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
'%[email protected]',
Ian,
It is NOT email.uscc.net. I did run down the entire list, and it is vmoble.com. which makes sense, as virgin and boost are both sprint brands, and basically the same network.
Now we know that a boost phone will get a text on @messaging.sprintpcs.com, @myboostmobile.com, and @vmobl.com, but can a virgin subscriber get one from either of the first two? or both? I used to have a virgin account for the car, but I have not anymore. I'll ask around and see if anyone has one in my circles.
Good luck!
On Wed, May 21, 2014 at 1:35 AM, Ian Webster [email protected]:
Got the chance to make some updates tonight - sorry for the delay.
@jessewmc https://github.com/jessewmc - I've removed bellmobility.caand txt.bellmobility.ca, leaving only txt.bell.ca. Thanks for the report!
@heartbt https://github.com/heartbt - I wonder if the duplicate is email.uscc.net + messaging.sprintpcs.com, as US Cellular sold part of itself to Sprint and may still be supporting their email-SMS gateways? Unfortunately, removing uscc will impact US Cellular-only customers.
We can confirm this theory if you can text yourself at ##@email.uscc.net. If not, the search will continue...
'%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]',
— Reply to this email directly or view it on GitHubhttps://github.com/typpo/textbelt/issues/4#issuecomment-43713949 .
Ian, it's official; not one person I know uses virgin mobile. Any luck on your end? Km On May 21, 2014 2:17 AM, "Kevin Moiles" [email protected] wrote:
Ian,
It is NOT email.uscc.net. I did run down the entire list, and it is vmoble.com. which makes sense, as virgin and boost are both sprint brands, and basically the same network.
Now we know that a boost phone will get a text on @ messaging.sprintpcs.com, @myboostmobile.com, and @vmobl.com, but can a virgin subscriber get one from either of the first two? or both? I used to have a virgin account for the car, but I have not anymore. I'll ask around and see if anyone has one in my circles.
Good luck!
On Wed, May 21, 2014 at 1:35 AM, Ian Webster [email protected]:
Got the chance to make some updates tonight - sorry for the delay.
@jessewmc https://github.com/jessewmc - I've removed bellmobility.caand txt.bellmobility.ca, leaving only txt.bell.ca. Thanks for the report!
@heartbt https://github.com/heartbt - I wonder if the duplicate is email.uscc.net + messaging.sprintpcs.com, as US Cellular sold part of itself to Sprint and may still be supporting their email-SMS gateways? Unfortunately, removing uscc will impact US Cellular-only customers.
We can confirm this theory if you can text yourself at ##@email.uscc.net. If not, the search will continue...
'%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]', '%[email protected]',
— Reply to this email directly or view it on GitHubhttps://github.com/typpo/textbelt/issues/4#issuecomment-43713949 .
Nope, unfortunately not.
I'm going to take a chance and remove vmobl from US providers. I assume that because messaging.sprintpcs.com works for other Sprint-affiliated brands, it will work for vmobl too, especially because Virgin Mobile is wholly owned by Sprint in the US.
Thank you for tracking this down! Leaving this ticket open for future duplicate message reports.
FYI - Virgin Mobile (Data Done Right) still receives double texts on a single invocation. Not a huge deal, as these plans are unlimited SMS but thought you should know.
Might be sporadic, for Virgin Mobile at least. Got 2x messages testing it after seeing the last comment. But I've never noticed duplicates before myself as I have Virgin. Though I only started toying with textbelt.com just a month or two ago.
Getting double messages on Sprint. However, when I test all of the US providers myself, only %[email protected] works (and does so as intended). I've only tested it today.
Textbelt was effectively DDOSed yesterday and I noticed that texts to most carriers were severely rate limited or not going through. That may explain reliability issues. Unfortunately, I would recommend self-hosting if you are not able to deliver texts reliably with the textbelt.com service.
Tested it again just now and it worked as expected (just one message). Dunno what was up earlier, but it's fine for me now.