Solved Activity Log Errors - Migrating from Cisco IPT to 3CX

[ipt_dude]

I've been documenting my organizations migration away from OVERPRICED and OVERLY COMPLEX Cisco to 3XC. We've got over a hundred Yealink phones deployed and I've noticed an increasing number of these messages in the Activity Log.

What might these be?

02/28/2022 1:30:39 PM - [CM503003]: Call(C:66564): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.98:5060

02/28/2022 1:30:26 PM - [CM503003]: Call(C:66580): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.84:5060

02/28/2022 1:30:11 PM - [CM503003]: Call(C:66580): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.84:5060

02/28/2022 1:29:46 PM - [CM503003]: Call(C:66580): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.84:5060

02/28/2022 1:29:21 PM - [CM503003]: Call(C:66580): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.84:5060

02/28/2022 1:28:55 PM - [CM503003]: Call(C:66580): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.84:5060

02/28/2022 1:28:41 PM - [CM503003]: Call(C:66575): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.155:5060

02/28/2022 1:28:34 PM - [CM503003]: Call(C:66523): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 10.10.124.83:5060

TIA,

Amir

 

[ipt_dude]

Ha- I love these forums and 3CX. I just found this and I highly suspect this is the case as we HEAVILY rely upon Call Queues.

I have some 30 departments that I've migrating from Cisco UCCX crap to CFD and within those CFDs, we route calls to call queues. Since we do 3,500 - 5,000 calls per day, we would DEFINITELY have a TON of those calls "cancelled to other agents" in the queue.

https://www.3cx.com/community/threads/487-request-cancelled-dropped-calls.67612/

A "487 request terminated" can be what a UAS will send to the client after the client sends a CANCEL request for the original unanswered INVITE request.

Translated this could easily be when a call has taken place but the destination user has "Cancelled" the call before a session has been established, often seen when you have a call queue/group (an agent picks up and the call is cancelled to the other users of the group).

I cannot say without more information as to your particular issue, but can say in regards to the 487 code that it can often be a red herring.

 

[NickD_3CX]

Hi!

Glad you are enjoying our product and to hear that your migration is going well.

It is exactly as you said, the 487 is the response endpoints give to a CANCEL request.

3CX sends CANCEL requests during Queue polling when moving from one agent to the other, so it is absolutely normal to see these messages.

 

[ipt_dude]

Thanks Nick. Soon upgrading to v18 and within a month or so - we will delete *.* Cisco!