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.
Related
I am building an app which requires phone number authentication, but all the online SMS API providers are relatively expensive compared to the SMS prices I can get from Mobile Service Providers here in my country.
Let me start by saying, I KNOW it's not possible to send SMS programaticaly directly but...
My server runs on cloud, so I can't exactly plug in a GSM module to the server computer, but would it be a viable option if I create an SMS server using a GSM module and a Raspberry PI, then have the Raspberry PI have a connection to my Server so it will be notified whenever there is a new authentication to be, and then it will receive the users information and send the user the authentication SMS. Is this a viable idea, I know this will work, I'm just curious speed wise?
I have seen some providers on internet where you can send Whatsapp messages using an API. Its not official WA API integration.
These providers will spawn a instance for you, show you a QR code. You need to scan the QR code in your WA app. Once scan is completed, that instance is added as linked device in your app.
Now they provide an API which you can use to send messages. API accepts instanceId, mobile number and message as query param.
These messages are send using your WA account and number. You can see those sent messages in your app.
Basically everything is happening from your account via web whatsapp but from a remote setup and using an API.
Here are a screenshot to help you understand what I am trying to convey.
Sample API call:
https://DOMAIN-HERE/api/send.php?number=84XXXXxxx&type=text&message=test%20message&instance_id=6XXXXXXXXXX&access_token=XXXXXXXXXXXX
I want to setup something similar. I searched the Internet on how does this work and how I can create my own similar setup but could not find anything.
Can someone please point me in the right direction.
What all these providers are doing is hosting a running instance of a whatsapp web client using your phone number, this is why they ask you to scan the QR code (same as whatsapp web does).
Users of this kind of services must be crazy to allow running an unattended instance of whatsapp against their own phone account, as on the host there's full access to your whatsapp encryption keys, contacts, history of messages,... but the security implications are for a different topic.
If you want to have a headless instance of whatsapp-web like the one they offer, you should have a look at repos like this one here: https://github.com/tulir/whatsmeow (there are others similar, for different languages).
I would like to build a browser-based client using WebRTC to join video conferencing meetings (could be any VC Provider like Zoom, Webex, MS Teams, etc.) using their SIP URIs.
So, I wanted to understand does the browser-based client that I am making, also needs to register with some SIP server and need to have a URI, or we can join a SIP call without requiring SIP Registration?
You generally* only need to register your SIP URI if you want other parties to be able to call you. If you're calling from a browser then it's likely you won't be receiving calls since the SIP agent will only be available while the browser tab is open. The best starting point for browser based SIP is jssip.net.
*Some SIP Providers do require a registration in order to place an outgoing call, however, that's due to their security policies rather than being required by the SIP protocol. In my experience this type of policy is rare and used by maybe <10% of SIP Providers.
(could be any VC Provider like Zoom, Webex, MS Teams, etc.) using their SIP URI
Of those I've spent a fair bit of time looking at MS Teams and am fairly confident there's no SIP option to call Teams Users or Meetings. The only option I know for Teams is the Microsoft Graph Communications API which is a closed source REST services based API. It does use WebRTC under the hood but the signalling mechanisms, which is where SIP fits in, are proprietary.
I don't know about Zoom, WebEx etc. but I suspect they may be similar and have their own SDK's.
i'm building a website that uses WebRTC to share audio and video. Now i'd like to access WebRTC features on Android devices so i can create an app that can receives audio and video streams from the website.
I've looked for a technology allowing me to do that and I've found SkylinkJS.
It looks great but i'm wondering something. Can i build a custom authentication system on top of SkylinkJS logic. What i mean is that i'd like to make sure the connection to SkylinkJS rooms are initiated by users actually authenticated on my platform.
At the moment, i do that using socket.io but i can do it since i'm using raw WebRTC. How can i do that using SkylinkJS? Using the REST API?
Thanks.
PS: i cannot tag this question with 'skylinkjs' since it's a new tag, but it mights be cool if someone could do it.
Yes you can integrate that with the REST API in this Applications REST API link here - . You can generate your own credentials.
You can generate the connecting credentials from your server and then when the User logs in, generate the credentials for Users to connect to the Room. See more in their support article.
SkylinkJS uses key based authentication mechanism to authenticate against the Temasys signaling servers. This ensures that any application using Skylink can only connect to calls in your application if the app can provide the same secure keys (from your Temasys developer account).
Your best bet in looping in Android would be to use the android counterpart. http://skylink.io/android/
I need to use Webrtc api for video and audio call between two users.Actually i have a Elearning learning management system with many users recently i have developed a chat system so that users logged in LMS can chat each other using simple php,ajax and jquery.Now i have implemented only text chat.
I need to develop video chat also like Google hangout and facebook video chat.Users registered in my system are having different email domains means some one have gmail account ,yahoo account etc.
Expecting quick reply
Thanks
To get started with WebRTC, I would suggest to first have a look at the following tutorial on WebRTC fundamentals.
You can then start to implement the native WebRTC API but be aware that you won’t be able to establish a video call if you don’t add a signaling server which does not come built-in with the WebRTC API.
Also if the caller and callee are connected to two different networks, you’ll often need ICE, STUN and TURN servers. Video chat is more complex to implement than text chat and if you don’t have the time and the resources to learn the fundamentals and deploy servers, I would suggest you give a try to a WebRTC Platform that already have an up and running cloud infrastructure to which you can access through an API.
It is the type of WebRTC Platform that we offer at Weemo.