17 Mar
2009
17 Mar
'09
4:58 p.m.
Iñaki Baz Castillo wrote:
El Martes, 17 de Marzo de 2009, Alex Balashov
escribió:
Ahh. So, then why does the "reason" code for 487 say something like
"transaction terminated," if the transaction has not existed for a long
time?
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
Iñaki Baz Castillo wrote:
The transaction was terminated when a branch replied a 200 (as RFC 3261
states). Not so easy. I've never tryed the only way to
process a *stateless* reply
is in "onreply_route[0]".
Theorically "check_trans()" works also in ONREPLY_ROUTE, but even if it
detects the reply, how to drop it? do "drop()" or "exit()" eliminate
a
response?
I would think drop() would do it.
Why is the response stateless? When a 487 is relayed by a proxy it is
statefully associated with an INVITE transaction that is being closed in
response to a CANCEL, right? Or did I not carefully read this thread
and miss something?