Endpoint ‘0000f30B0B02’: Could not create dialog to invalid URI ‘0000f30B0B02’

I have registered two endpoints 0000f30A0A01, 0000f30B0B02
and successfully called 200 for “hello world”

But when I tried to call 0000f30B0B02 from 0000f30A0A01, I 've got the following error .

– Executing [101@sets:1] Dial(“PJSIP/0000f30A0A01-00000015”, “PJSIP/0000f30B0B02”) in new stack
[Oct 22 08:17:45] ERROR[2414]: res_pjsip.c:3533 ast_sip_create_dialog_uac: Endpoint ‘0000f30B0B02’: Could not create dialog to invalid URI ‘0000f30B0B02’. Is endpoint registered and reachable?
[Oct 22 08:17:45] ERROR[2414]: chan_pjsip.c:2649 request: Failed to create outgoing session to endpoint ‘0000f30B0B02’
== Contact 0000f30B0B02/sip:0000f30B0B02@192.168.1.80;transport=udp has been deleted
== Endpoint 0000f30B0B02 is now Unreachable
[Oct 22 08:17:45] WARNING[2462][C-00000016]: app_dial.c:2578 dial_exec_full: Unable to create channel of type ‘PJSIP’ (cause 3 - No route to destination)
== Everyone is busy/congested at this time (1:0/0/1)
– Auto fallthrough, channel ‘PJSIP/0000f30A0A01-00000015’ status is ‘CHANUNAVAIL’

The version of asterisk installed is v16.6.2. I did configuration as described in “Asterisk: The Definitive Guide, 5th Edition”

I using PJSIP Realtime.

This is exactly the same problem as “douglas.1053” in his post Endpoint '0000f30B0B02': Could not create dialog to invalid URI '0000f30B0B02'

@jcolp аsked a question that went unanswered, so I opened the same post again.

A similar problem that is described in this post. I can’t find her solution, maybe someone has already come across and solved it?

I noticed that the “contact” field is not filled in the “ps_aors” table.

The table “ps_contact” contains entries.

If the “contact” field in the “ps_aors” table is filled in manually with data from the “ps_contacts” table, calls are made normally.

Is it a realtime bug, or is it a problem with the parameters of the asterisk configuration files that I registered?

The “contact” field on the AOR is for something else or more specifically statically configured contacts, it is perfectly fine for it to be NULL. Others have reported problems with the MySQL client libraries for ODBC, and another individual resolved it: [Solved] PJSIP Contact was deleted while dialing extension

Joshua, I am very happy to receive an answer from you.
Yes, I have seen and tried this solution. But unfortunately this did not solve the problem. Perhaps because I use Centos 8. What if I use the MySQL driver from the asterisk add-ons instead of ODBC? Or is it outdated and not recommended for use?

You are free to use the MySQL driver, it just isn’t core supported - meaning we (Sangoma) don’t fix bugs or solve problems in it, that is done by the community.

Hi @jcolp @i.shvets

I am also facing same issue.
I have registered one endpoint 9802188555.
##########################################################
Endpoint: <Endpoint/CID…> <State…> <Channels.>
I/OAuth: <AuthId/UserName…>
Aor: <Aor…>
Contact: <Aor/ContactUri…> <Hash…> <RTT(ms)…>
Transport: <TransportId…> <BindAddress…>
Identify: <Identify/Endpoint…>
Match: <criteria…>
Channel: <ChannelId…> <State…> <Time…>
Exten: <DialedExten…> CLCID: <ConnectedLineCID…>

Endpoint: 101 Unavailable 0 of inf
InAuth: 101/101
Aor: 101 1
Transport: transport-template udp 0 0 0.0.0.0:5060

Endpoint: 9802188555 Not in use 0 of inf
InAuth: 9802188555/9802188555
Aor: 9802188555 1
Transport: transport-template udp 0 0 0.0.0.0:5060

##############################################################

But when i execute pjsip show endpoints then endpoint becomes unreachable.
got message

== Contact 9802188555/sip:9802188555@10.193.2.159:38844;transport=UDP;rinstance=73fcf0cb992bf3eb has been deleted
== Endpoint 9802188555 is now Unreachable

Also when i initiate call on 9802188555 its becomes unreachable.

But if I reconfigure as statically in pjsip.conf the extensions register and work fine, switching to Realtime causes the issue.

The version of asterisk installed is v16.6.2.
ODBC Version 8.0

Please look into and help me if you have any solution.
Thanks

My Problem is resolved after using mysql add on connector.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.