Visit our support portal and click on the link at the bottom of the page to create a new ticket. Please include the following information to help us debug your issue:
- A description of your use case (for instance: app backgrounded, on wifi/mobile data, lot of network fluctuations)
- Your Plivo SDK Verbose Logs (Android application logs)
a. Pointers we'll be looking for in logs are like all the logs with tag ‘D/PlivoEndpoint’ or ‘E/PlivoEndpoint’
b. All SIP transactions, which look like:
HTML
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 52.9.254.127:5061;received=52.9.254.127;branch=z9hG4bKc497.8ec67418aa83e5d7d0f48ad11f78026c.0
Via: SIP/2.0/UDP 52.220.63.151:5080;rport=5080;received=52.220.63.151;branch=z9hG4bKKK6pv4Farvy9m
Record-Route: <sip:52.9.254.127:5061;transport=tls;lr;r2=on;ftag=NN36BrBcQ48pK;did=8c6.4611>
Record-Route: <sip:52.9.254.127;lr;r2=on;ftag=NN36BrBcQ48pK;did=8c6.4611>
Call-ID: 62b89520-3410-11e9-90de-d1c5e59c76a4
From: “android2181024115535” <sip:+654321@52.220.63.151>;tag=NN36BrBcQ48pK
To: <sip:android1181024115518@52.9.254.127>
CSeq: 725237 INVITE
Content-Length: 0
3. Plivo callUUID (like Call-ID:352231d3-3ea9-40c8-8259-e4843f5b02fc)
4. Plivo SDK version
5. Plivo SDK methods — for example:
a. endpoint.login();
b. outgoing.callH(num, headers);
6. Android device version (for example: android 8.0.1, android 9.0).
7. Android device model (for example: Samsung Galaxy A8 Plus)