Re: [OpenSIPS-Users] BYE from UAC bypasses OpenSIPS
Discovered that script_helper.so is incompatible with topology_hiding. (Simply because there is no place to use topology_hiding_match function in case of script_helper.so usage — because when using script_helper.so, we don’t add to the script the section with if(has_totag()) ). So, I fixed my error in script, now in-dialog requests work well. :^) --- BR, Alexey https://alexeyka.zantsev.com/ ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BYE from UAC bypasses OpenSIPS
The reason was that i executed route[relay] in the wrong place of the script. Like this: … … route(relay); # I added this, and it was a mistake (too early) … record_route; # default, but calls haven’t reached this line ... route(relay); --- BR, Alexey http://alexeyka.zantsev.com/ ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BYE from UAC bypasses OpenSIPS
Time to try the script_helper module has come :D Now works as expected https://ibb.co/6D3R0fJ Thanks everybody for advice! --- BR, Alexey http://alexeyka.zantsev.com/ ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BYE from UAC bypasses OpenSIPS
+1 for topology hiding, it saves a lot of debug time with strange device Alain --- John I highly recommend using the topology hiding module instead of inserting routes and forwarding the SIP message. Several IP devices have problems when you have a lot of routes. Even the SIP message size can be a problem if your call flows through several proxies. When you use topology hiding, your origin/destination will never know what's on the other side, so current problem can never occur anymore. Regards On Wed, Sep 1, 2021 at 10:12 AM John Burke via Users wrote: 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@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BYE from UAC bypasses OpenSIPS
John I highly recommend using the topology hiding module instead of inserting routes and forwarding the SIP message. Several IP devices have problems when you have a lot of routes. Even the SIP message size can be a problem if your call flows through several proxies. When you use topology hiding, your origin/destination will never know what's on the other side, so current problem can never occur anymore. Regards On Wed, Sep 1, 2021 at 10:12 AM John Burke via Users < users@lists.opensips.org> wrote: > 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 > listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] BYE from UAC bypasses OpenSIPS
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@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] BYE from UAC bypasses OpenSIPS
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@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
