I need to do some actions with sip phone from desktop application. The sip service provide api to handle events and send commands to manage calls. To control calls from specific phone device I need to know internal number.
The question is about how to automatically get the internal number attached to users sip device?
Users can change locations and when they logging in I need to detect internal phone number of device that used at this moment.
Related
I checked the device is paired with Tuya Smart App, and then use the device Id in Tuya Smart APP for control; I confirm the Id of the device to be controlled is correct.
I tried it a few times with the engineer，there are several situations:
The device to be controlled is not an OEM App created by the developer on the Tuya Open Platform; or the Tuya Smart APP is used to pair the device and then control the device through an interface call.
solution:
First check if the device is paired with Tuya Smart APP, and then use the device Id in Tuya Smart APP for control;
Then check whether the Id of the device to be controlled is correct and whether it is from an OEM APP created by its own developer account or an APP developed based on the SDK;
In the end, you need to make sure that the device and product created by the OEM APP created under your developer account can be controlled through the cloud-cloud docking API call.
The device requested to be controlled has been removed, restored to factory settings, or re-configured to the network.
solution:
If the device has been removed, please re-configure the network and add it in the APP;
Re-obtain the device list and refresh the device ids to be controlled.
Interface parameter passing error.
solution:
Check if the following parameters are correct：
The device id is wrong. Note that the device id is not uuid.
The area url is wrong. Pay attention to the area where the device is paired. At the same time, call the interface address of the corresponding area.
there are 3 different api explorer calls to retrieve the status, only one works for me: https://openapi.tuyaeu.com/v1.1/iot-03/ (General Device Management -> Get Device Information)
Does Google's SMS Retriever API get the list of phone numbers from the SIM lines on the user's device (which means that it's similar to TelephonyManager), or from the user's Google Play account?
I'm the product manager at Google for this API. Yes, as of the latest version of Play Services, the Phone Selector shows both the phone number for the device from the TelephonyManager (if it can be parsed as as a valid phone number) as well as recent phone numbers for the active Google Accounts on the device.
This is not directly addressed from the docs but if we infer from this statement in the Obtain the user's phone number:
Often, it is the best user experience to use the hint picker to prompt
the user to choose from the phone numbers stored on the device and
thereby avoid having to manually type a phone number
we can deduce that SMS Retriever API gets the contacts from your device.
Update
Please look at #Steven Soneff's answer
The numbers are retrieved from Smart Lock for Passwords on Android. They are retrieved if the user already stored it using Smart Lock else they will be empty. You may also ask the user to store the number for future use-cases using Smart Lock for Passwords.
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.
I'd like to develop a tracking system using an API of course (like the famous Orange API).
the idea is simple:
I send a SMS (from my Web interface) to the person i want to track
The person's mobile terminal (GPS like this) send me back automatically
the coordinates by SMS.
The sent information are displayed on the user's web interface.
The questions are simple:
How the terminal can send automatically the response?
How to indicate in the message that the information is for "user4655"?
How to make connection between the information and the database?
Thanks,
Regards.
* How the terminal can send automatically the response?
Ans: You set the gateway and the time intervals you want the device to send the sms to on the device itself.
* How to indicate in the message that the information is for "user4655"?
Ans: The gateway you use will have the API to determine that the number it is sent from. The device will use a registered phone number from either a sim or enabled by one of those cell providers.
* How to make connection between the information and the database?
Ans: I dont understand this. But I'm guessing you will have a database to keep track of the user data. You'll just probably need another table that is a child of the user, which has a list of the data and the time they came in.
I am developing an application in which I want to use push notification service. I have a server, now I want to know that
How do I handle multiple devices?
Is there a unique device id/name for every iphone?
Suppose I want to delete request for a specific device token, so how do I handle multiple users?
Is there a way I can generate unique name for every device through application?
You should really read the APNS documentation, this is all explained in depth there.
The short answer is that when you launch an app on the phone it requests a push notification key from the OS. You then take that key and send it back to your server. Your server uses that key when it sends a push via Apple's servers to indicate the devices to send the push out to.
The service just gives you a token. If you want accounts or device names you need to come up with them and store them with the credentials on your server.
You handle multiple users by same way you handle single users, you send message with the appropriate key to the service.
As for deleting a request, you can't. It is like a text message, there may be some latency before hits the device, but the moment you commit the push it could be delivered instantly.