24 Mar
2010
24 Mar
'10
9:04 a.m.
2010/3/24 Timo Reimann <timo.reimann(a)1und1.de>de>:
Iñaki Baz Castillo wrote:
According to dialog specification a dialog ends when a BYE is received
(and its 200) or the initial INVITE rejected.
Anyway TM mantains the terminated transaction for a while (3-4
seconds) and the dialog associated also remains in memory (this is the
current behavior).
2010/3/23 Timo Reimann
<timo.reimann(a)1und1.de>de>:
What do you mean by "ireal"? Heya,
what's the "rejected" state good for? Why is it needed now when it
wasn't before?
In the current Dailog module design, when a dialog ends (BYE) or is
rejected (any [3456]XX response for the INVITE) it remains in memory
for 3-4 seconds (due to some TM timeout).
So consider "rejected" and "terminated" as "ireal" states
since when a
dialog gets such states it could be inmediately removed from the list. So is there no difference in the handling of the two
states, i.e., both
will be deleted at the same time? If so, why are two states maintained?
Yes, it's just "informative". Note that in order to compute the status
of the dialog_in entry is required to inspect all the status of the
dialog_out entries (including those in "terminated" or "rejected"
state). After it, they can be removed of course.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>