Comment #4 on issue 1389 by jean.deruelle: ServerTransaction does not
timeout
http://code.google.com/p/mobicents/issues/detail?id=1389
I don't read it the same way.
"For unreliable transports, requests are retransmitted at an interval which
starts at
T1 and doubles until it hits T2. If a provisional response is received,
retransmissions continue for unreliable transports, but at an interval of
T2.
[...]
The default value of T2 is 4s, and it represents the amount of time a
non-INVITE
server transaction will take to respond to a request, if it does not respond
immediately"
T2 in my read is used only for CTx, T2 is for Timer E which ensures
retransmission of
the request.
T2 represents the amout of time blah blah so to me, it is just an
indication saying
normally the STx should reply within that time not saying the Stx should
start a
Timer
If the application doesn't send a final response to the non INVITE request
received
(on the STx) then it is an application bug IMO just like not cleaning up
resources
that could lead to memory leak.
The question is why or in which case the application or RA doesn't send a
final
response here ?
