I do not use the cseq_delay param.

What I do use is the exec_msg command in my script to spawn off an external script that uses sipsak to reply to client MWI SUBSCRIBEs (as there is an Asterisk voicemail server in the setup). I believe the issue to be with this script though as sipsak may wait for timeout if it cannot reach the client and OpenSER blocks during this time.

Thus the issue may not be caused by the Cseq after all. For now, I have turned debug logging and changed the script to spawn off the sipsak in background and return. So far, so good it seems.

On Wed, Apr 9, 2008 at 5:58 AM, Bogdan-Andrei Iancu <bogdan@voice-system.ro> wrote:
Hi Adrian,

That log means that there is a REGISTER attempt using the same callid and cseq as a previous one (during re-registration). Do you use cseq_delay param ?
  http://www.openser.org/docs/modules/1.3.x/usrloc.html#AEN326

can you identify the processes you think are blocked?

regards,
Bogdan

Adrian A wrote:
I am running OpenSER 1.3.1 on a Debian 4.0 system.
It seems that there's some sort of bug with OpenSER getting stuck and stops processing requests at least once a day. The logs only show the following line repeated every minute:

ERROR:registrar:update_contacts: invalid cseq for aor <1302>

At 1302 is a Cisco 7905 phone running the latest firmware. If I restart OpenSER then things get back to normal.

Does anyone know what the problem might be?

------------------------------------------------------------------------


_______________________________________________
Users mailing list
Users@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users