[OpenSIPS-Users] call loop, dialog and topology_hiding.
Alexander Kogan
akogan at 5gfuture.com
Tue May 14 20:33:22 UTC 2024
Hello,
is it possible to return the call back to the same OpenSIPS instance
when using topology hiding with Call-ID header encoding?
It doesn't work for me. The call flow is:
1. caller -> OpenSIPS, call_id_1 = 39e20b8211b311ef9f35a0369f28db67 at X.X.X.X
2. OpenSIPS -> the same OpenSIPS, call_id_2 =
PNiupb663sWqpd38kW1sITWF4YSZ1cFgODEw1emUldnJfUgxHay0ycnEBUVpETGBnYnV.b1pc,
encoded call_id of the first leg
3. OpenSIPS -> callee, call_id_3 =
PNiupb663sWqpFAgoHBsIQ2V6IxM3MQ1YUh4EeCMNEhYvXzMmCXgzAiEOLS4dRDYkBSgiLyMNPxIrATE9djgKBS83Bh8gARIGKwUzGwVnMnU2Ig--,
encoded call_id of the second leg
This scheme doesn't work for a subsequent requests from the first
OpenSIPS to itself including ACK to the INVITE transaction. It doesn't
work because OpenSIPS decodes call_id_2 when it receives the request and
decoded call_id doesn't match with the call_id of appropriate dialog
found by DID:
DBG:dialog:api_match_dialog: We found DID param in R-URI with value of
f72.357c45e4
DBG:dialog:dlg_onroute: route param is 'f72.357c45e4' (len=12)
DBG:dialog:lookup_dlg: dialog id=1314178899 found on entry 639
DBG:core:parse_headers: flags=58
WARNING:dialog:dlg_onroute: tight matching failed for ACK with
callid='39e20b8211b311ef9f35a0369f28db67 at X.X.X.X'/45,
ftag='vQ5R9OFRXdslE8jhUV3bJRPFV8VLpAAq'/32,
ttag='271887064-24388-26114'/21 and direction=0
WARNING:dialog:dlg_onroute: dialog identification elements are
callid='PNiupb663sWqpd38kW1sITWF4YSZ1cFgODEw1emUldnJfUgxHay0ycnEBUVpETGBnYnV.b1pc'/73,
caller tag='vQ5R9OFRXdslE8jhUV3bJRPFV8VLpAAq'/32, callee
tag='271887064-24388-26114'/21
DBG:core:parse_headers: flags=200
DBG:core:grep_sock_info_ext: checking if host==us: 9==9 && [127.0.0.1]
== [127.0.0.1]
DBG:core:grep_sock_info_ext: checking if port 5060 matches port 5060
Could you please explain, is it somehow possible to use call_id hiding
with call loops?
--
Best regards,
Alexander Kogan,
Director of R&D
5g Future
http://5gfuture.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240515/26a32b0c/attachment.html>
More information about the Users
mailing list