simultanious call feature leads to 780 call attempts (in 120 sec) to users cell phone.

[chrisbeam]

Today i noticed that one of our users had made a call to their own cell phone like 50x within 2 minutes.

as i investigated the situation i found this kind of system records about 50x:

15/11/2022 10:58:48 - [CM503003]: Call(C:69): Call to <sip:[email protected]:0> has failed; Cause: 486 Busy Here/INVITE from 127.0.0.1:5483

this is very odd as it states 127.0.0.1. Our 3CX Pro is running on AWS.

The user only uses the iOS which is on the newest version of 3cx and iOS.

 

[chrisbeam]

I just exported a call log for that extension. it dailed its cell phone nnumber 780x within 2 minutes.

Looking at the call that happened before this endless call cycle started, i see an incoming call to one of our call queues:

15/11/2022 10:55:23

(0176....)

Q 0 (CQ) (802)

Not Answered

As IP is 127.0.0.1 it was the 3CX PBX making ther calls.
What i find so strange is that there is no setting in the call queue nor in the users extension profile that would make 3cx call her.

Or is having the cell phone number in her profile a trigger to force 3cx to call her cell phone because of not taking a call via the app?

Situational Assumption:

I think it is maybe because her profile has the cell phone number.

=> That might trigger 3cx to try to call her but trying this 780x is madness!!!

This eventually blocks all out sip trunk channels

 

[chrisbeam]

I have found the most probable cause:

[x] Ring my mobile simultaneously

Nevertheless, why does 3cx try to call 780x within 120 seconds. ?????

 

[Vali_3CX]

To me it looks like the forwarding rule is misconfigured to call itself with a short (2 secs) no answer timeout.