Hi, I have found another bug in the sip_regc layer. If you send an unregister command, the tsx_callback set the regc->expires to 0. Then when you send a register command, the tsx_callback start the refresh timer to 5 secs instead of the value of the Expires received in the 200 OK (this is due to the regc->expires being 0). The problem occurs only once. Best regards Philippe Leuba _____ From: Philippe Leuba [mailto:philippe.leuba@xxxxxxxxxxxxx] Sent: lundi 28 f?vrier 2011 16:06 To: 'pjsip at lists.pjsip.org' Subject: RE: Bug in sip_regc Hi, I have found what I think is a bug in the sip_regc layer. When you encounter an error (different from 401/407/423), the current_op variable is not reset to REGC_IDLE, preventing to others REGISTER requests (sip_regc_send checks for current_op being REGC_IDLE). This occurs for example when your AOR is already registered for the maximum number of times allowed, you receive a 403 error, but you can not send an unregister_all command. Philippe Leuba -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20110301/a04ebc62/attachment.html>
