I have a helpdesk app I am developing for a client and they have a few people they have on as call people. Does each one need a different twilio number to be able to call out at the same time to different people? I have tried this already with my current setup but it only conferences the two people with the caller. I am using the twilio soft phone feature to allow agents to call out to different numbers. Do they each need to have a separate twilio number?
not at all. If you have already verified an outgoing number, you can use that or any Twilio number that you have on your account as the caller id. You certainly don't need a number per agent for outgoing calls.
Hope this helps.
Related
Currently, I am using WhatsApp Business api cloud on one of my web project, I would like to register a customer's phone number but via api instead through meta, developer platform like following:
"Here is the image to register customer's number in the meta developer platform"
I want do this:
(managing the phone numbers)
but via api, and later of that send the verification code via api as well.
If someone can help me , telling me if that is possible and sharing documentation or the endpoint I would appreciate it very much, I've been looking at the documentation and postman's examples for 2 days without any success.
I'm sorry I didn't share the pictures directly, it is my first question on Stackoverflow
Thanks in advance,
Greetings!
I guess you are using WhatsApp provided a test phone number in From, you need to read this, https://developers.facebook.com/docs/whatsapp/cloud-api/get-started#sent-test-message
Enter the recipient phone number you would like to message in the To field. Ensure the number is correct, and that you want to add it to your list of 5 possible message recipients —as you add phone numbers, follow the prompts on the screen to verify you have access to them. Once this number has been added, it cannot be removed from your list.
Note: This limitation is only for WhatsApp-provided test phone numbers. Real phone numbers that you register do not have a limit on the number of recipients.
You don't need to register receivers' phone numbers if you are using your own real business phone number in the sender's phone number.
I need to accept bitcoins on my website (PHP). I'm using blockchain and i have read the api: https://blockchain.info/api/api_receive Is quite simple but i have some questions, but first i will try to explain what i need.
Client send bitcoins to my wallet (Any amount they want)
Server will be notified with confirmations until gets OK.
Gets the sent amount and client wallet from callback and store in DB.
Now my questions:
"You provide a bitcoin address we generate unique addresses that forwards payments to that address instantly notifying a callback URL."
Q: Can we reuse that address and all clients use same address to send bitcoins? Or address will be deleted? The address have a lifetime?
Instead create address to pay is possible clients pay directly to my wallet and server got notified? I don't need extra params like tokens.
I end up in a website that use always the same wallet/address for each odd: http://bitzillions.com/satoshibones
I will like to have a pay system like that, one address per game.
Also should i use blockchain/blockchain (https://github.com/blockchain/api-v1-client-php) library or the simple library (https://github.com/blockchain/receive_payment_php_demo)?
Also if you have any suggestion or alternative i will like to hear.
I think I can help. Disclaimer that I work for BlockTrail.
It would not be good to use the same address because people can view the historical transactions associated with that address. It is recommended to use a new address for every transaction. These can be under the same wallet or different wallets. That may sound complicated but with the possibilities as long as the universe is old you can make a new address per transactions. Some wallets will do this for you automatically. This is called HD Wallets or Hierarchical Deterministic Wallets. You can also use this to have your clients always pay into the same wallet.
You can also use an API to create these wallets. If you are interested in using BlockTrail's here is the link: https://www.blocktrail.com/
We also have webhooks that will send you notifications for confirmations etc... If you want to learn more about our platform, here is a blog that describes it. BTW it is free! https://blog.blocktrail.com/2015/06/blocktrails-developer-platform/
This is an authentication flow, which logs in the user with only the phone number provided (Whatsapp style). The Steps are:
User enters phone number and sent to server.
Server generated 4 digit random key, and save the pair (phone,key) in DB.
Server asks 3rd party SMS service to send key to phone.
SMS service sends message.
User enters the key from sms, and together with phone, sent to server.
Server checks the pair against the DB.
If pair exists, server sends back a token for further calls.
What I am trying to understand is where services like Twilio and Nexmo fit in (or replace parts of the flow).
From what I understand, looking at Nexmo for example,
I can replace steps 2 and 3 with an API call to:
https://api.nexmo.com/verify/
and save the request_id from the response in the DB as pair (phone,request_id).
And now, when the user enters a 4 digit code and sends it back,
I need to call:
https://api.nexmo.com/verify/check/json
providing it with request_id and code.
But where do I get the request_id?
Do the server needs to send it back to the client, the moment it gets it from Nexmo?
I can't see the benefits of using Nexmo here, what will it save me?
Answer to your first question: the request_id is part of the response to the first verify API call. See: https://docs.nexmo.com/index.php/verify/verify
As to what are the benefits of Nexmo here, I believe you have two options:
Generate your own code, use Nexmo to text it to your user, have the user submit the code back to your application, verify code against your own database.
Use Nexmo verify service to generate and send the code to the user, store the returned request_id in your db, have user submit code to your application, call Nexmo verify API to validate code.
In some ways the first option is easier as it is less API calls. However the benefit of the second option, using Nexmo Verify, is that they provide a whole lot more capabilities into the service to fall back to a voice call if SMS isn't working, filter out virtual phone numbers to prevent spam, you don't have to pay for failed SMS attempts, reporting/analytics, etc. etc.
Hopefully that helps a little.
I'm setting up a new time clock-type application for one of my clients. We need the worker's location whenever the worker calls in to confirm they are at the proper job site.
So I found some services like this one http://timesheetmobile.com/ which claim to be able to: "Unlike other location applications that run on the phone, Timesheet Mobile utilizes the carrier's secure network (cell towers) to identify the location of the employee's phone." They claim this works with any cellphone - no app required.
Is this kind of location data available from Twilio for either incoming calls or SMS?
In short, no, you can't use sms for geolocation. At best you could use any number of databases to find out the general area that the senders phone number is from, based on their areacode/exchange but not where they were when they sent it.
My client requires an sms to be sent to him, whenever an invoice is made on his system by any of the employees. I have no idea how to configure it. Do I need to buy any sms-server service?
How to integrate into my application?
Any help will be highly appreciated.
Thanks
I am not sure what country you are in. But in the UK i use this provider.
They have excellent examples
I can send SMS from my webserver, my Windows .NET Form application, a iPhone app if i wanted to. This is possible because it uses a simple HTTP Request API, so even using JavaScript AJAX from the client will work.
Just search for SMS Gateway and find your countries advisability. Look at a few and decide which one suits your needs and also the costs involved.
My Provider charger per sms.. no signup fees, no contracts, just top up.
Using a mobile phone is more involved, but obviosly it has the benefit that you control every aspect of sending, receiving and processing data.
for example 1, 2, 3
You can even buy a module from china just designed to interface via Serial to send/recieve SMS, and even use the GPRS to get/send HTTP request.
There is two option
1) have to buy service from provider or
2) you have to connect your mobile with pc and send msg using AT command
A lot of carriers will allow SMS via e-mail. This may be a better option for you.
Here is a list of the e-mail address formats for a number of carriers.