Telnyx - No route found

[rt050]

Outbound route pictured here:

Thanks

[PitzKey]

@rt050

https://pastebin.com/E0t2verP

You have your Trunk misconfigured. Did you follow the instructions that Jose posted?

[rt050]

I did indeed. I’ve matched their settings and having the same results…

[miguel]

Make sure your trunk is totally connected before trying to make a call. Once is connected, make sure that you have configured a valid Caller ID on the Trunk, Outbound Routes, or the Extension itself.

[Bryan]

My VitalPBX just broke in this same way after the most recent update was applied. IP Authentication on Outbound calls through Flowroute. inbound are just find.

rt050’s log entry was:

[2022-02-09 11:59:18] ERROR[11107] res_pjsip.c: Endpoint ‘rtr20348’: Could not create dialog to invalid URI ‘rtr20348’. Is endpoint registered and reachable? [2022-02-09 11:59:18] ERROR[11107] chan_pjsip.c: Failed to create outgoing session to endpoint ‘rtr20348’

mine is:

“PJSIP/56xxxxxx1720462xxxx@56xxxxxx,90,kKtrU(sub-call-recording^833099fa1fe9a379^52^56xxxxxx1720462xxxx^no)”) in new stack
[2022-02-17 05:06:43] ERROR[15394] res_pjsip.c: Endpoint ‘56xxxxxx’: Could not create dialog to invalid URI ‘56xxxxxx’. Is endpoint registered and reachable?
[2022-02-17 05:06:43] ERROR[15394] chan_pjsip.c: Failed to create outgoing session to endpoint ‘56xxxxxx’
[2022-02-17 05:06:43] WARNING[15469][C-00000003] app_dial.c: Unable to create channel of type ‘PJSIP’ (cause 3 - No route to destination)

This only started a few days ago… likely when I updated to 3.1.4.

[PitzKey]

Can [both of] you please post the output of:

cat /etc/asterisk/vitalpbx/pjsip__50-1-trunks.conf

[miguel]

I just tried connecting a VitalPBX using the latest version with “FlowRoute” and everything seems to work flawlessly.

The trunk

Asterisk

Flowroute

Telnyx With VitalPBX 3.1.4 R4

Troubleshooting

Now, if you believe that you have issues with your systems, you can execute the commands below for troubleshooting.

1. Force to install the database migrations

vitalpbx --build-db

If the above command shows errors mean that there are unapplied migrations, so you can post the error here to get the right instructions.

2- Enter the Asterisk CLI and execute the command below.

module reload res_pjsip.so

The above command will show you a detailed debug, including errors. If there’s an error in the output, then post it here to get the right instructions on how to solve the issue.

Conclusion

Finally, if you have a VitalPBX license or subscription, you can open a case in our HelpDesk system for personalized attention.