I am trying out twilio using the quick start tutorial. I am doing browser to browser calls. I have followed the tutorial. When I try to make a call it rings and connects. It then plays the "free account" message and asks me to press any key to continue. When I press a key it does nothing for a few seconds and then hangs up without going through to the other browser.
Is this happening because I am on a free account or is there something else I need to do in order for it to register the key press from the browser?
Twilio evangelist here.
I can see where this might be confusing and its good feedback. The prompt to press any key is apparently making the assumption that you are calling from an actual phone, which would include a keypad that lets you press any key. Obviously with a simple Twilio Client app there isn't by default a number pad to press, but the JavaScript SDK does include the sendDigits function, which makes it pretty trivial to wire up a button (or some other UI) in your app to send the equivalent of a key press (aka a DTMF tone) to Twilio.
Hope that helps.
Related
I have been using trail account. I have made a application to make a call and say Birthday greetings. I can able to make a call to the registered phone number and the message is speaking when i press a button. I need to receive the message without pressing any button. is there any option to do this? Kindly share if we can do that.
Is there any feature that makes straightforward call without prompting the caller to press any keys in dial pad ?
Thank you in advance.
Twilio developer evangelist here.
The message prompt to get the recipient to press a key is a feature of our trial account. The way to remove that message is to upgrade your Twilio account by adding a credit card or PayPal account and adding some funds.
Once you have done that, the message will go away and your call recipient will only hear the birthday greetings.
I have searched and have not been able to find a definitive answer. I know that it is not possible to get the phone number of the current caller using Objective-C, but I don't need the number.
I want to send a text message to the current caller. Does iOS have a method to allow you to send a text message from an app to the current caller.
The scenario is this:
End user calls another user
They put the person they called on speaker phone and navigate to my app
The app has a button that allows them to share information via SMS to the person they are talking to while they are talking to them without having to do anything more than click a button (the user doesn't have to type the other person's phone number manually to send the SMS).
Sukhdeep is correct.iOS will never allow you to perform Messaging without user involvement.
The answer is No.
Apple will never allow you this.
I keep getting
Uncaught Twilio.Exception: Run Twilio.Device.setup()
when starting a call after the page posts back.
The problem is not consistent and after refreshing the page several times it goes away and i can make outbound calls again. But it happens at least once after a post back.
any ideas..?
Twilio evangelist here.
Just to be clear, are you using the Twilio Client JavaScript SDK?
If that is indeed the case, can you try hitting http://clientsupport.twilio.com/ to make sure that your browser will support Twilio Client. If everything lights up green there, I'd suggest taking the output from the browser check site and opening a case with our awesome customer support team. You can simply send and email to help#twilio.com
Hope that helps.
I've using the basic phone example from Twilio, have set it up to use the auth.php example and have directed a purchased phone number to basic-call.php.
When I try to call that number, I hear the default prompt, but then get a busy signal and nothing happens in the app. Both the auth.php and the basic-call.php are set to use the same client ID (basic), and I can't find any documentation on Twilio about what it means if there's a busy signal when directing to a client app.
I don't have any PHP errors in the logs or any errors showing up in the Twilio console, if that helps?
Turns out the problem was that I wasn't signing the request with the account SID and auth token of the subaccount that number was associated with. I sure hope this helps someone else!
I am working with a 3rd party web service to process credit card payments.
When I swipe a credit card via google chrome the payment is detected and processed.
However when I attempt to swipe a credit card via the built in Delphi web browser TChromium, nothing happens.
Can't figure out why its not working are their any settings I need to set on the TChromium browser?
Update
I have verified that that the card reader reads and posts the data to whatever field/component is selected.
One difference I have found with Chrome and the TChromium web browser is that when I process a card in the TChromium web browser it automatically tabs to the next html component after processing the card.. Where this does not happen in Chrome it just stays with the current field/component selected.
The Question title is misleading but only because I did not understand what was happening after some investigation I was able to solve the problem. I hope this answer might come in Handy for someone someday though its a pretty isolated problem.
So I found that the MagTek reader reads the credit card data to the field and then Sends a "Enter" button afterwards.
And the Program I am currently working with has an option where when a Enter Key is pushed it will instead send a Tab so that a user can get to the next fields by the enter key.
So the program was intercepting the MagTek reader initiated enter key and replacing it with a tab which interfered with the payment process.