Delayed calls without human action

mbedial

Member
Hi,
we are receiving some complaints from our clients that assure that their apps are making calls without any action.

We are using the webcallserver as gateway from the webrtc app in android to SIP. We initially thought that the problem was in the mobile app, but we finally reproduced it, and we could check that is the server who initiates the call.

It seems that in some cases the server queues the call and sends it later . We don't have any log, just this:

the console but continue.
flashphoner.log.2021-01-25-19:19:16:40,102 ERROR EventScanner - EventScannerThread-27 We cannot let this thread die under any circumstances. Protect ourselves by logging errors to the console but continue.
flashphoner.log.2021-01-25-19:19:16:44,101 ERROR EventScanner - EventScannerThread-27 We cannot let this thread die under any circumstances. Protect ourselves by logging errors to the console but continue.
flashphoner.log.2021-01-25-19:19:16:46,569 ERROR EventScanner - EventScannerThread-27 We cannot let this thread die under any circumstances. Protect ourselves by logging errors to the console but continue.
flashphoner.log.2021-01-25-19:19:16:47,069 ERROR EventScanner - EventScannerThread-27 We cannot let this thread die under any circumstances. Protect ourselves by logging errors to the console but continue.
flashphoner.log.2021-01-25-19:19:16:47,455 WARN SipCallProcessor - API-ASYNC-pool-12-thread-3 terminate: call already terminated sipCall.id=b20aa466-56dd-4cfe-9c83-c34669eb4401
flashphoner.log.2021-01-25-19:19:16:47,813 WARN Softphone - API-ASYNC-pool-12-thread-3 can't hangup, call with callId b20aa466-56dd-4cfe-9c83-c34669eb4401 doesn't exist
flashphoner.log.2021-01-25-19:19:16:48,069 ERROR EventScanner - EventScannerThread-27 We cannot let this thread die under any circumstances. Protect ourselves by logging errors
 

mbedial

Member
Hi Max,
it's being difficult to reproduce the issue.
We can add to the previous post this additional log that we have found just at the same time as the calls were launched:
Disconnected by server shutdown;/85.250.x.x:53482/90.169.x.x:9443-ff402e81-f4aa-4088-b54f-8d89d352c2cc

We'll keep trying to reproduce it to capture all the requested info.

M
 

Max

Administrator
Staff member
Disconnected by server shutdown;/85.250.x.x:53482/90.169.x.x:9443-ff402e81-f4aa-4088-b54f-8d89d352c2cc
This is probably from cdr.log file. This means the WCS server was stopped or restarted manually while client session was established.
 
Top