HI Alan,
I suspect a scripting issue, making the received hop-by-hop ACK (for
negative replies) to be "handled" by the dialog module, which treats it
as a end-2-end ACK (for 200 OK reply).
I guess your script lacks this block
https://github.com/OpenSIPS/opensips/blob/master/etc/opensips.cfg#L112
when comes to sequential requests; this block needs to be before the
loose_route or any dialog/TH matching.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 21.03.2024 12:29, Alain Bieuzent wrote:
Hi bogdan,
Find attached the sip traces where we have this error log:
Mar 21 11:24:13 lbsip-rtpe-test opensips[3108]:
WARNING:dialog:dlg_onroute: tight matching failed for ACK with
callid='[email protected]:5060'/52,
ftag='as5625de52'/10, ttag='b5a7-94b8b0d1dd76318f3d174a911be4ece2'/37
and direction=1
Mar 21 11:24:13 lbsip-rtpe-test opensips[3108]:
WARNING:dialog:dlg_onroute: dialog identification elements are
callid='[email protected]:5060'/52,
caller tag='as5625de52'/10, callee tag='3920005391-2017127892'/21
*De : *Bogdan-Andrei Iancu <[email protected]>
*Date : *mercredi 20 mars 2024 à 16:45
*À : *Alain Bieuzent <[email protected]>, OpenSIPS users mailling
list <[email protected]>
*Objet : *Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight
matching failed
Not the logs, but the trace/ SIP capture - I need to see the sip
traffic to understand the context of the issue.
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 20.03.2024 17:14, Alain Bieuzent wrote:
Bellow the link to the traces :
https://www.transfernow.net/dl/20240320jzEA98Vz
*De : *Bogdan-Andrei Iancu <[email protected]>
<mailto:[email protected]>
*Date : *mercredi 20 mars 2024 à 14:29
*À : *OpenSIPS users mailling list <[email protected]>
<mailto:[email protected]>, Alain Bieuzent
<[email protected]> <mailto:[email protected]>
*Objet : *Re: [OpenSIPS-Users] OPENSIP 3.4 send_reply and tight
matching failed
Hi,
The script snippet has nothing to do with the matching - it is
about a 200-ok ACK to be matched by the dialog module and the
TO-tag does not match at all.
The link to the trace expired, if you could repost.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 12.03.2024 14:57, Alain Bieuzent wrote:
Hi all,
I am in the process of migrating my proxies from 3.3.9 to 3.4.4.
In 3.4 I find myself with a fault when I try to rewrite a
final cause.
if (t_check_status("500"))
{
send_reply(503,"Service Unavailable");
exit;
}
with 3.3 version, this code works perfectly, since 3.4 I have
this error:
WARNING:dialog:dlg_onroute: tight matching failed for ACK with
callid='[email protected]:5060'/52,
ftag='as5328cea7'/10, ttag='b5a7-2a346bb9d510da893a
ee7cda850584cb'/37 and direction=1
WARNING:dialog:dlg_onroute: dialog identification elements are
callid='[email protected]:5060'/52,
caller tag='as5328cea7'/10, callee tag='3919223738-770090972'/ 20
Has anyone encountered this error before?
Complete traces here :
https://www.transfernow.net/dl/20240312qvAFfIAL.
Regards
_______________________________________________
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
