Inbound calls not working on Startup Free hosted edition

Status
Not open for further replies.

telforce

Customer
Basic Certified
Joined
Feb 7, 2019
Messages
40
Reaction score
2
Through our partner portal i have created a 3CX Startup instance and started testing. According to our accountmanager this should work out of the box once a DID and trunk is connected. Test results:

-outbound calling works
-inbound calls end up in a 3CX voicemailbox

I checked the routing options in the new minimal webclient admin area and tried them all out:

-routing the DID to an extension
-routing the DID to a ringroup
-routing the DID to a queue

All these routes give the same result: When you dial the DID you hear a 3CX voicemail message.

According to our 3CX accountmanager we should contact our SIP trunk provider (only 2 possible parties here in The Netherlands right now with 3CX Startup), so i contacted them. They also created a Startup instance and ran into the same problem, it's not working. They can't create a ticket with 3CX because the ticketsystem rejects the FQDN. So our accountmanager said i should post here.

We were thinking of selling 3CX Startup but it looks like it's not ready to be sold yet?
 
Hi @telforce

If you navigate to the "Voice & Chat" tab do you see your trunks as registered (Green box)?
Also in the users are the users you are directing the calls to registered? Can you call another extension from the list of users?
Does that work?

Which provider are you using?
 
3cxstartupinboundbroken.png

Here you can see. The provider is one of the two possible SIP trunk providers in The Netherlands.

I already did the test with users calling each other, they can call eachother just fine, and they can also dial external numbers over the sip trunk.
 
@telforce we are running some checks for this please bear with us.
 
I might have an idea what is happening here. It looks to me like the 3CX Startup edition is a multi-tenant server. In my experience when you use two or more trunks from Destiny in the same server you have to disable SIP trunk>Inbound parameters>Call Source Identification. But of course that option is not available for me.
 
I'm wasn't sure if I should make a separate thread or not, but this seems fairly similar to the issue I am experiencing. I'm using Skyetel for my trunk. I'm able to make outbound calls no problem. Inbound calls won't come through, though.
 
@seabre as I can see you have entered your number as "1xxxxxxx "
Now your Provider sends the call with " +1xxxxxxx "
Go to your Web Client and adjust your number and set it up wih a " + " as per the following guide :

https://www.3cx.com/docs/us-sip-trunk-skyetel/

5. Set the SIP format to “+1NPANXXXXXX”
 
  • Like
Reactions: seabre
@NikosT_3CX you are right. I had the SIP format right on the skyetel side, but forgot the `+`. Thanks!
 
  • Like
Reactions: NikosT_3CX
Hi @telforce

The problem with inbound calls is now resolved. Please try again and let us know.
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK