Telnyx New Trunk Missing from Template List

[Clark-Ritchotte]

I had to re-build a clients Hosted instance as they didn't pay for it in time, and now when we go to build out the trunks we can't find Telnyx as a trunk template under US or worldwide, where did they move it to?

 

[SweetAction]

I had to re-build a clients Hosted instance as they didn't pay for it in time, and now when we go to build out the trunks we can't find Telnyx as a trunk template under US or worldwide, where did they move it to?

https://www.3cx.com/community/threads/telnyx-removed-from-hosted.113752/

 

[Clark-Ritchotte]

The interesting thing is Nick said the template would stay under 3rd parties in that post, but other ones said they changed their mind. It's such a Pain on a partner's end to have to regularly migrate our clients between Carriers cause support for them keeps changing, How do we know if we move them all to the flow route that it's not going to be in the same boat a year from now? Also, it costs us time and money to have to pay our staff to do the migrations and also build training for customers to use these if they own them after the initial configuration.

 

[SweetAction]

The interesting thing is Nick said the template would stay under 3rd parties in that post, but other ones said they changed their mind. It's such a Pain on a partner's end to have to regularly migrate our clients between Carriers cause support for them keeps changing, How do we know if we move them all to the flow route that it's not going to be in the same boat a year from now? Also, it costs us time and money to have to pay our staff to do the migrations and also build training for customers to use these if they own them after the initial configuration.

You can still use Telnyx, you just have to import the template yourself or manually set settings as a generic SIP trunk.

 

[[email protected]]

I had to re-build a clients Hosted instance as they didn't pay for it in time, and now when we go to build out the trunks we can't find Telnyx as a trunk template under US or worldwide, where did they move it to?

I know this is a late response, but I was able to import, configure and register the import template from their configuration guildeline. You will find the drive link for the template under section 2.2. I was able to get all it all working, including SMS and SIP over TLS-- which has been touchy for me on a fresh Hosted by 3CX.

https://support.telnyx.com/en/articles/6161111-3cx-configuring-a-3cx-v18-pbx

Fair warning, it took some smooching to get it to register, and the configuration is unsupported longterm.

While I agree that flipping SIP providers to the flavor of the week isn't sustainable, take a look at VoxTelesys. They really have superb support and in my experience are one of the most forum-engaged vendors.

 

[Clark-Ritchotte]

yeah, I ended up Exporting another customer's Template and use it now.

 

[Clark-Ritchotte]

The interesting thing is Nick said the template would stay under 3rd parties in that post, but other ones said they changed their mind. It's such a Pain on a partner's end to have to regularly migrate our clients between Carriers cause support for them keeps changing, How do we know if we move them all to the flow route that it's not going to be in the same boat a year from now? Also, it costs us time and money to have to pay our staff to do the migrations and also build training for customers to use these if they own them after the initial configuration.

I would like to clarify that the contents of this post are unrelated to the management at 3CX or Flowroute. I want to emphasize that both platforms are excellent in their own right. As a partner, it was our responsibility to ensure that we diversified our carriers. Initially, when we were a small company, we aligned ourselves with a single carrier that offered the most competitive pricing, considering our target market of small businesses. However, we now recognize that consolidating all of our customers with one carrier was a mistake. In light of this, we have decided to partner with Flowroute and Skyetel, as they share the same parent company. Although the migration process for all of our customers has proven challenging, we acknowledge that it is ultimately our responsibility for not diversifying, and it should not be attributed to any shortcomings in 3CX management.