I have a trial account.
I have set up my webhook url in the number console.
I have set up a node server tunnelled with ngrok.
But when i call my twilio number, twilio does not send response to my
url. Even in the logs, the Request Inspector for all incoming call is
empty.
Since it is a trail account you need to press a key once the call is answered by Twilio to acknowledge it is a trial account before it will execute any TwiML.
Related
My service is sending SMS to users in two different ways:
The main one is the SMS API, my service sends a request to Twilio with all the SMS data, and get the SMS id in the response. With that id it waits for the sms status updates to check if the text was delivered.
But there is another way, as a response to a user sending a text to my service, using a TwiML <message> in the Response. In this case, I send back a SMS to the user, but there is no SMS id to check for status updates (because the service sends the text in the response, not in the request).
So in this scenario, there are status updates from SMS ids that the service can not recognize.
My question is: is there a way to get the SMS id from TwiML <message>s? Or be able to recognise which status updates come from TwiML messages?
Or my only way to do this is to always call the SMS API and do not return a text using TwiML for this scenario?
Thanks in advance!
Twilio developer evangelist here.
The way to get an SID from replying to a message using <Message> is to wait for the status callback webhook. Of course, as you say here, when you reply that way you don't store the details of the message in your system. What you could do is wait for the first status callback webhook and if you find a message SID that you don't already have in your system, use the REST API to look up that message, save the details and be prepared for further status callbacks.
Alternatively, there is nothing wrong with using the REST API to send the message instead of <Message> and just returning an empty <Response> to an incoming webhook.
I need to make outgoing calls from browser and i set capability token with the master account.
Then i make a call request to twilio from browser and return a twiml from my server.
In the twiml, i set the callerId to a subaccount validated outgoing phone number.
When dial to another client, it works fine. But, if dial to a phone number it not work.
From the debugger i saw this error:
it said callerId must be provided for TwilioClient and SIP calls when using Dial.
I dont know why, I need a help.
I connected Twilio connector to my registered Bot.
Whenever I send a sms to my Twilio number, I can see in the logs that Twilio service gets 404 when trying to post a message to
https://sms.botframework.com/api/sms
The bot itself works well. I can test it with the webchat iframe or through the test console. But it seems that the Twilio integration to the bot framework is broken
Twilio developer evangelist here. I've just been through the process and was able to get my messages sent to & from my bot.
The fact that your unable to do that suggests you missed a step in the configuration, so I will try and describe what I did here to see if it helps you out.
Created a TwiML application here and set its messaging url to https://sms.botframework.com/api/sms
Purchased a phone number and changed the messaging section to use my TwiML app.
Added my twilio credentials and twilio phone number to the SMS config section as follows:
One thing I noticed is that when Twilio makes a request to this URL to send an SMS, the url returns a 502.
But according to a Microsoft employee this is "harmless".
Let me know if this helps you at all, or if you still need any help.
We have a twilio number.
When ever any one call on that twilio number then there is an automated voice of twilio play. Can we customize this to a new message?
Thanks,
Rajendra
Twilio developer evangelist here.
You can customise Twilio calls as much as you want! I recommend you take a look through this QuickStart for handling incoming phone calls with Twilio which should get you up and running.
To quickly describe it though, you have a Twilio number and that number has a Voice Request URL configured in the number's settings. When you make a call to that Twilio number, Twilio makes an HTTP request to the URL. That URL needs to return TwiML (a set of instructions to Twilio in XML) which tells Twilio what to do with the call.
If you update the URL to something you control and then return different TwiML, then you can change the message and do a whole lot of other stuff with your Twilio number.
I need to make calls to some Twilio clients that will received the call through the browser. The problem is, these clients don't necessarily have their browser open.
I know normally, a user would have to open up the browser and through the twilio util capability and twilio device to turn their browser into a device. And THEN they can receive incoming call.
Is there way to dial clients, when they haven't initialize their twilio client yet?
Twilio evangelist here.
If you try to dial a client who is not online Twilio will view that as a no-answer. You can get a notification of this by providing a URL for the <Dial> verbs action parameter.
When the call ends Twilio will make a request to this URL with a parameter named DialCallStatus which you can use to determine what happened when Twilio tried to dial the Client.
Hope that helps.