ip to ip.NullPointerException: null upcall object in pj::Call::onCallState ， java.lang.NullPointerException: null upcall object in pj::Call::onCallTsxState and resend old msg 180 rinding #3950
Comments
|
This seems to be a pretty standard scenario: Remote cancelled the call during early state. So there might be some unexpected situation here that caused the retransmission to continue (Btw, the timing is also a bit curious here with the exception happening at 15:20 while the rest of the log is at 16:07.) But unfortunately, without a more detailed log (that should at least include the INVITE message and the CANCEL), or steps to reproduce, there's not much we can do here. |
Yes, both A and B. Device B crashed during the call, causing device A to have problems as described in the log. Regarding exceptions, the exception log at 15 o'clock is not stored. Starting from the 180 retransmission, the null exception begins to exist. I just found a more detailed log. Observing from the latest logs obtained does not seem to have anything to do with this. About this exception. Let me ask another question |
Describe the bug
I'm running Android 8.1, using IP to IP for LAN communication. This problem seems to occur when multiple CALLs are disconnected from the network after calling/ringing. Not entirely sure how to reproduce. Appeared 2 times. What the log shows seems to be that the expired CALL timer is not destroyed, resulting in repeated attempts to retransmit. This causes "null upcall object in pj::Call::onCallTsxState" and "null upcall object in pj::Call::onCallState". There is currently no more detailed log
java.lang.NullPointerException: null upcall object in pj::Call::onCallState
java.lang.NullPointerException: null upcall object in pj::Call::onCallTsxState
05-09 16:07:55.060 3883 3972 D pjsip-pjsua_0: 16:07:55.058 tsx0xc0cfc864 Retransmit timer event
05-09 16:07:55.062 3883 3972 D pjsip-pjsua_0: 16:07:55.061 tsx0xc0cfc864 .Retransmiting Response msg 180/INVITE/cseq=7220 (tdta0xc41c6064), count=80, restart?=1
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: 16:07:55.063 pjsua_core.c .TX 545 bytes Response msg 180/INVITE/cseq=7220 (tdta0xc41c6064) to UDP 192.168.1.105:5060:
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: SIP/2.0 180 Ringing
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: Via: SIP/2.0/UDP 192.168.1.105:5060;rport=5060;received=192.168.1.105;branch=z9hG4bKPjCsMdhdUVEEZzcZWtPD8Q7qLo4cgnwk3r
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: Call-ID: S.yf6J.qiGUy3xpIPG-mQMDeNUtbrxxf
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: From: sip:405579132320223232@192.168.1.105;tag=TQjK-HyH2C67MSu5mmkx61vnFbgEMLS2
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: To: sip:457007454442622976@192.168.1.101;tag=07a8aa0c-1689-4121-beca-5b4509559138
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: CSeq: 7220 INVITE
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: Contact: sip:457007454442622976@192.168.1.101:5060
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: Content-Length: 0
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0:
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0:
05-09 16:07:55.064 3883 3972 D pjsip-pjsua_0: --end msg--
05-09 16:07:55.079 3883 3972 D pjsip-pjsua_0: 16:07:55.076 tlsc0xc1035414 Sending 4 byte(s) keep-alive to open-sips.gvs-icloud.com:5061
05-09 16:07:55.089 3883 3972 D pjsip-pjsua_0: 16:07:55.087 tsx0xc1da7864 Retransmit timer event
05-09 16:07:55.091 3883 3972 D pjsip-pjsua_0: 16:07:55.090 tsx0xc1da7864 .Retransmiting Response msg 180/INVITE/cseq=15161 (tdta0xc1dab064), count=82, restart?=1
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: 16:07:55.092 pjsua_core.c .TX 546 bytes Response msg 180/INVITE/cseq=15161 (tdta0xc1dab064) to UDP 192.168.1.105:5060:
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: SIP/2.0 180 Ringing
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: Via: SIP/2.0/UDP 192.168.1.105:5060;rport=5060;received=192.168.1.105;branch=z9hG4bKPjE9NuBy1TwUJVAtftQ06TRV3IjYIFPE84
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: Call-ID: K1X4ZMmHAI.ra3EjP2kR-uhcsU6vJ-oT
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: From: sip:405579132320223232@192.168.1.105;tag=Qd.we67wAtzidA6h01BCCJdiJV50mwdh
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: To: sip:457007454442622976@192.168.1.101;tag=6b3241a5-5875-4830-9342-f0e73756ab43
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: CSeq: 15161 INVITE
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: Contact: sip:457007454442622976@192.168.1.101:5060
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: Content-Length: 0
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0:
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0:
05-09 16:07:55.093 3883 3972 D pjsip-pjsua_0: --end msg--
05-09 16:07:55.106 3883 3972 D pjsip-pjsua_0: 16:07:55.104 tsx0xc10a0864 Retransmit timer event
05-09 16:07:55.108 3883 3972 D pjsip-pjsua_0: 16:07:55.107 tsx0xc10a0864 .Retransmiting Response msg 180/INVITE/cseq=679 (tdta0xc10b1064), count=77, restart?=1
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: 16:07:55.108 pjsua_core.c .TX 544 bytes Response msg 180/INVITE/cseq=679 (tdta0xc10b1064) to UDP 192.168.1.105:5060:
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: SIP/2.0 180 Ringing
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: Via: SIP/2.0/UDP 192.168.1.105:5060;rport=5060;received=192.168.1.105;branch=z9hG4bKPjWqOObqaXPE-r0BAa3fcjUlNSp2AE3jzh
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: Call-ID: 82SGKjymwlqJY8Sj0a0NUm5RkQ6ibBNj
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: From: sip:405579132320223232@192.168.1.105;tag=bQmB1e.pkib4aWc1lHtKwVQp2Vp7M8XL
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: To: sip:457007454442622976@192.168.1.101;tag=00a628fc-065f-4785-983b-c3a88bb38036
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: CSeq: 679 INVITE
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: Contact: sip:457007454442622976@192.168.1.101:5060
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: Content-Length: 0
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0:
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0:
05-09 16:07:55.110 3883 3972 D pjsip-pjsua_0: --end msg--
Steps to reproduce
I'm running Android 8.1, using IP to IP for LAN communication. This problem seems to occur when multiple CALLs are disconnected from the network after calling/ringing. Not entirely sure how to reproduce. Appeared 2 times. What the log shows seems to be that the expired CALL timer is not destroyed, resulting in repeated attempts to retransmit. This causes "null upcall object in pj::Call::onCallTsxState" and "null upcall object in pj::Call::onCallState". There is currently no more detailed log
PJSIP version
2.12
Context
Android OS 8.1
Log, call stack, etc
The text was updated successfully, but these errors were encountered: