Hi,
are you sure that Openser is processing the ACK packet with t_relay() to
match it against existing transaction?
This is the same issue i had 2 days ago and solved putting a:
if (method=="CANCEL" || method=="ACK") {
route(1);
return;
}
in my main routing block. The route[1] is route block that process
request with t_relay().
Before i didn't put the ACK in the if clause but only the CANCEL.
Hope to helped,
Bye,
Marcello
Tobias Lindgren wrote:
Hello all,
I'm having problems with ACKs not beeing matched to an ongoing call,
thus OpenSER resends a 487 many times.
My question is, would OpenSER deny an ACK depending on how the headers
are sorted in the packet? Eg. if the VIA-header is found at the end of
the packet? How does it actually match the 487 and the ACK?
Packet from proxy that OpenSER doesn't seem to match:
User-Agent: hotsip-transactron
Max-Forwards: 70
Content-Length: 0
To: <sip:[EMAIL PROTECTED]>;tag=1499854882
From: "PBX" <sip:[EMAIL PROTECTED]>;tag=as2fa86da4
Call-ID: [EMAIL PROTECTED]
CSeq: 103 ACK
Via: SIP/2.0/UDP
192.168.0.1:5060;branch=z9hG4bK-81056ef2a1e003b87474dfaa6a5e7959;rport=5060
Br,
/Tobias
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
