Hi Matthew,
If I understand correctly, if you use EITHER sip, EITHER file tracing
(but only one at the time), it works ok. But using both in the same time
doesn't ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 29.03.2024 19:57, Matthew Schumacher wrote:
On 3/29/24 9:08 AM, Matthew Schumacher wrote:
Hello All,
I have this config:
modparam("tracer","trace_id","[siptrace]uri=sip:127.0.0.1:9999")
modparam("tracer","trace_id","[siptrace]uri=file:/var/log/siptrace.log")
route {
trace("siptrace","d","sip");
...
When I look at the messages that show up on UDP:9999 I only see
egress sip messages, but when I look at /var/log/siptrace.log I see
both sides of the conversation. Is this by design? Is there a way
to send all messages to a port, or a socket, or perhaps define a pipe
to another process? I'm trying to setup a second daemon that
monitors all of the sip dialog between opensips and other hosts.
Thanks!
Matt
Correction, I only see ingress SIP messages, not egress when using the
sip: uri in the tracer module. If I use file: or hep: I see both sides.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
