Solved Incoming calls not ringing to correct extension and DID

[AlanGrnja]

Configured extension 001 with specific DID... when I call the DID it just rings and rings. Does not show on my web client ext. 101.

 

[leejor]

Check the 3CX Activity Log right after a failed call. That should show the DID number being sent. It may be, that the number in the rules. is not an exact match with that number.

 

[Saqqara]

check the activity log for the correct format of the DID number being passed to 3CX

You may have to enter *12345 as the DID number (for example, * is a wildcard)

Have you setup inbound rules for the DDI, as entering the DDI under the extension is for outgoing calls.

https://www.3cx.com/docs/manual/inbound-did-call-routing/

 

[AlanGrnja]

OverrideExt.001 has inactive profile override ?

 

[AlanGrnja]

Nothing in activity log about incoming calls....it just rings for about a minute then disconnects

 

[leejor]

If there is no Activity Log regarding the call, then it is not being sent to you. That being the case, I would contact your provider, and have them trace the destination of the call.

 

[AlanGrnja]

vendor stated "I am seeing a Proxy Authentication Required that is failing the call.

 

[craigreilly]

Is the DID listed in the incoming rule list as Saqqara mentioned?

 

[AlanGrnja]

yes routed to the extension 001

 

[craigreilly]

Did you use a * in front of the number?

 

[AlanGrnja]

Spoke to provider.. under sip trunk Type of authentication i changed it to register/Account based was on ip based(document i had showed this) . Now incoming calls come through.
Thank you everyone for the help!

 

[craigreilly]

I didn’t mention that because you had sorted out the truck registration on your outbound forum post ...

 

[AlanGrnja]

That's the strange part because i was able to make outgoing calls so it threw me off.

 

[YiannisH_3CX]

Glad to see that issue has been resolved and thank you for sharing your solution in the thread.