SOLVED IncrediblePBX 2021 Not Receiving Calls From Vitelity

[aroundi]

Hello,

Inbound calls on my premise hardware with a newly configured Ubuntu IPBX 2021 system can not receive calls from Vitelity. I am able to place outbound calls through Vitelity without a problem. I upgraded from CentOS IPBX 2020 which was working.

I tested 2021 in a VBox VM which installed nicely on my laptop and tested outbound calls through Anveo Direct. So I built a 2021 system on hardware at home which also installed nicely. I did cut and paste from the working 2020 install for both. I brought the 2021 VM on site and swapped out the 2020 system as a test before upgrading the hardware. The 2021 VM worked nicely with inbound and outbound working. I also made a Clonezilla image of the 2021 hardware install, that I tested restoring on my hardware at home, which I then installed over the 2020 system. The install could not receive calls. After troubleshooting for possible configuration mistakes and finding nothing to fix I swapped back to the VM which was working just before (and during) the Clonezilla image restore. The VM 2021 also could no longer receive inbound calls now. At this point I'm concerned.

I then pointed the Vitelity DID to the 2021 hardware at home and it can't receive calls. I installed a fresh IPBX 2021 and just configured the Vtitelity trunk and routes and it can't receive calls. So, I'm at the end of my rope now with a down system on site and not sure what to try next.

I opened an urgent ticket with Vitelity when the previously working VM failed. They got back to me and said they were not getting any responses to their sip invites. He felt it was a network issue. The only thing I can think of doing now is downgrading back to IPBX 2020, but my gut tells me that is likely not my problem.

Has anyone seen this problem with IPBX 2021? Or with Vitelity or any other providers? Any insight would be highly appreciated.

Thanks.

 

[dhoppy]

I have 3 IPBX 2021 systems working with Vitelity. All using IP-based authentication and PJSIP trunks. Kind of early on the west coast for my systems to be receiving calls, but they were working yesterday.

 

[wardmundy]

Use /root/add-fqdn to add the FQDN of your Vitelity server.

 

[kenn10]

Best advice with Vitelity is to use registration to keep the pathway open. Tell your trunk to register to your Vitelity account. If you are switching back and forth between a couple of systems, Vitelity can be slow to move the inbound calls to the most recently registered system.

 

[aroundi]

Thanks for getting back to me guys. The registration string and some waiting time did the trick.

 

[kenn10]

Here's what a PJSIP Vitelity trunk looks like:

 

[aroundi]

@kenn10 , I think I'm going to have to start taking pjsip seriously.

It's interesting that the tech I spoke with turned registration off (on the portal side).

In any event, I'm glad that equipment, configuration, image restoration were all sound and a little bit of education was the solution.

Thanks to all for the support