Solved Nexmo Incoming Calls not working

Status
Not open for further replies.

kiomon

Joined
Feb 11, 2018
Messages
4
Reaction score
0
I am just setting up our 3CX PBX. We have it hosted on our AWS account and we used the PBX Express service to set it up. We have signed up for Nexmo, and linked our Trunk (following the guide in the blog), and everything works great for outbound calls after we made the outbound rule. We then made an inbound rule for the DID, but when we call the number nothing happens. Do we need to configure anything special again at Nexmo for each of the numbers?

Also it seems like the DNS is taking a while to propogate? On some of our devices, we can resolve https://ourdomain.3cx.us some other ISPs cant resolve our domain yet. Could this be the reason we aren't receiving the calls?
 
Hello @kiomon

Make sure that the DIDs are listed the Your numbers section in Nexmos portal. If they are the numbers should be correctly routed to your PBX. DNS propagation should not be related to the issue you are facing as the PBX registers to the provider with its public IP.

Are the calls hitting the PBX when the DID is called? Do you hear an error message / Busy tone when calling?
 
Hi! @YiannisH_3CX

Thanks for the reply. Yes the DID are listed, and no they do NOT hit the PBX. I was able to get it working, but i want to be sure i did it correctly. I selected each number in Nexmo, and selected "Forward to SIP" (the option of where to send the calls was initially blank), and the in the SIP URL i put [email protected] and i did this for all the DID numbers and they all now hit the right extenstion and the system works. Is this an ok workaround? Am i doing anything wrong?
 
Someone needs to contact Peter about improving this page:
We have provided examples for a number of different SIP capable systems
If the yearly interop fee is only $2500 that seems too small to not pay for as large of a company as they are
 
Glad to see the issue has been resolved. You are correct regarding the extra step and it will be added to our documentation to avoid future confusion. Thank you for pointing it out.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,883
Messages
589,537
Members
164,741
Latest member
Carsonix