Closed luukschipperheyn closed 5 years ago
@luukschipperheyn
Thanks for reaching out and providing detailed description and logs.
Can you please try the same scenario using a different device? We have validated SDK functionality using API 19 devices and have not seen this issue. We would like to make sure the issue you are facing is not device specific.
@kbagchiGWC
I found the cause of this problem. The identity string used for generating the access token contained an @
-character.
You can reproduce this behaviour by changing the identity in voice-quickstart-android:
private static String identity = "alice@";
From the docs:
The identity provided in the accessToken may only contain alpha-numeric and underscore characters. Other characters, including spaces, will result in undefined behavior.
I'll go ahead and close this one
Description
When I run the example, i consistently get the following error message:
Call Error: 31503, Service Unavailable
From what I can tell, this seems to be the critical part of the log, having to do with finding matching TLS transport:
Steps to Reproduce
Code
Android code:
voice-quickstart-android
. The only changes I made:hardcoding an accessToken:
Increasing Twilio log level:
I generated the token with
voice-quickstart-server-python
, using the following SID's:Expected Behavior
I expect the call to start
Actual Behavior
App returns to start screen, shows toast message:
Call Error: 31503, Service Unavailable
Reproduces How Often
100%
Logs
Versions
Voice Android SDK
4.4.0
OS Version
andoid 8.1.0
Device Model
Samsung tab active 2