AFAIK, registrar module does not do this. I believe you can test for Expires and expires parameters in Contact of REGISTER (SER 2.0 and eval module because you must evaluate a value below a certain number), add a Min-Expires and statelessly reply with a 423, but I have never tried. It is probably far easier to add the capability to registar module controlled by a modparam value. We gladly accept patches, but send a request to serdev first to hear if somebody has done it. g-)

Kostas Marneris wrote:

Hello all,

I have an issue with some SIP clients (like Linksys SPA 1001) that have not comply with the "expires" parameter of the Contact header of a "200 OK" Registrar Response.

My SER conf : modparam("registrar", "default_expires", 1800) modparam("registrar", "min_expires", 300) modparam("registrar", "max_expires", 1800)

Although the (200 OK) response contains the 'expires' parameter : Contact: sip:userb2@192.168.2.10:5061;expires=300;received="sip:1.2.3.4:5061" the SIP client ignores it and keeps sending REGISTERs every 5 sec (if configured so).

Is there a way for SER to reject these registrations with (423 Interval Too Brief), according to RFC3261 - 21.4.17 (423 Interval Too Brief) & 10.3 (Processing REGISTER Requests).

The 'retry_after()' registrar modparam is not my case.

thank you, Kostas

---

Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers