Inbound calls routing directly to voicemail

[tommyh]

I had set up 3cx on a raspberry pi 4. I am able to make outbound calls. However I am not able to receive inbound calls.

I had added the SIP Trunk with 1 DID which goes to extension 100. Outside office hours also routes to extension 100.
I had to use port 6060 for SIP base on documentation from SIP provider. I had setup 3cx to use port 6060.
I had opened the following ports: 6060 (both), 5061 (both), 9000-10999 (udp), 5090 (both) and 5001 (tcp).
I ran the firewall check which has passed.
I had created an Inbound Rule taking DID to extension 100. Outside office hours also routes to extension 100.
I am able to place calls to and from the 3cx android and the web client phone.
I can place outbound call calls 3cx android (and web client phone).
However all inbound calls route directly to 3cx voicemail. I know this because I recorded a personal vm greeting in 3cx.
Call Log only shows outbound calls.
Activity Log (with verbose) only shows outbound calls.

I googled and read several forum threads regarding others with similar issue. Unfortunately I didn't find anything to help resolve my issue.
I am new to this so please let me know if I missed a step.
Your assistance is greatly appreciated. Please and thank you.

 

[leejor]

If callers are reaching 3CX voicemail, then the incoming call should be in the Activity Log. It should show all calls. Have you tried not using a DID rule and simply routing all calls, on that trunk, to one extension? I'm assuming that the extension shows as registered, and DND (Do not Disturb), or another feature, is not active. Are you able to sucessfully call the extension internally?

 

[tommyh]

Thanks for the response Lee.
I tried both with and without an inbound rule.
Yes the 3cx android and 3cx web client shows green (Available).
I can call the extension internally between the 3cx android and also the 3cx web client.

My Firewall Check is below.

• resolving 'stun-us.3cx.com'... done
• resolving 'stun2.3cx.com'... done
• resolving 'stun3.3cx.com'... done
• resolving 'sip-alg-detector.3cx.com'... done
• testing 3CX SIP Server... done
  • stopping service... done
  • detecting SIP ALG... not detected
  • testing port 6060... done
  • starting service... done
• testing 3CX Tunneling Proxy... done
  • stopping service... done
  • testing port 5090... done
  • starting service... done
• testing 3CX Media Server... done
  • stopping service... done
  • testing ports [9000..9398]... done
    • testing port 9000... done
    • testing port 9002... done
    • ..
      testing port 10996... done
    • testing port 10998... done
    • starting service... done

 

[cobaltit]

Did you ever try to setup 3CX before? Almost sounds like it's hitting another instance.

 

[YiannisH_3CX]

Hi @tommyh

To ensure that your calls are hitting your PBX make an inbound call, let the voicemail answer it and while the call is active check your dashboard for active calls. You can see active calls under the "PBX Status" column in the "Number of calls in use" menu. Opening the menu will show the active call and where the call is routed to.

The next step is to open your trunk settings and checking where the main trunk number is routing. More information on inbound rules and how to set those up can be found here: https://www.3cx.com/3cxacademy/videos/basic/configuring-voip-providers/