I changed the level for the “noisy” rtp log messages, and I have attached the full log from yesterday collected with debug level 3.
There were 2 incidents where one of the customer’s siptrunks were deemed as unreachable:
When the AOR is deemed unreacheble I see pjsip_transport_events.c reporting MONITOR_DESTROYED for the TLS transport object.
I hope that you can figure put where it goes wrong.
I have also added our transport and siptrunk configuration, in case you need this
Please file an issue[1] and attach all of the logs and configuration. I believe the issue is that the remote side keeps dropping the connection and we are reacting to that, in this case we shouldn’t.
Which logs and what configuration do you need that I didn’t include in my last post for this issue?
And do you need me to create a seperate issue, or is this one good enough?
If you want the entire log, then it exceeds your maximum allowed size. It is 35MB, and I were not permitted to upload a zip file.
You can naturally get the complete configuration for everything, but then I would prefer to email you this if possible.
The forum is not an issue tracker. It’s a forum. We track issues on Github. It is preferred that you attach things there, and not email directly. Emailing directly means you limit anyone fixing it to whomever has been emailed the logs and configuration, and thus not community members.