Hello Jorge,
Just as RFC3261 says, 1XX responses create "early dialogs", while 2XX
final responses create "dialogs". OpenSIPS follows the same rules, only
that it considers that the "true" lifetime of a dialog begins when the
callee picks up his/her phone. That is why those fields are still unused
- they are initialized to zero, since the 200 OK is still to come.
If that dialog were to remain in the early state, the transaction would
expire eventually, triggering a delete of that early dialog.
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 05/21/2014 07:23 PM, Jorge Ortea wrote:
Hi all,
when I execute 'opensipsctl fifo dlg_list' shows this:
dialog:: hash=206:862937179
state:: 2
user_flags:: 0
timestart:: 0
timeout:: 0
callid:: 786344563@A.B.C.D
from_uri:: sip:xxxxxxxxx@MyDomain
to_uri:: sip:yyyyyyyyy@MyDomain
caller_tag:: 356538242
caller_contact:: sip:xxxxxxxx@A.B.C.D:5062
callee_cseq:: 2
caller_route_set::
caller_bind_addr:: udp:MyDomain
callee_tag:: as28f3b5f8
callee_contact::
caller_cseq:: 2
callee_route_set::
callee_bind_addr:: udp:MyDomain
This segment refered to a call from UAC to a mediagateway through
Proxy SIP (Opensips 1.6.4-2-tls)
Is it normal that both timestart and timeout are 0?
Thanks.
Regards.
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
