[OpenSIPS-Users] BYE from UAC bypasses OpenSIPS

[John Burke]

Hey Alexey,

 From your screenshots, it's not only the BYE but also the ACK that 
bypasses your proxy (both of which being sequential requests).  To get 
your proxy in the path of sequential reqs, you need to either (1) call 
record_route, or (2) use topology hiding module.  The UAC otherwise 
doesn't know about your proxy, as the 200 won't contain any Record-Route 
headers to build the route set for sequential reqs nor will the 200 
contain a URI referencing your proxy in the Contact header.

Thanks,
John Burke

On 9/1/21 6:48 AM, Alexey Kazantsev via Users wrote:
> Hi list,
> feeling shamefully but still can not fix the problem, trying different 
> configurations.
> I’m setting drouting (INVITEs are routed well).
> But BYEs from UAC go directly to dr_gateway, not through OpenSIPS.
> I understand that this all is about in-dialog request, having to_tag, 
> loose_route.
> I compared my config with config files of previously 
> configured servers (not for drouting)
> which work well (I tested BYE routing).
> But still can not fix this issue.
> Here’re 2 screenshots of the same call, captured on UAC:
> [1] demonstrating INVITE from UAC,
> [2] demonstrating BYE from UAC (which goes directly, bypassing 
> OpenSIPS, and I need to fix this behaviour).
> [1] https://ibb.co/NNNvHhM
> [2] https://ibb.co/bKd4c0r
> What should I pay attention to, to route BYE requests from UAC via 
> OpenSIPS?
> -----------------------------------------------
> BR, Alexey
> http://alexeyka.zantsev.com/
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210901/b39aa9cd/attachment.html>