Weird Errors in activity log

[TLCtech]

• 3CX Version, e.g. Standard Annual 16.0.9
• Server OS, Raspberry Pi 4
• 3cx hosted locally
• Provisioning Method: Local
• Trunk Provider: Call Centric
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Ive been getting these weird error messages all day. Does anyone have any idea what these are? I copied these before I ran the firewall checker. That cleared out the logs I can see through the dash. Im wondering if I should revert back a day or two.

05/11/2021 1:04:52 PM - [CM503003]: Call(C:379): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

05/11/2021 1:04:52 PM - [CM503003]: Call(C:379): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

05/11/2021 1:04:52 PM - [CM503003]: Call(C:379): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.59:60718

05/11/2021 12:55:55 PM - x-call-control DROP: call is not found: Ig-W1aHpQNYbxVggTEkqpg..;from-tag=f8774478;to-tag=4ca30a40

05/11/2021 12:55:55 PM - [CM503003]: Call(C:377): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

05/11/2021 12:55:55 PM - [CM503003]: Call(C:377): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

05/11/2021 12:55:16 PM - [CM503003]: Call(C:377): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

05/11/2021 12:55:16 PM - [CM503003]: Call(C:377): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

05/11/2021 12:55:16 PM - [CM503003]: Call(C:377): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.59:60718

05/11/2021 12:47:54 PM - x-call-control DROP: call is not found: mJ1gPBPIp9GA_Xkt8uDoCw..;from-tag=59137001;to-tag=3fb61f0f

05/11/2021 12:47:53 PM - [CM503003]: Call(C:376): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

05/11/2021 12:47:53 PM - [CM503003]: Call(C:376): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

05/11/2021 12:42:25 PM - [CM503003]: Call(C:375): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

05/11/2021 12:42:17 PM - [CM503003]: Call(C:375): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

05/11/2021 12:37:28 PM - x-call-control DROP: call is not found: Sv03Ls_ZreXrfbgcOnU9TA..;from-tag=e8293115;to-tag=bc2aaf74

05/11/2021 12:37:28 PM - [CM503003]: Call(C:374): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

05/11/2021 12:37:28 PM - [CM503003]: Call(C:374): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

05/11/2021 12:36:40 PM - x-call-control DROP: call is not found: ePGsdMiN1kR_tQ_lTXO8pw..;from-tag=0b2bdc6a;to-tag=f0396410

05/11/2021 12:36:39 PM - [CM503003]: Call(C:373): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

 

[jcostlow]

Those look like calls to a ring group that were answered on another extension. Is ext 10 a member of a ring group?

 

[TLCtech]

Yes. That's what sip 10 is. OK, gotcha. I have ring groups, but they aren't active yet. We are toying with using them in another thread. Is that just the system saying that extention got a call? Because I have ALL inbound calls going to another extention right now.

 

[jcostlow]

That looks like a call went to a ring group that is sending calls to ext 10 and 13 that was answered elsewhere. It usually only shows up if someone calls the RG extension. Below is a log of ring group call on one of our PBXs:

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.186:58035

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.189:34015

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.173:37475

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.127:45622

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.187:35409

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.176:42911

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "Copy Room" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.170:46193

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.188:46414

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.115:48937

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.184:56953

05/11/2021 4:58:27 PM - [CM503003]: Call(C:1989): Call to "" <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.177:50290