Can you please enlighten on how billing server is to integrate with IVR? I mean when a call is terminated to IVR if it has to check billing/credit eligibility before transferring the call to an agent/terminating user.
If your billing server supports Diameter for real time billing, you can use Restcomm jDiameter in your application to connect to your Billing System and have the IVR being notified if the user runs out of money and cut the call.
If your billing server supports HTTP then you can do the same thing via REST API calls to your Billing server without any additional software
Related
I am working on implementing a POC application that needs to use Whatsapp API e-commerce features. https://blog.whatsapp.com/making-it-easier-to-shop-on-whatsapp-with-carts
For that, I have already set up the On-Premises Docker setup. But I am stuck with registering the phone number.
seems it will take time to verify the account. actually, we don't have much time and need to do a quick demo for our client.
is there any other way / any sandbox environment to try these features without those registration and verification processes?
I'm working on developing a mobile app to buy and sell cryptocurrency, and I want to allow the user to setup recurring purchases. The user should be able to schedule their purchases, and then a service running on a server will purchase the correct amount of crypto at the correct time.
The issue I'm having is that I don't know how to handle the authentication that would allow my server to make the requests on behalf of the user. Currently, I am trying to use the Coinbase API, but I would be willing to use a different cryptocurrency API if there is one that allows for this type of authentication. Is there a way to make this work?
I am writing an iOS app that will use data from Skype for Business, and am following the guide from Microsoft called Create an application, which must be done before being able to use the API's.
What is unclear to me is when exactly to create an application? Is it:
per client, i.e. only once ever?
per home server?
per user?
per session?
The application here is more a kind of "virtual object (the application)"
which needs to be created here, until you can start using Skype for Business (SfB) features.
So your question isn´t that easy to answer as its not clear what you wish to perform (e.g. did you wish to login, perform some task and then logoff again?). So it depends a little bit on your application and which features you are using. Therefore its no "only once ever" as the "virtual object (the application)" is destroyed at some time (e.g. your application crash and the SfB server no longer got a "yes we are still here and are listening" requests). This is controlled by the lifetime of a token which is eight (8) hours for authenticated users so you need to renew that or your application will stop working. So its more a "per taskuser & login & time" approach...
Microsoft explained the above as well in the following statement: "This is how you register your application with UCWA 2.0 as an agent of the user whose credentials you obtained in a previous step."
If you are creating an iOS application that will interact with a Skype for Business server, you can use the Skype for Business App SDK for iOS. This client library handles anonymous meeting joins for users who are not homed on a Skype for Business server. For all other Skype for Business features, you'll need to use an iOS REST library of your choice. The REST endpoint that works best for a client application is actually the Skype Web SDK. The Skype Trusted Application API is designed for server-to-server communications where your server is talking to a Skype for Business Online instance. In that case, your server obtains and processes Skype data and then it makes it available to a client such as an iOS app. Unless you intend to create a middle tier between Skype for Business Online and your iOS app, you should use the Web SDK.
I want to configure sms gateway. my scenario is as:
We have a list of enrolled students. Each one is assigned a tutor. They have to get information about their tutor such as tutor name and contact etc.
I want that they send a formatted sms to the server and server provides the requested information to them via sms.
Please tell me what things, I will need?
Infrastructure?
any demo server available to test my application?
I will be implementing it in PHP
Thanks
Have you seen Twilio's REST API for SMS already? https://www.twilio.com/sms/api. That will save you lots of time configuring own GSM modem firmware and maintaining own SMS transactions. With 3rd party SMS service provider you can just focus on your client app such as sending back tutor's profile to the provider and the provider will carry your message push it back to the student's mobile number.
Of course the old way is that everything (data and GSM software) sits within our own network. I used to have HTC's GSM model like 7 years ago) with my J2ME apps for Nokia, HTC and Motorola smartphones. But nowadays, you have lots or cheaper and better options. Even Android phones can be used as bare bones GSM modem already :D
Enjoy!
Before you go on implementing something by yourself, I suggest that you check services that already do it well. Maybe you can just use them? One such easy-to-use service is Twilio.
I am curious about SMS aggregators and I would like to get info about build one but I have no point to start getting info. Do you know?
Necessary hardware/Software
Good SMSCs to start the bussiness
Most price-competitive SMSCs
Minimum SMS volume to start
Any contact/company
To build your own you could probably start by registering to become a PRSP and content provider. Then you could get a short code from a Mobile Service Provider. Connect to the Mobile Service Provider using SMPP Protocol.
The Mobile Service Provider should give you cridentials: username passwords etc to connect to them.
You could then use Kannel: Open Source WAP and SMS gateway to configure a value added service gateway that you could use to provider sms aggregation services amongst other services such as football updates etc.
You could also host more than one service(client) on the same shortcode/vas gateway.