I have tried to setup twilio click to call java Servlet example by following the below url.
https://www.twilio.com/docs/tutorials/walkthrough/click-to-call/java/servlets
However, when I am providing the phone number to call (it's an India number starts with +91), no call is coming to that mobile.
The number which I am calling has been verified in twilio account. It can receive twilio sms.
No error is coming back from twilio. But still I am not getting any call. I have verified by providing another phone number (of another service provider) ...but same result.
twilio console shows the call has happened for 15 seconds..in each case. But in none of the case I have got any ring in my phone.
I am am not also getting any call in the callback url (/connect ) from twilio which I am supposed to get after the call is connected...that is twilio is supposed to call back my url.
I have also provided a permission in the following place to for voice call in India.
https://www.twilio.com/console/voice/settings/geo-permissions
Thanks in advance
SR
Kevin from Twilio here.
It sounds like there may be something here worth investigating with support. If you could, please send an e-mail to help#twilio.com with this description. If you also provide your Account SID and if possible a call SID for the calls you are debugging in the console, that should help debug the issue more quickly.
Thanks, and sorry you're having troubles.
Related
I've integrated Google inApp billing in my android App. It was working fine, But now I noticed that on one device its always returning BILLING_RESPONSE_RESULT_ERROR response. In Logcat it shows following error.
BillingClient: getSkuDetails() failed. Response code: 6
I couldn't find any help regarding this issue, Can someone help me what could be the possible problems and solution. Thanks.
This generally happens when you have signed out from Google account in your device. All you need to do is just sign in again, if needed do a full restart.
Well, my situation is the connection between my device and google's servers is unstable.Try to open the GooglePlay,and check if the connection is healthy.And it wroks.
In my case, this happened when a new app I submitted was in "Draft" status, not yet approved by Google. Just wait until it's approved and payments will start to work.
An alternative would be to submit it in the internal track and add the email for you play account as a test user.
I recently received the notification from google that my app uses some of the permissions that are not necessary so I need to submit a declaration form .So I submitted the declaration form .
They asked these questions so I replied this:-
1: In one sentence, please describe the core functionality of your app.
This is an security app, app uses sms in sense when there is not internet, app will send sms after asking user and giving full awarness about the sms sending, sms only will be send when user need not intensively, and will send to only user declear person whom user want to send
2: What is the core functionality in your app requiring the Call Log and / or SMS permissions?
Connected device companion apps that enable send and receive of SMS or calls [SEND_SMS, WRITE_SMS, RECEIVE_SMS, RECEIVE_MMS, READ_SMS, READ_CALL_LOG, PROCESS_OUTGOING_CALLS, WRITE_CALL_LOG], N/A
4: Do any of the following other use cases apply to your app’s core functionality request for Call Log or SMS permissions?
Physical safety or emergency alerts.
After few Days I got this reply
We reviewed your request and found that your app does not qualify for use of the requested permissions for the following reasons:
The declared functionality {CONNECTED_COMPANION_DEVICES} is determined to be unnecessary or not aligned with the core functionality of your app.
It looks like you are using SMS/Call Log permissions group for functions that might qualify for exceptions: {SAFETY_EMERGENCY_ALERT}.
Please declare it in the declaration and resubmit the form.
Please Tell me is there any solution to fix it ? What changes I need to make in my code?
The first app that I developed and put on the playstore (very ugly) did exactly what yours does and so I received YOUR SAME NOTICE.
In fact, I am at the next step as I have started a "challenge" to request an exception.
They answered me like this:
SMS / Call Log permissions group for ineligible functions: {Device Locator}
.... but my app is a DEVICE LOCATOR! It's its main feature!Mahh
I suggest you do, as I did, by replying to the e-mail and saying if the localization apps are allowed or not via sms ... there is no written anywhere in the policies that is not allowed.
I have a running and working implementation of the Java Mail API. I am using the api to send out bulk email messages. On some occasions, the login gets blocked by google. So, I go to my gmail account and allow access to apps and set the security level to give access to apps that don't use what google calls "modern security". So, the google page tells me to try my program again. I try it again and it still won't let me log in. On some occasions when I have a login fail, I can go to the account, log in, and type in the recaptcha. This will allow me to log back in shortly after and send emails. However, the problem I am now experiencing does not show any recaptcha, nor does it say anything about any unknown apps that tried to access the account. It says nothing, and just wont let me log in to my account. I created two new accounts for testing and they worked fine. The account that I created that doesn't work only allowed me to send 17 emails before it blocked my service. Does anyone have any suggestions? Thanks!
Go to your Gmail account setting page and Enable access of Less secure apps. Then try with Java Mail API. Hope it works for you.
Make sure that your JavaMail with google auth is working fine, Check concurrently with Different app. If not post your code
If you're using a free Gmail account, Google might think your bulk email is spam (duh). If you're going to send bulk email, it may be time to pay someone for a business account that will let you do that.
I am trying to get my app id from Telegram API by using the method register.saveDeveloperInfo, but I cannot find the way to do it.
I'm using de MTProto Java library.
This is what I had done by now:
I made my own register.saveDeveloperInfo implemmentation in Java.
I call the method with the corrects params (https://core.telegram.org/api/obtaining_api_id)
The method returns a true boolean but I have not received the sms with my app_id.
When I enter in my app section of the telegram web (https://core.telegram.org/myapp) shows the "Your app is not ready yet" message.
Anyway, I'm trying to use the app_id from the source code of the official client but I can't send or receive message.
Does anyone know how to do it or where can I find more information?
You can get your app api_id and app api_hash from your Telegram app page. This is what you'll be using as of this writing. If you are asked a password, provide the mobile phone number you'll be using to develop and Telegram will send you the password.
If you are asked a password and Telegram didn't send it to you, try to provide the mobile phone number without "+".
Try disabling any anti-spam software or VPN. Disabling ABP for https://my.telegram.org/apps helped me
The task is to validate an US phone number. Checking format of the number is not enough.
So I should make a call to the number and determine if the subscriber answers.
Is it possible to automate it using VOIP solutions?
Please, suggest any ideas to start with.
I'm going to implement it on Windows platform (probably .NET or Java). It can me for example a console application that receives a parameter (a phone number) and returns true or false.
I would recommend using Twilio (twilio.com) for this. It is a simple to use web application that allows you to build this type of functionality in the cloud. Your system would make an HTTP POST request to initiate the process - and your web server would end up being called with the outcome of the call. Their website provides many examples that would fit what you're looking to do.
Probably you may try to use "options ping" for that (see http://hive1.hive.packetizer.com/users/packetizer/pocs/POCS-1.pdf).
I didn't try this myself yet, but in theory, if you try to send an OPTIONS request to device, then you should have 200 or 503 in responce. That means device recieved your packet => device number is valid and route is known. Other responce codes will indicate an error.