Hi Xaled,
The record routing is incompatible with the b2b, by SIP definition. The
record routing is done only by a SIP proxy, not by a SIP b2b2.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 2021 online
https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 4/11/21 9:32 PM, xa...@web.de wrote:
Hi,
would it be possible to respect loose routing on the caller side of B2B module
and set route header on the callee side accordingly
Something like this:
Incoming INVITE:
INVITE sip:+12345678@1.2.3.4;user=phone SIP/2.0
Via: SIP/2.0/TCP
4.3.2.1:5060;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route: <sip:orig-t...@test.com:5060;transport=tcp;lr>,
<sip:605e7788/5.1.0.17@4.3.2.1:5060;transport=tcp;lr>
Wanted outgoing INVITE:
INVITE sip:+87654321@1.1.1.1;user=phone SIP/2.0
Via: SIP/2.0/TCP
test.com;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route: <sip:605e7788/5.1.0.17@4.3.2.1:5060;transport=tcp;lr>
I tried setting loose_route in both the original route and in the resulting b2b
route but without success.
route[b2b_test_logic] {
<------>loose_route();
if ($rm != "BYE") {
# for requests other than BYE, no special actions needs to be done,
# just pass the request to the peer
b2b_pass_request();
exit;
}
...
Thanks,
Xaled
_______________________________________________
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
