Hi Ali,
yes, that's a bit of known issue - there is a conflict between the point
where the tracer modules grabs data versus the point where the dialog
module is doing the call-id changes :(
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 3/11/26 17:55, Ali Dogan wrote:
Hello All,
I’m using Topology hiding module with “UCA” parameters and I’m
creating new call-id for outgoing leg(This is I can see from SNGREP).
However, the Tracer module does not reflect this. It logs both the
inbound and outbound legs under the original Call-ID, ignoring the new
one generated by topology_hiding(). My trace call is at the top of the
main route block:
route {
trace("tid");
...
}
This creates a troubleshooting gap: when correlating traces with
downstream systems or with packet captures, the Call-ID in the trace
log does not match the Call-ID that was actually sent to the outbound leg.
1. Is this the expected behaviour of the Tracer module when used
alongside topology_hiding("UCA")?
2. Is there a way to make the Tracer log the outbound leg under its
real (rewritten) Call-ID?
Best Regards,
Ali
Ali Dogan
+44(0)3300 88 18 18 <tel:+44(0)3300%2088%2018%2018>
[email protected]
The mobile network, built to keep you fully in control.
Why choose us <https://www.plan.com/>
Stay connected
Linked In <https://www.linkedin.com/company/plan-com/>
Facebook <https://www.facebook.com/plan.im>
Instagram <https://www.instagram.com/plandotcom/?hl=en-gb>
plan.com is the trading name of Plan Communications Limited,
registered in the Isle of Man with company number 010273V and
Registered Office at No.5 Victoria Street, Douglas, Isle of Man, IM1
2LR. This email and any attachments to it may be confidential and are
intended solely for the use of the individual to whom it is addressed.
Any views or opinions expressed are solely those of the author and do
not necessarily represent those of Plan. If you are not the intended
recipient of this email, you must neither take any action based upon
its contents, nor copy or show it to anyone. Please contact the sender
if you believe you have received this email in error.
_______________________________________________
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
