SOLVED Incredible PBX 13.13.7 - Asterisk 13.22 inbound Vitelity Routing

[mark847]

MY question: I just installed the latest IncrediblePBX for the RaspberryPi, with all of the updates. I have not made any manual changes to GVsip1. Google Voice is working, and a couple of extensions as well. I can't get the Vitelity inbound route to work. Vitelity Outbound works, the DID is correct, I called Vitelity on that. I have left CID to "Any". I even created a route from Any DID and Any CID, and still no answer. At one point it was working, but then GVsip1 was not, now GVsip1 is working and now Vitelity inbound is not. The extensions are working.

I don't have a fixed external IP, and my internal IP is 192.168.1.206. Do I need to add this to /ect/hosts ?
I also don't have a FQDN.

My DID is correct.
But Vitelity sends me an email that "chanunavail" error. In the log I see:
So Vitelity is getting thru. From the debug information:
Both Vitelity inbound and outbound are registered, but unmonitored.

Splitting 'inbound18.vitelity.net' into...
...host 'inbound18.vitelity.net' and port '' ".
...but it keeps trying retransmission.

[2018-10-25 01:45:29] DEBUG[1926]: chan_sip.c:4535 __sip_ack: Stopping retransmission on '[email protected]' of Request 105: Match Found
[2018-10-25 01:45:29] DEBUG[1926]: chan_sip.c:24548 handle_response_register: Registration successful
[2018-10-25 01:45:29] DEBUG[1926]: chan_sip.c:24550 handle_response_register: Cancelling timeout 9
[2018-10-25 01:45:29] DEBUG[1926]: chan_sip.c:6587 sip_pvt_dtor: Destroying SIP dialog [email protected]
[2018-10-25 01:45:44] DEBUG[1899]: res_pjsip_registrar.c:1186 check_expiration_thread: Woke up at 1540449944 Interval: 30
[2018-10-25 01:45:44] DEBUG[1899]: res_pjsip_registrar.c:1193 check_expiration_thread: Expiring 0 contacts
[2018-10-25 01:45:44] DEBUG[2970]: threadpool.c:1137 worker_idle: Worker thread idle timeout reached. Dying.

What am I missing?
Where else should I look?
Do you need the entire output of asterisk -rddddddd for this transaction?

Thanks for your help.

 

[mark847]

Where can I find help for this issue? Thanks in advance for a response.

 

[wardmundy]

Please post a sanitized version of your inbound trunk setup.

 

[mark847]

The Vitelity Inbound quick busy was partially resolved. Vitelity was not sending the inbound information to Asterisk. Somewhere along the way the SIP routing on the Vitelity side was lost. For those who might have the same problem, here is the solution from Vitelity Support. Make sure you have an endpoint in the Subaccount:

To update the routing method for your numbers, please follow the

1. Log into the user portal (portal.vitelity.net)
2. Go to the “My products and services” menu on the left side of the
   screen
3. Click on “My Numbers”
4. Choose “All”
5. Locate the DID you would like to change the routing for , click on
   the “Action Menu”
6. Choose "Routing method "
7. Keep protocol as “SIP via UDP”
8. Choose device type (server, ata device etc)
9. Put a check mark next to the sub accounts/ IP endpoints you
   would like the DID to be routing to
10. Confirm settings, and press “Submit”

It is now partially working. It works and connects to my extension the first time, but the next time it rings once, and then says that the extension is busy. I need to search the threads to see if this issue has already been covered.

 

[mark847]

If you mean the Sip Settings, here is the Vitelity Inbound Configuration:
username=xxxxxxxxx
type=friend
t38pt_udptl=no
t38pt_tcp=no
t38pt_rtp=no
secret=zzzzzzzzz
insecure=port,invite
nat=yes
host=inbound18.vitelity.net
disallow=all
context=from-trunk
canreinvite=no
allow=ulaw

It appears that the Vitelity inbound is timing out. From the log file: