Re: [Sofia-sip-devel] reINVITE / reREGISTER

[Colin Whittaker]

Hi Pekka, I am not seeing refresh of registration. Here are the final lines from the stack: nta: received 200 OK for REGISTER (64166714) nta: 200 OK going to a transaction nta_outgoing: RTT is 30.843 ms tport_release(0x103d7110): 0x103e3d70 by 0x103e4358 with 0x103e48f0 nua: ua_event: entering nua(0x103d7e60): r_register 200 OK nua: nua_event: entering    ::tag_null: 0 nta: timer K fired, terminate REGISTER (64166712) outgoing_reclaim_all((nil), (nil), 0x7fffe8c0) nta_outgoing_timer: 0/0 resent, 0/0 tout, 1/3 term, 1/3 free nta: timer K fired, terminate REGISTER (64166713) nta: timer K fired, terminate REGISTER (64166714) outgoing_reclaim_all((nil), (nil), 0x7fffe8c0) nta_outgoing_timer: 0/0 resent, 0/0 tout, 2/2 term, 2/2 free The SIP trace is as follows: nua_register() REGISTER -> <- 401 Unauthorized nua_authenticate() REGISTER -> <- 423 Interval Too Brief REGISTER -> <- 200 OK Which timer is nua using to refresh REGISTER ? Pekka Pessi wrote: On 2/18/06, Colin Whittaker <[EMAIL PROTECTED]> wrote: Does the sofia NUA stack support automatic re-REGISTERING ? Or is it up to the App to time out and send the register before the Expires: timeout ? NUA should refresh registrations. I've been looking at the code, and there appears to be some testing of the Expires parameter in the Contact: header to set a timer, but it doesn't seem to ever send a new REGISTER. The code is not very straightforward to say least. ;-) What actually happens? Do you see any complaints in log if you increase NUA_DEBUG environment variable to 9 (nua tries to send re-regeister but fails)? Same question for INVITE. I see the SESSION_TIMER stuff, but I was wondering if the proxy does not support the timer extension, should the stack still send reINVITES after the Expires: timeout ? Or is it upto the App ? UAC should send CANCEL if no final answer has been sent to INVITE until Expires timeout (section13.2.1 in RFC 3261). We don't do that, I think. Is there a good description of the NTA timers and what they are suppose to do ? I see there are a bunch, with names like B,D,K,F. RFC 3261 section 17 and appendix A "Table of Timer Values": http://www.faqs.org/rfcs/rfc3261.html. There are also "N" timers for things not described in 3261, N1 is responsible for sending "100 trying" to INVITE if application does not send a response soon enough. N2 is reponsible for retransmitting preliminary responses on server side, preventing timer C from expiring. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel