Hi,
some updates and a cleaner scenario.
same issue appears in the following scenario
local remote
invite ->
<- 183 Session Progress
prack ->
<- ok
<- update
ok ->
<- 183 Session Progress (same callid, different to_tag, so new dialog)
<- 183 Session Progress
<- 183 Session Progress
... unitil we get a gateway timeout ...
basically remote is a b2bua which does a call transfer by issuing
an update to local and then sending a progress while remote_2 is ringing.
The different thing is that on second 183 the to_tag is different,
since is a different dialog.
Placing some debug into nta.c, agent_recv_response, after found outgoing
I notice that first 183 had orq->orq_destroyed == 0, next 183s have
orq->orq_destroyed == 1 , so get not handled after...
any hint?
regards,
matteo.
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
