Please share support tickets or issues in below format so that it will help us debug issues quickly:

  1. Description of the use-case you are trying to accomplish (like app backgrounded, on wifi / mobile data, lot of network fluctuations).

  2. Plivo SDK Verbose Logs (Android application logs).

    1. Pointers we will be looking for logs are like all the logs with tag ‘D/PlivoEndpoint’ or ‘E/PlivoEndpoint’

    2. All SIP transactions are like:

SIP/2.0 100 Trying

Via: SIP/2.0/TLS;received=;branch=z9hG4bKc497.8ec67418aa83e5d7d0f48ad11f78026c.0

Via: SIP/2.0/UDP;rport=5080;received=;branch=z9hG4bKKK6pv4Farvy9m

Record-Route: <sip:;transport=tls;lr;r2=on;ftag=NN36BrBcQ48pK;did=8c6.4611>

Record-Route: <sip:;lr;r2=on;ftag=NN36BrBcQ48pK;did=8c6.4611>

Call-ID: 62b89520-3410-11e9-90de-d1c5e59c76a4

From: “android2181024115535” <sip:+654321@>;tag=NN36BrBcQ48pK

To: <sip:android1181024115518@>

CSeq: 725237 INVITE

Content-Length: 0


  1. Plivo callUUID (like Call-ID:352231d3-3ea9-40c8-8259-e4843f5b02fc).

  2. Plivo SDK version.

  3. Plivo SDK methods call flows, for example:

    1. endpoint.login();

    2. outgoing.callH(num, headers);

  4. Android device version (for example: android 8.0.1, android 9.0).

  5. Android device model (for example: Samsung Galaxy A8 Plus).