Solved Inbound calls not working

[anon42]

I use a generic sip trunk and the outbound calls are working fine. Inbound calls are forwarded directly to the voicemail.

This is what the log shows.

04/03/2021 2:17:17 PM - [CM503003]: Call(C:54): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/03/2021 2:15:09 PM - x-call-control DROP: call is not found: W39jOpiZyf2moovK2jqDxA..;from-tag=7ab11a5c;to-tag=f23eae2c

Any ideas how to solve that? Any help is appreciated a lot!

 

[leejor]

Not really a lot of information to go on.

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

What type of extensions (devices) are being used, can you call internally?

 

[anon42]

• 3CX Version, Standard Annual 16.0.8.9
• Server OS, Google Compute Engine
• Is the 3CX Server Hosted and where? Google Compute Engine
• IP Phone Make/Model/Firmware 3CX App
• Provisioning Method: STUN
• Trunk Provider or Gateway Make/Model Netvoip
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Sorry, here are the information. Internal calls are working fine. I only use the web client and the 3CX app.

 

[YiannisH_3CX]

Have you created inbound rules for your DIDs or are you using the main trunk number destination? Have you verified that calls are indeed reaching your system and are redirected to your voicemail?

 

[anon42]

I've one DID where the main trunk number is directed to my extension. It rings for about 1 second and the goes to voice mail. I can see the missed calls in my system log, so i assume they are reaching my system.

 

[YiannisH_3CX]

In that case go to your dashboard / Activity Log / Settings and turn the logging level to verbose. Then make another call and check the logs for details.
You can filter by call so choose the last call you made and you will only see logs for that call. Please note that the log is read from the bottom to top.
You should be able to see why the call drops

 

[anon42]

That helped me understand the issue. The extension seemed to be busy. I still can't explained, why it happened, but after re-provisioning my phone and restarting all services, it works.

Thanks for the support!

 

[YiannisH_3CX]

Glad to see the issue has been resolved. Perhaps there was a stuck call somewhere that was released with the restart of the services. Remember to switch verbose logging off to save on resources.