Hi!

We have one problem for which I really did not find a solution in the good 
documentation or the samples of the stack. 

Description:
We are using the nua interface to establish a call. While the call is in 
state "ready" we are sending INFO messages with nua_info to the other party. 
In some cases the other party did not respond to this message with 200 OK (or 
others). As a consequence the nta timeouts the transaction (after 32 seconds) 
and the nua terminates the INVITE session.

Questions:
Is there any tag or method to prevent the call termination? Maybe cancel the 
transaction before the timeout occurs. 
Is it possible to send the INFO message without transaction in the context of 
the existing nua call?

Trace:

nta: sent INFO (112842756) to tcp/195.176.152.24:5060
tport_pend(01713908): pending 017112D0 for tcp/195.176.152.24:5060 (already 0)
nta: timer set next to 17920 ms
nta: timer F fired, terminating ACK (112842755)
outgoing_reclaim_all(00000000, 00000000, 0100F950)
nta_outgoing_timer: 0/0 resent, 1/2 tout, 0/0 term, 1/2 free
nta: timer set next to 5232 ms
nta: timer F fired, timeout INFO (112842756)
tport(01713908): 017112D0 by 01712288 with 00000000
nta: outgoing_free(01712288)
tport(01713908): set timer at 1767403 ms because idle since send
nua(01710B70): removing session usage
nua(01710B70): call state changed: ready -> terminated

Thank you for your help!



------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel

Reply via email to