How to use huawei e5573cs api for send ussd
and test in postmanenter image description here
Related
I already have a SIM card with a company that allows tethering and A2P.
I want to be able to send an SMS with a unique sender ID (company name) using that sim card.
Is this possible and if so, what should I purchase and how do I set it up?
It is NOT possible to alter the senderid when sending SMS using a SIM card + modem. The senderid will simply be the number belonging to that SIM.
If you want to have a custom (alpha) senderid, your only option is using a professional A2P SMS gateway. But even then it is not always possible, as not all countries allow alpha senderids. They might get overwritten to a short/longcode, or the operators require senderid whitelisting (basically, you need to request "access" to an alpha senderid, by sending your personal/company details and SMS content details to the operators. This is done to battle SPAM messages)
Yes this is possible.
Most of the time you don't need any SIM card as you'll be using some sort of API, most of the time a HTTPS/JSON or HTTPS/XML API. If you intend to use a SIM to send SMSes, having a dedicated sender ID will be most probably impossible: using a SIM will make your request arrive through the "regular" signaling link just as "any subscriber" that sends an SMS from his mobile, while using an API will make you use the SMPP links to the SMS-C where specific configuration can be done on per client basis. If I misunderstood something, please sent a comment.
Anyway, you have to have an agreement with your SMS API provider or telco to use a dedicated ID
How can I send an “invisible” SMS via a GSM modem using the C# (the recipient won’t see it, but I will know the status of receipt) to find out if the phone is on or not - “Ping-SMS”
You must set PS_MESSAGE_CLASS0 value as CLASS parameter provided in a call to SmsSendMessage.
In a perfect world, the solution I'm looking for would be an api resource tied to my physical phone, e.g. I could POST an sms message to https://url.com/api/sms, and this api would have the end result of sending an sms from my physical phone. This means that the sms conversation would appear natively in my phone; if the recipient replies to the sms, it would appear just as a normal conversation as if I had physically typed the original sms via my phone.
I understand that I could set the replyto/callback/caller-id via Twilio's api. This would mean that the sms gets sent out by the api, and if the recipient replies to it, I could have the reply forwarded to my phone. But what would be missing in this scenario is the original message sent via the api, that the recipient is replying to.
Is there a streamlined way to achieve this, perhaps with Zapier?
One arduous solution I have in mind is to write an on-phone-app to intermediate the sms transmission so that I essentially have an sms-controlled api on the physical phone vs. a traditional http api. (On android, the api would "listen" via DATA_SMS_RECEIVED_ACTION and then send via sendTextMessage). But this seems cumbersome and would also require updating the app code when/if android changes the underlying SmsManager library. The advantage of this is that I could avoid Twilio altogether, by using my service provider's email-to-sms to send to the on-phone-makeshift-sms-api.
Twilio developer evangelist here.
I think you are looking for a feature that we just announced in preview. This is known as Hosted SMS and allows you to add SMS powered by Twilio to your existing phone number.
You need to apply to get access to Hosted SMS as it is newly in testing. You can do so with the form here: https://www.twilio.com/sms/hosted
I've set up texting to a physical phone by using Twilio's SIM cards and associating it to a phone number.
I'm trying to link Backback and Tropo to send reminders to groups.
Backpack can send reminders via email or SMS, and Tropo can receive messages via a custom SMS number; the problem is that Backback sends the SMS via email, and needs a provider. It can also be activated with a specific url and receives REST or JSON data.
Is there any way to activate a Tropo application using email or find out what provider setting I should use for Tropo?
ON TROPO:
Phone Numbers:
Voice & Messaging: (705) xxx-xxxx
Outbound Tokens:
Voice: ...
Messaging: ...
Tropo does not have an email gateway for receiving SMS. Applications that send SMS by email won't be able to send to Tropo.
One thing you could do is built a small catcher application that receives the REST call from backpack and then makes a REST call to Tropo to send the SMS. It would be sort of like a translator from Backpack's REST api to Tropo's.
I'm using the service of a web site,and I can send text message using their interface(in PHP),but when I try to send an image :
<img src="http://www.google.com/images/srpr/nav_logo27.png" />
I'm receiving exactly the same code,not an image.
Anyone has experience with SMS services?
"Short Messages" are intended for plain text and losing money to Telcos. If you want do to anything with multimedia (like sending images), use EMS (Enhanced Message Service) or MMS (Multimedia Messaging Service). If you want to embed stuff from the web, use e-mail - the person who receives your message has to load the image from the internet anyway, and it's free for you if you send it from a computer.