V20 Import Inbound Routes

[jaywagener]

Hello all, we have noticed an issue with the upgrade from V18 to V20 where we have previously supported SIP trunks, which are no longer supported on V20, are not able to be accessed for changes in V20. When clicking on the trunk and selecting "Edit", it just brings me to the "Teams" page.

The issue we are having is if any changes need to be done, 3CX support has confirmed that the only way to do this is by deleting and re-creating the SIP trunk. On V18, no problem! We would have done an export of the routes, built the new trunk, then do an import of the inbound routes with the new trunk ID in the CSV file. Unfortunately, we have been told that this will require doing all of these inbound routes 1 by 1. Sadly, this is not a viable option for us. We have some systems that have 150-200+ inbound routes. This would require considerable downtime for the client as well as unnecessary man hours to make those changes.

So my question here is, has anyone found a way to import inbound routes in a similar method to V18? Also to 3CX support/developers, are there any plans to include this in future releases? This seems like a huge oversight and is a big enough time waster to have us likely migrate clients away from 3CX instead of moving forward with this tedious method of deleting and re-creating the trunk.

Any help/thoughts are greatly appreciated. Thanks in advance!

 

[Charles_3CX]

In version 20, there are no longer any inbound rules. DIDs are now directly assigned to endpoints, such as departments, from which routes can be easily configured to any destination—whether users, queues, ring groups, IVRs or assigned directly to the endpoints.

You can also import DIDs directly into trunks without needing to delete or recreate them. Once the DIDs are added, they can be assigned to the desired destination.

For detailed instructions on how to do this, you can refer to the documentation here.

 

[jaywagener]

Thanks for the reply Charles.

I guess the issue here is that we have to do this in multiple places, there is not a single screen to make these changes and no way to do a bulk upload, which means that it will require hours and hours of time to make these changes. It's hard to believe that 3CX development missed this in their meetings, or it was just decided that it was not important enough for development at this time. Either way, it is difficult to believe that this is the official method that is being suggested in these situations.

 

[bitn2]

That happens because the template is missing. try to manually upload your trunk template and try again.