If the former:
Does anything appear in the Asterisk log on an attempted call? If so, post details.
If nothing in the Asterisk log, do the incoming INVITEs appear in sngrep? If so, you have a FreePBX firewall issue. If not, confirm that at VoIP.ms, the DID is routed to the correct sub-account and post details about your hardware router/firewall.
If the latter:
Confirm that you can call ext. 400 from another extension. Temporarily set the DID Number field of the Inbound Route to (blank) (will show as ANY) and report whether the call reaches the extension.
Thx for pointers … Not sure I can address this right away - but it looks like the truth out there … Fathers day celebration has started… will look at this later…
You have a DID for inbound and you use the outbound link with that DID as a Caller ID. It really never helps to think of the inbound and outbound legs of a SIP call process as “a line”.
Your inbound calling hits your PBX because your ITSP sent it to your box. The fact that is has your DID as the “destination” is a cool feature. Outbound calling can (depending on your settings and your ITSP) have literally any Caller ID in the world.
Confirm thatin VOIP.MS DID Settings:
DID>Routing Settings>Main
Is set to “SIP/IAX” pointed at your Trunk "SIP/[Acc#]_TrunkName
Also, make sure that the DID is on the same POP as the Trunk. If not the inbound call will fail
Check on the FreePBX Trunk under “sip Settings” the Register String should have the same POP as the DID Setting in the VOIP.MS Portal
Just got back home … thx for replies…and suggestions …
I reached out to Voip.ms, and they said to have calls routed to the main account, not the sub account. The sub account was not registered …
I did that in the admin portal of voip.ms, and inbound calling works.
Is a sub-account required all ? Somewhere I think I saw a post and a video saying you needed a sub account … but this seems to work fine with just the main account.