Call to <sip:[email protected]:0> has failed

[Pav Grewal]

We are seeing the following message in our logs. What could be causing this issue?
12/15/2021 1:08:41 PM - [CM503003]: Call(C:55): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063
12/15/2021 1:08:41 PM - [CM503003]: Call(C:55): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063
12/15/2021 1:08:41 PM - [CM503003]: Call(C:55): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063
12/15/2021 1:08:41 PM - [CM503003]: Call(C:55): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5063
12/15/2021 1:08:41 PM - [CM503003]: Call(C:55): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483
12/15/2021 1:08:41 PM - [CM503003]: Call(C:55): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483
12/15/2021 1:06:54 PM - [CM503003]: Call(C:54): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483
12/15/2021 1:06:54 PM - [CM503003]: Call(C:54): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

 

[VasilisV_3CX]

Hi @Pav Grewal,

Can you provide more information? https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Also how are these extensions provisioned (local, STUN, behind a SBC etc)?

 

[Pav Grewal]

Here you go

• 3CX Version, 18.0 Update 2 (Build 307)
• Server OS, Hosted By 3CX
• Is the 3CX Server Hosted and where? Hosted by 3CX]
• IP Phone Make/Model/Firmware version, No IP Phone all using Web Client/Desktop App
• Provisioning Method: Not sure Hosted by 3CX with Web Client/Desktop App
• Trunk Provider or VoIP Gateway Make/Model, Skyetel, DIDlogic and Telnyx
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Also how are these extensions provisioned (local, STUN, behind a SBC etc)? Not sure its all hosted by 3CX and my users are using Web Client/Desktop App.

 

[VasilisV_3CX]

Hi @Pav Grewal,

Are these extensions apart of a ring group by chance?

Apart from these errors, do you have any other issues?

 

[Pav Grewal]

Hi @Pav Grewal,

Are these extensions apart of a ring group by chance?

Apart from these errors, do you have any other issues?

Yes these extensions are part of a ring group.

No I don't see any other errors.

 

[VasilisV_3CX]

Hi @Pav Grewal,

What you are seeing is the teardown of the Ring All call of the Ring Group when 1 extension answers it. You can reproduce this by calling the RG and answering as a different extension, you should see all extensions except the extension that answered producing a "Cause: 487 Request Terminated/INVITE from 127.0.0.1..." error.

No need to worry.